[Bug] maweb dot2 some Button exectuors don't output any values

[joshuabloemer]

When mapping the following dot2 onPc button executors with midimonster no values are sent.
(B-wing 1)
508 to 501
608 to 601
708 to 701
808 to 801

(B-wing 2)
616 to 609
716 to 709
816 to 809

all other executors seem to be working

Below is my config

[maweb ma]
; That's the IP of your console or OnPC.
host = 127.0.0.1 80

; If a Dot2 is used, the username is automatically set to "remote".
;user = midimonster
;password = midimonster

[lua debug]
script = print.lua
default-handler = printchannel

[map]
ma.page1.button601 > debug.1

[Spacelord09]

Hi @joshuabloemer,
can you please try if this section in our documentation fixes the issue?:
When requesting button executor events on the fader pages (execs 101 to 222) of a dot2 console, map at least one fader control from the 0 - 22 range or input will not work due to strange limitations in the MA Web API.

[joshuabloemer]

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

[joshuabloemer]

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 be the complete range but either increasing the start value to 601 or decreasing the end value to 800 does not work
I have no idea what's going on there but I guess mapping everything to an empty lua instance if something doesn't work could be a workaround if it's not too performance heavy

[maweb ma]
; That's the IP of your console or OnPC.
host = 127.0.0.1 80

; If a Dot2 is used, the username is automatically set to "remote".
;user = midimonster
;password = midimonster

[lua debug]
script = print.lua
default-handler = printchannel

[map]
ma.page1.button815 > debug.1
ma.page1.button{600..801} > debug.2

[joshuabloemer]

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

[joshuabloemer]

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 order to receive any values.
Minimal setup to reproduce on Dot2 onPC:

1. Create a new empty show
2. Set up the webremote
3. Create an empty fader on executor 1
4. Use the following config

[maweb ma]
host = 127.0.0.1 80

[lua debug]
script = print.lua
default-handler = printchannel

[map]
    ma.page1.fader1 > debug.1
    ; uncomment any line below
    ; ma.page1.fader3 > debug.1
    ; ma.page1.button80 > debug.2
    

[joshuabloemer]

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 2 or more faders on page 2 and page 1 are mapped all of those start outputting values.

This mapping works

[map]
    ma.page1.fader{1..4} > debug.1
    ma.page2.fader{1..2} > debug.1

But this doesn't

[map]
    ma.page1.fader{1..4} > debug.1
    ma.page2.fader1 > debug.1

[joshuabloemer]

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 mapping to page 2 doesn't change anyting.

[joshuabloemer]

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

[joshuabloemer]

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 does so regardless if it's mapped from or to dot2

[joshuabloemer]

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

[joshuabloemer]

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 to see what's going on

[cbdevnet]

Hi @joshuabloemer, thanks for your interest and effort in investigating this!

I'll try to look into this on the Weekend and will get back to you as soon as I have some ideas :)

[joshuabloemer]

I've managed to get a working setup for my requirements by moving everything to page 2. That still doesn't solve the issues but faders 1 to 9 are working on page 1 now, but none of the buttons