Clone function for internal midi routing or something else?

Using Zynthian
1

Ok, since I am now officially new user of this strange machine (v5.1 with 8 gigabyte ram running latest stable Oram) I have to post a question here that is meant to either confirm my own inferences about how to use, or at least prompt someone knowledgeable to correct me. Anyway…

So, I purchased this machine because I liked the idea of building my own pure data patches and trigger them in zynseq. in relation to this, if I create a midi generating pure data patch, could I route its output to play a virtual instrument in another chain? Is this what clone function is for?

To picture this better: for instance, in Ableton Live I can send midi data from one track to another internally, that is, drive a virtual instrument on track A by playing midi clips on track B.

Is this possible currently? Or do I have to send midi data outside Zynthian from Midi out and then route it back to Midi in?

I appreciate your patience and useful answers :slight_smile:

2

I’m still yearning for the old “clone” function as well :upside_down_face:

3

“Clone” function doesn’t exist any more. This function had sense when only one chain can use a given MIDI channel. Now we have the possibility of having several chains in the same MIDI channel, and more powerful MIDI routing, so no need for a specific “clone” function.

Of course. You have to route MIDI-out from your PD chain to the instrument chains you want. Remember, when generating MIDI from a PD patch that MIDI channel matters.

To take profit of the zynthian’s MIDI router (active/multi modes, channel translation, key range, transposing, etc.) you can alternately route the PD chain MIDI output to the “Router Feedback”. With this setting, MIDI output will act as it’s coming from the MIDI player, reaching all chains.

Enjoy!

1 Like