Re: AAC/MP3 to raw audio
Re: AAC/MP3 to raw audio
- Subject: Re: AAC/MP3 to raw audio
- From: William Stewart <email@hidden>
- Date: Mon, 8 May 2006 15:28:20 -0700
On 08/05/2006, at 1:15 PM, Alexander von Below wrote:
On 08.05.2006, at 21:12, William Stewart wrote:
What bug?
4470243
Thanks! If you make a reference to "a bug" in a posting to this list,
please list the bug number. We get many postings that mention "a bug"
that have never been filed with us (and so it is often news to us
too!), or were mentioned in an email 2 months ago, etc..
As we've stated many times: If you see behaviour that is
unexpected, etc, then it is perfectly fine to ask questions about
this on this list. However, this is not the end of the story.
I have asked questions about this on the list, and the list has
been very, very helpful. I appreciate that. Without the help from
this list, I would not have found any solution at all.
Maybe I just lack the skills, but solving exactly this problem (for
my system requirements) has been very, very frustrating for me. I
would like to help other developers choose the right path, as I
have reached some dead-ends in my development. In the process I
filed minor (4400389) and - in my mind - major (4532604) bugs.
You must file bugs with behaviours that are reproducible and
wrong. We don't necessarily know about these and you cannot assume
as you do below that we do.
The bugs I have filed above are all reproducible with Apple sample
code, and they look certainly wrong to me.
To file a bug go to http://bugreporter.apple.com and file a
report. If at all possible, including sample code, media files,
etc that can reproduce the problem is a tremendous help. If you
are uncertain about the reproducibility of a problem, then include
as much information as you do know. The less reproducible a
problem is, the more likely it is that we will request further
information!, so the more you provide up front, the better for
everyone.
I agree, 100%., and I try to take the time to file every issue
because I know Apple cares, and I know that good bug reports help
you create a better system.
That said, the bugs I encountered only happen with certain files.
The bug 4470243 was found not by me, but by quality control when
they ran the code against a huge sample base of MP3 files. If our
sample file had not contained such a malformed file, then it would
have been users instead.
So I want to save others the misery of completing their code,
giving it to QA (or worse, users) and finding out that they run
into a dead end like me.
I look forward to seeing your bug report on this issue.
I was glad to provide them. I know that without a solid,
reproducible bug report fixing stuff is almost impossible. And I
gladly take any constructive criticism on my bug reports.
Again, please let there be no misunderstanding: I do not wish to
badmouth anyone or anything. But the issue at hand has proven much
more complex that I ever thought it to be.
Yes, it can often be the case. And I certainly appreciate your
efforts and diligence in filing bugs.
As a follow up, one of the bugs you mention above has been misfiled
with another group (so, I'm in the process of following up on that).
It is always very helpful to either file bugs, or if filed, to refer
to the bug numbers in any correspondence.
Thanks again
Bill
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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