I'm using an MCU w/w T2 - what I want to be able to do is set up an arrangement - let's say put 4 different vstis on four different tracks. Then I want to record on them one at a time by arming the first track then recording, arming the second track then recording etc. Since I am using the same MIDI keyboard for all four tracks I have to go to the mouse and reassign the imput between each pass.
More important I wold love to be able to use the MCU, which I have on a rolling stand, to record multiple passes of myself say seated at a drumset - so again I would just assign the input for many tracks to the same mic and then I could record several tracks just arming and muting without having to return to the computer.
I love the original drag the input mode when I'm using the computer , but the other mode, with record ready switches, only makes sense when one input can be sent to many tracks.
FR - one input for many tracks
-
- KVRAF
- 1615 posts since 28 Mar, 2005
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
I use the per-track mode. Seems to make sense even though I can't send one input to many tracks. 
If you're already at your computer, dragging the pointer to the next track down or right-clicking and selecting a new input on the next track seems like it takes such a similar amount of time that it's negligible.
For audio, you'd still be screwed.
For MIDI, however, surely between MIDI Yoke and MIDI Ox, you could set up 4 inputs? Just rout the real MCU signal into 4 "virtual" MIDI Yoke patch cables and assign them to different tracks.
Just a thought, and not owning an MCU (not knowing exactly what one is, to be honest, I didn't Google and I'm just assuming it's a MIDI control surface) I haven't tested it, but it seems to me that it could be made to work!
Greg
If you're already at your computer, dragging the pointer to the next track down or right-clicking and selecting a new input on the next track seems like it takes such a similar amount of time that it's negligible.
For audio, you'd still be screwed.
For MIDI, however, surely between MIDI Yoke and MIDI Ox, you could set up 4 inputs? Just rout the real MCU signal into 4 "virtual" MIDI Yoke patch cables and assign them to different tracks.
Just a thought, and not owning an MCU (not knowing exactly what one is, to be honest, I didn't Google and I'm just assuming it's a MIDI control surface) I haven't tested it, but it seems to me that it could be made to work!
Greg
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
It would definitely be easier to do it natively than to use MIDI Yoke. I'm all for the FR, sorry if it didn't seem like I was. 
I was merely making a suggestion to getcha going in the meantime.
Greg
I was merely making a suggestion to getcha going in the meantime. Greg
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Not sure if this helps:
Make a rack with nothing in it but the MIDI going through end to end.
Drop it into the track to which your MCU is attached. Now put your VSTi after the racks in the tracks, EXCEPT for the one where your MIDI device is actually active (due to the nature of e-to-e, you'll be able to hear devices on this track, so just leave it empty).
Then, you can mute/unmute the other tracks as you see fit. Now, the problem with this is that your MIDI data will all pile up on top of each other in the "controller" track, but when you go back to your desk, you can shift+drag them into their own tracks. It also doesn't help if you need to play back all those MIDI tracks before going back to your desk.
In this example, you can see the level meter on track 1, but that's just indicating MIDI data, and it's not making sound. The only track making sound is the one with 4front Piano on it. (track 2)
Greg
Make a rack with nothing in it but the MIDI going through end to end.
Drop it into the track to which your MCU is attached. Now put your VSTi after the racks in the tracks, EXCEPT for the one where your MIDI device is actually active (due to the nature of e-to-e, you'll be able to hear devices on this track, so just leave it empty).
Then, you can mute/unmute the other tracks as you see fit. Now, the problem with this is that your MIDI data will all pile up on top of each other in the "controller" track, but when you go back to your desk, you can shift+drag them into their own tracks. It also doesn't help if you need to play back all those MIDI tracks before going back to your desk.
In this example, you can see the level meter on track 1, but that's just indicating MIDI data, and it's not making sound. The only track making sound is the one with 4front Piano on it. (track 2)
Greg
-
- KVRer
- 2 posts since 5 May, 2004
Let's say I want to hook up to my MIDI input a keyboard controller with a key-split configuration that is sending everything below C3 out on MIDI channel 1 and everything above C3 on MIDI channel 2. I want channel 1 to play a bass patch on a VSTi on Tracktion channel 1 and midi channel 2 to route to a VSTi playing a lead patch on Tracktion channel 2.
Do I have to do everything described in this thread just to accomplish this or are these instructions for something more sophisticated? It seems that Tracktion's MIDI implementation ignores (or maybe "overrides" is more accurate) MIDI channel data. I'm just having trouble believing that Tracktion would handle something so basic to the MIDI spec as channels so poorly - I'm not trying to be rhetorical, I know it sounds that way - I *must* be missing something.
Do I have to do everything described in this thread just to accomplish this or are these instructions for something more sophisticated? It seems that Tracktion's MIDI implementation ignores (or maybe "overrides" is more accurate) MIDI channel data. I'm just having trouble believing that Tracktion would handle something so basic to the MIDI spec as channels so poorly - I'm not trying to be rhetorical, I know it sounds that way - I *must* be missing something.
-
- KVRAF
- 3364 posts since 16 Feb, 2004 from atop a katamari
nope, you're right. Tracktion doesn't store the channel number with the notes, instead having a single channel value for each clip.
Kick, punch, it's all in the mind.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
BUT,
If your INSTRUMENT is set up to only respond to the channel you want it to, the rack system I showed is golden and takes only a second to set up. Just have the clip send "all" channels and let your instruments sort them out.
Or if your instruments don't allow you to do this, use Niall Moody's MIDI Channelizer to force into a specific channel.
Again, the drawback would be that all of your recorded notes are in 1 clip instead of several; but it'd still work.
Another option is using MIDI Ox/MIDI Yoke to assign your key splits. And I'm sure there are bazillions of other ways of doing it. What you want is achievable, and in some cases very easily; however, NONE quite as easily as simply having one input for many tracks, as per your feature request.
Greg
If your INSTRUMENT is set up to only respond to the channel you want it to, the rack system I showed is golden and takes only a second to set up. Just have the clip send "all" channels and let your instruments sort them out.
Or if your instruments don't allow you to do this, use Niall Moody's MIDI Channelizer to force into a specific channel.
Again, the drawback would be that all of your recorded notes are in 1 clip instead of several; but it'd still work.
Another option is using MIDI Ox/MIDI Yoke to assign your key splits. And I'm sure there are bazillions of other ways of doing it. What you want is achievable, and in some cases very easily; however, NONE quite as easily as simply having one input for many tracks, as per your feature request.
Greg