<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - The client has not a chance to provide data, when absolute offset is used in a stream without prebuffering and underrun happend for long time"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103103#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - The client has not a chance to provide data, when absolute offset is used in a stream without prebuffering and underrun happend for long time"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103103">bug 103103</a>
from <span class="vcard"><a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> <span class="fn">Tanu Kaskinen</span></a>
</span></b>
<pre>If the write index is behind the read index by 30 seconds, writing 30 seconds
of audio should succeed. The stream buffer size limit should only kick in after
the write index has passed the read index. I read the code, but I didn't find
any bug. can_push() in memblockq.c seems to handle the "write index behind read
index" case correctly.
The behaviour that you describe sounds like pulsesink is writing the 30 second
block at the current read index, not 30 seconds behind the read index. Can you
do further debugging to verify what is really happening?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>