Pipelining alsasrc to alsasink with different interfaceĪlsasrc device="hw:0" ! something ! alsasink device="hw:1"ĥ. Pipelining alsasrc to alsasink with same interfaceĪlsasrc device="hw:0" ! something ! alsasink device="hw:0"Ĥ. The "alsasrc ! … ! alsasink" pipeline is only for demonstration purpose : the bug appears *also* with this pipeline, and I can verify the bug with this simple pipeline putting a physical source and physical monitor to ear sound (or not due to the bug when the bug appears :) ).īut I have tested thoses pipelines (written from memory, you get the idea) :ģ. > Are the source and sink both on the same physical > and then PLAYING to make it work again? Or is > Is it enough to set the pipeline back to PAUSED There is a discussion about this bug on the mailing list : * some distros (Debian Squeeze, Wheezy, Sid, Ubuntu 12.10) * several Gstreamer versions (0.10 → 1.0) * several linux build (2.6.32 → 3.2.0), rt-kernels or not rt-kernels * several soundcards (usb Muse Pocket LT3, pci Audigy CA0106, internal Intel 82801, Nvidia MCP51, some Realtek chip) So you can restart the pipeline every 3 hours to have sound several days dealing with some milliseconds of silence every 3 hours) * Restarting the pipeline without destroying it (set then set ) fix it. * Some pipeline get noise instead of silent.
#How to use ps4 controller on steam without bug picture mode software
* Nothing seems broken, there is no sound so people could say "I got the bug" but software does'nt know there is a bug. * The pipeline isn't broken, state is always and the pipeline seems functionnal * GST_DEBUG=3 said nothing about any problem. * gst-inspect with -v option said nothing about any problem. Note : pipelining alsasrc with alsasink is one of the faster way to get a bug, only 3 or 4 hours instead of more than 12 hours. * let the pipeline running a complete day to be sure to get the bug * build a pipeline using alsasrc or alsasink * I use soundcards directly without alsa modules (no 'plug', no 'dmix', no 'dsnoop') or with alsa modules (that changes nothing) * The fact of getting noise or silence depend on the whole pipeline. * The time before become silent depend on the whole pipeline. * The bug appears every time an alsa module (alsasrc or alsasink) is used, just wait long. * This bug affect both Gstreamer 0.10 and Gstreamer 1.0 * I don't get this problem on other Gstreamer modules. I have some other examples with "alsasrc ! … ! udpsink" or "udpsrc ! … ! alsasink". Gst-launch-1.0 alsasrc device="hw:0 ! 'audio/x-raw, format=S16LE' ! audioconvert ! audioresample ! 'audio/x-raw, format=F32LE, channels=2' ! jackaudiosink sync=0
Gst-launch-0.10 -v alsasrc device="hw:0" audioconvert ! audioresample ! "audio/x-raw-int,rate=44100,width=16,channels=2" ! alsasink device="hw:1" sync=falseĪnd another pipeline (Gst 1.0) that breaks : Gst-launch-0.10 jackaudiosrc ! "audio/x-raw-float" ! audioconvert ! audioresample ! "audio/x-raw-int, rate=44100, width=16" ! alsasink device="hw:1" sync=0
This is a complete pipeline that breaks : On some use case, I get noise instead of silence. I have tried different uses case, sometimes it's the alsasrc module that become silent, sometimes it's the alsasink module. The time before become silent or noisy depend on the whole pipeline.Ī pipeline like "udpsrc ! … ! alsasink" breaks after 3 ou 4 hours.Ī pipeline like "alsasrc ! … ! alsasink" does the same.Ī pipeline like "jackaudiosrc ! … ! alsasink" breaks after 14 hours. Hi, alsa modules (alsasrc, alsasink) become silent when used for several hours.
0 kommentar(er)
