My current patch works well, but not always. I have repeatedly noticed that gates and pitch do not arrive at my mother 32.
The patch contains 4-5 clock dependent modules. After every restart I have to refresh the midi map for the modules otherwise I get no signals. After further investigation I realized that not every module is affected. Currently I have tested a handful and repeatedly get the same results. I have created the patches in vcv but also in MM.
The modules VCV-ADSR, VCV-SEQ3 as an example are started when I start the clock from external (midi).
However, the modules VCV-LFO, OrangeLine-Dejavu, ClonedInst-Envelopes do not get a clock signal after they have been mapped and the mm has been restarted. I didn’t want to test more modules for now. I use the FW
v2 10.3…
I have checked the patches again. This time, however, I added a midi module from the rackcore and connected the clock via cable. These patches start without errors after restarting mm. This directs the view to the midi map…
Hi Okami, when you say “refresh the midi map” are you referring to needing to go back into each module and re-map every parameter, or restart the patch? As in, the settings get lost on save and power down?
Yes, that describes exactly the procedure. But only for the clock connection to the midi map. All other mappings are unaffected. I have not yet tried changing the patch without restarting.
Ok, I think this is fixed now, and will be in the next version.
The problem was the MIDI clock and transport mappings were not informing the connected module that the jack now has a cable patched. Some modules don’t care and will accept an input even if they don’t get the message that a cable is patched, but some modules will skip processing. So that’s why it happens on some and not others.
Also, I fixed a related issue where you couldn’t have two different divided MIDI
clocks in the same patch. When making MIDI maps with the VCV MIDI->CV module, this is also the case – you only have one CLK/N jack so you can only have one MIDI clock divider. But if you make MIDI mappings from within the MetaModule you can create multiple different MIDI divided clock mappings and choose a different division amount for each. However, that wasn’t working properly until now (all the divided clock mappings would end up running at the same rate). So that will also be in the next version v1.6.x and v2.0-dev
Even if working with MM is a bit tedious at times and rarely investigative.
I am very satisfied with the communication and the prompt response, thumbs up…