CC1 keeps resetting on 'Stop'

richardjay · March 8, 2012, 12:05pm

My string libraries (VSL & LASS) are setup to control dynamics via CC1 (ie mezzoforte is CC1 value of 64). These are added via Score or Key Editor, but the problem is when the project is not playing CC1 goes down to zero, so everything I play at the keyboard is pianissimo !

How can I ensure that CC1 is a specific value unless a project is playing. Can’t Cubase just leave CC1 at whatever the last value was ? I’ve tried playing with the MIDI > Chase Events preferences but it doesn’t seem to help; Reset on Stop is also unchecked. Incidentally, the CC1 values are ONLY being sent by the Score & Key Editors. I thought that’s why this was happening so I tried leaving my mod wheel left at a CC1 value of about 64 but still CC1 reset’s to zero when I stop Cubase.

Martin.Jirsak · March 8, 2012, 9:53pm

Hello,

This is weird. I have no problem with this. I’m using VSL too. I’m using EWQLSO, and if I choose instrument with MOD signature, the Modulation control the Expression. I have never had problem with this.

My Reset on Stop is Off (unchecked).

Chase Events: All is On (checked), except the SysEx (unchecked).

Cubase just leave CC1 at whatever the last value was in my settings. Can you check when exactly the Cubase set the MIDI CC1 to the 0 Value? Try to use some MIDI monitor. Is it at the moment, you stop the project, Or different one?

What about different MIDI CCs? Volume (7), Pan (10), Expression (11), etc.?

Best,

GargoyleStudio · March 9, 2012, 11:03am

I’ve had a lot of trouble with this using both a VSTi and external hardware synths. I would like Steinberg to provide a check box for the CC values which get reset or chased automatically by the system. They’re fixed and not assignable at the moment, and for me too, none of these setting you mention worked either, the CCs were still sent.

I found two solutions. One was to adjust the VSTi so it used a different CC number.

The other one I used (more applicable to my external hardware) was to install midiox and midiyoke, then start midiox running with a CC filter between two midiyoke ports. Then I’d start cubase and send the midi track through midiyoke → midiox → filter → midoyoke → VSTi. That got rid of it, but it’s a right pita.

Mike.

richardjay · March 9, 2012, 11:05am

Hi Martin,

But are you using Dynamic Mapping ? If you open a completely blank project, add a dynamic (say, mf) press play and then hit stop after the dynamic does whatever CC you have assigned to Dynamic Mapping (CC1 in my case) stay where it was (the value for mf) or return to zero ?

richardjay · March 9, 2012, 11:38am

Mike - are you saying that some CC’s don’t get reset to zero, if used by Dynamic Mapping ? Do you happen to remember which ones ? I’m guessing it’s the less common, unassigned ones …

GargoyleStudio · March 9, 2012, 12:45pm

Sorry, I don’t really remember, it was quite a long time ago and I don’t have those projects handy anymore. But I do remember that it’s not clear anywhere in the Cb documentation which CC values are chased and when. I personally found that both VST and external hardware sounds would change apparently randomly and I used midiox+midiyoke to investigate what the real midi messages were that Cubase was transmitting because there’s no other way to see them. Once I’d found out I filtered them or changed the VSTi CC value and all was well.

I think they’re always chased to zero though. Also the CC121 is transmit IIRC, which is ResetAllControllers.

But I’m not using dynamic mapping, this is just the normal Cubase response I’m talking about here.

Mike.

Chris_Beuermann · March 13, 2012, 1:13pm

Hello,

Some Controller will be set automaticly to 0, to avoid “accidents”

Every controller with the word “true” will get a reset:

Cheers,

Chris

Martin.Jirsak · March 13, 2012, 1:40pm

Hello,

Your problem is maybye solved in the Cubase 6.0.6 or Cubase 6.5.1 update, released today.

Best,

richardjay · March 13, 2012, 2:11pm

This should be something the user can enable or disable …

richardjay · March 13, 2012, 2:14pm

Well, it sounds like Steinberg consider it a feature rather than a bug …

Rexxyboy · April 22, 2020, 5:30am

Old thread this one! I had a similar issue today with Modwheel modulation CC1 getting reset, it turned out to be midi ch 1 in East West Play wreaking the havoc. It didn’t solve it but i worked around it my not using Ch1 in Play on those sessions…

ekmusic · April 23, 2020, 3:03pm

I wasn’t sure I understand the solution.
Is there a way to solve this issue?

Thanks

Rexxyboy · May 4, 2020, 4:07am

it’s like i said, i stopped using midi ch 1 to EW Play in that session and the problem stopped. (changed Violins from ch1 to ch 11 instead). It’s a fix rather than a solution, but this worked for me in this case.

musicianlaurence · May 12, 2021, 10:01am

The answer is:

Preferences - Midi - Never Reset Chased Controllers (tick/check this box).