@jofemodo There is a pending PR to use the Jack properties to set the port alias, it would be very interesting to have for remote device drivers…
I just merged your PR with the changes to jack connect for UMP.
Regarding the other “bigger” PR … please, split into 2 PRs. One with the ctrldev driver changes and another one with your git management proposal. The last one is quite critic and needs extra verification.
Thanks a lot!
Sorry for the confusion, I’ll fix the PR asap. And thanks for merging the other one!
BTW, the jacknetumpd version is also updated.
Regards,
Ready! This is the new PR:
Many thanks!
Ohhh yes! It’s merged now!
Thanks @oscaracena !
Regarding UMP client integration, it would be nice to have the list of available “UMP devices” in the MIDI-OUT menu, like any other MIDI destiny. Same for MIDI-IN.
I mean, when a zynthian device has UMP enabled, everything should be transparent and easy.
The zynthian device see other UMP devices and can route MIDI to/from them. The zynthian device is seem by other UMP devices that can send/receive MIDI to/from it.
How do you see all this? I’m totally new to UMP and i don’t know what is the “spirit” behind, but it feels like it should be easy and straightforward. Indeed, it would be nice if each zynthian could “export” its chains and see other zynthian’s chains. Dreaming?
Regards,
I would expect UMP to present similar to USB MIDI due to its dynamic (hot plug) nature.
I have a Dev branch that allows zynthian to see other zynthians’ audio via AoIP and would expect UMP to be similar for MIDI. I haven’t had time to look at UMP yet.
I know this thread is regarding netUMP, but thought it may be worth mentioning that i don’t think USB MIDI UMP for Midi 2.0 is enabled by default in the Raspberry PI OS kernel.
I don’t know if jack gets around this or not.
I rolled my own kernel to have a play, but frankly gave up when I couldnt get my Keystage to be recognised as a midi 2.0 device (although after doing a bit of research I don’t think it will at the moment)