[gstreamer-bugs] [Bug 351742] New: [vorbisenc] discontinuity detection too sensitive, might garble output
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Thu Aug 17 04:28:43 PDT 2006
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=351742
GStreamer | gst-plugins-base | Ver: HEAD CVS
Summary: [vorbisenc] discontinuity detection too sensitive, might
garble output
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-base
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: t.i.m at zen.co.uk
QAContact: gstreamer-bugs at lists.sourceforge.net
CC: msmith at fluendo.com
GNOME version: Unspecified
GNOME milestone: Unspecified
The newly-added discontinuity detection based on previous_timestamp +
previous_duration vs. current_timestamp is too sensitive. It will trigger even
for minor stream imperfections or rounding errors in timestamps/durations,
leading to unusuble output. Case in point: recent cddabasesrc fix, where
0.0233333333 + 0.0166666666 added up to 0.0399999999 which was !=
0.0400000000
and a discontinuity was assumed, the decoder reset etc. The resulting .ogg was
pretty much broken, with 'stuttering' multiple times per second.
Don't know if this is a problem with how the decoder is reset/data flushed or
not, but I think vorbisenc should be a bit less sensitive to such errors.
--
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.
More information about the Gstreamer-bugs
mailing list