<html style="direction: ltr;"> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style> <style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style> </head> <body style="direction: ltr;" bidimailui-detected-decoding-type="latin-charset" bgcolor="#FFFFFF" text="#000000"> I'm writing a server that broadcasts to multiple PulseAudio sinks over the network. It works great when it works. :) Except that it does not tolerate network failure nicely: it's enough for one of the sinks to go down, and the stream stops for *all* sinks. In fact, the pipeline won't even start playing if one of the sinks cannot connect. The pipeline looks like this: <tt>playbin2 ! tee ! valve ! queue ! pulsesink</tt> Where the "! valve ! queue ! pulsesink" branch is duplicated for each sink, and in each branch is contained in bin. (I need the valve in order to allow for safe removal these branches while playing.) The easiest way to test this is to create a pipeline with two such branches, where one branch points to a network host that doesn't exist. The pipeline won't play. Any ideas on how to proceed? I don't even know which element is the stubborn one here. I just want the pipeline to ignore the "bad" sink and work around it! -Tal </body> </html>