Comment 93 for bug 602934

(In reply to comment #80)
>> AAC export on Ubuntu (native encoder using "M4A files") is still wrong -
>> seems to be a silent file - "playable" but very small file size.
> I'm pretty sure the small file size is expected, but the silent file is not.
> Can you send me one of those via email?
I have sent you "silent.m4a". But I cannot reproduce an issue now, either with
WAV or WMA input or tone input. That file was produced last night though there
is a very small possibility it came from the 1.3.12 Ubuntu release and not from
1.3.13 - I did not name it clearly enough and it was the only M4A I had time to
export. However the 1.3.12 Ubuntu release is not currently producing silent
files either, so I'm still kind of suspicious.

What I want to do now to complete testing is to generate AMR/AC3/M4A/WMA files
outside Audacity and try those on Audacity on Win and Ubuntu. If those files
actually import and play properly I think we could close this once it is
committed. Then:

* Have a P4 moonphase bug for silenced M4A exports with native encoder.

* Bug 317 stands but modified to be an issue with either AAC encoder when you
export using "M4A files". Think it should be P3 as it is very annoying.

* I've already opened Bug 339 "watch libfaad and native AAC encoder in case
they fix issues that prevent us using them in Audacity's FFmpeg". That gives us
a release note:

"(Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder.
Files exported using the FFmpeg native encoder are of very poor quality. These
are both issues with the library itself."

So this means we do what you suggested and in the Win/Mac FFmpeg we distribute,
we use the native AAC decoder and the libfaac encoder.

Does this cover everything?

> don't let me forget to fix the start time check.
Now at bug 338.(In reply to comment #80)