Rebind incomming midi commands to other ones, mainly done to interpret SysEx messages from a GMAlighting
Go to file
Maximilien Rigaut 9178690b8b Adding all the repo files 2021-11-01 06:27:37 +01:00
.github/workflows Adding all the repo files 2021-11-01 06:27:37 +01:00
src Tweaking the pulseServer 2021-11-01 06:27:18 +01:00
tests Adding all the repo files 2021-11-01 06:27:37 +01:00
.gitignore Testing and slow move toward a standard architecture 2021-11-01 04:44:58 +01:00
.gitmodules Testing and slow move toward a standard architecture 2021-11-01 04:44:58 +01:00
LICENSE Initial commit 2019-04-20 14:47:00 +02:00
README.md Adding all the repo files 2021-11-01 06:27:37 +01:00
TODO.md Adding all the repo files 2021-11-01 06:27:37 +01:00
main.py Testing and slow move toward a standard architecture 2021-11-01 04:44:58 +01:00
pyproject.toml Adding all the repo files 2021-11-01 06:27:37 +01:00
requirements.txt Adding all the repo files 2021-11-01 06:27:37 +01:00
requirements_dev.txt Adding all the repo files 2021-11-01 06:27:37 +01:00
setup.cfg Adding all the repo files 2021-11-01 06:27:37 +01:00
test.py Testing and slow move toward a standard architecture 2021-11-01 04:44:58 +01:00
tox.ini Adding all the repo files 2021-11-01 06:27:37 +01:00

README.md

midiRebind

Was originally designed to get/send midi commands to a GrandMA but can be configured to bind any custom SysEx or midi (or whatever actually) message

To do so add a custom patch (or use a currently defined one, but chances are patches made for one SysEx won't work on another) and add a parser in the mapping directory

Depends

  • Mostly mido (pip install mido) for the midi binding and rtmidi (sudo apt install python-rtmidi)
  • test.py depends on the submodule minitest witch also depends on blessings (pip install blessings). test.py is not a core part of the program
  • This program is python3 dependant (on linux you must install the python3 dependencies instead (pip3 install mido and install python3-rtmidi))

Config Syntax

  • [interface] : All important information concerning the midi interface
    • input : Choose which Midi interface to listen to
    • output1 : Choose which Midi interface to output to; an arbitrary number can be specified that way
    • inputchanel : Which midi channel to listen to
    • outputchannel1 : Which midi channel to output to
    • mapping : The python file in mapping to setup all the mapping between input and output
  • [set/1] patch the first layer of set commands, what is defined as the first layer is in the mapping file
    • Basic usage : incomming note = interface/commandtype/note/intensity
    • Exemples:
      • 5-50 = 1/cc/11 #Map the faders 5-50 to the control change 11-45 (Straight patch) on output 1
      • 57-67 = 1/cc/12-32 # Will map linearly 57 to 12; 58 to 14 etc on output 1
      • 56 = 2/note/152 #Map fader 56 to note 152 on output 2
    • Advanced usage: Can add logic to the notes. NB: they must be defined first
      • 56/cond = lambda x: x==50 # Function choosing conditions on the value to send
      • 57/toggle = 0/127: Toggle the val between 127 and 0 every time the note is received
      • 68/func = functionMappedInTheMappingInterface(note,intensity,parameters)