Re: Using MIDISend/MIDISendSysex for Line 6 USB Device
Re: Using MIDISend/MIDISendSysex for Line 6 USB Device
- Subject: Re: Using MIDISend/MIDISendSysex for Line 6 USB Device
- From: Kurt Revis <email@hidden>
- Date: Thu, 18 Oct 2007 21:48:18 -0700
On Oct 18, 2007, at 5:27 PM, Boyd Timothy wrote:
I can see my MIDI messages showing up in MIDI
Monitor and they're not invalid anymore. But, for some reason, the
POD X3 isn't changing anything. So perhaps I need to send some sort
of SysEx message to let it know to "trust" the messages I'm sending
it?
I've never heard of any device that requires that. Where did you get
that idea?
Here's my main hacky file: http://pastebin.ca/741834
Are you sure you're sending to the correct output on your device?
You're just sending to the first available destination, which could
be anything.
One thing that hasn't made sense is how I would request information to
the POD and then read the data it sends back. Should that come from
my notify proc that I specify during MIDIClientCreate() ?
No, that's for notifications about setup changes, like devices being
plugged in or unplugged. You've already got code that receives MIDI
input (it's MyReadProc()).
MIDI is a pretty ancient protocol, and in general it doesn't provide
any method for bidirectional communication. CoreMIDI doesn't provide
anything to help you. If you want to have a "conversation" with a
device, it's entirely up to you to keep track of it, probably with
some kind of state machine.
--
Kurt Revis
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden