Ticket #270 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

Latency issues in gst-pulse

Reported by: rikai Owned by: lennart
Milestone: Component: gst-pulse
Keywords: Cc:

Description

Encountered some issues in GST-pulse when using gnome-sound-properties and gstreamer-properties. Not sure how to explain them as i'm quite a novice, so i'll just attach the output of gnome-sound-properties --gst-debug-level=3 and hope its self-explanatorly.

The symptoms being: If I select 'pulseaudio sound server' as my sound input with my usb mic set as the default source in pulseaudio and press test, it plays the microphone output for a fraction of a second and then quickly degrades, and then is silent.

and i get a series of output similar to:

0:00:03.501275672 11042 0x84fe3b0 WARN         baseaudiosink      gstbaseaudiosink.c:919:gst_base_audio_sink_skew_slaving:<autoaudiosink0-actual-sink-pulse> correct clock skew -5963085 < -5000000

Talked to some of the folks in #gstreamer on freenode about it and they had the following to say:

<wtay> rikai, yeah, something with pulseaudio and latency, it needs fixing at some point
<rikai> wtay, ahh, so its a known issue then?
<wtay> rikai, yep
<rikai> wtay, any chance you could point me in the direction of the bug report? I'd like to keep tabs on it.
<wtay> rikai, there is no bug report for it yet
<rikai> ahh, so its a new issue too, then? That explains why it just started happening recently.
<rikai> so, is the problem gstreamer-side or pulse side? i'd think it'd be in gst-pulse, which is gstreamer side, correct? Sorry for asking so many questions, i just want to know where i should follow any progress and such.
<wtay> rikai, pulse side, likely. I think the gstreamer side should do things right..}}}

Attachments

gstreamer-debugging.txt (75.7 kB) - added by rikai 4 years ago.

Change History

Changed 4 years ago by rikai

Changed 4 years ago by slomo

  • status changed from new to closed
  • resolution set to invalid

As gst-pulse was moved to gst-plugins-good the bug is now at http://bugzilla.gnome.org/show_bug.cgi?id=537537

Note: See TracTickets for help on using tickets.