I have two tracks. On track one, the vsti’s CC volume resets to zero whenever I hit stop. On track two , with another vsti, the CC volume stays on it’s most recent setting.
I set up track 1 to use track 2’s vsti, and it now makes that other vsti reset to zero.
This indicates that there is some kind of “reset on stop” function happening due to a setting on track one. The problem seems to have started recently, as I don’t remember having this problem before.
Notes: There is no automation. The ‘read’ setting is off. I don’t see that there are any external midi devices set up on the tracks.
Hi,
I’m just wondering, if your issue is similar to this one.
Since it is happening differently on different tracks, setting any global “reset CC” options won’t solve this particular issue.
On track two, the one that doesn’t reset CC7 to zero, I duplicated the track/channel, erased the midi, created a new midi section, wrote in new notes and it is ok (it doestn’t reset cc7).
… but… When I paste the midi file from track one (which was resetting cc7 to zero) into that duplicated “track two”, all of the sudden it resets cc7 to zero when I hit stop.
Therefore, there is something in the (corrupted) midi file itself that is making the vsti go into “reset midi cc” mode??
p.s. I looked for any other midi data (besides Velocity, Pitch Bend and Volume) on that ‘corrupted’ midi file and I don’t see anything (in case there is a “reset midi cc” type of message that I don’t know about).
Hi,
Isn’t there any SysEx message in the given MIDI Part?
I didn’t add any sysex, unless it was accidental somehow. Is there a way to check that?
I’m using Kontakt 5 by the way. If you know of any other way to diagnose the problem, by either shutting off Kontakt midi CC, sysex, etc, functionality, or shutting of functionality in Cubase to zero in on the problem, let me know.
Hi,
You can see all MIDI Mesages in the List Editor.
Could you attach a project with a single tracks, where is the problematic MIDI Part?
I took all the cc7 data out on the track, and it stopped doing the ‘reset to zero’. I then, on a whim, put all the cc7 data back, selected all of that data (there is a lot), switched it to “ramp/curve” and then back to “step” and it solved the problem.
Any idea why this is an issue?