Tracktion needs a simpler way to use the MIDI output of one track as the MIDI input of other tracks

[tonedef71]

Back in the early days of MIDI sequencing software, a typical feature they had was the ability to designate any sequencer track's MIDI input to be the MIDI output from another sequencer track. So far, the only way I have been able to accomplish MIDI routing like this is via a virtual MIDI loopback driver (e.g. loopMIDI) assigned to multiple pre-defined Tracktion virtual MIDI inputs. First, I set the output of the track that contained the MIDI event data to be the virtual MIDI loopback port. Then for each of the tracks to be driven by another track's MIDI input, I assign one of the Tracktion virtual MIDI inputs as the input source. Each Tracktion virtual MIDI input is assigned the virtual MIDI loopback port as a MIDI input.



While the setup I describe here does indeed work, I cannot help feeling that this MIDI routing technique should be simpler to accomplish in Tracktion without involving a third-party MIDI loopback driver and multiple identically-defined virtual MIDI inputs.

I know there are alternative ways to achieve multiple synths playing the same source material, but I feel that this master-slave MIDI track routing technique is a straight-forward and economical way to accomplish the goal.

[Peter Widdicombe]

You're right - you are missing something...

The MIDI track you have is say, on track 2. On track 3, put the alternate .vst; and the INPUT to track 3 is MIDI track 2. That's it.

Now, there IS a limitation here - remember the input to track 3 will be the output of track 2. So, if you already have a .vst on track 2 playing audio, then the output of track 2 is audio, which will NOT play a MIDI .vst on track 3 (not without some finangling - I'm sure some rack setup would do that for you.

What's interesting about this, is that if you ENABLE the vst on track 2, track 2 plays. DISABLE the .vst, and the .vst for track 3 plays - allowing you a quick way to "comp" 2 different .vst's.

Learned something new. You CAN take the VST on track 2, point and right click on it and "wrap" it in a rack. Then take the midi output from the vst and delete it within the rack, and take the midi INPUT from the left side of the rack and drag it to the midi OUTPUT of the rack. THEN the track 2 will output both the audio from the vst, and pass the MIDI through so that it can be used as input to track 3; playing both at once. If you like the combo, you could then put both vst's in the same rack so they always play together, and do it on a single track... Possibilities are endless.

Not sure how you would send one track to MULTIPLE tracks, though... it seems track outputs can only go one place. Use the track as input to another, and the previous one goes away. Again, there's probably a way, but other than a rack *I* haven't figured that one out.

My guess is - you could probably also do it with ReWire, but I've never tried that.

[AegisPrime]

Why not just use a Rack?

[DaveL60]

I suspect the reason not to use a rack is wrapped up in "I cannot help feeling that this MIDI routing technique should be simpler to accomplish in Tracktion". Another reason I could see is that having VSTis on separate tracks makes it easier to do automation for each without getting confused.

That said, how about having the MIDI on Track 2, and the VSTis on Tracks 3, 4, ..., and then selecting the input for the tracks with VSTis to be the track with the MIDI? Basically take Peter W's solution w/o the problem of feeding audio instead of MIDI to the "second" VSTi.

[Peter Widdicombe]

I'm not sure you can do that - I tried briefly. basically, the first time you assign it (say track 3), it works perfectly. Then when you assign track 4's input to be track 2, input to 3 gets lost. A track seems to only have one "output" destination.

A MIDI channel strip or MIDI aux send/receive might fit the bill, but they don't seem to exist ?

[jabe]

I was a bit confused by this; assigning a track's output (Or Destination) is done in the Properties Panel, but Peter has mentioned assigning an input and I couldn't find a way to do that other than the Track Destination setting.

[jabe]

Another option is to duplicate the MIDI. It's not like it takes up a vast amount of storage space.

[AegisPrime]

I suspect the reason not to use a rack is wrapped up in "I cannot help feeling that this MIDI routing technique should be simpler to accomplish in Tracktion". Another reason I could see is that having VSTis on separate tracks makes it easier to do automation for each without getting confused.

This isn't simple?

[frankvg]

Even more simple: take an empty rack, connect the midi in- and output. Use an instance as a midi through before every synth.

[jabe]

Even more simple: take an empty rack, connect the midi in- and output. Use an instance as a midi through before every synth.

I'm not getting this to work. I did this on track 1, with a VSTi after it, and set the Track Destination to another track with a VSTi on it, but I'm only getting one VSTi playing.

No, wait, I got it to work by setting the MIDI input for the track...

Nope, something too weird was happening. The sounds wouldn't stop even after pressing stop. I'll look into that another time.

[DaveL60]

I'm not sure you can do that - I tried briefly. basically, the first time you assign it (say track 3), it works perfectly. Then when you assign track 4's input to be track 2, input to 3 gets lost. A track seems to only have one "output" destination.

Guess I should have tested first. But I'm upstairs and the studio isn't, so ...

Or, for that matter, carefully reading Peter's post all the way to the end.

[frankvg]

and set the Track Destination to another track with a VSTi on it,

Why ever would you want to do that? And also don't set any midi input for a track. Only an instance of a 'midi through rack' before the vsts.

[jabe]

and set the Track Destination to another track with a VSTi on it,

Why ever would you want to do that? And also don't set any midi input for a track. Only an instance of a 'midi through rack' before the vsts.

I was trying to follow what Peter had done, but not managing.

[jabe]

and set the Track Destination to another track with a VSTi on it,

Why ever would you want to do that? And also don't set any midi input for a track. Only an instance of a 'midi through rack' before the vsts.

I don't see where the MIDI through goes.

[AegisPrime]

I don't see where the MIDI through goes.

Like this:



1. Create a rack and just link the MIDI in/out.
2. Add a synth (or whatever) after it.
3. Drag copies of the rack to whichever tracks you want to use that MIDI on and add more instruments after them (their audio inputs/outputs will automatically get added to the rack but you can ignore those).