mysqlcheck -A -r<br><br><div><span class="gmail_quote">On 2/23/06, <b class="gmail_sendername">Steven Adeff</b> <<a href="mailto:adeffs.mythtv@gmail.com">adeffs.mythtv@gmail.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;">
On 2/23/06, Daniel Kristjansson <<a href="mailto:danielk@cuymedia.net">danielk@cuymedia.net</a>> wrote:<br>> On Thu, 2006-02-23 at 14:40 -0500, Steven Adeff wrote:<br>> > On 2/23/06, Daniel Kristjansson <
<a href="mailto:danielk@cuymedia.net">danielk@cuymedia.net</a>> wrote:<br>> > sadly, I have no idea what you guys are talking about, but I sure hope<br>> > it will lead to fixing the glitches in the new method that aren't
<br>> > present in the old method =)<br>><br>> I haven't been following this thread, but I'm pretty sure this<br>> could be fixed by adding some buffering via DeviceReadBuffering<br>> or another method. FindKeyframes will be even more heavy duty
<br>> when #799 is fixed.<br>><br>> You can probably fix the problem right now by putting the<br>> database on a separate disk from the video volume. And by<br>> making sure the DB is not corrupted and so taking a long
<br>> time to insert the keyframes.<br>><br>> -- Daniel<br><br>I've already got my DB on another drive. I also had this problem<br>starting with a fresh DB when I rebuilt my system so I don't think<br>thats it either. Again, it only happens with the firewire stream, my
<br>HD3000 (both being fed by my cable company) works fine.<br><br>time to dig up the command for checking my db...<br><br>--<br>Steve<br>_______________________________________________<br>mythtv-dev mailing list<br><a href="mailto:mythtv-dev@mythtv.org">
mythtv-dev@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</a><br></blockquote></div><br>