Skip to content

Mapping

Jump to bottom
Björn Kalkbrenner edited this page Jul 18, 2021 · 4 revisions

Rebellion mapping

install_name_tool -change @rpath/librebellion.dylib librebellion.dylib rebellion_host

chmod 755 ./rebellion_host

in the extracted folder where you find the 'rebellion_host' executable. If you have problems contact me. I'll fix the problems within the next alpha.

  • Check the configuration file if the device you want to use it the only device
  • Remove every log file in the rebellion folder (like print.log)
  • Open udf.lua and add the following to the end of the file:

niproto.CONST_ITEM = {}

  • Start the rebellion_host application
    1. On macOS: rebellion_host 2>&1|tee stdout.log
    2. On Windows: rebellion_host.exe >stdout.log
  • Press a button, pad, knob or rotate a knob

Understanding the output:

On the stdout you may see something like

Event: "BTN_DATA" Data: { "data": { "button": 7, "buttonid": 7, "state": "RELEASED", "stategroups": [ "7" ], "unk1": 82592736 }, "device": "MASCHINE_MK3", "id": 57888256, "name": "BTN_DATA", "self": {}, "serial": „…\u0000" }

Feedback

Please write down, what buttonid is printed on stdout when you press a button, pad or knob. It would be nice to have that whole block as information but it may be enough just to note something like:

  • Button over display 8: btnid 7
  • Button SHIFT: btnid 6
  • Knob1: btnid 79
  • Pad 1: padid 1
  • ...

The same data is visible (unparsed) in the print.log. Pressing a button may result in a line like: L> [INFO 15:21:20] niproto.lua:1870: BTN_DATA: 413733 -810041014 1 6 1

Where the last two numbers are buttonid and state (pressed or released).

It would be nice to have more information (if you can put the lines which appear when you press or rotate something into a form a human can read and understand with the additional information what was pressed) but I am happy to have some data to work with.

Also when reporting the mapping to me, please add the print.log, printdebug.log and also the redirected stdout.log to the mail.

LED mapping

Rotate the first knob (under the displays) counter clockwise (back), you should see some white led light jumping from pad/button to the previous pad/button. Rotate as long as no jumping occurs anymore and it will stop on one Button.

Write down the button name and then, carefully rotate clockwise to the next button/pad/led. Please write down what will light up next. You should have a list of elements then where you can rotate the knob forward and backwards.

The LED mapping may not work, maybe some additional debug messages are needed to get that work on your device - if it's not working as described please contact me.

Clone this wiki locally