<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>I did some more playing around and troubleshooting and I found the source of the error.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It turns out I was sending an audio format to the sink that the sink doesn’t accept. This must have propagated back up the pipeline until it resulted in the no pads available issue, somewhere in the middle. There was no mention in the debug output that this had anything to do with ALSA! I only found the cause with some luck and a lot of trial and error. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I recall having a similar problem a couple of years ago, where there was some ALSA related problem but there was no mention of it in any Gstreamer debug info that I could access.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Maybe this is one area where alsasink and alsasrc could be improved?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> gstreamer-devel <gstreamer-devel-bounces@lists.freedesktop.org> <b>On Behalf Of </b>Charlie Laub via gstreamer-devel<br><b>Sent:</b> Sunday, July 11, 2021 7:19 PM<br><b>To:</b> charleslaub@sbcglobal.net; 'Discussion of the development of and with GStreamer' <gstreamer-devel@lists.freedesktop.org><br><b>Cc:</b> Charlie Laub <charleslaub@sbcglobal.net><br><b>Subject:</b> RE: strange "no more pads available" error generated by a deinterleave element<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For one last check, I replaced the FIRST alsasinnk with fakesink and allowed audio to play to the new, second alsasink (DAC). The pipeline worked without error and the DAC produced audio as intended. So there does not seem to be a problem with the second DAC itself, only when the pipeline attempts to direct audio to both alsasinks.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Maybe this is an ALSA related problem???<o:p></o:p></p></div></body></html>