Re: audio file bug in AudioUnitHosting
Re: audio file bug in AudioUnitHosting
- Subject: Re: audio file bug in AudioUnitHosting
- From: David Duncan <email@hidden>
- Date: Sun, 4 Jan 2004 12:25:43 -0500
On Jan 4, 2004, at 12:05 PM, Robert Grant wrote:
Here's an example that caused me to scratch my head recently: The
AudioFile API uses FSRef to identify files, but right next door the
MusicPlayer API uses FSSpec to identify files for SMF loading/saving.
(And arbitrarily uses FSRef when loading a MIDI file with flags). Why
the two different methods?
In that case, I think it's more a question of why they even bothered to
support FSSpecs!
It seems that Apple should identify the preferred API for working with
files and identify when using the alternatives is called for. Rather
than just (what seems to be) capriciously using whatever is familiar
to the developer that's working on that part of the API (or example
code).
Taking the recent Quicktime updates, it would seem that they are fully
intent on support CFURL, FSRefs and UTF-8 path strings. I know, it
makes my head hurt too.
--
Reality is what, when you stop believing in it, doesn't go away.
Failure is not an option. It is a privilege reserved for those who try.
David Duncan
_______________________________________________
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.