CV to Midi Additional Trigger on Onset- help!

Hi Everyone, Hope you can help me with this- as seen in screenshot attached, I am encountering an issue with CV-Midi- with an additional short trigger on the onset of each note. I am sending a gate and V/Oct to Ableton Live to drive an external sampler via the IAC bus.

Aim: sending CV to Midi V/OCT + Gate to drive external Sampler in Live via IAC Bus Channel 1. Problem: Receiving additional midi trigger at onset of each note from VCV CV-to Midi (short note in midi file as seen in screenshot attached) which basically make Cv to Midi unusable for my use case.

Does anyone know how I can resolve this?

1 Like

Please share your VCV patch with us, so we get a real chance to help.

Strange. It might be an unintended consequence of the many MIDI fixes over the last couple of years. Strange that you would be the first to notice though. I would definately write about this to: support@vcvrack.com

250413_VCV Cv to Midi Trouble Shoot.vcv (9.9 KB) not a lot going on it at the moment, just trying to resolve this issue.

Thank you!

I took a scope and took a look at the CV signals that are passed to the CV2MIDI module (gate=red, pitch=yellow):

As you can see, the pitch changes do not align in time with the gate. When the gate is high, every change in pitch will trigger a new MIDI note.

Maybe use a delay on the gate to align both signals.

4 Likes

Great! Will try this tomorrow. Sorry should have checked this.

Just out of curiosity (away from computer at the moment) was this a teletype/Hetrick issue in the patch above or is this all CV/Gate being passed to Cv-Midi? Suppose im a bit surprised this discrepancy is the case when taking let’s say trig and v/oct from teletype.

But teletype can be driven my separate clocks and output separate streams of data, if they need to be entangled in time, you can realign with sample hold, use the gates to trigger and cv the source and the output.

Oh man - this must be in the air - i was having the exact same issue a few weeks back ha!

Same use case, and issue too - its almost like a hot-cold inlet issue in MaxMSP, where the gate is triggering a split second too early or late and making the on/off MIDI pairs scrambled.

The solution I was able to find, which works, though still doesn’t seem to be optimal was to use either a ‘dummy’ open VCA (or any other module) to delay the gate (or CV) signal as needed to they arrive at same time, or use something like the Bacon-brand ‘sample delay’ module to keep things synchronized.

There was a thread I started awhile back, lemme see if i can find/link it if helpful - glad i’m not alone on this!