This is interesting. As a new Cantabile user, I came up 'against' MIDI passthrough as I was learning the system and came up with the following solution which works for me - I was wondering if anyone else had come to the same conclusion:-dluther wrote:
Once a strategic decision is made poorly (like midi pass through in the midi routing table) it can't be easily taken back because the data occurs in sessions then and has to be supported. On a change you have to support both to be compatible with legacy data... not a very great situation.
I found that it wasn't easy to see at a glance whether MIDI passthrough was enabled for a particular routing and what the 'flow' of MIDI data through the racks was. I was also getting situations where I couldn't tell via what path a sound was occurring - whether it was happening as a result of a MIDI routing or simply due to 'spare' MIDI data coming out at the end of the list (dunno if any of that just made sense...). I also found that not being able to choose between passthrough or no passthrough for any particular sub-session was causing me to have to create more routings than was necessary. And in any case, having the option at all seemed overly complex. I felt that it would be better to ALWAYS have passthrough on, but then have a way of blocking the end of the list up so that only the active routings in a sub-session play sounds.
Therefore, I realised the following. If I always set MIDI passthrough to ON for every MIDI routing and then just create a routing called -=END=- (or whatever) with NO passthrough at the end of the list which took all incoming MIDI data and sent it nowhere (ie. destination NONE), then everything works brilliantly. I can create routings with splits, filters, transpositions and everything and if a routing is turned on in a sub-session then it always works independently and is never affected by another routing. Also, if there are areas of the keyboard range where no routings are assigned then those notes are silent and don't play on every other channel not involved with the routings. Just make sure -=END=- stays at the end of the list to stop un-routed MIDI data from reaching the racks. This behaviour seems much more like that of a workstation type keyboard to me and suits my style of programming.
Dunno if that is of any relevance to anyone or maybe it seems so basic that it's obvious to everyone, but it pleased me to find a solution and with the comment above (from another thread), I thought I'd share.
