Hi all. I haven’t been as active here as I was for a while, because I’ve been lost in the sauce trying to make music. But, I really want to get a few things ironed out to make my Zynthian experience much smoother.
Sometimes, I will use the Zynthian in the way you’d expect, hosting the VSTs there, and just feeding the audio to my DAW. However, I will also often use the Zynthian in an extremely basic MIDI filtering/pass-through mode. So, I have a Snapshot that I just call Double Passthrough. It consists entirely of two MIDI chains. One takes the input of my Casio piano, and passes it through on MIDI Channel 1 via MIDI DIN cables to my SSL2+ MKII.. The other takes the input of my AKAI MPK249 and does the same, except on Channel 2.
My experience is that when the machine has just restarted (after being properly shutdown, etc.), the device requires me to reload the snapshot, otherwise, it will always send duplicate MIDI messages (one on Channel 1 and one on Channel 2). So, it seems like something just doesn’t work right after a fresh boot to properly route MIDI.
Hi @jigglydad! That sounds like the snapshot isn’t being saved / loaded properly at startup. Zynthian uses a snapshot called, “last_state” which should retain the configuration that was loaded when you shut down. It sounds like a bug so please use webconf’s Report Issue button to report this. That way we will get useful info about your software and hardware configuration. Please also upload to that ticket the snapshot that is failing (Double Passthrough).
Sorry. I was looking for a place to attach something, and when I was on the small compose window, I didn’t see it. Here is the snapshot.
I was just in the process of trying to submit it through the webconf as mentioned by riban….but, in the process of trying to write the steps (generally pretty basic) to reproduce, I found that it was not doing it each time. That makes it a lot harder. I really thought it was pretty consistent, and I JUST got it before I posted.
To attach a file to a GitHub issue, just drag the file from a file browser to the GitHub entry window. GitHub limits the types of files it accepts so you may need to zip the file first.
Adding a GitHub ticket from webconf really helps us because it adds details about the software and hardware you are running and it guides you through the steps that allow us to diagnose the problem. As you can imagine, without the steps to reproduce, we will find it hard to work our the problem. But even if it only sometimes occurs, the ticket is advantageous. Make sure you describe such inconsistency.
I’ve had somewhat similar issue with my MIDI input configuration (done from the Admin menu): I want to use multitimbral configuration but after reboot and / or shutdown it’s back to active channel mode. Weirdly enough this doesn’t always happen, but at least 90% of the time it does. I’ve tried saving my snapshot as last_state and this doesn’t seem to make any difference. I’ve also tried to make a new snapshot from scratch, but the problem persists. Is the MIDI Inpt setting supposed to be saved with the snapshot?
