RE: User presentation of device names in Jaguar
RE: User presentation of device names in Jaguar
- Subject: RE: User presentation of device names in Jaguar
- From: "Cianflone, Chris" <email@hidden>
- Date: Wed, 14 May 2003 17:00:57 -0500
Darn 8K limit. Sending again with some stuff from the end deleted.
>
----------
>
From: Cianflone, Chris
>
Sent: Wednesday, May 14, 2003 4:57 PM
>
To: Cianflone, Chris; 'Pete Yandell'; email@hidden
>
Subject: RE: User presentation of device names in Jaguar
>
>
Busy weekend (and week) so sorry for the delay in responding...
>
>
<<What if there is more than one device connected to a port and I
>
move
>
one of the attached devices to another port?>>
>
>
Perhaps the external devices should be listed separately? This seems to
>
be how FreeMIDI and OMS did it (of course the user would need to know that
>
MIDI channel collision could occur in that case, i.e. I picked one device
>
but 2 devices are playing back). Would someone from Apple (Doug?) care to
>
comment on this and other issues brought up here. Here is the original
>
question:
>
>
Which UniqueID should I be saving for the selection of an endpoint, the
>
one given by the kMIDIPropertyUniqueID of the original MIDIEndpointRef, or
>
the one given by kMIDIPropertyConnectionUniqueID of the external device?
>
>
I am willing to do it the way Pete Y. has mentioned, but it does seem
>
somewhat wrong in comparison with what I would expect from past MIDI
>
systems on the Mac. It seems that something as simple as replacing one
>
MIDI interface with another (not the external devices attached to them)
>
would be enough to really make the kMIDIPropertyUniqueID method useless.
>
So I am really looking for some advice from Apple.
>
>
Thanks,
>
>
Chris Cianflone
>
Software Engineer
>
MakeMusic!, Inc.
>
>
----------
>
From: Pete Yandell
>
Sent: Friday, May 2, 2003 7:38 PM
>
To: Cianflone, Chris
>
Cc: email@hidden
>
Subject: Re: User presentation of device names in Jaguar
>
>
Putting on my devil's advocate hat:
>
>
What if there is more than one device connected to a port and I move
>
>
one of the attached devices to another port?
>
>
What if I unplug a device altogether? Does the program then revert
>
back
>
to tracking things by endpoint? Will I be confused by the way the
>
program seems to track by external device at some times and endpoint
>
at
>
others?
>
>
>
In the end I've decided to track by endpoint rather than by external
>
>
device in all my software simply because I think the complexity of
>
implementing tracking by external device is too high to justify the
>
implementation. Changing the arrangement of their MIDI setup is
>
something that most users do very rarely.
>
>
Of course simply storing unique IDs is not enough in either case, as
>
>
per lengthy previous discussions on this list. :)
>
>
>
On Friday, May 2, 2003, at 05:05 AM, Cianflone, Chris wrote:
>
>
> Thanks! I somehow missed that docu. However, this raises some
>
> questions:
>
>
>
> Which UniqueID should I be saving for the selection of an
>
endpoint,
>
> the one
>
> given by the kMIDIPropertyUniqueID of the original
>
MIDIEndpointRef, or
>
> the
>
> one given by kMIDIPropertyConnectionUniqueID of the external
>
device?
>
> Here
>
> is an example to hopefully make this clear:
>
>
>
> Suppose I have the following setup:
>
>
>
> A "FastLane USB" MIDI interface, and then I create an external
>
device
>
> on
>
> this called "JV-1000". Before I instituted the code below for
>
"Display
>
> of
>
> endpoint names" I would get the following names I choices in our
>
app:
>
> "Port
>
> A" and "Port B", and yes, I could have "fixed" this to show
>
"FastLane
>
> USB
>
> Port A" and "FastLane USB Port B".
>
>
>
> Now, I replace my interface with another one I have, a "Super
>
MPU64"
>
> and
>
> plug in the "JV-1000" to it. Now, if I am storing the UniqueID
>
given
>
> by
>
> kMIDIPropertyUniqueID, presumably my "JV-1000" would not be found,
>
>
> because
>
> what I was really storing was the UniqueID of "FastLane USB Port
>
A".
>
> But if
>
> I store the one given by kMIDIPropertyConnectionUniqueID, it would
>
be
>
> found?
>
> Do I assume I store the later (which is of course complicated by
>
the
>
> fact
>
> that there could be several IDs given by
>
> kMIDIPropertyConnectionUniqueID)?
>
> But are we supposed to be storing these UniqueIDs? Everything I
>
have
>
> ever
>
> read has talked about saving kMIDIPropertyUniqueID.
>
>
>
> By the way: Could we please get back a "Test Studio" feature in
>
Audio
>
> MIDI
>
> Setup? I hope no one has a problem with copying good features
>
from the
>
> applications OMS Setup and FreeMIDI Setup :)
>
>
>
> Thanks,
>
> Chris
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.