Solution for new w next midi channel?

[jtnyc]

I found this on Gearsluts posted by Stephen Trask. It's a way to create "new with next midi channel" in the main (arrange) window.

It's a bit of a go around, but if you were to set it up once in a template session and then import it, it might be useful.

Check it out -

 

((((((( - Create a software instrument, choose "Multimbral" and choose the maximum ammount wich is 16 tracks. This will create a Sum Stack.

- Load your VI , in Stereo version in the first track.

- Shift-Select and delete all the tracks that you don't need. All 15 tracks if you want, and just keep one.

- If you need additional tracks later, just select track one, and choose in the Menu : Track>Other>New Track with next channel.

- Guess what ? It will create... a next track ( using the SAME instrument, NOT next instrument ) with the next midi channel.

- If you need more just repeat, and it will keep creating next tracks until you reach the maximum ( 16 midi tracks ). All using the same Instrument, in Stereo version, with no additional mixer channels.

- You can take some of those tracks out of the stack , drop them in another stack if you want , etc... )))))))

 

It will only let you create as many "new with next channel" tracks as you create in the original multi so choose 16.

The new "new with next channel" tracks that you create will not be part of the stack, but you can drag them in if you want. It's a workaround to say the least, but it's something.

 

Another strange and Illogical way to get something done in Logic.

Gotta love it.

 

Thanks Stephen -

[route-electrique]

((((((( - Create a software instrument, choose "Multimbral" and choose the maximum ammount wich is 16 tracks. This will create a Sum Stack.

- Load your VI , in Stereo version in the first track.

- Shift-Select and delete all the tracks that you don't need. All 15 tracks if you want, and just keep one.

- If you need additional tracks later, just select track one, and choose in the Menu : Track>Other>New Track with next channel.

- Guess what ? It will create... a next track ( using the SAME instrument, NOT next instrument ) with the next midi channel.

- If you need more just repeat, and it will keep creating next tracks until you reach the maximum ( 16 midi tracks ). All using the same Instrument, in Stereo version, with no additional mixer channels.

- You can take some of those tracks out of the stack , drop them in another stack if you want , etc... )))))))

 

It will only let you create as many "new with next channel" tracks as you create in the original multi so choose 16.

The new "new with next channel" tracks that you create will not be part of the stack, but you can drag them in if you want. It's a workaround to say the least, but it's something.

 

Thanks!. Brilliant!.

[vanhaze]

Great tip, many thanx !

[KC]

I saw this posted yesterday from Jay Asher:

 

...Totally screwed up New With Next MIDI Channel. Unless you initially create a multi-timbral software instrument with the right amount of MIDI channels, it does not do what it is supposed to. They have already promised me a fix for this.

 

I haven't ever used this command, so maybe I am missing something huge in my workflow. But why not just make the instrument with 16 channels to start with and not use them all if you don't have too? Is it a CPU usage thing? I can see that it would clutter up things a bit, but now that you can nest folders, doesn't that help?

 

I have always just made enough channels for what I need. i.e. in Lass, I create a multi with 3 channels, Vlns I a,b,c... Or in Stylus, I make it with 8 and not necessarily use all 8 - the others just sit there waiting. Maybe this uses CPU cycles by just having them there?

 

I'm not trying to be confrontational or say that this isn't a big missing feature. I'm just trying to understand why it seems to be such a big deal and should I be more upset about it

 

Thanks

cheers -

kc

[jtnyc]

I saw this posted yesterday from Jay Asher:

 

...Totally screwed up New With Next MIDI Channel. Unless you initially create a multi-timbral software instrument with the right amount of MIDI channels, it does not do what it is supposed to. They have already promised me a fix for this.

 

I haven't ever used this command, so maybe I am missing something huge in my workflow. But why not just make the instrument with 16 channels to start with and not use them all if you don't have too? Is it a CPU usage thing? I can see that it would clutter up things a bit, but now that you can nest folders, doesn't that help?

 

I have always just made enough channels for what I need. i.e. in Lass, I create a multi with 3 channels, Vlns I a,b,c... Or in Stylus, I make it with 8 and not necessarily use all 8 - the others just sit there waiting. Maybe this uses CPU cycles by just having them there?

 

I'm not trying to be confrontational or say that this isn't a big missing feature. I'm just trying to understand why it seems to be such a big deal and should I be more upset about it

 

Thanks

cheers -

kc

 

Hi KC -

 

The way you do it does not use up more cpu resources, and if your comfortable just creating the channels in advance, your all good. For me, the clutter can be annoying. If I only record 2 or 3 tracks in Kontakt, I don't want several empty tracks taking up space on my screen. I can of coarse close the stack which is a really cool new feature, but a lot of the time I want to see those 2 or 3 tracks without wasting 7 inches of screen real estate. It's also a workflow habit thing. It was so simple. Just create a stereo Kontakt track and add tracks as needed.

 

I'm not sure of the best way to handle multi timbral VI's in LPX for me yet. I will experiment. I do hope they restore "new with next midi channel". It just works.

[KC]

Thanks JT -

 

Yeah, I can see your point about the screen real-estate issues.

 

But, it looks like the fixed it in the update today - so I guess this is a moot point.

 

cheers -

kc

[Eric Cardenas]

The best solution is to update to 10.0.1!