[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 #120 from Thomas DEBESSE <thomas.debesse at rcf.fr> 2013-09-09 15:26:43 UTC ---
> What does the CPU usage look like now (after a few days)?

htop said me:

Mem:1008M used:169M buffers:0M cache:186M
Avg:  6.9% sy:  3.8% ni:  0.0% hi:  0.0% si:  0.0% wa:  0.0% st:  0.0%


remember Comment #111:

Mem:1008M used:143M buffers:0M cache:183M
Avg:  8.0% sy:  2.7% ni:  0.0% hi:  0.0% si:  0.0% wa:  0.0% st:  0.0%

There is three new pipelines since Comment #111 ("alsasrc ! rtpsink", "rtpsrc !
alsasink"; and another "audiotestsrc ! jackaudiosink")

All of this seems ok.

> These are good tests.  The JACK sinks are connected to actual audio hardware
then?

The "jack dummy" is not connected itself to any audio interface, I connect this
patchbay to sound card with "alsasrc ! jackaudiosink" or "jackaudiosrc !
alsasink".

The "jack alsa" is connected to an audio interface and manage it alone.

In both case, the pipeline "jackaudiosrc ! jackaudiosink sync=true" is fine,
the only difference are in warnings, perhaps due to internal jack clock.

> Makes me think that this alsasink problem has been around for a while in some for or another.

Is it possible that the magic trick of "sync=false" has prevented us from
seeing the problem, because it hides the bug at first sight?

> Additionally, JACK sits on top of ALSA as does Pulse.  Is possibly the usage of the ALSA API in alsasink at fault?  Is it employed correctly under JACK and Pulse but not under the GStreamer alsasink plugin?

Indeed we find that "alsa → gstreamer" does'nt work but "alsa → jackaudio →
gstreamer" works. This would mean that:

1. alsa works
2. jack works
3. gstreamer works for other than alsa

I never use "alsasink sync=true" because distortions comes in minutes (see
Comment #75 ).

-- 
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.