Repository navigation
Feature Request: M32R Button and Fader Bank Handling #49
Description
There are two M32R-specific areas that could be improved.
The first is the assign section. Since the M32R does not have the full assign section of the larger consoles and instead only provides eight assignable buttons, it might make sense to have an M32R-specific configuration page where only those eight buttons can be mapped and configured.
The second concerns fader bank selection. On the M32R, the left and right fader banks can normally be controlled independently, and combinations can be selected by pressing buttons on both sides, just like in the original firmware.
Currently, the right-side bank selection buttons (e.g. Matrix/Main) do not appear to function, which makes parts of the fader bank layout inaccessible. It would be great if the left and right sides could be controlled independently, matching the behavior of the original console.
Activity
schulz-alexander commentedon Jun 7, 2026
@niklasarnitz can you please have a look at this with your M32R?
schulz-alexander commentedon Jun 7, 2026
I created a new issue for that: #51
schulz-alexander commentedon Jun 8, 2026
@flipfi on the screen should update a debug line every time you press a key. When you send me a 'screenshot' per pressed key, I can make it work
schulz-alexander commentedon Jun 8, 2026
The boardid and value (and of course which button ;-) )
flipfi commentedon Jun 8, 2026
DCA:
BUS 1-8:
BUS 9-16:
MAIN/MATRIX:
(DAW)-REMOTE (There was already the idea of controlling one console from another. The DAW-Remote button could be used for this in the future: when pressed, it would start blinking to indicate that all controls and the display are currently operating the remote console.)
FADERFLIP:
schulz-alexander commentedon Jun 9, 2026
Thanks!
fixed button mapping for M32R on bus section
schulz-alexander commentedon Jun 9, 2026
Please test and report back. If you find more unmapped buttons or encoders, please also report back :-)
dcp_corefs_openx32_beta_2026-06-09.run.zip
flipfi commentedon Jun 9, 2026
Issue: M32R Buttons Not Working in Latest Build
The latest build 2026-06-09 appears to have broken several M32R buttons.
In previous builds, most buttons around the display were functional (except the monitor button). Now only Home and Mute Groups seem to work reliably, while the other screen-selection buttons no longer respond.
The new fader-layer mappings are also currently inaccessible.
schulz-alexander commentedon Jun 9, 2026
hm... let me investigate .. there must be some issue with my build ...
13 remaining items
schulz-alexander commentedon Jun 9, 2026
I think I found it. Your button values where in the pressed state. Additionally in our mapping we used the wrong board id.
New build is on its way...
schulz-alexander commentedon Jun 9, 2026
dcp_corefs_openx32_beta_2026-06-09--4.run.zip
schulz-alexander commentedon Jun 9, 2026
oh, I can confirm the issue with the Displaybuttons... oh no...
flipfi commentedon Jun 9, 2026
First of all, huge kudos for the patience and persistence in tracking this down and working through all these M32R-specific issues. It’s really appreciated.
Quick update: the new buttons are now working. The only exception is Fader Flip, but I assume that is simply not implemented yet.
However, the display-related buttons no longer work as they did in version 26.06.05_2. So while the new button mappings appear to be fixed, there seems to be a regression affecting the display button functionality.
schulz-alexander commentedon Jun 9, 2026
😎
that's not implemented :-)
found the issue, it's a bad if-statement
fixed: most of the display buttons didn't work
schulz-alexander commentedon Jun 9, 2026
dcp_corefs_openx32_beta_2026-06-09--5.run.zip
flipfi commentedon Jun 9, 2026
Fantastic, it’s working now! 🎉
Many thanks for taking the time to investigate and fix this.
schulz-alexander commentedon Jun 9, 2026
so that's your release :-) happy mixing and testing!
https://github.com/OpenMixerProject/OpenX32/releases/tag/beta-2026-06-09--5
flipfi commentedon Jun 9, 2026
I’ll likely have access to a full-size M32 for a short time and can take screenshots/photos of all button assignments if that would help with integration.
Is there a preferred format or table for documenting them? Also, do you need a complete mapping of every button, or mainly the bank-selection and display-related buttons? Just let me know what information would be most useful, and I’ll try to collect it while I have access to the console.
schulz-alexander commentedon Jun 9, 2026
that would be great!
the format is not critical, as long I have the button name, board id and value after you let the key go
for faders and encoders I need the index instead of the value
its best to test all buttons, but if you find a pattern you can describe that instead of writing down all the values
schulz-alexander commentedon Jun 9, 2026
I need all the buttons, faders and encoders
Leds are a bit more tricky, but thats not critical for now
fixed: M32R: wrong board and button values
fixed: most of the display buttons didn't work