Confussed with MIDI in Cantabile: assignments, routing...

[krraqk]

Im loving more and more Cantabile and starting to be comfortable with it and considering very much to purchase it with the hope to use it in live in a near future.

But Im confused with the midi routing in Cantabile.


What I want is to be able to send midi messages to some external devices while play and control the different vstis and plugins in the Cantabile rack. I use a midi guitar controller (axon ax50 via usb) and an FCB1010 (pedalboard midi control midi connected to an usb midi interface).

I can play the vsti in the racks with the Axon and the FCB but I want to send ALSO some midi commands to my Axon or effects unit (VG99).

To do that I make a midi routing entry and assign the midi input port from the FCB1010 to the output ports of the Axon and vg99 (two midi routing entries in fact) the problem is that when I do that midi routing entries the racks dont receive anymore the midi commands from the FCB1010! so I loss the control over the rack vstis.

Now im very confused about the midi routing in Cantabile, how I can control the racks and the external gear routing the midi signal with cantabile??

[TiUser]

The midi routing table is really somewhat confusing... Have you tried to set all "pass through" switches? If not the routed events are stolen and don't reach the next routing table line...

If you don't need all commands in a routing you can still use midi filters in the routing settings.

You can also use triggers to automatically send midi values or to start other actions... up to starting external programs.

[krraqk]

Thanks TiUser your contributions are always very helpful.

So do you think that the problem I described is a bug or the normal behaviour? I mean, why if I make an aditional route with the midi routing the already existent route to the rack stops working? I dont think its the best solution or at least I would like to understand it, the logic of it to be able to use it at the full lenght.

About your proposal:

1. with set all "pass through" switches, you mean the pass through in every plugin in every rack? I have activated the pass through in all the plugins which have a subsequent plugin in the rack where I want the midi to arrive. Or you mean the last plugin in a rack? if I set it in the latest what I can get? the midi goes out of the Cantabile? in in each of the ports?

2. Yes I filter some midi commands that I dont want to be sent to some plugins, but the problem that I have is not being able to send commands to racks and external devices simultaneously, sorry but I dont get how filtering something will solve that...

3. Triggers... well I dont know yet what triggers can do , but i supposed that my problem was very simple and dont needed esoteric functions to do it or Im wrong?

[TiUser]

Try midi pass through in the midi routing table.

Try a dedicated additional midi routing in the table to your vst racks if this does not help.

Normal behavior? Well, concerning to Brads current midi routing definition yes...

[krraqk]

Midi bypass? bypassing what? sorry I dont understand.

Making an additional midi routing, hmm... maybe it will solve it, but sounds a lot of redundant, because there is a routing already in the rack

I dont think that the fact that making a midi routing voids an already existing one is a "normal behaviour", to me it sounds more like a bug.

Now that i was so hopeful about Cantabile im finding some big difficulties, how I hate when this happens..


Thanks anyway

[TiUser]

...sorry, it's called "midi pass through"... I mean the round midi plug icon with the green arrow down when activated... I've corrected the typo in my prior post.

If you pass through all midi routings in the midi routing table I think your racks routings should work - I am just not perfectly sure...