Hi @martin,
Could it be that in the latest FW (3.2) the MSB part of a NRPN is treated wrong? (in that a value of 127 becomes 0)? I seem to see that pattern
Cheers,
Joris
Hi @martin,
Could it be that in the latest FW (3.2) the MSB part of a NRPN is treated wrong? (in that a value of 127 becomes 0)? I seem to see that pattern
Cheers,
Joris
Nah, it was my own mistake
Ignore!