Assigning a MIDI Controller to the Ctrl Key?

[davinwv]

Is this possible? I'd like to assign a button on my MIDI controller to the Ctrl key so that I could use it along with other buttons to Solo multiple Racks as described in the manual without using my laptop's keyboard.

I am currently testing Cantabile Lite, so I apologize if this is obvious once one purchases Cantabile Solo. The manual is unclear as to whether or not this type of assignment can be made.

[TiUser]

Such assignments are not possible in any version of Cantabile - emulating PC keyboard keystrokes via midi controllers.

If you are using Lite there are no midi controller assignments at all - no context menu and no button on the ribbon to access that. Get the 30 days trial of Solo or Performer to check that.


For further details check out the feature comparison here:
http://www.cantabilesoftware.com/features/

[davinwv]

Thanks for the info.

I have a session set up with one software instrument per rack (I read somewhere that this yields better multi-core processing than placing many instruments in a single rack).

If I mute/bypass all racks other than the ones I am playing at the time, does this manage the processing the same as soloing the racks I am playing?

Also, when a rack only holds a single virtual instrument, what is the difference between muting and bypassing that rack? I know that audio and MIDI pass through a bypassed rack, but not a muted rack.

Thanks in advance for your help as I continue to wrap my mind around this new live host (I am a recent Forte defector!).

[TiUser]

1) Basically Mute means to cut off the output - Bypass means passing by the input. If you just have a synth in the rack there might be no obvious difference. Things change if you process incoming audio in the rack too. Solo is related to mute. A bypassed rack will not sound even when soloed.

2) Yes, Cantabile can process vsts in parallel only when you place them in separate racks. However the benefit is not linear - 4 cores are not 4 times as powerful - there is significant overhead. Things become even more difficult when the plugins have different cpu needs. Finally you should check out the plugins you use to see how much you can gain here.

3) The only way to reduce cpu for unused plugins is to suspend them.