When I select insert new rack, C3 opens a folder location?? I have not actually created any racks yet, and I would have thought “load” rack would exhibit that behaviour, not insert “new”…or am I missing something?
“New Rack” means you’re planning to create a rack. Once you are sent to the default rack folder location, create a name for the rack, click OK and then you can start adding plugins.
thanks, seems a bit odd, but well…okay. I created a rack and got the routings all set complete with the standard audio out, but I get no output from the plug in the rack (followed the same procedure as if creating a song)…is there some other output that needs to be set?
It’s okay - I need to dbl click the rack and THEN insert the plug!
Not so odd if you consider that a rack is a file like a song. Cantabile needs to know what file it needs to save the rack to. Essentially, a song references a rack by its file name, so this needs to be defined when you create the rack.
Just to add a bit more complexity: there are two different ways to get output from a rack (provided you have something in there that actually makes noise):
- route it to a global output within the rack → sound gets send to an output directly
- route it to the rack audio output port (racks can have input and output ports, both for MIDI and audio) and then create routes at song level to do something with the rack output. Pretty convenient if you want to further process the rack output (compress, add FX etc).
C3 has become a pretty complex beast - tons of possibilities if you want to do really sophisticated things. Maybe this has made it a bit unwieldy for “basic” usage - there is a lot that can go wrong when setting up things.
To some extent, there will always be a learning curve with powerful instruments like C3, but maybe @brad can tune the “default” settings a bit to make things a bit more intuitive for straightforward use (principle of least surprise). For me one of the classic counter-intuitive settings is that racks by default have their “activation” state behavior turned off. Result: a lot of users asking themselves why their racks stay on (or off) across state changes.
Definitely some of the defaults could use some looking over…
Cheers,
Torsten
That is how I have come to relate with C3 - as a powerful instrument!
Terry