[gstreamer-bugs] [Bug 640665] basesink: drops too many buffers when there's no duration
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Mon Jan 31 06:42:06 PST 2011
https://bugzilla.gnome.org/show_bug.cgi?id=640665
GStreamer | gstreamer (core) | git
Wim Taymans <wim.taymans> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wim.taymans at gmail.com
--- Comment #3 from Wim Taymans <wim.taymans at gmail.com> 2011-01-31 14:42:04 UTC ---
I'm thinking that -1 as the duration on a buffer means that the buffer has
infinite duration and should thus be displayed at all times.
On the other hand, we don't want to display a frame that should have been
displayed a long time ago because it might end up badly synced with the audio.
For 'low' framerates, the eye does not care about late frames much but for high
framerates the effects can be very disturbing.
So I'm thinking that there should be a limit, even for frames with a duration.
Probably this limit should depend on the average number of frames per second or
something.
Calculating the average time between incoming buffer timestamps is probably
something interesting we can use in this metric too.
--
Configure bugmail: https://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