Processing control commands:
tags -1 fixed-upstream
Bug #736088 [libavformat54] libavcodec54: wrongly set bitrate in XING header
(mp3enc)
Added tag(s) fixed-upstream.
--
736088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736088
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing commands for cont...@bugs.debian.org:
tags 736088 +upstream
Bug #736088 [libavformat54] libavcodec54: wrongly set bitrate in XING header
(mp3enc)
Added tag(s) upstream.
stop
Stopping processing here.
Please contact me if you need assistance.
--
736088:
tags 736088 +upstream
stop
On Fri, Mar 07, 2014 at 12:04:25PM +0100, Alessandro Ghedini wrote:
So, I've done a bit of investigation, and it turns out that this is caused by
the way libavformat writes the XING header to mp3 files. Essentially, it uses
a fixed value for bitrate_idx... for any
On sab, mar 08, 2014 at 09:25:35 -0500, Reinhard Tartler wrote:
tags 736088 +upstream
stop
On Fri, Mar 07, 2014 at 12:04:25PM +0100, Alessandro Ghedini wrote:
So, I've done a bit of investigation, and it turns out that this is caused
by
the way libavformat writes the XING header to mp3
Control: reassing -1 libavformat54
Control: retitle libavcodec54: wrongly set bitrate in XING header (mp3enc)
On dom, gen 19, 2014 at 11:33:13 -0500, Reinhard Tartler wrote:
Also note that avprobe does report the correct bitrate:
avprobe version 0.8.9-6:0.8.9-0ubuntu0.13.04.1, Copyright (c)
Package: libavcodec54
Version: 6:9.10-2
Severity: normal
Hi,
I recently noticed something weird, but I'm not sure if it's actually a libav
bug (it doesn't happen with ffmpeg though). I noticed this while using mpv's
encoding facility, but it happens when using avconv as well.
So, basically,
Also note that avprobe does report the correct bitrate:
avprobe version 0.8.9-6:0.8.9-0ubuntu0.13.04.1, Copyright (c)
2007-2013 the Libav developers
built on Nov 9 2013 19:09:48 with gcc 4.7.3
Input #0, mp3, from 'noise_avconv.mp3':
Metadata:
encoder : Lavf53.21.1
Duration:
