Hello everyone,
maybe I'm not the only one experiencing this, but I have some issues with the MIDI Out feature of Voltage Modular.
When I open VM as a VST instrument in Cubase Pro 10.5 (Windows 10 Pro 64bit), the MIDI Out only transmits pitch, note on/off (gate), velocity and aftertouch events. Everything else is not received by a MIDI track.
But when I output the same data to a LoopMIDI device, everything gets transmitted just fine.
The left MIDI Monitor shows what's going on on the VM MIDI output, the right one shows the LoopMIDI device.
You will also notice the different time stamps (which I'm fine with, I guess) and the Aftertouch-PolyPress difference.
Since I can achieve what I need using the LoopMIDI device, this is actually not a problem for me. I just thought I'd share this if other people are experiencing similar issues.
@cherryaudio : Did I discover a bug or am I just missing something obvious here?
Best regards and stay safe,
Martin
MIDI Out issues
- honki-bobo
- Posts: 305
- Joined: Sat Nov 09, 2019 1:18 pm
- honki-bobo
- Posts: 305
- Joined: Sat Nov 09, 2019 1:18 pm
Re: MIDI Out issues
While I was experimenting some more with the MIDI Out issue, I found the following:
When setting all CV TO MIDI inputs to 0 except for the gate, the resulting event is a "Note Off" on both open and closed gate on the VM MIDI output, while it is "Note On" and "Note Off" on the LoopMIDI device, as one would expect.
After some fidling around I found that a new "Note On" event is only generated, when the velocity input is greater than 0. The LoopMIDI device still behaves as expected.
When setting all CV TO MIDI inputs to 0 except for the gate, the resulting event is a "Note Off" on both open and closed gate on the VM MIDI output, while it is "Note On" and "Note Off" on the LoopMIDI device, as one would expect.
After some fidling around I found that a new "Note On" event is only generated, when the velocity input is greater than 0. The LoopMIDI device still behaves as expected.
- Attachments
-
- VM MIDI Out 2b.jpg (375.21 KiB) Viewed 4860 times
- honki-bobo
- Posts: 305
- Joined: Sat Nov 09, 2019 1:18 pm
Re: MIDI Out issues
And yet another issue:
I have created a 1 bar MIDI track with rising 16th notes at every quarter beat, sent the data to VM and used the MIDI In module to get pitch and gate data. Then I've sent the gate signal to the gate of the CV To MIDI module and the pitch signal to everything else, just to get different values for each note. I've then recorded the MIDI data from the VM MIDI output and the LoopMIDI device.
Besides the aforementioned issues with most MIDI data not getting through the VM MIDI output, I have noticed two things:
1. The timings of the "Note On" and "Note Off" events jitter massively (up to 15/120 of a 16th note at 120 BPM, that's about 16 ms or 750 samples at 48k)
2. The output of the LoopMIDI device is about 66/120 of a 16th note ahead (about 69 ms or 3300 sample at 48k)
The top editor shows the input MIDI track.
Next up is the VM patch I used.
The third window is the list editor of the track recorded from the VM MIDI output
The last editor shows the data from the track recorded on the LoopMIDI device.
I have been following the Sync with DAW - Cubase Artist 10 post on this forum and the MIDI timing issue only seems to affect Cubase. From what I have read, you (CherryAudio) seem to have fixed the sync problem on the input side of things. Can this fix be ported to the MIDI Out module maybe, so it would fix timing issues on all available MIDI devices?
I have created a 1 bar MIDI track with rising 16th notes at every quarter beat, sent the data to VM and used the MIDI In module to get pitch and gate data. Then I've sent the gate signal to the gate of the CV To MIDI module and the pitch signal to everything else, just to get different values for each note. I've then recorded the MIDI data from the VM MIDI output and the LoopMIDI device.
Besides the aforementioned issues with most MIDI data not getting through the VM MIDI output, I have noticed two things:
1. The timings of the "Note On" and "Note Off" events jitter massively (up to 15/120 of a 16th note at 120 BPM, that's about 16 ms or 750 samples at 48k)
2. The output of the LoopMIDI device is about 66/120 of a 16th note ahead (about 69 ms or 3300 sample at 48k)
The top editor shows the input MIDI track.
Next up is the VM patch I used.
The third window is the list editor of the track recorded from the VM MIDI output
The last editor shows the data from the track recorded on the LoopMIDI device.
I have been following the Sync with DAW - Cubase Artist 10 post on this forum and the MIDI timing issue only seems to affect Cubase. From what I have read, you (CherryAudio) seem to have fixed the sync problem on the input side of things. Can this fix be ported to the MIDI Out module maybe, so it would fix timing issues on all available MIDI devices?
- honki-bobo
- Posts: 305
- Joined: Sat Nov 09, 2019 1:18 pm
Re: MIDI Out issues
Am I the only one having these issues with MIDI output from VM?
@CherryAudio : Am I doing something wrong or missing something?
@CherryAudio : Am I doing something wrong or missing something?
-
- Site Admin
- Posts: 256
- Joined: Fri Jul 27, 2018 5:36 pm
Re: MIDI Out issues
Hi there,
There's a lot to unpack here, but here's some information:
Thanks!
- Dan @ Cherry Audio
There's a lot to unpack here, but here's some information:
- Regarding the Note Off events when there should be a Note On event, you discovered a flaw in the CV To MIDI module. See, an odd aspect of the MIDI spec is that a Note On message with a velocity of 0 is considered a Note Off message. This quirk has plagued many MIDI developers over the years. Anyway, it turns out if you plug a cable into the velocity input of the CV to MIDI module, and feed 0 volts into it, and then trigger a gate, it will send a Note On message with a velocity of 0, which is incorrect. It should be sending a velocity of 1. I've published a new version of the CV to MIDI module, so this issue should now be resolved, and you should be able to proceed with your tests.
- Regarding various MIDI messages not getting to your host, I'd bet that you're loading the VST3 version of Voltage Modular. The VST3 design is pretty flawed when it comes to outputting MIDI to hosts, and without getting into technical details, it's likely that you wouldn't have this issue with the VST2. Is there any way you can test that?
- Regarding MIDI timing, MIDI is an old, slow protocol, so there are efforts put into place to ensure that we do not overload it with too many messages. Conventional MIDI ports utilizing DIN cables are very slow, and vintage hardware will often freak out if you send too many MIDI messages at a time. Your DAW is probably mixing and buffering audio from the plug-in a bit ahead of playback in order to guarantee a smooth playback experience. Voltage Modular mixes audio when your DAW asks for it, and has no way to know how long it will be before you actually hear the audio, so that might explain the MIDI messages clocking in slightly early.
Thanks!
- Dan @ Cherry Audio
- honki-bobo
- Posts: 305
- Joined: Sat Nov 09, 2019 1:18 pm
Re: MIDI Out issues
Hi Dan,
I finally had the time to test the update and the VST2 version. From my tests I can report the following:
VST2 version - VM MIDI and LoopMIDI output: VST3 version - VM MIDI and LoopMIDI output:
VST2 version - VM MIDI and LoopMIDI output:
I finally had the time to test the update and the VST2 version. From my tests I can report the following:
I can confirm that this has been fixed. It works in the VST2 and VST3 version.Cherry Dan wrote: ↑Sun May 03, 2020 7:11 pm Regarding the Note Off events when there should be a Note On event, you discovered a flaw in the CV To MIDI module. See, an odd aspect of the MIDI spec is that a Note On message with a velocity of 0 is considered a Note Off message. This quirk has plagued many MIDI developers over the years. Anyway, it turns out if you plug a cable into the velocity input of the CV to MIDI module, and feed 0 volts into it, and then trigger a gate, it will send a Note On message with a velocity of 0, which is incorrect. It should be sending a velocity of 1. I've published a new version of the CV to MIDI module, so this issue should now be resolved, and you should be able to proceed with your tests.
VST2 version - VM MIDI and LoopMIDI output: VST3 version - VM MIDI and LoopMIDI output:
I can also confirm this. The VST3 version filters out (unwillingly, I assume) most MIDI messages.Cherry Dan wrote: ↑Sun May 03, 2020 7:11 pm Regarding various MIDI messages not getting to your host, I'd bet that you're loading the VST3 version of Voltage Modular. The VST3 design is pretty flawed when it comes to outputting MIDI to hosts, and without getting into technical details, it's likely that you wouldn't have this issue with the VST2. Is there any way you can test that?
VST2 version - VM MIDI and LoopMIDI output:
- honki-bobo
- Posts: 305
- Joined: Sat Nov 09, 2019 1:18 pm
Re: MIDI Out issues
VST3 version - VM MIDI and LoopMIDI output:
Nevertheless, and for completeness sake, I have re-recorded the MIDI tracks with the VST2 and VST3 versions. Here are the results:
VST2 version: VST3 version (VM MIDI device omits most messages): Thanks for the update of the MIDI Out module and for your help!
I grew up in the 80s and started using MIDI in the late 80s/early 90s. I have worked with all kinds of gadgets, MIDI Thru boxes, MIDI mergers, MIDI patch bays, you name it. So, yes, I know all about the quirks of MIDICherry Dan wrote: ↑Sun May 03, 2020 7:11 pm Regarding MIDI timing, MIDI is an old, slow protocol, so there are efforts put into place to ensure that we do not overload it with too many messages. Conventional MIDI ports utilizing DIN cables are very slow, and vintage hardware will often freak out if you send too many MIDI messages at a time. Your DAW is probably mixing and buffering audio from the plug-in a bit ahead of playback in order to guarantee a smooth playback experience. Voltage Modular mixes audio when your DAW asks for it, and has no way to know how long it will be before you actually hear the audio, so that might explain the MIDI messages clocking in slightly early.
Nevertheless, and for completeness sake, I have re-recorded the MIDI tracks with the VST2 and VST3 versions. Here are the results:
VST2 version: VST3 version (VM MIDI device omits most messages): Thanks for the update of the MIDI Out module and for your help!