Re: magic cookies
Re: magic cookies
- Subject: Re: magic cookies
- From: Richard Dobson <email@hidden>
- Date: Wed, 15 Oct 2003 01:18:33 +0100
If you are meaning 32bit float formats, then it simply ~has~ to be
AIFF-C - there is no way to represent float samples using plain AIFF
("32bit" by itself can ambiguously indicate both floats and ints). You
could almost say that AIFF-C was designed expressly to enable floats to
be used, as well as to support compressed formats. Like any chunked
format, AIFF-C can act as a container for all sorts of stuff. They
should with the benefit of hindsight have called it AIFF-X. WAV can be
used the same way. It is a completely independent thing - nothing to do
with Quicktime, any more than the WAV format is; though Quicktime may
happen to use it.
Though funnily enough, I have yet to read any official public Apple
document that describes the floats format in AIFF-C. It post-dates
Apple's AIFF-C draft spec of 1991 vintage, so lots of folk got used to
writing "FL32" in the header before later finding that Apple wanted
"fl32".
I heartily agree that having to open a soundfile in the Quicktime player
by using a menu item "Open Movie" is very silly. Soundfiles were around
long before movie formats were even thought of.
And I am still awaiting an announcement of a 64bit version of AIFF-C
(i.e. with 8-byte chunk sizes etc), which someone on this list said was
being "worked on". Panther?
Richard Dobson
Stanko Juzbasic wrote:
This may be a reasonable answer for you and web streaming commerce,
mac.com, even Apple philosophy. It is probably also wise what you try
to evangelize, but my work has nothing to do with compression. I
mostly deal with 32-bit formats - IS THIS ALSO OUT OF REALITY, for
you? Why do I use this format is way beyond the scope of this mail...
(-:
What do I have to do in order NOT TO BE FORCED TO ACCEPT what your
proverb proclaims as REALITY? Not have to deal with one extra step in
decompressing what isn't compressed at all.
NOT TO BE FORCED INTO ACCEPTING QuickTIme as master guardian of audio
file traffic, which decides WHAT AUDIO IS AND WHAT IS NOT? Why should
an audio file be interpreted as sound track of a non-existent movie,
against user's will and freedom to decide otherwise, if I may ask?
_______________________________________________
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.