Re: FLLR (compression ?) in AIFF file
Re: FLLR (compression ?) in AIFF file
- Subject: Re: FLLR (compression ?) in AIFF file
- From: Brian Willoughby <email@hidden>
- Date: Thu, 14 Aug 2008 00:00:28 -0700
Stephen, I don't really want to jump into the middle of a heated
debate, but I will say that I don't understand your response to Bill
in the paragraph quoted below.
Bill offered a multi-threaded solution, saying that you can simply
create one ExtAudioFile object per thread. You dismissed this
outright, with nothing more than a vague claim that you cannot do
this in your application for various reasons. Would it be so
difficult to mention the reasons? I would be very curious to know
specifically why you cannot create additional ExtAudioFile objects in
your additional threads. Conversely, I'd like to know what you mean
when you say that you expect this to "just work." I bet everyone
would be willing to accept the facts if you backed them up with a few
details.
For the record, I use my own private Objective C framework which
supports AIFF, FLAC, and WAVE (and eventually CAF). I developed
these long before CoreAudio released the AudioFile API, and they are
well-tested, so I have no reason to switch to a less object-oriented
solution. In other words, I totally understand why someone might
choose not to use every API that Apple offers, just because it is
geared towards a particular solution. But even though I'm
practically in your shoes, you're not making a very clear case for
your points, and I don't see how Apple can improve the situation
without more information.
It might be time for a new thread, and/or a bugreport with some
detailed code.
Brian Willoughby
Sound Consulting
On Aug 13, 2008, at 23:34, Stephan M. Bernsee wrote:
On 14.08.2008, at 00:38, William Stewart wrote:
Because there is a potentially complex operation going on between
the file system and the client code, you really can't do this well
though multi-threaded access using a single object. If you want to
read the file from different threads then you can simply create one
ExtAudioFile object per thread.
I cannot do this in my application for various reasons, therefore I
had to create a layer that serialized the calls to a single instance
of ExtAudioFile. This was definitely not fun and as a developer I
would have preferred that it rather "just worked". If you're
interested in learning what your developers' needs are then I would
kindly ask you to accept this as a fact rather than trying to explain
away my needs. Of course there are always ways to deal with a
situation like this by working around a given limitation but it costs
time and money and doesn't really help the project forward.
_______________________________________________
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