Closed stubbulon5 closed 5 years ago
@danomatika what do you think? Shall I contact the owner of rtMidi library as it seems the issue might be a High Sierra one. Any opinions / ideas would be highly valued!
I don't have any time to look into this right now.
Asking RTMidi people could be good, although I would suggest testing RTMidi by itself first to see if the issue is there or with the ofxMidi wrapper for RTMidi.
Dan Wilcox danomatika.com robotcowboy.com
On Sep 27, 2018, at 12:12 PM, Stu notifications@github.com wrote:
@danomatika what do you think? Shall I contact the owner of rtMidi library as it seems the issue might be a High Sierra one. Any opinions / ideas would be highly valued!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Did you get this to work? I've not had any problems on my macOS 10.14 system.
Closing due to inactivity. Reopen if/when needed.
I ran into the same issue with OF 10.0 on macOS 10.12.
That specific issue only happens when I try to open the port by number
midiOut.openPort(0);
It works when when I run
midiOut.openVirtualPort("ofxMidiOut");
Hi there,
Thanks for a most excellent plugin. I've taken the sample usage code from midiOutputExample and it runs beautifully on Windows. However, the same code does not produce any sound on a mac (latester version of macOS). It gets hung up on
returns zero ports and when I attempt to
midiOut.openPort(0);
an error message is logged:Have you had any similar reports / experience? Your assistance is greatly appreciated!