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: "Boyd Timothy" <email@hidden>
- Date: Fri, 19 Oct 2007 13:55:35 -0600
On 10/18/07, Kurt Revis <email@hidden> wrote:
> 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?
>
Well, since it seems like I'm sending the codes properly but it's not
reacting to them. My brain started wondering? :)
> 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.
If I unplug the POD, no input/output sources are shown from the API
calls returning the count. If I plug it in, there's only one. So
even though this code would definitely not be releasable in a product,
I assume it should be talking to the right output destination.
> > 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()).
Strange that MyReadProc() never gets called. I noticed in the MIDI
Monitor code that the CFRunLoopRun () is called in a separate thread.
I assume this is so the messages sent by other MIDI devices can be
read at any point in time. I tried modifying my code to set it up
similarly. Unfortunately, I still don't get anything, though that
might be because I didn't do all the same port stuff that the MIDI
Monitor code does for the run loop.
> 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.
Ah, okay.
I'm quickly realizing that without further documentation/information
from Line 6 about the POD X3, I'm probably not going to make progress.
So, I'll give my best shot at contacting them for some more info.
Wish me luck!
Boyd
_______________________________________________
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