MIDI > CV module sends old retrigs from being bypassed after being enabled again

Development
1

Dunno where to report bugs, but here it is:

I found a bug with the fundamental MIDI - CV module, if you have it working with a midi controller then disable it with CTRL+E, then press keys on the midi controller, as soon as it’s enabled again it will send a retrig pulse for any poly channel that was pressed while it was disabled/bypassed. Happens in mono too.

1 Like
2

Fundamental MIDI-CV is created by VCV, so the way to report bugs is using the form on the page VCV - Support (vcvrack.com), or email support@vcvrack.com.

(I wish the standard module menu had a “Report a bug” entry.)

1 Like
3

I’m dealing with the same bug as well right now… I thought first I’m getting crazy: I’m not playing right now :sweat_smile:

I’ll report the bug as well to VCV. Apperantly nothing changed…

@sethmerkley: did you manage to report the bug? And if yes, did you get an answer?

4

Also happens if you have no audio device initially (happens sometimes under Linux if you switch on devices in a different order) and start playing on your MIDI keyboard before you realize there is no audio. Once you select an audio device after some random time (many seconds) all the keys you played start to come out of whatever queue was holding them.

5

mmmhhh… I hope there is a good fix or workaround somehow… it starts to become quite troublesome when using VCV on different instances within a project. I’m using it mostly for sfx creations for my instruments in my DAW. But I also need MIDI input for triggering certain things within the patch.

Until now I’m mostly working on one patch at a time. But ideally I would like to be able switch between patches while playing. Right now that might result in the midi to cv module firing the previous input again… which is not ideal :sweat_smile:

well, I got a request from the VCV team today to send in a Reaper Project file that has this issue. I hope they can help finding a solution or at least point me in the right direction. :crossed_fingers:

6

Just wanted to send an update:

I had contact with the VCV-Support and first of all they could recreate my bug (Yeah, I’m not crazy) and also found a workaround.

This is how the bug in my system is created:

DAW = Reaper v.7.48 on macOS-arm64

Setup with two tracks with one VCV instance each. Each VCV instance has one MIDI to CV module and both are set to Core MIDI and QWERTY-keyboard as a midi input device (the bug also happens with an external MIDI-keyboard through Core MIDI).

  1. I mute Track 02
  2. I open the VCV instance on Track 01.
  3. I click once within the VCV window to focus it and that the keyboard input is sent to this fx.
  4. I play a couple of notes with the QWERTY-Keyboard (literally just 3 or 4 are enough)
  5. I close the VCV-window on Track 01
  6. I unmute Track 02
  7. I open the VCV instance on Track 02
  8. I click once within the VCV window to focus it and that the keyboard input is sent to this fx.
  9. and then the bug happens aka “MIDI to CV” on Track 02 repeats the previous input from Track 01

Solution or Workaround: Setting the “MIDI > CV” to DAW/DAW.

For Reaper I then need to either put the input to my MIDI controller/QWERTY-Keyboard. Or I have a midi send from another track towards the track with the VCV instance.

So far I could not recreate the bug :slight_smile:

I still hope there is fix for this in a further update, but so far so good.

Did anyone else experience something like that outside of Reaper?