<div><span class="gmail_quote">On 1/31/07, <b class="gmail_sendername">Klaus Schmidinger</b> <<a href="mailto:Klaus.Schmidinger@cadsoft.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Klaus.Schmidinger@cadsoft.de
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
VDR User wrote:<br>> From what he's saying, the problem is buffer overrun's, not underrun's.<br>> Too much data is being sent and the device isn't able to keep up. If<br>> that's the case then it would make sense for vdr to have a user setting
<br>> to limit how many seconds (or milliseconds perhaps?) worth of data is<br>> sent to the buffer. I can't think of any reason not to add such a<br>> feature if it means better usability for the end-user.
<br>If the device can't take any more data, it should just refuse to<br>accept it and return from the write() call without anything written.<br></blockquote></div><br>I disagree. Simply returning from write() implies the data was written and the device is ready for more. If this is not true then you risk making the sync even worse.
I consulted with people familiar with this type of stuff and it was suggested the problem could (and should) be fixed at the driver level so I'm following up on that now. Hopefully we'll find a good (or at least resonable) solution to this last little bit of a/v sync frustration.