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 585569 - rtsp/rtp streaming fails when skipping explicit PAUSED state change
rtsp/rtp streaming fails when skipping explicit PAUSED state change
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.10.24
Assigned To: Wim Taymans
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-12 14:37 UTC by René Stadler
Modified: 2009-06-15 16:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test program (378 bytes, text/x-python)
2009-06-12 14:38 UTC, René Stadler 		Details

Description René Stadler 2009-06-12 14:37:38 UTC 
Attaching a pygst test program. Run it without arguments to get this:
0:00:01.166385865 19608      0x1058c40 WARN               rtpsource rtpsource.c:925:calculate_jitter: cannot get current time
0:00:01.371305072 19608      0x1058c40 WARN               rtpsource rtpsource.c:925:calculate_jitter: cannot get current time
0:00:01.591286913 19608      0x1058c40 WARN               rtpsource rtpsource.c:925:calculate_jitter: cannot get current time
[...]

and no playback. If you comment in the intermediate state change to PAUSED, it works:
    ## p.set_state (gst.STATE_PAUSED)
    p.set_state (gst.STATE_PLAYING)
-->
    p.set_state (gst.STATE_PAUSED)
    p.set_state (gst.STATE_PLAYING)

Doesn't make much sense at all; I debugged it a little and it seems that the pipeline clock isn't distributed correctly for some reason...
Comment 1 René Stadler 2009-06-12 14:38:09 UTC 
Created attachment 136437 [details]
Test program
Comment 2 Wim Taymans 2009-06-12 15:04:06 UTC 
true and interesting indeed.
Comment 3 Wim Taymans 2009-06-15 16:47:16 UTC 
commit d881bf69d1337e5bdd72dc3d238fb291d7322196
Author: Wim Taymans <wim.taymans@collabora.co.uk>
Date:   Mon Jun 15 18:44:45 2009 +0200

    bin: make sure we set the next state correctly
    
    When the continue function is scheduled, make sure we set the next state instead
    of the pending state.
    Add some more debug info.
    
    fixes #585569