OK, I’ve found out what was confusing me. With the latest Oram update (now I get a nice pic on the boot screen) and Akai MPK mini MK3 1.26, when I push pad 3 in mixer mode the MPK is put back into MPC mode and I have to go back into MIDI In/MPK mini3/Controller driver and reselect Controller driver. This doesn’t seem correct as it would be a pain in a live performance to get put back into MPC mode. Also Controller driver selection does not seem to be saved in snapshot.
The Akai MPK mini3 driver is not longer auto-loaded by default as it causes confusion to users wanting to use the keyboard “normally” (no UI control), just for playing and MIDI learning. Users wanting “normal” behavior don’t even know about the existence of controller drivers for their devices, so they get confused and obviously they think there is something wrong. In the other hand, users wanting “UI-control” know about the drivers and how to load. So, for devices used “normally” by most users, driver autoloading could be disabled. Drivers have an internal flag for autoloading, so please don’t assume ALL drivers will be auto-loaded by default.
Anyway, the controller drivers state (enable/disable) should be saved in snapshot. I just tested and it works for me with my AkaiMPKmini3. Could you re-check, please?
Regarding the other issue:
when I push pad 3 in mixer mode the MPK is put back into MPC mode
I couldn’t say. Perhaps it’s a bug in the driver. Could you reproduce this behaviour?
Thanks
1 Like
OK. I was fully updated but I don’t remember from which image. Quite possible it was a old image. Lesson learned. Pad 1 now takes me to MPC mode but I can get back to the driver MIXER mode via pad 5. Restoring snapshot establishes correct state. All seems good.
Thanks,
Harry
1 Like
@oscaracena, this is for you 
In fact sometimes I can get back to MPK mixer, sometimes I can’t…
Just document the hardware/software:
Raspberry Pi 5 Model B Rev 1.0
Audio: Behringer UCA222
Display: WaveShare 7 HDMI+USB 1024x600
Wiring: DUMMIES
I2C: Not detected
Profile:
2024-09-23-zynthianos-bookworm-aarch64-oram-2409.img.xz
zyncoder: oram (71de6d2)
zynthian-ui: oram (18349e3)
zynthian-sys: oram (1e45187)
zynthian-data: oram (6fa0db4)
zynthian-webconf: oram (640087f)
Akai MPK mini MK3 1.26
I’ll check what’s happening, as soon as I have the spare time! 
1 Like
I just loaded oram up on a Pi 5, I couldn’t get it to boot with the MPK Mini mk3 plugged in, it plays notes if i plug it in after boot but no control surface, I presume that loads during boot.
I managed to find this error in the UI log
Nov 16 21:43:55 zynthian startx[2031]: jack server is not running or cannot be started
Nov 16 21:43:55 zynthian startx[2031]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Nov 16 21:43:55 zynthian startx[2031]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Nov 16 21:43:55 zynthian startx[2031]: ZynMidiRouter: Error connecting with jack server.
Nov 16 21:43:55 zynthian startx[2031]: ERROR:zynthian_gui_config.: lib_zyncore: Failed to initialise zynmidirouter (2)
Nov 16 21:43:55 zynthian startx[928]: *******************
Nov 16 21:43:55 zynthian startx[928]: EXIT STATUS => 202
Nov 16 21:43:55 zynthian startx[928]: *******************
Ran an update, didn’t fix it
I noticed that the midi sync also wasn’t reaching the MPK, dont know if this is related to needing to plug it in after boot, I assume as much
Maybe your jack configuration is wrong. Please post it here from webconf HARDWARE ->Audio.
Interesting.
I also get this error on my Pi4 based Zynthian if it’s booted while my midi controller is switched on.
If I boot the Zynthian while the controller is switched off and turn it on afterwards it works fine.
This is with both a USB sound card and a USB controller. (An M-Vave SMK-25 II)
Please provide your jack options. It is likely a bad config.
-P 70 -s -S -d alsa -d hw:0 -r 48000 -p 256 -n 2 -X raw
Yes, the problem is hw:0 which is trying to use the first hardware card, finding the USB MIDI and failing. You need to change this to the name of your soundcard as shown in aplay -l.
2 Likes
Thank you.
Oh weird. aplay -L lists the USB MIDI controller as the default audio card despite it not having any audio support at all.
Audio & MIDI are regarded as similar beasts from the perspective of ALSA.
For some time my MPK mini 3 has not worked as intended. The driver is not automatically enabled, end it also disables itself often. And when enabled no all features are working. That is the low row of pads shifts between mixer, zynpad, tempo, subsnaps. But after between 1-10 pad presses, the driver disables. The top row of pads are simply not working as intended, at least not now. But as i remember they were working occasionally a month ago. (been a long time since i last fiddled with the MPK mini).
Im now running Oram staple 2502, but this was also the case when running Vangelis and staging before the release of the last stable. Thankfully receiving any directions how to get this working again.
Was very happy and had just begun learning to really use these features before they got unstable (in december last year i guess)
EDIT: i have the V5.1 kit. Running overclocked with a Tascam US 16x08 audio module
It may be a problem with an internal API change that need fixing. Could you submit an issue to the tracker, so I can have a look?
I will try, thanks. But it will be my first so bare with me 
1 Like
Then it is submitted. Hopefully not to unclear
2 Likes