Re: magic cookies
Re: magic cookies
- Subject: Re: magic cookies
- From: Stanko Juzbasic <email@hidden>
- Date: Wed, 15 Oct 2003 01:24:32 +0200
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?
Best Regards,
Stanko
On Tuesday, October 14, 2003, at 11:45 PM, David Duncan wrote:
On Oct 14, 2003, at 04:50 PM, Stanko Juzbasic wrote:
On Tuesday, October 14, 2003, at 06:36 PM, Holger Hvrich wrote:
But as I understood the magic cookies, those are data structures
inside of AudioUnits e.g. holding information about compressed
audio files which are not to be understood by anybody else...
Why are these things suddenly needed for professional audio file
format ( 16-bit linear as low end )?
What do they serve for - ENCRYPTED COMPRESSION - (?)- iPod or Music
e-Commerce Copyright authorization ?
Magic cookies are for extra data that is needed to decompress the
data. For example AC3 audio decompression to less than full 5.1
should use a down mix matrix that provides the coefficients for each
channel so that the down mix virtualizes correctly. Purportedly other
formats can require extra information to decode as well.
Why does QuickTIme utterly and consistently convert any AIFF file
into AIFC, whether asked so or not?
Does this also have to do with magic cookies?
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 =).
--
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.