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 579782 - playbin2 always picks GstSystemClock
playbin2 always picks GstSystemClock
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: 0.10.23
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-21 23:21 UTC by Jan Schmidt
Modified: 2009-05-15 09:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jan Schmidt 2009-04-21 23:21:42 UTC 
For me in current git, playbin2 always ends up picking the GstSystemClock, which I guess means the audio device is slaved to it, and probably is the reason I get stuttery audio quite frequently.
Comment 1 Wim Taymans 2009-04-22 13:40:37 UTC 
with all kinds of files? I don't get that...
Comment 2 Jan Schmidt 2009-04-22 14:02:32 UTC 
No - you're right, it's just some files.

With a quick test, some ogg files, flv and mpeg select GstPulseSinkClock.
DVD always seems to pick the SystemClock. Some mov files pick the audio clock, some the system clock.

I guess it depends on some characteristic of the audio streams.
Comment 3 Jan Schmidt 2009-05-15 09:49:14 UTC 
This was also fixed by:

commit c05541c19505cf52f4e76fcc27f2b85328e5660b
Author: Wim Taymans <wim.taymans@collabora.co.uk>
Date:   Thu May 7 14:28:30 2009 +0200

    playbin2: make playsink go ASYNC to PAUSED

    Make playsink go async to the PAUSED state instead of relying on
uridecodebin
    for async behaviour in playbin. This solves some problems (mainly with DVD)
    where the pipeline would go to PLAYING before preroll completed, failing to
    select the audiosink clock.
    Fixes #581727