Yes, as i commented above, this is implemented in testing (vangelis) and also staging (oram) branches. Simply check the “Router Feedback” entry in the chain’s MIDI Out submenu.
This is useful if you really need the MIDI output to be re-processed by the MIDI router. Important to note that MIDI feedback is routed thru the “MIDI player” port.
If you only need to send MIDI notes to other chains, you could route directly to the MIDI chain’s instead of feeding back the MIDI router.
Enjoy!
sorry we commented at the same time 
Amazing! I will test it out as soon as I can. Thank you!
sending pd to the router really gives it that swiss army knife feeling
first thing i locked on too tbh… it is a lot newer than my vw 
i enjoyed the song and the technology advancement too.
Wizard.
'96 mk1 last one before the face lift, iirc the lights arent how they’re meant to be
I didn’t think they were still making mk1’s in 1996… Such a baby though… My old VW is from 1973 
only in south africa I think, called it citi golf, after the facelift they kept doing it till 2009
So we’ve done a stage performance with two of them, it was a bit of a disaster, since then I’ve done a post mortem and done lots of little tweaks to the setup and my midi master clocks code… its behaving a little better now and I managed to make music reliably with it last night, I’ve adapted the whole thing to double as a stage setup by using my other audio interface on it (it would be really nice to be able to set a fallback usb audio interface, cause I keep having to change the settings when I change audio interfaces.
Other than that I’ve had to chase down loads of issues and add workaround for various problems with the delay effects, timing around the phrasing threshold, getting used to the various startup issues, getting it to auto configure my focusrites mixer settings (found a nice gui for it) and balancing the latency.
The next challenge will be pre-processing the midi signals, I need to set up a situation where the cc for delay control ranges from 64 to 127 instead of from 0 to 127, since the first half is negative range, or modify the plugin somehow
all the calf filters seem to cram the control into the first 10% , so there needs to be some calculus applied to its frequency and res, once again either have to make custom plugins or map the midi
my whammy effect doesn’t stick when it’s close to unmodified, what I’d like to do there is make it stick when its near 50% and then during it’s sticking, actually bypass it and just play clean audio, that probably means i have to produce two opposite cc’s that represent whether its near 0 or not and sticking to adjust its volume vs a clean volume
it’s getting complicated and the cracks are showing fast, every time i have to make a change i have to change all of my preset banks one by one, if its structural its hectic, so I’m trying not to set up too much of the system’s snapshots before I get the fundamental structure of the effects chains down
Yes - multiple audio and midi tracks grouped in scenes with (midi controlled) follow actions.
Certainly a feature I would like to see.
There’s and app for that!
did a quick take to test the setup…
I used this state
last_state.zss (89.0 KB)
It’s been one hell of a ride so far, I’ve made hundreds and hundreds of small tweaks to the setup as a whole over the course of the past month, did a few small stage performances at open mic scenarios, used it for a recording station once or twice
(quad mic recording)
this is my midi controller script for the apc25 mk1
zynthian_ctrldev_akai_apc_key25.py (33.2 KB)
I am also using a hardware midi clock right now, so sooperlooper is set to outboard midi sync in this scene, you can change that to loop1 for onboard midi sync, (still need to map a button for that)
the source code for my midi clock is here, it runs on esp and outputs its own midi cable and usb uart midi, I’m currently using a slight offset between them to keep everything onboard and outboard syncing together
it requires this to be set in /etc/systemd/system/mod-ttymidi.sh
mod-ttymidi.service (314 Bytes)
to keep it from being overridden I’m currently experimenting with this in startup
rc.local (477 Bytes)
update-zynthian.sys.sh (491 Bytes)
this is probably more advanced use of zynthian, so HBD lol
