Re: Greyed out/duplicated MIDI devices in Audio/MIDI setup?
Re: Greyed out/duplicated MIDI devices in Audio/MIDI setup?
- Subject: Re: Greyed out/duplicated MIDI devices in Audio/MIDI setup?
- From: Doug Wyatt <email@hidden>
- Date: Fri, 10 Aug 2007 00:25:31 -0700
Yes I'm listening (tonight)... But please write a bug at
bugreporter.apple.com. I read and delete hundreds of emails a day
while Radar is forever, as they say.
Thanks
~Doug
On Aug 9, 2007, at 1:55 PM, Herbie Robinson <hrob@curbside-
recording.com> wrote:
At 10:29 AM -0700 8/9/07, Jason Staczek wrote:
I don't think there's a separate Core MIDI list, so I'll try this
here.
On every Mac I have MIDI devices attached to (seen on at least 3 of
mine, reported by others), about 50% of the time after restarting the
machine, Audio/MIDI setup "grays out" the original MIDI device and
shows an enabled device instead called "<device name> 2". Doesn't
seem
to be any rhyme or reason, and the original device is, of course,
still connected as it was.
Is this a well-known issue? Any pointers on how Audio/MIDI setup does
it's scanning at startup to help prevent this? If you happen to
have a
big device with lots of connections, it's extremely tedious to have
to
re-make all those connections on device #2. And of course, once you
do, on the next restart, you're just as likely to have device #2
greyed out and the original one enabled back in its place.
Any insight would be much appreciated.
There may be other reasons, but the usual reason this happens is
because the driver is unable to recognize that the device hasn't
changed. It is actually the responsibility of the MIDI driver to
correlate the currently configured hardware with the current MIDI
setup. Note that the only reliable way to do this with a USB or
Firewire device is to put some sort of UID into the hardware and
also keep it with the MIDI device entry. If the device in question
doesn't have any machine readable serial number and doesn't have
EEPROM that the host can put a UID into, then the only way one can
ID the same device is from the topology (for USB, the OS gives the
driver a magic number derived from the topology, but that can change
when seemingly unrelated hardware changes and when one loads new
versions of the OS). You would think they could sort it out if the
machine only has one device of a particular type and there was only
one device of that type in the MIDI config, but apparently some of
the driver writers don't think about the most common case.
I had this problem happening with an 8 port MOTU interface (which
does have an EEPROM). I eventually figured out that the EEPROM
config wasn't working at all; so, I guessed it was related to the
cheap chip sockets they were using. Sure enough, re-seating
(carefully !!!) all the socketed chips (didn't know which one was
the EEPROM) cured problem.
At 10:36 AM -0700 8/9/07, Richard Burnett wrote:
What I have been meaning to do ( and haven't had a chance) is to
create a utility that will analyze the XML file that has the MIDI
setup in it and pull those settings off of one and put them onto
the other. I did this by hand once as proof of concept, and it
works, I just haven't gotten around to writing code for it.
I'd love to not have to do this anymore myself though.
That would seem like a really good thing for AMS to do. Maybe by
dragging one device on top of the other. This would be useful if
one bought a new interface, too. Doug, are you listening?
--
-*****************************************
** 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:
40apple.com
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