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 758911 - audiobasesink/src: send latency message on setcaps
audiobasesink/src: send latency message on setcaps
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: 1.7.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-12-01 17:26 UTC by Michael Olbrich
Modified: 2015-12-01 17:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (1.07 KB, patch)
2015-12-01 17:26 UTC, Michael Olbrich
committed Details | Review

Description Michael Olbrich 2015-12-01 17:26:40 UTC
Created attachment 316619 [details] [review]
patch

Any latency query before this will not get the correct latency so a new
latency query should be triggered once the audio sink know its own latency.

Without this the initial latency query from the pipeline arrives too early
sometimes and the resulting latency is too short.
Comment 1 Sebastian Dröge (slomo) 2015-12-01 17:59:16 UTC
commit 2f3eb47a954ec0be764965b807182a63950cab4e
Author: Sebastian Dröge <sebastian@centricular.com>
Date:   Tue Dec 1 19:57:10 2015 +0200

    audiobasesrc: Post latency message on the bus after set_caps()
    
    The latency is only known once the caps are known, and might change
    whenever the caps are changing.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=758911

commit 43155807cdbe5d2d74832b5c7444205244a57531
Author: Michael Olbrich <m.olbrich@pengutronix.de>
Date:   Fri Sep 25 14:47:48 2015 +0200

    audiobasesink: Post latency message on the bus after set_caps()
    
    Any latency query before this will not get the correct latency so a new
    latency query should be triggered once the audio sink know its own latency.
    
    Without this the initial latency query from the pipeline arrives too early
    sometimes and the resulting latency is too short.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=758911