Triggers won’t work because only CC values are accepted. Note on/off values are different, they are not CC values. I strongly suggest spending some time reading the Midi standard. I find a lot of people don’t do this and have problems with Midi. Any CV level can be converted to CC values across 4 inputs. A CC value is a level from 0-127 for a particular CC#. Note on values are treated differently in the Midi protocol. Note that rapidly changing CV values can overflow the buffer which is why there is a b-limit parameter.I'm trying to figure it out, but as Dubonaire said - I don't think you can send triggers to Cirklon, just CV to convert to CC. So that Idea may not work. But LFOs and envelopes from Pams should work as a CC modulations in the Cirklon.Wouldn't you get most of these advantages if you use a CV-to-MIDI/CC module (i.e., Addac221) to send MIDI commands directly to the Cirklon, which can then record, merge, and re-route them, or are there limitations to this approach?I suppose the main advantage is you are going through one port and channel without using a midi merge device. Other advantages are the flexibility to route the values to different or multiple synths, and Cirklon’s ability to scale the values. You can also record the CC values in Cirklon.
I am genuinely curious. I have been expanding into 19" rack synths (i.e., a Mellotron M4000D rack unit), and I am trying to figure out the best way to integrate the Cirklon/MIDI side with the CV side of my setup.In am super interested in this application. Are you sending Euclidean patterns from PAM's to the Cirklon to trigger MIDI notes played by the Cirklon to attached MIDI synths? Can the Cirklon do that, i.e., be triggered by external CV triggers (I do have the CVIO break-out box attached to the Cirklon)?Yep and using something like Pam’s pro workout, you can easily generate Euclidean automation sequences which can be cool on top of a more straight pattern.
Statistics: Posted by dubonaire — Mon Nov 04, 2024 4:39 am