keith/mustang-midi-bridge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update status

Browse source
This commit is contained in:
hirsch 2016-09-03 13:01:40 -04:00
parent b851dc3a10
commit 956a2a489b
1 changed files with 15 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

30
README.md
View file

@ -18,14 +18,11 @@ The command line parameter for MIDI controller port is now assumed to
start at 0 rather than 1 in order to match the way Linux ALSA start at 0 rather than 1 in order to match the way Linux ALSA
enumerates devices (see 'Run' below). enumerates devices (see 'Run' below).
I have added the first version of a runtime framework that starts and I have added a runtime framework that starts and stops the program
stops the program automatically based on attached MIDI devices. This automatically based on attached MIDI devices. There is a small amount
seems to be working on a Beaglebone SBC, but has not been extensively of customization required to account for your specific amp model and
tested or documented yet. There is a small amount of customization MIDI controller interface. Please see below (for experts) or the
required to account for your specific amp model and MIDI controller Install Wiki page (link below) for complete step-by-step details.
interface. Technically oriented users can probably work this out,
otherwise wait a bit until I can refine the packaging and arrange to
have the various pieces configured from a common setup file.
Support added for amp and effects models specific to the Mustang v2 Support added for amp and effects models specific to the Mustang v2
products. products.
@ -40,8 +37,8 @@ to the 'v2' series.
I am developing on a Ubuntu Precise desktop machine, but the code is I am developing on a Ubuntu Precise desktop machine, but the code is
routinely tested on a Raspberry Pi 'B' and Beagelbone Green to ensure routinely tested on a Raspberry Pi 'B' and Beagelbone Green to ensure
these remain viable deployment targets. At this point I'm still these remain viable deployment targets. I have had just enough issues
experiencing issues with USB latency on the RPi and am currently with USB on the RPi to make me leary of that platform and am
recommending the BBG for real-world use. recommending the BBG for real-world use.
Special thanks to: Special thanks to:
@ -62,10 +59,10 @@ I have written a Wiki page here:
https://github.com/snhirsch/mustang-midi-bridge/wiki/Install https://github.com/snhirsch/mustang-midi-bridge/wiki/Install
that attempts to walk less technical users through the installation that attempts a detailed walk-through of the installation and build
and build process on Raspberry Pi or Beaglebone. It's hard to know process on Raspberry Pi or Beaglebone. It's hard to know what level
what level of detail to hit and suggestions or comments would be of detail to hit and suggestions or comments would be appreciated if
appreciated if I've omitted or glossed over something critical. I've omitted or glossed over something critical.
# Status # Status
@ -136,12 +133,15 @@ Would appreciate feedback on requirements for other distributions.
# Build # Build
``` ```
$ make $ make
or
$ make CPPFLAGS=-DRTMIDI_2_0 (for older librtmidi)
``` ```
# Configure # Configure
1. Update ```60-midi.rules``` with the USB VID (vendor id) and PID 1. Update ```60-midi.rules``` with the USB VID (vendor id) and PID
(product id) of your controller. (product id) of your controller. Must be on both lines, although the
attribute names are different.
2. Edit ```mustang_bridge_start``` to set values marked as user 2. Edit ```mustang_bridge_start``` to set values marked as user
edits. In addition to setting the VID and PID, you need to specify edits. In addition to setting the VID and PID, you need to specify