MIDI device/entity/endpoint names
MIDI device/entity/endpoint names
- Subject: MIDI device/entity/endpoint names
- From: Doug Wyatt <email@hidden>
- Date: Tue, 13 Nov 2001 16:49:45 -0800
In looking at some MIDI apps and drivers that are starting to appear,
I've realized that there's a convention I'd like to see used, but hasn't
been documented beyond its use in sample code (if even there).
Driver writers should name things like this:
Manufacturer: MyGreatHardware
Model: MyBox
Device: MyBox #1 (i.e. append some sort of unique identifier if there
are multiple instances)
Entity: Port 1
Endpoints will inherit "Port 1" as their name -- so you don't have to
bother to name the endpoints, unless there are more than one of each,
which is usually not as good an idea as having one pair of endpoints per
entity.
Then, application writers can make a choice:
If the endpoint name "Port 1" is unique, as it will be in a
single-device studio, you can choose to display just that, and it's nice
and short.
Or, if you always want to be precise, you can concatenate the device and
endpoint names, and even prepend the manufacturer name if you like.
In summary, the driver writers should be identifying the individual
elements, and the application writers can choose how to assemble them
for display to the user, based on space constraints, etc.
There'll be another level of possibilities open when people start using
the new system-level support in 10.1 for defining externally-connected
devices ... but I'll save that for another time.
I welcome your questions and constructive suggestions ...
Doug
--
Doug Wyatt
work: email@hidden (CoreAudio)
personal: email@hidden
http://www.sonosphere.com
"to be nobody but yourself in a world which is doing its best night and
day to make you like everybody else means to fight the hardest battle
any human being can fight and never stop fighting."
-- e. e. cummings