<div><span class="gmail_quote">On 9/19/05, <b class="gmail_sendername">Michael T. Dean</b> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</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;">
Could this be a problem with your system (instead of a problem with<br>Myth) that others are seeing where running mythfilldatabase (or wget of<br>any kind) while recording causes an IOBOUND situation that prevents<br>information from being written properly and causes an A/V sync offset?
<br>In other words, does Charlie Rose happen to record around the time your<br>mythfilldatabase runs?<br><br><a href="http://www.gossamer-threads.com/lists/mythtv/commits/150176">http://www.gossamer-threads.com/lists/mythtv/commits/150176
</a></blockquote><div><br>
Yes Mike ! In the mythbackend.log, there are IOBOUND entries that<br>
correspond in time exactly! to the discontinuities in the Charlie Rose show.<br>
<br>
But here's the thing: I had already suspected mythfilldatabase because<br>
it had been running within the Charlie Rose hour. So, I changed the <br>
window for mythfilldatabase to run outside of that hour - problem still<br>
occurred.<br>
<br>
So, mythfilldatabase is not the cause, BUT the system is recording<br>
Letterman (in HDTV) from an HD3000 card at the same time. <br>
I guess that the simultaneous recordings are too much for the I/O<br>
system to handle - a bit of a surprise to me.<br>
<br>
But now, thanks to you pointing me to the logs, I can set up the<br>
recording schedules so that only one recording takes place at a time.<br>
(Of course, I feel that I should have looked in the logs without having<br>
to be told to.)<br>
<br>
One more observation, about a specific time: Last night's out-of-sync<br>
break occurred at 36:19 into the Charlie Rose show. That's within the<br>
first two minutes of Letterman. Maybe there is extra overhead at the start<br>
of a recording?<br>
<br>
Anyway, Thanks Mike, for the heads-up to look in the logs. <br>
It's quite likely that I can avoid the problem, at least for the near-term.<br>
<br>
-- <br>
MM<br>
<br>
</div></div>