[Bug 640610] basesink: QoS events are wrong in live pipelines

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=640610

--- Comment #25 from Olivier Crête <olivier.crete at ocrete.ca> ---
(In reply to Sebastian Dröge (slomo) from comment #24)
> @@ +1404,3 @@
> + * Maximum amount of time (in nanoseconds) that the pipeline can take
> + * for processing the buffer. This is added to the latency of live
> + * pipelines.
> 
> How would a subclass decide on a good value for this? Based on how much time
> it thinks it will take to get buffers from render() to the display? Or
> prepare() to render()?

Maybe we shouldn't expose it, it's mostly meant for subclass that want to
override the "processing-deadline" property.

The value is really meant to be selected by the application as an acceptable
deadline. My original idea was to set this and default max-lateness to 0, but
I'm worried it would have unintented side-effects.

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