-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SnoizeMIDI: Minimal setup to capture messages #36
Comments
That looks reasonable. I see you've found the code in SysEx Librarian (SSEMIDIController) that does the same thing.
|
A Cocoa Mac app. I used the assistant to scaffold it and just added the MidiController class (printed above).
No I didn't! Added it to AppDelegate now ... but still no cigar.
Yes, it lists all endpoints (the same list that SysexLibrarian has at that point).
One more thing: When I pause at the end of MidiController.init, send some Midi and continue, the debugger halts at nonretainedDelegate parser:self didReadMessages:messages with EXC_BAD_ACCESS(code=EXC_I386_GPFLT). Thanks for your help! |
It sounds like your Is some other object keeping a strong reference to it? The If that isn't it, send me your whole Xcdoe project (email krevis@snoize.com) and I can take a look. |
That did the trick! Thanks for your help! |
Hi Kurt,
thanks for the SnoizeMIDI framework! Unfortunately there's not much documentation about its API.
I'm looking for the absolute minimal setup to capture midi messages on all available interfaces. IMHO it should be the code below, but it's not working. takeMIDImessages is never called.
Any help on this is greatly appreciated!
The text was updated successfully, but these errors were encountered: