[lavabiopsy]

Which problem are you referring to? a2jmidi should work fine as long as you have access to the device. But in any case that should not be necessary anymore if you use pipewire, which should be able to manage all the devices at once.

[sasaf5]

The problem was that extra a2jmidi hoop adding a lot of friction to my creative process. Also I wanted to keep it on indefinitely to use it as an instrument, and a2jmidi would crash after a few days.

Also there was the night spent recompiling the right version of bison in the middle of Qsampler's dependency hell, so that I could have a piano sound. That was all in 2017.

[lavabiopsy]

I'm not sure what you mean extra hoop? You just start a2jmidi and then connect the device. Crashes would indeed be an issue, generally if you want to mitigate those, you would want to:

- Auto restart any important services (with systemd or similar)

- Use JACK/Pipewire session management

- Report the crash to the developers (of a2jmidi in this case, but it could be anything)

I honestly have never used LinuxSampler so I can't comment on that, I believe they have some strange licensing thing going on.

[PaulDavisThe1st]

The extra hoop is having to start a2jmidi and have the ports not be as "integrated" into the JACK server ports as they could be.

By contrast, JACK1 contains a2jmidid as a builtin client, no extra work is needed. You just start JACK, all your MIDI devices are listed.

[lavabiopsy]

I have switched to Pipewire but last time I tried JACK2 there were tools that would auto-start a2jmidi for all available midi ports. This is trivial to do. If hotplug was a concern then someone could just write it to run based on udev triggers.