I'm pretty sure this is not related to 2431, which is about hot plugging.
For the record, our bug database suggests 2431 is fixed and will ship in a
future version of the driver. I don't have a date for when that might happen
and I can't distribute builds outside our normal release process.
This problem sounds to me more like 2535. I ended up squinting at a USB
analyzer trying to figure out why the USB data toggles were out of synch. Of
course, a MIDI driver has no control over USB data toggles; this seems to be
a firmware issue, though it only manifests on Mac OS X (which usually means
Mac OS X is correct and every other OS is ... ahem ... tolerant, to put it
diplomatically). I worked around it in the 8x8/s control panel by sending a
request, waiting for a response, and sending the request a second time if
necessary. The panel times out only if it gets no response the second time.
The panel only does this on launch when it is trying to find all the 8x8/s
devices; once found in this way, a device can be relied upon to work
correctly. I realize you are working with a 4x4, but the firmware is very
similar, so it would be worthwhile to attempt some variation on this idea.
circa 12/20/04 7:57 AM, "Peter Karlsson" <email@hidden> wrote:
> I have checked the archives and it seems like this is not an unknown bug.
>
> Pete, can you please tell me the status of issue #2431?
>
> BTW: My controller messages at startup did not work.
>> I'm having trouble with my MIDISport 4x4 and sysex.
>>
>> I have just found out that if I send a dump request message from my app:
>>
>> - Kurt Revis MIDI Monitor says that 6 bytes has been sent to port A, and it's
>> the complete request message.
>>
>> - MIDISPORT 4x4 is not receiving sysex (no red lamp is blinking) and my
>> synthesizer is not responding.
>>
>> This happens only after my app is just started. If I send the same sysex
>> request again, everything works and willl continue working. Until the next
>> time I start my app.
>>
>> I made a change in my app so it now sends out some controller messages after
>> startup, this seems to solve the problem (not 100% sure). So it seems that
>> the MIDISport driver is having trouble with some sysex status flag or
>> something. Can this be a driver problem in the MIDISport 4x4? The driver
>> version I'm using is 3.1 with latest OS X panther version.
--
Pete Gontier
http://www.m-audio.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
This email sent to email@hidden
