I restored all backups including system backups (from RC2210) But now, all MID-CCs from my USB Launchpad-X are blocked. I read somewhere, that is on purpose, cause of MIDI-learn.
I started MIDI-Log. It shows Program Change, but not MIDI-CC from LaunchpadX.
Please, can I has back MIDI control for my MOD-UI?
I have similar problem with stable 2211. I made a fresh install, added a MOD-UI chain, and added plugins on web interface.
When I try to assign a parameter to MIDI on the web interface, nothing happens (almost nothing, it’s seems like the parameter is assigned to something).
When I try to map a MOD-UI effect parameter on Zynthian UI, the CC number appears, but that’s all, I can’t control the parameter.
MIDI learning works perfectly outside of MOD-UI. All my controllers work in MOD-UI with stable 2109.
I’m seeing this issue also, and the workaround I found was to click on MIDI PORTS in the mod-ui lower right and select Aggregated Mode, Save, then Save the pedalboard.
I don’t know if Separated mode is ever useful on a Zynthian hosted environment, we could consider hard-coding midi_aggregated_mode = True always in a host.py patch:
Something strange happened, but not related with the latest fix, that it’s only available on testing. Stable branch has not changed in the latest days.
Anyway, i just updated my “stable” V4 machine and everything worked fine, so i don’t think it’s a problem with stable updates. Please try updating again and restart the device.
Thank you again! After a few restarts (and a power outage) it seems back to normal now. Concerning testing branches: is it best to set every branch to testing? Or just the one needed for the fix? That would be “zynthian-ui”, I guess?
I would caution against flopping back and forward between testing and stable and it seems best to stick to one on a specfic machine.
Best practise is to keep seperate SSD’s in such circumstances.
I’ve had issues with snapshot reloading after changing with unrecognised parameters in the file formats.
Back up frequently and keep decent notes as to which backup came from where. I’m probably one of the most cavalier users in these regards, so if my message appears dismissive, it’s not. I fully appreciate the effort the developers put into ensuring compatibility, but if you have done something along these lines, suspect that before looking for wider issues.
Been on stable all the time. But I am tempted to go to testing. I always do complete backups, so I even could go back to staging 2210, where the MIDI learn of MOD UI still worked.
Personally I have tended to live on testing but the Audio Mixer has been essential to me for some time now and this was a testing feature.
It also depends a lot on what you are tending to do. Using a machine live is certainly not a good time to make such a switch as any kind of issue will almost certainly raise it’s head in such a situation.
I caught a patch of this during a Rehearsal last Friday where the absence of a top left encoder due to changes left me unable to answer the question, “Why can’t I adjust the volume like I used to…?”
My fault, of course, as I’d concentrated on features I wanted to use rather than what people expected to be available.
We aim to make backwards compatible to ease migration but find it challenging to do forwards compatibility. If we knew the future we might not be doing this! So saving snapshots then found back to an older version is likely to fail
True. That’s why I always do a complete backup and seperate ones for presets, soundfonts and system settings etc. They all go into one folder, so I can always revert back to an old state of the machine.
I’m afraid of saying it… but no- it doesnt work. same as before. I can assign a CC, it shows on the display, but using it doesn’t change the assigned value…