<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style type="text/css">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 hope you can still answer my question about draining network
sinks.<br>
<br>
Also, a new issue came up after some heavier testing: sometimes both
during adding and removing sinks dynamically, the pipeline changes
itself to PAUSES state! Why would it do this? What could be the
cause? What can I do to avoid it?<br>
<br>
<div class="moz-cite-prefix">On 12/30/2012 05:16 PM, Tal Liron
wrote:<br>
</div>
<blockquote cite="mid:50E0CB63.9070109@gmail.com" type="cite">Thanks,
Tim! I have a followup question.
<br>
<br>
On 12/30/2012 04:53 PM, Tim-Philipp Müller wrote:
<br>
<blockquote type="cite">What's the context here? What kind of sink
is it? Perhaps it's enough to just unlink it, then set it to
NULL state and remove it from the pipeline? Draining is only
required if you need to make sure that e.g. muxers finalize
headers and everything gets written to disk properly etc. </blockquote>
Ah, I see what you mean here. Draining *should* only matter if I'm
using file sinks.
<br>
<br>
But ... what about network sinks? I currently support a udpsink
(with an rtpL15pay). Would there be any harm in unlinking it and
removing it while there's still something in its buffers?
<br>
<br>
I don't care about data loss here, I just want to avoid memory
leaks, assertion failures, or other crashes. I'm assuming the sink
elements know how to destroy themselves properly and release their
resources, ... well, I'm hoping. ;)
<br>
</blockquote>
<br>
</body>
</html>