-
Notifications
You must be signed in to change notification settings - Fork 1
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
Please do not translate JACK port names, use pretty-name JACK metadatas ! #12
Comments
Hi, I've introduced a quick change such that the port name at least is not translated. It's the following problem: this software is made with RTMidi, and that library doesn't give access to the JACK client. If JACK has to be better supported, it would really require a separate implementation from that of RTMidi. Note also, for communicating sys-ex messages, these can be sometimes very large. |
Ok thanks. of course the group name should also not be translated. I understand the problematic for the different groups. |
Hello !
I just saw at Houston4444/RaySession#112 (comment) that this program translate the JACK port names. The problem is that session managers (or simple shell scripts) will memorize JACK connections with their port names. Translate port names means that sessions shared between strangers are broken.
Instead you can use JACK pretty-name metadata https://jackaudio.org/metadata/ .
I also wonder why the two MIDI ports aren't in the same group.
and not simply:
Cheers
Mathieu
The text was updated successfully, but these errors were encountered: