After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 314253 - xingheader property on lame plugin is unimplemented
xingheader property on lame plugin is unimplemented
Status: RESOLVED DUPLICATE of bug 322461
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.10
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-08-23 11:28 UTC by Andy Hanton
Modified: 2006-01-13 15:49 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Andy Hanton 2005-08-23 11:28:50 UTC 
Without a xing header applications can't correctly find the length of the file.
 If implementing the header isn't a current priority, the properties for vbr and
presets should be commented out so users don't waste time trying them.
Comment 1 Jan Schmidt 2006-01-13 11:28:27 UTC 
I'm not familiar at all with lame, or the gst plugin, but I've had a quick look.

As far as I can tell, the appropriate Xing header bits are implemented in gstlame, except I can't see any way in the LAME API to actually write the Xing header EXCEPT lame_mp3_tags_fid, which requires a seekable file descriptor in order to write the header - which GStreamer can't supply because it's a processing pipeline. 

I guess in order to implement the Xing header, we need to do it outside of lame. The Xing header itself is not complicated, but finding out the statistics to put into it is tricker. It might be a candidate for a separate xingwriter element that goes in the pipeline after lame.
Comment 2 Andy Wingo 2006-01-13 15:29:51 UTC 
Jan: is this a dup of bug #322461?
Comment 3 Jan Schmidt 2006-01-13 15:49:33 UTC 
yes it is, bugmaster

*** This bug has been marked as a duplicate of 322461 ***