Re: New MusicDevice and PrepareInstrument
Re: New MusicDevice and PrepareInstrument
- Subject: Re: New MusicDevice and PrepareInstrument
- From: Airy André <email@hidden>
- Date: Sun, 15 Jun 2003 22:35:19 +0200
I did not meant it was useless to support the MusicDevice API. Just
that you could not support ONLY the MusicDevice API if want your
MusicDevices to be useful right now.
So, basically, what I do with all my current MusicDevice is to
implement the StartNote and StopNote API, which call the AUMIDIBase API.
(while I don't support the PrepareInstrument... API yet.)
Airy
Le dimanche, 15 juin 2003, ` 22:15 Europe/Paris, Bill Stewart a icrit :
I couldn't agree more with Marc's sentiments...
If we can get this sorted soon we can well get this sorted soon if you
know what I mean:)
Bill
On Sunday, June 15, 2003, at 05:12 AM, Marc Poirier wrote:
My questions are: If I release a MusicDevice AU with Instruments will
any hosts (other than my own - and even Rax doesn't grok it right
now)
actually be able to use it? Or should I switch to a "no presets or
instruments mode" and handle it all through custom properties and a
custom UI?
Thoughts?
Well, I guess my feelings are pretty different from the other people
who
have responded, so for what it's worth (some balance perhaps, at
least),
here's what I think:
I would prefer to see you (and anyone else making MusicDevices) use
the
API as it was intended and so, if utilizing Instruments is what suits
your
needs best, then use them and don't make workarounds for the
inadequacies
and lack of AU compliance in existing hosts.
For one thing, it provides necessary pressure for hosts to get their
act
together (it probably should be pretty easy to sway the chiefs at
Granted
Software anyway ;). But perhaps more importantly, the more that
people
don't follow the API and instead use workarounds that happen to work
in
existing hosts, the more that hosts will deal with and expect this
behavior from AUs and the more of a problem we have with supporting
workarounds way past their day of usefulness simply for historical
compatibility reasons.
We're at a pretty fortunate point to take this sort of stance, too,
because there are still not tons of AU hosts or plugins, and for all
of
the hosts, AU hosting is still young. Particularly for MusicDevices,
I
think that there is only Logic, Rax, and SynthTest. So all you have
to do
is work on Emagic and Chris Reed. Digital Performer is coming right
up,
too, and it would be best to see them do things properly regarding
MusicDevices right from the start (perhaps you can get in on some
mutual
beta access with them, too, if you are working on an MD and then have
better channels to get them to implement the API correctly regarding
MD
Instruments).
So anyway, that's what I hope would happen...
Marc
_______________________________________________
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.
-- mailto:email@hidden
tel: +1 408 974 4056
_______________________________________________________________________
___
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
_______________________________________________________________________
___
_______________________________________________
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.
_______________________________________________
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.