strange "no more pads available" error generated by a deinterleave element

[Charlie Laub]

I did some more playing around and troubleshooting and I found the source of
the error.

 

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. 

 

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.

 

Maybe this is one area where alsasink and alsasrc could be improved?

 

 

From: gstreamer-devel <gstreamer-devel-bounces at lists.freedesktop.org> On
Behalf Of Charlie Laub via gstreamer-devel
Sent: Sunday, July 11, 2021 7:19 PM
To: charleslaub at sbcglobal.net; 'Discussion of the development of and with
GStreamer' <gstreamer-devel at lists.freedesktop.org>
Cc: Charlie Laub <charleslaub at sbcglobal.net>
Subject: RE: strange "no more pads available" error generated by a
deinterleave element

 

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.

 

Maybe this is an ALSA related problem???

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20210713/b4fa6ad0/attachment.htm>