Joshua Blömer

Faders 1-9 are already mapped but to a different Lua instance, I will try mapping them to the same instance

Mapping the faders did not work, however mapping buttons 600 to 801 (either to the same or a different instance) did work ... I don't know if it needs to...

Apparently this only works if buttons 508 to 501 are not mapped but does if buttons 408 to 401 are mapped instead, I think this needs some more testing

I don't know if I should create a new issue or not since it seems related: When mapping faders at least 2 faders or buttons have to be mapped in...

Mappings to page 2 also seem to contribute to that issue, if only one fader one page 2 is mapped no faders on page 1 or 2 output values, if...

Adding debug.1 > ma.page1.button{316..309} to the first config mentioned in my last comment breaks outputs from page two faders but still keeps outputs from page 1 faders. Adding the same...

Adding ma.page1.button{600..801} > debug.2 or ma.page1.button{600..801} < debug.2 also breaks page 2 faders and doesn't give any outputs from ma on the buttons mapped

The only useful piece of information I found so far is that it doesn't seems like it matters which direction the faders/buttons are mapped. If something breaks of fixes outputs...

It seems like mapping any button after button 100 on page one causes everything on any other page to not output anything

In the maweb backend source code the number 100 is mentioned a couple of times, might this have something to do with that? I don't really understand the code enough...