[Bug 745724] jpegparse: set framerate to 0/1 when duration is not known

[GStreamer (GNOME Bugzilla)]

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

Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #15 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
(In reply to Guillermo Rodriguez from comment #14)
> Just stumbled upon this one.
> 
> The following pipeline results in a sluggish 1 fps playback (source stream
> is approx 10fps):
> 
> gst-launch-1.0 souphttpsrc is-live=true location=... ! jpegparse !
> avdec_mjpeg ! autovideosink
> 
> This works fine:
> 
> gst-launch-1.0 souphttpsrc is-live=true location=... !
> image/jpeg,framerate=0/1 ! jpegparse ! avdec_mjpeg ! autovideosink
> 
> I too believe that jpegparse should default to 0/1, and not 1/1, if the
> source does not set the framerate.

Default is usually 25/1, but your server is too slow, the reason you get 1/1.
It's up to the application to select the framerates. All you have to do is
specify what you want 0/1.

  gst-launch-1.0 souphttpsrc is-live=true location=... !
image/jpeg,framerate=0/1 ! ...

Also, a 0/1 default only make sense for live pipeline, with timestamp (see
do-timestamp), which is not even your case. What you basically endup with is
the equivalent of "autovideosink sync=0".

Is there anything in this bug that cannot be solved at application lever by
giving more information to the pipeline ?

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