# CV \> MIDI module behaves differently depending on how patch was created

**URL:** <https://forum.4ms.info/t/cv-midi-module-behaves-differently-depending-on-how-patch-was-created/1086>\
**Category:** Dev Firmware Discussion\
**Created:** [February 14, 2025, 10:33pm UTC](https://forum.4ms.info/t/cv-midi-module-behaves-differently-depending-on-how-patch-was-created/1086 "2025-02-14T22:33:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gabrielroth](https://forum.4ms.info/user_avatar/forum.4ms.info/gabrielroth/32/17_2.png) [@gabrielroth](https://forum.4ms.info/u/gabrielroth)\
**Post date:** [February 14, 2025, 10:33pm UTC](https://forum.4ms.info/t/cv-midi-module-behaves-differently-depending-on-how-patch-was-created/1086/1 "2025-02-14T22:33:39Z")

</div>

I know we can’t yet set MIDI channels in the CV \> MIDI module in VCV Rack, but this is another level of complexity:

- When I create a patch on the MM, then create a CV \> MIDI module within that patch, the CV \> MIDI module has an Options menu with the MIDI Channel, Pitch Bend Range, and other settings.

- But when I create a patch in VCV, send it to the MM, _and then add a CV \> MIDI module on the MM,_ the Options menu is not there!

It is weird for patches to behave differently on the MM depending on where they originated!