The last couple of weeks I have been working on a system in VCV Vst to enable me to create sequences on the fly: recording them live. The issues I’m confronted with are: when I send the gate/trig out to the DAW (bitwig in my case) using the CV-MIDI fundamental module, some of the triggers get lost. I have to insert a gate modifier to ensure consistent gating/triggering. I also encountered inconsistencies in the V/Oct behaviour which disappeared after deleting and reinserting the CV-MIDI module: the octaves of the sequenced notes got mixed up; notes that are lower in VCV get interpreted as higher in bitwig.
Before I make a bug report, does anyone experience similar issues?
(Win10, bitwig 4.1.2, VCV vst 2.0.4) (I had issues with 2.0.5 and 2.0.6 so I reinstalled 2.0.4)
I am aware of the “middle C isn’t middle C” issue. It differs from DAW to DAW, but this is not what I mean. I probably didn’t explain well enough. I’ll try again. Say I have a sequence: C4, G3, G4, A3. (To keep it simple.) What I then hear, after being sent to bitwig, is: C4, G4, G4, A3 or a variation thereof. So the G3 becomes a G4 while the C4 stays a C4. And soforth with longer sequences. It also seems completely arbitrary and unpredictable. As mentioned, the issue disappeared after reloading the CV-MIDI module.
I just wanted to get some feedback if this was an issue for other people as well before contacting support. Because I’m sure they’re working on all kinds of issues.