[Bug 730070] hlsdemux: add support for stream RESOLUTION extension

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=730070
  GStreamer | gst-plugins-bad | 1.3.1

--- Comment #1 from m][sko <xlazom00 at gmail.com> 2014-05-27 06:40:31 UTC ---
>From mail conversation with Sebastian Dröge

The resolution is usually propagated upstream to elements with the CAPS
query, and the elements are notified of something changing with the
RECONFIGURE event. Unfortunately in this case this won't work yet as
1) after hlsdemux there is another demuxer that does not forward and
   transform the CAPS query downstream (and can't sensibly). This
   is tsdemux usually.
2) after that second demuxer there is a video decoder, and video
   decoders currently don't forward and transform the CAPS query.
   The decoder could do this quite easily, and it could probably
   even be implemented in the video decoder base class.

1) is a real problem and I currently don't know how to solve that
without putting demuxers inside hlsdemux so that hlsdemux can directly
query the CAPS on the video stream.

Hi sebastian
I checked xvideosink and other video sinks
and I simply can't find any notice that videosink sent upstream information
when window size change.
ximagesink send gst_event_new_reconfigure() in
gst_ximagesink_xwindow_update_geometry => regenerate caps
As this isn't caps related it is just some event that will notify upstream
elements  

The reconfigure event is sent upstream, and tells upstream elements that
they should reconfigure. I.e. check with downstream if there's a more
optimal configuration now, regarding caps (e.g. the resolution!) or the
used allocation mechanism. hlsdemux would get this event whenever the
resolution changes and can then do something.

But as explained in the previous mail, it currently can't do much and
you would need to find a way to proxy the resolution in the caps up to
hlsdemux.

-- 
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.