Re: magic cookies
Re: magic cookies
- Subject: Re: magic cookies
- From: Brian Willoughby <email@hidden>
- Date: Wed, 15 Oct 2003 16:41:31 -0700
[ > Why does QuickTIme utterly and consistently convert any AIFF file into
[ > AIFC, whether asked so or not?
I've noticed that it isn't just QuickTime. If I create a pure AIFF (without
the extended COMM chunk), or copy one, using Unix utilities, then it seems that
the Mac OS X system notices there is no Type and Creator code, and for some
reason it marks these files as AIFC. This is wrong. I can't tell you how many
times I have manually run ResEdit to change them to the AIFF type. This
happens even when the extension is .aiff, and of course even when the head of
the file itself says AIFF and not AIFC.
[ There is only a small practical difference between AIFF and AIFC files, such
[ that if you can parse AIFF you can quite nearly parse AIFC as well. There is
[ truthfully no reason to write a plain AIFF file except for backward
[ compatibility, or if you just *must* save those extra 10 or 20 bytes that
[ AIFC adds =).
There are several good reasons to use plain AIFF. I've noticed that many Mac
OS programs will not even show files with the AIFC Type code in their File Open
browsers. If they are shown, they are often grayed out. This is when I am
forced to run ResEdit and change the Type code so it correctly indicates AIFF.
I'm no Mac OS expert, having jumped on the Mac platform after Rhapsody was
available, but it seems that most of the audio programs I have found (mostly
free programs) do not support AIFC at all. Or at least, in my case, they do
not support AIFF marked as AIFC Type.
Brian Willoughby
Sound Consulting
_______________________________________________
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.