@lanmower I have updated some of the tickets relating to sooperlooper. I think the crux of the issue for which you seem most vocal is captured by ticket #762 which I have posted a proposed solution. I have also fixed a couple of bugs and made a post in a sooperlooper specific topic where this dicussion may better reside.
I appreciate you have mentioned many bugbares in this topic but they have mostly been presented as proposed technical implementations rather than descriptions of the workflow issue, which has not been as productive as it could have been.
If I understand correctly, you want to have remove control of each parameter of each loop within sooperlooper and I think you also ideally want this to be triggered by MIDI note on/off rather than CC commands. Issue #762 proposes a solution for the first part of that requirement. The second part can already be done by using zynthian’s MIDI mapping and filtering rules, accessed in webconf’s INTERFACE->MIDI Options page by clicking the button below the title: “Midi filter rules” and adding rules to map note-on to CC, e.g. MAP CH#0 NON#60 => CH#1 CC#43 will map MIDI channel 1, note-on 60 (middle C) to MIDI channel 2, CC 43. Note-on velocity is used for CC value. If writting these rules directly into the textbox in webconf remember that MIDI channel is zero based so MIDI channel 1 is represente by CH#0.
You may also be able to do some of what you want already by using the prev/next nudge control to select loops. It isn’t the direct access you crave but it is better than nothing and may fill the gap until we resolve issue #762.
I really hope that this helps you to move forward towards using zynthian’s integration of the powerful sooperlooper and avoids breaking other user’s workflows.