[Bug 692953] alsa modules are silent or noisy after several hours of use

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=692953
  GStreamer | gst-plugins-base | 1.0.9

--- Comment #78 from Thomas DEBESSE <thomas.debesse at rcf.fr> 2013-08-30 12:12:47 UTC ---
This is the full output log:

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full.stdout.txt

This is the full audio record (mono, I discarded the right channel because left
and right channels are identically) :

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-mono-logsync.flac

These are some screenshots:

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-0.png

The first distortion appears at approximatively 4:20 (approximatively the half
of 8:34).

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-4.20-0.png

We can see that the sound is distorded BEFORE the first log line.

The first "correct clock skew" log message appears at 8:34 (sound is already
distorded):

0:08:34.112173174  4737  0x87b0c90 WARN           audiobasesink
gstaudiobasesink.c:1273:gst_audio_base_sink_skew_slaving:<alsasink0> correc
t clock skew 20001262 > 20000000

This first "correct clock skew" log message is followed by the only one
"resyncing" log message.

0:08:34.112215429  4737  0x87b0c90 WARN           audiobasesink
gstaudiobasesink.c:1579:gst_audio_base_sink_get_alignment:<alsasink0>
Unexpected discontinuity in audio timestamps of +0:00:00.010340136, resyncing

At this time, the sound IS REPAIRED (before returning noisy later):

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-1.png
http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-2.png
http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-3.png
http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-4.png

We can see at approximatively 13:07 the first silence appearing:

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-5.png

And we can see at approximatively 16:55 the pipeline becoming definitively
silent:

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-6.png

This picture summarizes it all:

http://dl.illwieckz.net/u/thomas-debesse/bug-report/gstreamer/bug-692953/20130830.gstreamer-drift-problem-full-8.34-0-comment.png





> What about running:
>
> gst-launch-1.0 alsasrc device=hw:XFi
> latency-time=20000 buffer-time=800000 !
> audioresample ! audioconvert !
> alsasink device=hw:XFi sync=true

I will try it.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.