[Audacity-cvs] FFmpeg 0.5 WAS: lib-src/ffmpeg/libavutil avutil.h...
siretart at tauware.de
Fri Jul 24 18:22:32 UTC 2009
The following message is a courtesy copy of an article
that has been posted to gmane.comp.audio.audacity.devel as well.
please let me introduce myself, I'm Reinhard Tartler, Debian and Ubuntu
developer and I'm taking care of the ffmpeg packages in both
distros as member pf the multimedia packages maintainers team. Recently
the topic of audacity came up on our mailing list and I'm currently
reading up the relevant discussion via gmane.
So here we go.
LRN <lrn1986 at gmail.com> writes:
> Gale Andrews wrote:
>>> The lack of GPLv3 in ffmpeg source tree is clearly a bug, a critical
>>> blocker that should be fixed immediately.
>> Have you reported that to them?
> That was a joke. I don't think they actually care.
They do seriously care. That's the main point of the upcoming 0.5.1
release. The old libamr support was replaced with opencore support.
BTW, debian and ubuntu track the 0.5 release branch.
>> Also we now have the position that user can click on the AMR WB
>> export filter (no comments in the filter text), see a message that
>> FFmpeg needs configuring, install it, and then the WB export filter
>> has disappeared. That is going to lead to support issues (it will
>> look like our bug).
> H-m-m...didn't thought of that. We should comment-out that export option
> then, until it is supported by Opencore AMR and libav*.
you could try to dlopen() libavcodec *and* try to load the amr codec
using avcodec_find_codec() or avcodec_find_encoder_by_name() or
something. Dependening on this check a sensible diagnostic message can
be printed out.
>> I'm not quite clear here. I thought I saw that the non-open AMR
>> libraries had been removed from FFmpeg 0.5. If that's true, then I
>> presume even user who self builds FFmpeg won't now have AMR
>> WB encoding ability. Or, if someone builds or has an older FFmpeg
>> system library and compiles Audacity, does Audacity still work with
>> that older library?
> No. Due to interface changes libav* prior to 0.5 is not supported
> anymore (i *could* have made it to support more than one version, but
> that's silly).
Why would that be silly? Please reconsider this decision, Linux distros
and other downstreams of ffmpeg like gstreamer-ffmpeg are currently
tracking the 0.5 branch and have no plans to track trunk again. Having a
common ffmpeg baseline seriously lowered the bug filing rate in ubuntu
of crasher bugs in libavcodec.
Reinhard Tartler, KeyID 945348A4
More information about the pkg-multimedia-maintainers