Re: Midisport and sysex
Re: Midisport and sysex
- Subject: Re: Midisport and sysex
- From: Herbie Robinson <email@hidden>
- Date: Tue, 21 Dec 2004 15:41:28 -0500
At 1:35 PM +0100 12/20/04, Peter Karlsson wrote:
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.
I found it necessary to sleep for several seconds after initializing
MIDI or else data got lost. It wasn't driver specific. The problem
is that the USB devices essentially initialize asynchronously and
often aren't there for a few seconds.
One of the reasons it would be better to leave the MIDI Server
running all the time....
--
-*****************************************
** http://www.curbside-recording.com/ **
******************************************
_______________________________________________
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