2011-11-07 18:43:54 +02:00
|
|
|
midi2osc register itself as a writeable MIDI device. It then forwards
|
|
|
|
|
the MIDI messages it receives to the specified OSC destination.
|
|
|
|
|
|
2011-11-08 08:52:02 +02:00
|
|
|
Build prerequisites:
|
|
|
|
|
|
|
|
|
|
libasound(-dev) (ALSA)
|
|
|
|
|
liblo(-dev) (OSC)
|
|
|
|
|
|
|
|
|
|
Compilation:
|
|
|
|
|
|
|
|
|
|
make
|
|
|
|
|
|
2011-11-07 18:43:54 +02:00
|
|
|
To use it with the Milkymist One,
|
|
|
|
|
|
|
|
|
|
- enable Ethernet on the M1
|
|
|
|
|
- ./midi2osc IP-address-or-host-name
|
|
|
|
|
- launch qjackctl
|
|
|
|
|
- click on the Connect button in qjackctl
|
|
|
|
|
- in the "Connections" window, drag a connection from each MIDI device
|
|
|
|
|
you want to connect to midi2osc
|
|
|
|
|
- MIDI events will now show up in the MIDI settings dialog, etc.
|
2011-11-24 07:51:10 +02:00
|
|
|
|
|
|
|
|
midi2osc can also remap MIDI controls. The syntax is
|
|
|
|
|
|
|
|
|
|
c<chan>[.<control>]=c<chan>[.<control>]
|
|
|
|
|
|
|
|
|
|
where <chan> is a channel number and <control> is the optional control
|
|
|
|
|
number. For example,
|
|
|
|
|
|
|
|
|
|
./midi2osc c8.1=c0.1 c8.2=c0.2 c9.1=c0.3 c9.2=c0.4 c0.7=c0.5 c7.7=c0.6 m1
|
|
|
|
|
|
|
|
|
|
would map the joysticks and two faders of a Faderfox LV3 to the
|
|
|
|
|
controls 1 through 6 on channel 0, and send the OSC messages to
|
|
|
|
|
a host called "m1".
|
