[gstreamer-bugs] [Bug 322461] [lame] creates bogus metadata when using variable bitrate

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=322461
 GStreamer | gst-plugins-ugly | Ver: HEAD CVS





------- Comment #14 from Tim-Philipp Müller  2006-04-06 13:34 UTC -------
mmacleod:

I think there are different issues here. One is what the lame element produces.
This issue has been 'resolved' in that it doesn't (and shouldn't) produce xing
headers any longer. For that there will be xingmux in future.

What banshee and other GStreamer-based players recognise VBR-wise is a
different issue. If you have a file with an xing-header that other
non-GStreamer players read fine but GStreamer doesn't read, then please open a
new bug against mad so it can be fixed. That is a different issue than the
original issue here though, isn't it?

Finally, it is possible of course to scan an entire mp3 file at start-up to
find out the exact length and average bitrate for VBR files, but so far the
decision has been not to do that (as it might be slow if the file isn't local
or rather large). This could certainly be implemented conditionally, e.g. when
an index is set on mad.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.