Re: Midisport and sysex
Re: Midisport and sysex
- Subject: Re: Midisport and sysex
- From: Jeremy Sagan <email@hidden>
- Date: Tue, 21 Dec 2004 11:30:41 -0500
Peter,
I have a Roland UM-880, and also a MOTU MIDInterface that both work
perfectly for sending and receiving sysex. I had the same problem
several years ago with the 8x8 MIDISport and had to return it.
Jeremy
www.sagantech.biz
On Dec 21, 2004, at 9:13 AM, Peter Karlsson wrote:
Dear list!
A couple of month ago I sold my 2 Opcode Studio 4 midi interfaces
because
they could not be used with sysex in Mac OS X.
Now I have this MIDISport 4x4 and this will not work either. And I
can't
get my workaround to fix the sysex problem.
Open question to M-Audio. What is M-AUDIO going to do about it?
If M-Audio don't solve this I can't recommend the use of MIDISport as a
interface for my app.
I will sell this interface as soon as possible. I need some feedback
from
the users on this list. What midi interface is the best? Or maybe I
should
put it this way. Is there a interface that works?
Peter
Ursprungligt meddelande
MIDISPORT 8x8/s has an extra imaginary port pair which is dedicated to
configuring the device. None of the other MIDISPORT models support
this,
so
there is nothing I can tell you about communicating through them. You
will
need to find a harmless transaction you can perform with your
synthesizer.
This may persuade the interface (a MIDISPORT 4x4 in your case) to get
its
USB data toggles synchronized.
circa 12/20/04 11:54 AM, "Peter Karlsson" <email@hidden> wrote:
Hi Pete!
I suppose I have to workaround it, even if it's not the perfect
solution to
the problem. I think a firmware update to the MIDISport would be a
better
way, if possible. But I leave that for now.
Ok, when you say that you are sending a request to check if there is
any
8x8 there, do you mean that you send a sysex message to the
MIDISport?
If
so, how does the sysex message looks like and what do I get back from
the
MIDISport if it answers me?
Peter
Ursprungligt meddelande
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:
email@hidden
This email sent to email@hidden
--
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:
email@hidden
This email sent to 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