I’ve modified the code to only send the All-Notes-Off when changing to a “Synth” layer, so, when “click-rotating” layers or when using the layer list for selecting an active layer, notes wont be cutted if you are not selecting a different Synth layer.
Of course, it’s not perfect and i will try to improve all this in the next days/weeks …
Anyway, the best way of managing SooperLooper is by using MIDI-Learning
And seems Sooperlooper lost working midi mapping again.
or better, saved midi mapping is present but does not work. must repeat learning.
once remapped, cc works, but Debug says:
ERROR:root:Can't exec engine command: \set_control 3, 0.000000 => isalive() encountered condition where "terminated" is 0, but there was no child process. Did someone else call waitpid() on our process?
Strange error. It seems to be related with LinuxSampler and loading of big soundfonts from disk. If you restart the zynthian service from command line and try loading the snapshot again, it loads perfectly. If you reboot the zynthian, it fails again ;-(
I would recommend to update from the command line and send the log.
Also, you could try to re-burn the SD with a fresh Gorgona Omega image and update twice from the command line, capturing and sending back the log if it doesn’t work.
I don’t know if you (@jofemodo) fixed it in your working branch.
But now the logic seems to be inverted.
If Single Channel is “Off”, I can use the Single Channel feature. But when it’s “On”, my Channel1-Only-Keyboard doesn’t switch sounds, when I press the Volume sector (I have a Touch-Only Zynthian).
Sorry, currently the Zynthian-UI has not “checkboxes” …
Also, the standard tkinter widget set doesn’t support checkboxes inside listboxes … perhaps in the future
Maybe my suggestion is not clear, what i mean exactly. Happy New Year … uhuh! …
Checkbox as just part of message string. Of course this depends of symbols, available in used fonts, but i mean something like this and this.
[*] Wifi
vs
[ ] Wifi
or
[*]TouchOSC Enabled vs
[ ]TouchOSC Enabled
etc
This doesn’t need exact checkbox implementation, just two strings as now e.g.
‘Start Wifi’ --> ‘[ ] Wifi Network’ (selecting this turns Wifi ON)
‘Stop Wifi’ --> ‘[*] Wifi Network’ (selecting this menuitem turns Wifi OFF)
In this way if one looks at Zynthian UI, then menu items are
[ * ] Single channel
[ . ] Wifi Network
[ * ] Qmidinet
[ * ] TouchOSC
…
You can see, which menuitems are active and which not… without reading and “decoding in mind” entire menuitem meaning.
On some keyboards, circle means enabled and X disabled (an old Korg T3 inside global page) but maybe a simple an enabled “o” and disabled “-” or a less visible “.” Could be fine