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 143703 - duration always 0 for some (gst produced) .ogg files
duration always 0 for some (gst produced) .ogg files
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: 0.8.3
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-04 12:01 UTC by Tim-Philipp Müller
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2004-06-04 12:01:43 UTC
gst_element_query () returns a total duration of 0 for some .ogg files I have 
(while the correct total duration should be 70-something minutes). 99% of 
all .ogg files I have work perfectly fine, it's just a few that don't work. 
All of those that do not work were GStreamer-produced with 
 
 filesrc ! monkeysdec ! audioconvert ! rawvorbisenc quality=0.7 ! oggmux ! 
filesink, 
 
(it's not that all gst-produced .ogg files fail though). 
 
This problem happens in rhythmbox and in my own code, and I could not extract 
the correct duration from the audiosink no matter what - even later when the 
file is playing. 
 
The full file is more than 100 MB. I'll make the first couple of MB of the 
file available in the hope that that's sufficient. If it is not, let me know 
and I'll put up the full file somewhere. 
 
Cheers 
 -Tim
Comment 1 Tim-Philipp Müller 2004-06-04 12:06:15 UTC
Here's the beginning of one of the problematic oggs: 
 
http://www.zen18864.zen.co.uk/tmp/zero-duration-143703.ogg 
 
Cheers 
 -Tim 
 
Comment 2 Benjamin Otte (Company) 2004-06-07 02:55:31 UTC
I guess the problem is that the oggs are not properly finisahed with an eos
page. Could you confirm that by looking at the whole file?
Comment 3 Tim-Philipp Müller 2004-06-07 11:56:21 UTC
Yes, you are right, that seems to be the problem (if I was supposed to look at 
whether the last OggS page has bit 0x04 set, that is - otherwise I don't know 
what to look for). 
 
Manually setting that bit didn't change much though (not sure if that's 
supposed to work anyway). 
 
ogg123 shows the correct length, btw. ;) 
 
Cheers 
 -Tim 
 
Comment 4 Ronald Bultje 2004-06-17 00:51:37 UTC
If it's what Benjamin suggests, than this is a dup of bug #144241 .
Comment 5 Tim-Philipp Müller 2004-06-17 01:01:36 UTC
I actually filed bug #144241 as a separate bug on purpose, because it's a bug 
in oggmux, while this bug is more general. I'd expect GStreamer to correctly 
determine the approximate length even of truncated ogg/vorbis files (like 
ogg123 apparently does), independent of why the EOS flag is missing or not or 
who is responsible for that. 
 
Comment 6 Benjamin Otte (Company) 2004-07-04 14:10:52 UTC
I believe the recent setup reorganization properly detects the size of truncated
ogg streams.
At least this file is correctly identified as having a length of 1:22 in
Rhythmbox and it allows seeking.
So I'm closing this.