You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am developing a specialized control device driver for AKAI APC key25 mk2 (always a mouthful!). And there already is another driver for that device (an excellent one by the way), targeting general control and specialized for the sequencer.
Since I see no sane way of integrating the two drivers (no key combos left to switch from one mode to the other). And each of these drivers already has a ton of submodes.
Describe the solution you'd like
I think the only way to support both is to support multiple drivers for the same device, and let the user choose which driver they want to use for which device. Of course, if you have two the same devices, one could be ruled by one driver and the other by the other.
Describe alternatives you've considered
Combining the two drivers. But as I said, there are no keys left to switch modes. And I would need to adjust my coding style to oscaracena's I think. Might be a good thing though.
And running my first (nodejs) implementation of the driver on another machine, connected with the zynthian via a utp-cable. I have two issues with this:
Dropped packets? It seems sooperlooper does not always respond to all OSC messages. It seems that not all of them arrive. I think I have better chance when running the program on the same machine.
I do not want to have to carry a laptop around just for this. I tried running the nodejs program on the zynthian itself but had a hard time going behind zynthian's back in terms of MIDI connections.
It requires me to run a second program (with an OSC server) on the zynthian just to get tallies on the saved sessions.
Is your feature request related to a problem? Please describe.
I am developing a specialized control device driver for AKAI APC key25 mk2 (always a mouthful!). And there already is another driver for that device (an excellent one by the way), targeting general control and specialized for the sequencer.
Since I see no sane way of integrating the two drivers (no key combos left to switch from one mode to the other). And each of these drivers already has a ton of submodes.
Describe the solution you'd like
I think the only way to support both is to support multiple drivers for the same device, and let the user choose which driver they want to use for which device. Of course, if you have two the same devices, one could be ruled by one driver and the other by the other.
Describe alternatives you've considered
Combining the two drivers. But as I said, there are no keys left to switch modes. And I would need to adjust my coding style to oscaracena's I think. Might be a good thing though.
And running my first (nodejs) implementation of the driver on another machine, connected with the zynthian via a utp-cable. I have two issues with this:
Additional context
For the curious: My driver is at https://github.com/pft/zynthian-ui, branch pft-sooperlooper (I disabled oscaracena's driver so it is in no way ready to be merged!), (partial) explanation of the driver is at https://github.com/pft/sl-apckey25mk2.
The text was updated successfully, but these errors were encountered: