Re: Questions on data in MIDIPackets
Re: Questions on data in MIDIPackets
- Subject: Re: Questions on data in MIDIPackets
- From: Kurt Bigler <email@hidden>
- Date: Mon, 25 Feb 2002 14:31:22 -0800
on 2/25/02 9:58 AM, Bill Stewart <email@hidden> wrote:
>
The MIDI Services on X are just that - getting MIDI data in and out of the
>
system to MIDI Devices (and some IA facilities). How could we possibly
>
design and implement an API for a protocol that doesn't exist yet and has no
>
real hardware support?
>
>
We also know that MIDI is not the be all and end all of these kinds of
>
protocols (particularly for Software based rendering) so we specifically
>
provided APIs for the MusicDevice component (AudioUnit/MusicDevice.h) that
>
allows for:
>
Floating Pt note numbers
>
Floating Pt parameter lists to new notes of arbitrary lengths
>
Arbitrary numbers of groups (ie. Think MIDI Channels) - where also groups
>
are NOT defined to be notes on a particular instrument, but are user defined
>
Floating Pt parameter values
>
Sample offsets for all of these.
>
(As well as MIDI APIs)
A point that I neglected in my last message...
I had not (prior to Bill Stewart's message) looked at AudioUnits yet, not
expecting to find there what I have been calling "MIDI-replacement"
functionality.
Though I still haven't looked at AudioUnit/MusicDevice.h functionality in
detail, it may well be that Apple HAS address my concerns there, provided I
am willing to push what I thought of as application functionality down into
an audio unit. However, there are many potential reasons NOT to do that,
which keeps open the question about making the same abstractions available
to an application as a midi-stream substitute, through a set of services
parallel to the OS X MIDI Services.
-Kurt Bigler
_______________________________________________
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.