Sessions and Master Levels

[Pepi70]

Hi,
I wonder if is there a way to leave Master Levels controls indipendent by the session.
Every time a session is loaded, Master Levels parameters are reset as they are stored in the session file.
For me it would be nice to leave a Master Volume (eg.) the same for all session once I've set up it from a MIDI control.

Thanks in advance for your help.

Regards.

Giuseppe

[TiUser]

Agreed.

I see no way to work around this, I just ask my self how to specify that feature - as it applies to all controller assignments.

It's something like a controller value latch/snap from the last session before closing to the next when opening - right?

Next question is should that be a global behavior or individual to each control?

Reminds me on the controller midi feedback feature requested by some rare guys like me for long too - without much chance to see this soon or at all...

[Pepi70]

I'm a Cantabile very beginner, but in my mind I thought that a global setup were a "truely" a global setup. Were not Sessions level setup whose have the job to save setup for sessions?

I though that global setup were saved in a kind of cantabile.setup file (or Global.session file) that works together with the other session files.
Now I know that this is not how Cantabile works.

I don't know if a latch/snap behavior is the solution. Probably it is more complex than having a "global-global setup".

I wonder,
. what's the difference between session and global setup (I know, I'll read with more attention the manual)?
. in a real gig, how is your way of doing about this problem?

Regards!

Giuseppe

[TiUser]

Global means the controller number assignment is global.

If you choose session you can use a different controller number (fader) in each session for the assignment. That may be practically a bit overdone with the global level - just it works the same with every control of Cantabile's gui.

As said, concerning the value handling there's more than this that should be reconsidered / extended. Did you note the value jumps when values change but your faders can't move to reflect that? No catchup option either...

Only workaround for now is not using that at all... unfortunately. Not sure if a midi filter can help here...

If you are a picky observer you may note also that the popup help of the master volume tells it is a "gain" control. Gain controls are meant to adjust a level to a technical standard but not serving as a performance control. This is why I guess it works like it works.

Practically that's a bit absurd, I know.

I can't help it but recommend you to send a mail to topten software to discuss this issue.

[humphrey]

Hi,

sorry to say but I'm happy with the functionality as it is. I think I understand the idea behind but for me it's really useful to have the control over the whole session volume with only one fader storable as I use to balance the volumes of all sets to each other. To do this without the possibility to afterwards store this to the session would mean I'd have to trim each rack separately which can be lot's of work when you have stacked plugs & have 2 or 3 MIDI keyboards.

Nevertheless I also have the need to control the volume of my whole setup at once when I'm on stage. For this purpose I got me a TC Level Pilot which sits on one of my keyboards and controls the volume sent from my soundcard to the main mixer. The additional advantage of this scenario is I'd be able to turn down the volume in a second if there should be a blue screen or something like that if it should occour for some reason.

Only my 2 cents,

regards, humphrey

[TiUser]

You are right - that's exactly the usage of "gain" controls.

I personally agree to your setup with separate volume controls - I don't think doing this digitally is the best way doing it.

However there are reasons to use Cantabile's sliders, buttons,... mapped to midi controls not just to trim things during editing but for performance too. It's not just the session recall thing technically odd, missing value catchup and midi value feedback return simply set unnecessary restrictions.

I am nor about replacing the current behavior but adding some missing things... but I've asked for these already and being told it's low to no-go priority because few people have asked for it.

[humphrey]

-------------------------------------------------------------------------------
I am nor about replacing the current behavior but adding some missing things...
-------------------------------------------------------------------------------

in this case I totally agree of course

regards, humphrey