<div class="gmail_quote">On Sun, Oct 9, 2011 at 6:05 PM, Matt Mossholder <span dir="ltr"><<a href="mailto:matt@mossholder.com">matt@mossholder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">While all of what you say may be true, you can't argue with results.</div>
I've now recorded 3 X .5 hour shows, with no glitching. Also keep in<br>
mind that the average ping response time between the VM and the host<br>
is between .2 and .3 _milliseconds_. We're talking about everything<br>
living on one box here. 10 microseconds sure sounds like a lot in<br>
comparison.<br>
<div class="im"><br></div></blockquote><div><br></div><div>.2 milliseconds = 200 microseconds. I'm not sure what you mean by 10 microseconds sounding like a lot in comparison. </div><div> </div><div>That being said... Other than the latency of the start/stop commands, and the latency of the beginning of the video frames, it's not likely to be a problem as long as there's large bandwidth AND there's no need for individual ACK packets (like in TCP). It's similar to pulling IPTV off of a satellite receiver in a way... Lots of bandwidth, fairly slow latency. Nothing that can't be worked around with appropriate buffering and other methodologies, but that said, the hdpvr driver may not like it much.</div>
<div><br></div><div>All that being said, there should be no reason you can't run the backend right in the main box (i.e. not in a VM). It's more likely to work correctly too.</div></div>