[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 #64 from Thomas DEBESSE <thomas.debesse at rcf.fr> 2013-08-26 19:26:34 UTC ---
There is no hardware path in the unix pipe. :)

So, arecord and aplay appear to me to be overbloated softwares that do more
than what they should do. They emulate so many things! When these programs are
used to query the characteristics of a sound card as described in the
documentation, they respond what alsa emulates over physical abilities instead
of physical habilities. These two programs allow anything but reliable use of a
sound card. Using arecord or aplay without cabalistic option on a "default"
sound card is like running two resample and two converter

This kind of command:
arecord -D default-f dat | aplay -D default-f dat
hides 4 converters and 4 resamplers. More than necessary.

In this kind of command:
gst-launch-1.0 alsasrc ! capsfilter caps="audio/x-raw, format=S16LE,
rate=48000, channels=2" ! alsasink
there is 0 converter and 0 resampler, and it is slower than the arecord/aplay
alternative due to the latency default value, and only slower because of these
default values. I think it is not necessary to slower. These values ​​are
already very good default values.

But do not feed more the troll, aplay and arecord are slow. It's just a fact.

My problem is not why GStreamer can be faster than a slow combination of
arecord with aplayn when reducing the prudent Gstreamer options provided for
all use cases in the world. Yes, Gstreamer can be faster than arecord/aplay
with better values than defaults.

But my problem is why my pipelines become silent without saying anything, even
with default values that are cautious and prudent. :)

And with so many and so various tests, I don't know why. :(

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