Closed MattPutnam closed 10 years ago
I ran into this issue in my application too. Did you find any workaround?
Not yet. It's pretty low priority, apparently it's common on Mac OS for applications that connect to a MIDI or audio device to be very picky about the order in which you plug them in and start the application. I worked with someone recently who was running MainStage, and for her, you couldn't have the interface plugged in when you started MainStage.
After further investigation this issue is too far beyond reasonable to fix. It's something very fundamental in the Java library, possibly in native code. Even using reflection to blast out caches from every object available hasn't fixed this.
Closing this issue as "won't fix". Considering migrating the whole application to C++ with JUCE or Qt.
I recently ran into the same problem, and there is now a library that correctly supports hot-plugging MIDI devices in Java on macOS: https://github.com/DerekCook/CoreMidi4J
The Mac OS X Java implementation has a bug that prevents refreshing the list of MIDI devices. Research ways to get around this.