Re: writing aiff file to disk
Re: writing aiff file to disk
- Subject: Re: writing aiff file to disk
- From: Robert Grant <email@hidden>
- Date: Thu, 8 Jan 2004 14:27:52 -0500
Does the AudioFile API not count? I'm confused why everyone is ignoring
it?
Robert.
On Jan 8, 2004, at 1:50 PM, Stanko Juzbasic wrote:
Thanks for the message. However, this is NOT my point, sorry. Your
statement still does not convince me of de facto standard solutions -
it is arguable.
I know Erik's work, keep in touch, and admire his code - even made a
contribution, so do I know Michael Pruett's libaudiofile, which is the
open source version of the IRIX audio file library, and Bill
Schottstaedt's sndlib, etc...
I also did not wait for Apple to release OSX, nor ObjectiveC to
ressurect, so I could do my work.
My point is that Apple does not seem to be clear if they want people
to write as many private audio file libraries as application (setting
aside Apple's advocacy of QuickTime), or infer OpenSource, non-apple
stuff, for competitive reasons, or buy commercial libraries, then
suddenly jump with a jack-in-a-box...
Is there a strategy? If so, would be great to know.
(-;
I hope someone from Apple would also react on this message.
Thanks in advance.
Stanko
On Thursday, January 8, 2004, at 06:12 PM, Richard Dobson wrote:
The de facto standard solution (setting aside Apple's advocacy of
QuickTime) to this is to use libsndfile:
http://www.zip.com.au/~erikd/libsndfile/
It is a very comprehensive library, under the LGPL, cross-platform,
supports virtually all AIFF-C and WAVE variants plus lots else,
well-designed, and very actively maintained by the author. Much
better than trying to roll your own unless you really are interested
in file format design, or have some unique/idiosyncratic approach to
soundfile handling, or require something out of the ordinary (but
Eric is always ready to incorporate enhancements, additions, etc).
You would need to do that if you really wanted to create a library in
objective-C, but I can't really see the point or need for that.
Richard Dobson
Stanko Juzbasic wrote:
Hi, John,
I took a look at your sample code. Does it actually mean there is no
standard system-level audio file code,
but you actually have to "re-invent" practically all the headers for
all the types of chunks for AIFF/C files,
deal with endianness and sample width issue "manually", on a per
file type basis,
then do the same thing for opening and closing and writing and
reading literally all the other audio file
standards - not to mention error detection and correction issues. In
other words, are the audio programmers
really being encouraged into writing each one's own proprietary
audio file library, rather than using a system-level one, just
because there is none, or because it's so well hidden that almost
nobody believes it's there?
_______________________________________________
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.
_______________________________________________
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.
_______________________________________________
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.