__       ___             
                             /\ \     /\_ \            
  ___ ___   __  __    ___ ___\ \ \____\//\ \      __   
/' __` __`\/\ \/\ \ /' __` __`\ \ '__`\ \ \ \   /'__`\ 
/\ \/\ \/\ \ \ \_\ \/\ \/\ \/\ \ \ \L\ \ \_\ \_/\  __/ 
\ \_\ \_\ \_\ \____/\ \_\ \_\ \_\ \_,__/ /\____\ \____\
 \/_/\/_/\/_/\/___/  \/_/\/_/\/_/\/___/  \/____/\/____/
                                                       
monome + midi
                                                  

A monome app that enables your monome to send midi messages to midi-enabled devices.

This monome app currently:

• Allows you to play midi notes starting at "low C", or the midi note 24, with a range of 56 notes, ending a midi note 80.
• Allows you to record a bank of 8 loops, and deactivate them at any time. (this will probably be configurable in the future).
• Allows you to specify monomes and midi devices that should should be targted in a configuration file.

I've also had some success using my chronome to control midi devices! If it uses libmonome, this app might work with it! :D

• libmonome
• lphread
• lyaml
• lcheck (for testing)

Still investigating the prefered build tools of the C-World, but as of now, I have a custom Makefile that blindly uses the dependencies listed above. This has only been tested for building in Arch Linux, so tread carefully :3

make
sudo make install

This will place mumble in /usr/bin, so be sure to include that in your $PATH. In the future, I hope to add a --prefix option so that users may be able to configure their build path.

You can configure mumble to use the monomes and midi devices you so desire by creating a ~/.mumble/config.yml file:

# in ~/.mumble/config.yml
monome_path: "osc.udp://127.0.0.1:12345/monome"
midi_device: "/dev/snd/midiC1D1"
managed: true

• monome_path is the url accessible path to your monome.
• midi_device is the file descriptor that points to your midi device. Virtual Midi devices may also be connected, which is paticularly useful if you're using mumble as a middle-man to connect to other MIDI-enabled software.
• managed specifies if the monome is controlled by mumble's features (currently looping and playing midi notes), or if the monome should be configured by a third party. If set to false, the monome will only send ON and OFF messages to the midi_device.

Mumble currently uses the super rad check library to keep itself afloat. Test coverage is still a bit shaky, but if you would like to run the tests, feel free to do so with the following command:

make test

• provide different key mappings (like different scales, etc)
• provide the ability to customize the midi muxer via a configuration file / potentially python bindings?
• provide more interesting midi controls like pitch bending / volume control, etc.
• configure, or tap-to-set the BPM.

Nothing beats testing on a real midi device, but if you're in a pinch, you can virutualize your midi setup by following the steps below. There are other ways to achieve this, but I've found that a combination of timidity and aconnect work pretty well!

# A way to virutalize MIDI ports
timidity -iA &
sudo modprobe snd-virmidi # you may need to reload this kernel module if you're on Arch Linux.

# Connecting Virtual MIDI ports to other MIDI-consumable services (like Hydrogen)
# aconnect <midi-through-port-address>:0 <timidity-forward-port-address>:0
aconnect 14:0 20:0
<edit mumble configuration to point to /dev/snd/midiC1D0 or something similar>