Re: MIDI interface UniqueID changes depending on user
Re: MIDI interface UniqueID changes depending on user
- Subject: Re: MIDI interface UniqueID changes depending on user
- From: Doug Wyatt <email@hidden>
- Date: Wed, 22 Mar 2006 12:34:50 -0800
On Mar 21, 2006, at 14:00, Malcolm Haylock wrote:
Hi everyone,
I've run into a problem trying to store a reference to a MIDI
destination so that the connection can be restored between boots.
The program stores the UniqueID for the MIDI destination, which
works fine for a single user. However I've discovered that this
approach can not be used when a different user logs on as the
UniqueID for the MIDI destination changes. This occurs with two
MIDI interfaces so far tested: a MIDISPORT 1x1 and Edirol UM-1.
I thought the UniqueID was the way to store a reference to a MIDI
port. How else should I store the reference to the port?
There are a number of other properties associated with a given device
that you could latch onto (e.g. name, USB location [if any]) but
these are fragile in various ways. The unique ID was intended for this.
The underlying issue is that CoreMIDI's idea of the world is per-user
(and per-host, though you'd only see that in a network home diretory
situation). There is an enhancement request to allow shared user
state, which might not be as simple as we'd like; some properties
obviously can be shared (name, unique ID), others are clearly per-
user (e.g. the network driver's address book).
Doug
--
Doug Wyatt
Core Audio, Apple
_______________________________________________
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