Tracktion needs a simpler way to use the MIDI output of one track as the MIDI input of other tracks
-
- KVRAF
- 2461 posts since 9 Oct, 2008 from UK
Ah, got it. Thanks. I had tried to work out how to add more input and output tracks, but missed the + signs (as well as some of the thinking behind it all).
Thank you.
Thank you.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.
-
- KVRist
- 212 posts since 4 Nov, 2004 from France
==> Thanks a lot to you "AegisPrime" !!
You saved my neurons and all my hair !!...
Lutin mutin.
You saved my neurons and all my hair !!...
Lutin mutin.
-
- KVRist
- 473 posts since 1 Feb, 2006
also thanks from the sideline ...
to be (and stay) aware of the "splitter" function of racks is really helpful (be it midi or audio).
to be (and stay) aware of the "splitter" function of racks is really helpful (be it midi or audio).
- KVRAF
- Topic Starter
- 1728 posts since 21 Sep, 2007 from USA
Thank you to everyone for your ideas and suggestions. Thank you to AegisPrime for patiently demonstrating the MIDI Thru rack component technique. This technique works quite well, but again, I think the Master/Slave MIDI routing technique should be easier to accomplish in Tracktion without manually re-creating unique instances of a rack for the master MIDI tracks and then making copies of one of the unique instances for the slave MIDI tracks.
The feature that already exists in Tracktion which allows one MIDI track to be the input source for one other track is still the simplest and most intuitive approach. It really should be enhanced to allow a MIDI track to be the input source for any number of other tracks, like so (I added colored stars to denote the different sets of slave MIDI tracks):

To the Tracktion development team, would you be willing to implement this enhancement for your MIDI-centric customers?
The feature that already exists in Tracktion which allows one MIDI track to be the input source for one other track is still the simplest and most intuitive approach. It really should be enhanced to allow a MIDI track to be the input source for any number of other tracks, like so (I added colored stars to denote the different sets of slave MIDI tracks):

[Core i7 8700 | 32GB DDR4 | Win11 x64 | Studio One 7 Pro | WASAPI ]
- KVRian
- 599 posts since 8 Apr, 2014 from USA
Save the rack as a preset, then all you need do is drag it to a track.tonedef71 wrote:Thank you to everyone for your ideas and suggestions. Thank you to AegisPrime for patiently demonstrating the MIDI Thru rack component technique. This technique works quite well, but again, I think the Master/Slave MIDI routing technique should be easier to accomplish in Tracktion without manually re-creating unique instances of a rack for the master MIDI tracks and then making copies of one of the unique instances for the slave MIDI tracks.
<SNIP>
- KVRAF
- Topic Starter
- 1728 posts since 21 Sep, 2007 from USA
Yes, Aegis Prime's technique already covers dragging unique instances of a rack preset for master tracks and dragging copies of a unique instance for slave tracks. I think configuring a MIDI thru route involves more work than should be needed. It is easier accomplished and more elegant as I mocked it up by simply sharing a master MIDI track as a MIDI source for MIDI slave tracks; less "moving parts". Tracktion simply needs to permit sharing a MIDI source track with more than just one other MIDI destination track. The name of the DAW is "Tracktion" after all; more flexible track sourcing would handle this use case elegantly.gesslr wrote:Save the rack as a preset, then all you need do is drag it to a track.
[Core i7 8700 | 32GB DDR4 | Win11 x64 | Studio One 7 Pro | WASAPI ]
