Re: AIF Files (was Audio Converter and Endians problem)
Re: AIF Files (was Audio Converter and Endians problem)
- Subject: Re: AIF Files (was Audio Converter and Endians problem)
- From: Richard Dobson <email@hidden>
- Date: Tue, 28 Jan 2003 20:04:36 +0000
Ah well, QT on Windows has never worked for me. It is dire as a browser plugin,
and I ended up uninstalling it completely. Unless it has been fixed recently, on
both Windows and the Mac (when I had one last year, running OS X) it doesn't
render AIFF-C float files properly, unless the header gives the wordsize as
16bits (!!!). I discovered this trying to find out why AIFF-C floats files
generated in CSound were not being rendered properly. We naturally presumed that
for a 32bit floats file, the wordsize should be recorded as 32. Basically, I
avoid anything to do with QuickTime! Any applications that rely on the QT
libraries I have to assume are similarly afflicted.
So even if QT exports a little-endian AIFF-C file, I cannot have 100% confidence
it is doing it "correctly". How would I know for sure, without a written spec
for the format to check it against, anyway? A program, library, or even an API,
is not an adequate specification for a file format.
Richard Dobson.
Bill Stewart wrote:
Try using QT on Windows - it will do the same things and you can export
I think to both the big and little endian flavours... and as Mark said,
a WAV file is remarkably similar to an AIF file...
This has been in use for a number of years.
And, just as little-endian data is considered a "compression" format,
so is Float32 - thus this should be contained within an AIFC file
_______________________________________________
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.