USB Midi behaves differently in VCV rack vs MetaModule

General
1
  1. Patches played in the metamodule hardware are two or three octaves higher for me than the same patch played in VCV rack. I tried this with both an Arturia Keystep and an ASM Hydrasynth via USB midi, with VCV rack running on an Apple silicon MacBook, using the VCV Midi->CV module v/oct jack straight into any oscillator’s pitch jack.
  2. On a monophonic patch, VCV rack’s Midi->CV with a VCV VCA module will keep the gate open as long as I have a key held down. For example, when I hold down an A key, then press another key B while still holding down A, and then release key B, in VCV rack, note A will still play. In the metamodule, doing the same thing with the same patch will terminate note A (The gate is closed, A will not play again until I release it and press it down again.)

Are these limitations of the Metamodule Midi to CV implementation, or are there some settings I am not seeing? Or should I be using a different module? I would really like my patches to respond to midi the same in VCV rack as in the hardware module.

Thanks!

2

i noticed also about the octaves higher issue

3

Thanks for the detailed reports.

  1. I’ll check this out. There shouldn’t be a difference between using MIDI in VCV vs. on MM, but I’ll see if I can reproduce that. IIRC there are at least two “standards” for MIDI Note middle C is, so maybe VCV and MM are using different standards (though, odd I never noticed that before).

  2. OK, I might know why this is. The MM has an algorithm for this type of thing (more notes pressed than the polyphony#). I’ll bet VCV’s way of handling that is different than MM.

4

Ok the MIDI pitch difference was fixed in firmware v1.2.0 (releasing it now…)

2 Likes