After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726656 - Video decoder could (should ?) return EOS when it has pushed buffers past the limits of the segment.
Video decoder could (should ?) return EOS when it has pushed buffers past the...
Status: RESOLVED DUPLICATE of bug 709224
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-18 17:24 UTC by Mathieu Duponchelle
Modified: 2014-03-18 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This patch is an example of how I would fix the reported issue (2.17 KB, patch)
2014-03-18 17:27 UTC, Mathieu Duponchelle
none Details | Review

Description Mathieu Duponchelle 2014-03-18 17:24:10 UTC
Easy way to reproduce the unwanted behaviour:

GST_DEBUG=*libav*:5 gst-launch-1.0 gnlurisource uri=file:///anything/with/h264 inpoint=0 duration=5000000000 caps=video/x-raw ! xvimagesink qos=false 2>&1 | grep "Received new data of size"

I've got a simplistic patch which I'll attach after, which doesn't take the rate into account, but shows what I would like to see happen (past 5 seconds, the decoder returns EOS which ends up stopping the pipeline way sooner, in my case with HD samples, decoding speed is roughly equal to playback speed, and I end up waiting way too much time for my liking :)

I suppose there might be a very good reason for my patch not to be correct (apart from the rate considerations), but I have a hard time figuring it out.
Comment 1 Mathieu Duponchelle 2014-03-18 17:27:09 UTC
Created attachment 272316 [details] [review]
This patch is an example of how I would fix the reported issue
Comment 2 Mathieu Duponchelle 2014-03-18 19:01:27 UTC

*** This bug has been marked as a duplicate of bug 709224 ***