I have a Juce app that connects to usb hardware (Snyderphonics Manta) and converts activity on that into Midi which it outputs over a virtual midi out.
It was originally made with Juce 4 and the Juce 4 builds work fine.
I want to make a new version and I have been working on getting it going on Juce 5.
However the versions built with juce 5 although they run, have a problem connecting to the system alsa midi.
The output seems to be created, but it doesn’t show up in the qjackctl control panel for alsa midi, and Kmidimon can see it as an option but fails to connect to it.
when jack tries to connect to the midi output i see the following in qjackctl messages:
02:51:53.998 ALSA connection graph change.
02:51:53.999 JACK connection graph change.
Wed May 16 02:51:53 2018: ERROR: can’t subscribe to 130:0 - Operation not permitted
Wed May 16 02:51:53 2018: port deleted: MantaJuce3:midi/playback_1
I have tried this on two different machines with identical results, although both were running Mint 18.3 and the environment was very similar.
Other apps with virtual outs work correctly, as do my old builds of this app.
I have changed nothing at all in my Midi code, and very little so far in the rest of the app.
So - has something changed in Juce 5 that could cause this?
Everything is running as the same user, and I’m not aware of any permissions differences between the working apps and my failing one.
Is anyone else successfully creating a virtual midi out on linux using Juce 5?