These buggers arent exporting too midi

[rorzamcbean]

Screen Shot 2025-01-02 at 8.34.19 pm.png (60.34 KiB) Viewed 10904 times

These two modules make up the pitch and gate controls. I want to print them to a midi track in Logic so i can pipe them out to my real life modular.

Screen Shot 2025-01-02 at 8.31.46 pm.png (580.09 KiB) Viewed 10904 times

But all i get is this... Each long note you see is like dozens of midi clips/notes

[SpaceDog]

Try the FX version of VM and see if that works.

[ChR_is]

it's hard to tell what's actually going on in your patch, but i'm guessing that your CV is not quantized and synced to the "gate". midi is a message based system whereas cv is continuous, therefore it's oftentimes difficult to express one system in the other and vice versa. e.g. pitch cv can vary every moment, whereas the pitch of a midi note is set for the whole duration of the note and pitch bend, which is a separate midi message, is needed to change pitch during the held note.
what's likely happening here is that the pitch is not pinned to one exact value for the duration of each gate. in midi there is no way to express pitch changes during a held note (besides pitch bend) and therefore the cv-to-midi module simply chooses to create another midi note for the change in pitch. note that pitch bend is a separate input on the cv-to-midi module. i don't know the details of its implementation, but i guess pitch cv and pitch bend are treated independently.
it could also be that velocity is a fluctuating signal, which triggers the cv-to-midi module to output multiple midi messages, but i'm not sure about that.

you can try to use a sample and hold module to fix the pitch (and velocity) to one value during a gate and see if that helps.

btw. the M4 Turing module does not output gates. its product page says: "Output: Outputs static value of current step." There is no clear definition of gate threshold in modular. some modules treat any signal greater than 0V (or any slight offset from 0V) as a gate whereas others use 2.5V or any other value. try converting the output to a regular gate signal before patching into cv-to-midi, maybe that helps as well.

[rorzamcbean]

it's hard to tell what's actually going on in your patch, but i'm guessing that your CV is not quantized and synced to the "gate". midi is a message based system whereas cv is continuous, therefore it's oftentimes difficult to express one system in the other and vice versa. e.g. pitch cv can vary every moment, whereas the pitch of a midi note is set for the whole duration of the note and pitch bend, which is a separate midi message, is needed to change pitch during the held note.
what's likely happening here is that the pitch is not pinned to one exact value for the duration of each gate. in midi there is no way to express pitch changes during a held note (besides pitch bend) and therefore the cv-to-midi module simply chooses to create another midi note for the change in pitch. note that pitch bend is a separate input on the cv-to-midi module. i don't know the details of its implementation, but i guess pitch cv and pitch bend are treated independently.
it could also be that velocity is a fluctuating signal, which triggers the cv-to-midi module to output multiple midi messages, but i'm not sure about that.

you can try to use a sample and hold module to fix the pitch (and velocity) to one value during a gate and see if that helps.

btw. the M4 Turing module does not output gates. its product page says: "Output: Outputs static value of current step." There is no clear definition of gate threshold in modular. some modules treat any signal greater than 0V (or any slight offset from 0V) as a gate whereas others use 2.5V or any other value. try converting the output to a regular gate signal before patching into cv-to-midi, maybe that helps as well.

Thanks for such a generous contemplation as to what could be happening. I will try the S&H suggestion next chance i get with the patch.

My intent is to capture the cv note (which is quantised) as the turing triggers. Because i want to send it on through to some LPGs in my physical modular and figure triggers will work just fine with that.

[marltetz]

I think Andrew Macaulay's "CV Change Gate" does something for you.

It generates gates (or just slight lengthy triggers?) at any change of CV value.

Screenshot_turing+cvchangegate.png (582.64 KiB) Viewed 10659 times

see the MULTI OSCILLOSCOPE
- Red line shows Trigger from QWERTY Keyboard
- Green line is CV value from Turing module
- Blue line show a gate generated by "CHANGED (CV Change Gate)" module

It needs some tweaks if you want more "control" for gate lengths, but it can be converted to MIDI note on(and off) messages as the change of pitch CV value.

[Steve W]

My intent is to capture the cv note (which is quantised) as the turing triggers. Because i want to send it on through to some LPGs in my physical modular and figure triggers will work just fine with that.

I am trying to wrap my head around things that used to be more intuitive for me, so as an exercise I have been trying to sort out your patch and what you are trying to do. Correct me if I am wrong, but it seems to me you want to pass on to a modular synth (1) a CV value corresponding to midi pitch as generated by the turing module (triggered by something) and quantized by the Quantizer module and (2) a trigger from the same trigger source that is used to trigger the turing module.

But all i get is this... Each long note you see is like dozens of midi clips/notes

This makes sense to me. It seems like you are expecting the turing module to also send out note on and note off data (aka duration).

At least this what I can tell from the patch section you posted.

[Steve W]

https://store.cherryaudio.com/modules/turing

I think Andrew Macaulay's "CV Change Gate" does something for you.

Interesting idea! Are you suggesting that rorzamcbean doesn't want a trigger to be passed on based on the trigger into the Truring module as I first thought, but wants a trigger to be sent for each of the module's steps?

[marltetz]

>Steve W
Turing has triggers from somewhere in his picture. I guessed he had some reasons to separate triggers and generated MIDI notes, or wanted triggers only at the change of musical notes.
But I just made things complicated, thank you for clarifying!
Maybe, as you said in (2), patching same source of trigger(connected with Trig on Turing) to the GATE input of 'CV to MIDI' module is enough (and removing a cable between Turing's output and CV to MIDI's GATE input).

>rorzamcbean
In your patch, you already have trigger signal for triggering Turing. What's the source of that trigger signal? Where does it come from (another module or outside of VM?)

btw, another problem can be there
>Each long note you see is like dozens of midi clips/notes
This can happen when you connect a VM's MIDI output to same VM instance's MIDI input through DAW because it causes feedback loop.