How to save wiring in patchage?

Using Zynthian
1

Hi all,

I have connected a Behringer Neutron to the audio input of Zynthian and I added some audio fx layers. Just to see how it works, I changed the wiring to the image hereunder:

Config Neutron 1
Config Neutron 11150Ă—696 89.9 KB

I saved it to a snapshot.

After rebooting I noticed that the wiring was back to the original settings:

Config Neutron 2
Config Neutron 21046Ă—726 93.8 KB

Is there a way to keep the settings I made?

2

You can’t, sorry. It’s a planned feature but not implemented yet.

Regards

3

All patching must currently be done within Zynthian using the context menu of each engine to select what its inputs and outputs connect to. Changes at that level are stored in snapshots. As @jofemodo says, we aspire to a more complete state model but that is not yet implemented. You can do quite a lot with the zynthian audio routing so may be able to create a configuration that suits you.

4

Yes, that works fine. Thanks.

5

for those that search for this: i needed this so i found a work-around, kinda cumbersome but it works.
make a script and safe it somewhere in /zynthian/zynthian-my-data/my-patch.sh

jack_connect "a2j:Pure Data [129] (capture): Pure Data Midi-out 1" "Obxd-01:lv2_events_in"
jack_connect "a2j:Pure Data [129] (capture): Pure Data Midi-out 2" "OPNplug-01:lv2_events_in"
jack_disconnect "Noize_Mak3r-01:lv2_audio_out_1" "zynmixer:input_06a"
jack_disconnect "Noize_Mak3r-01:lv2_audio_out_2" "zynmixer:input_06b"
jack_connect "Noize_Mak3r-01:lv2_audio_out_1" "Surge_XT-01:audio_in_1"
jack_connect "Noize_Mak3r-01:lv2_audio_out_2" "Surge_XT-01:audio_in_2"

(this is just an example, but you need to type the names EXACTLY like in Patchage, case sensitive!)
Then find a way to execute the script when needed with
sh /zynthian/zynthian-my-data/my-patch.sh

In my case i found i could do this from PureData with an object called [ggee/shell] and connected a message to it containing the command above.
(i did put this in the zynthian_startup.pd)

1 Like
6

What were you not able to do with zynthian routing? I am interested to know whether there are normal workflows we don’t support our whether this is a particularly esoteric requirement.

7

in my case i wanted my own arp/sequencer that i could trigger with certain keys… i had my eye on the Pd part of Zynthian in regards to midi and all the synths that come with Zynthian.
Then i recently found out i cannot use Pd as a regular midi-effect… it has to be a seperate “special” chain… and there can only run 1 of it (which is kinda weird because while Pd is running one can open as much seperate patches as one could want).

So in order to control multiple synths with seperate midi channels (All plugins only listen to channel 1… unless they are multi-timbral like ZynAddSubFx or ADLplug/OPNplug)… i had to:

Add a special Pd chain
Inside Pd (from VNC, i can do all patching there… really awesome!) i have to configure it to have multiple midi-ports… each one has their own 16 channels.
i have to make that configuration so that it does that with every boot-up so i use to send messages via [send pd] in the zynthian_startup.pd. (you can “catch” setting-commands in [receive pd] to [print] while using the settings and re-use them to automate settings.)

after that Pd loses its jack connections so i have to reconnect them AND do my connections to the synths how i want in the way in my post above.

I guess it is NOT “normal” casual synth use… but still… people like to have their options… and only a few where met with Zynthians own interface in my usecase

8

please don´t get my critique wrong… i am willing to help make things better and find solutions that could benefit any future users

1 Like