THANKS!
That’s great. I assumed, Zynswitch were the new buttons beyond the 4 main encoders…
Now the BACK works better as well 
2 Likes
What Akai model are you using?
FYI, I’m working on a controller driver system for zynthian. It’s almost finished and it will allow to have device specific “drivers” including customized maps, led feedback, controller feedback, etc.
So you plug your launchpad mini mk3 and it perfectly integrates with the zynpad , managing pads and scenes. You plug an Akai MIDI-Mix, and it perfectly maps the mixer, including mute/solo with LED feedback. You plug a Beringer motor keyboard, and the motorized faders get mapped to the mixer ones. Etc. The “driver” model is simple enough to allow skilled people to contribute drivers and create a good collection with the more popular devices well supported. Stay tuned!!
The best!
5 Likes
This might get @wyleu off my back about his “one pixel display”! 
1 Like
Admit it you thrive on the attention…
1 Like
Wait, what ?!
That look great!
Feedback is hard if you do it the midi way. For encoders with led rings it’s “simple” as listening midi and give it back to the interface, but for the rest of the features it’s not !
And the plug and play in opposite to “midi learn aaaaaaal the controls” is NICE !
PS: just curious of one thing… is the “driver” really a driver or it’s an other thing ? As I understand, if a plugged device is recognized, it as a Linux driver somehow.
1 Like
It’s not a kernel driver but a simple python file that implements a class. Easy!
1 Like
I meant Alesis V25. Not many knobs here.
But your new toy might be perfect for my Arturia Keylab Mk II
1 Like
I’ve just found this. Looks like a great way to do a different implementation of the V5 control set.
I’ve got a bunch of mechanical keyswitches, and have used addresseable RGB LEDs a lot. I also have several RGB midi keypads.
So my only real question is how would we get the button LED states out of the Pi and into a midi controller?
2 Likes
Using MIDI messages, obviously 
You can implement as you like, or perhaps adhere to MCU protocol.
For instance, my launchpad uses MIDI notes for most buttons: when the button is pushed, a note-on is send from the controller. When button is released, a note-off. The LED state for the button is send from the “host” using a note-on (same note). In this case, the velocity encode the color/bright info.
CC messages can be used in a very similar way.
Alternately, you could use SysEx.
MCU uses a combination of everything. For instance, fader state for each channel is sent with pitch bend messages, what gives 14 bits of precision instead of the 7 you get with a single CC message.
Regards
1 Like