Please do not translate JACK port names, use pretty-name JACK metadatas !
Houston4444 opened this issue · comments
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.
Sortie Sysexxer:Sortie MIDI Sysexxer
Entrée Sysexxer:Entrée MIDI Sysexxer
and not simply:
Sysexxer:midi out
Sysexxer:midi in
Cheers
Mathieu
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.
Beside this, having 2 Midi ports is implemented by 2 jack clients in one app, it's why they're separated.
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.
The message possibly doesn't fit in a JACK midi buffer, and so ALSA is the preferrable option over JACK.
Ok thanks. of course the group name should also not be translated.
I understand the problematic for the different groups.
If I understand correctly, use ALSA through A2J isn't a good idea either.