[gstreamer-bugs] [Bug 156387] New: - [oggdemux] seeking is off by up to 30 secs (regression)

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=156387
GStreamer | gst-plugins | Ver: HEAD CVS

           Summary: [oggdemux] seeking is off by up to 30 secs (regression)
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net


Seeking with current CVS HEAD's oggdemux isn't exact enough. 
 
I'm getting deviations of up to 30 seconds, e.g. I'm seeking to 3223 seconds 
(53:43 mins) from the start of the file, and it actually seeks to 53:12 
minutes. 
 
That's pretty bad if you have a continuous stream with multiple songs, e.g. a 
whole album (.ogg + .cue file) and want to seek to a certain song within the 
album. 
 
Would be great if this got fixed before the next plugins release. 
 
Cheers  
 -Tim 
 
<__tim> BBB: is there some kind of accepted error margin with oggdemux seeking 
now? 
<BBB> yeah 
<__tim> BBB: 'cause I'm seeking to 3223 seconds into the file, and it goes to 
53:12 instead of 53:43 
<__tim> that's 30 seconds ... 
<BBB> we can get that more eaxct, but I didn't include binary tree search in 
my first try 
<__tim> oh, okay. So that's within the expected margin then? 
<BBB> I guess so 
<BBB> it just seeks to byte_length*position_time/length_time

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.