Re: ExtAudioFile 4GB file size limitation on WAV files
Re: ExtAudioFile 4GB file size limitation on WAV files
- Subject: Re: ExtAudioFile 4GB file size limitation on WAV files
- From: Brian Willoughby <email@hidden>
- Date: Tue, 03 May 2011 15:38:04 -0700
On May 3, 2011, at 14:44, Paul Davis wrote:
I'm not sure you understand how open source works in this respect, but
no matter. I wasn't trying to provide a list of phrases designed to
irritate anyone. I should have been more terse and simply said "an
equivalent cross-platform proprietary library that people can rely on
in the way that open source developers can rely on libsndfile?"
What it all boils down to, for me, is this: If I can't change
libsndfile to be correct for everyone, then I'm still stuck with my
private changes to this open source project. I don't see how that's
much different than using ExtAudioFile until I need to change by
switching to my own private implementation under certain edge cases.
Granted, it's easier to build a private change to libsndfile because
it's open source. ExtAudioFile is closed source, so a private
solution has to be designed from the ground up (unless you consider
that you still have Apple's file system API to build on without
writing your own disk drivers).
I did not intend to start an argument, either, which is why I opened
by saying that I can't disagree. What frustrates me is that I don't
want to endorse libsndfile by using it when I already know of flaws.
It's sort of DOA for me, and I don't even want to get started. Ego
gets in the way of fixing libsndfile for everyone, so I don't see how
a small, single-developer open source library is much better than a
closed-source API from Apple.
I will admit that the biggest factor here is that Apple (CoreAudio)
does things the right way according to the Audio Engineering Society,
mathematicians, and other reputable industry experts. In my book, I
prefer a closed source API that gives me undistorted audio to a
small, single-developer, open source API that does things the wrong
way and can't be changed because of a single ego. Other proprietary
versus open source competitions might turn out differently, because
in my experience most open source projects involve more than one ego
and there is thus less resistance to change, improvement, and good
design. I have had an excellent experience with the open source FLAC
project because, although it is still primarily a single developer,
there are actually a few people involved and there doesn't seem to be
much resistance to improvements to design or implementation.
Granted, that project doesn't change any more because there simply
isn't anything "wrong" to correct.
In other words, that's why I ended my message with the challenge:
Does anyone know of a really open audio file library that delivers
everything that Apple's CoreAudio delivers? If so, I will gladly
endorse it, no offense to Apple.
Brian Willoughby
Sound Consulting
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden