Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux Midi port names #41

Closed
ngradwohl opened this issue Apr 17, 2017 · 4 comments
Closed

Linux Midi port names #41

ngradwohl opened this issue Apr 17, 2017 · 4 comments

Comments

@ngradwohl
Copy link

On a linux system the alsa midi port names are prefixed by the device name and conain a ":", which is not allowed by the regex in OscInProcessor::ProcessMessage
it works when the regex gets changed to

regex addressRegex("/(([[:alnum:]]|\\:|\\s|\\*)+)/(([[:alnum:]]|_)+)");

@llloret
Copy link
Owner

llloret commented Apr 17, 2017

Hi, thanks for reporting. I'm not sure what the problem is exactly, since things seem to work on Linux. Can you provide some more info, and I'll have a look?

Thank you again.

The project is very young still, so having people like you using it and reporting problems is really great!

@ngradwohl
Copy link
Author

on a linux system using alsa 'o2m -l" reports the midi port names in the format ": '

for example on my box my launchpad mini gets reported as

...
(23): Launchpad Mini: Launchpad Mini MIDI 1
... 

so when I send a note on osc message using sonic pi it works if I send it to all devices with
/*/note_off
But since I have a lot of midi devices connected to my box I want to send the messages to a specific port. Unfortunately this results in a osc message like
"/Launchpad Mini: Launchpad Mini MIDI 1/note_on"
which results in an address unknown error because the regex rejects the ":"

so it can be fixed by adding \\: to the addressRegex in OscInProcessor like shown above

@llloret
Copy link
Owner

llloret commented Apr 19, 2017

Hi, @ngradwohl, I have committed your proposed fix to master. Can you confirm that master works ok for you now?

Thanks,
Luis

@ngradwohl
Copy link
Author

Hi, yes works - thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants