Sven GregoriThanks to the folks at http://pid.codes/, 4chord MIDI has now its own unique USB vendor/product ID pair! In practice this means that one could add a udev rule specific to 4chord MIDI, and for example automatically execute a shell script whenever a device gets plugged in, which could then start fluidsynth and automatically connect it via aconnect. Or start jackd and a2jmidid to get Ardour ready for MIDI recording.
Well, I guess those two example udev rules just made it on my TODO list..
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
Thanks for sharing this! USB VID/PID is a gotcha for many Open Source Hardware projects, so it is great that you've explained how to get one.
Are you sure? yes | no
Some more background on it is in the Hackaday article I heard about pid.codes in the first place: http://hackaday.com/2015/04/03/usb-pids-for-all/
If one is familiar with git workflow, it's really straightforward if you follow their instructions. They are quite strict on the licensing part - if you don't put an open source license file into your project directory, you won't get lucky, which I think is a good thing (despite me learning that the hard way).
Also worth noting is that this is some volunteer side project and not operated like a business, so pull requests might take some time (weeks even) until they get handled.
Are you sure? yes | no
Wasn't even kidding, at least the fluidsynth udev rule example is now in the Github repository, including a little installation script: https://github.com/sgreg/4chord-midi/tree/master/sys/udev
Are you sure? yes | no