Forward Midi events to a redis and an OSC server.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sam fe6a56efaa Bugfixs 2 months ago
libs Bugfixs 2 months ago
.gitignore Third commit 8 months ago first commit 8 months ago Redis publish bugfix 2 months ago
miredis.json Doc update 2 months ago Redis publish bugfix 2 months ago

Forward Midi events to redis/OSC

Miredis hooks to all midi devices connected and listen for events. Miredis can optionnaly hook to opensourced Link protocol (200+ music & videos apps) -> “/beat” & “/bpm” All events are forwarded to a redis server and an OSC server.


Run (not with python 3.9)


See options :

python3 -h

To enable Link :

python3 -link

New Features

  • Added verbose mode -v
  • Added redis subscribe events
  • Added Clitools program selection mode for Launchpads
  • Added custom redis ‘key event’, to be more semantic/hardware agnostic with Configuration file : miredis.json. i.e “/feedback/1/114/value” is generated each time a CC message on channel 1, CC 114 is recevied.


/midi/noteon midichannel note velocity

/midi/noteoff midichannel note

/midi/cc midichannel ccnumber value




/beat beatnumber

/bpm bpm

/Your custom (see configuration file). Ex : /feedback midichannel ccnumber value

Redis keys

”/midi/noteon/midichannel” value : “note/velocity”

”/midi/noteoff/midichannel” value : “note”

”/midi/cc/midichannel/ccnumber” value : “ccvalue”

”/beat” value : “beatnumber”

”/bpm” value : “currentbpm”

custom ones

Redis : midi events published to “/midi/last_event”




customs one like “/feedback/1/114/value”