<br><br><div class="gmail_quote">On Tue, Nov 13, 2012 at 2:12 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><br><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Again, there's no error, yet. Again, talk to the guys who make the hardware or the drivers and explain to them that if they don't produce any data for the app to read, /they/ should make the decision that an error occurred and /they/ should report the error, rather than writing MythTV to assume a failure exists and break working hardware...<br>
<br></blockquote><div><br>Yeah well they don't in all cases. And surely it would be simple to add a test, say 30 seconds after a recording starts, that finds if any data has been written and do something sensible if it hasn't. In an ideal world, passing bug reports upstream would result in fixes. In the real world developers work around upstream bugs.<br>
<br>Sorry this may appear grumpy, and I haven't exactly contributed any patches, but it had to be said!<br></div></div><br>