<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Mar 19, 2006, at 4:59 PM, Chris Lynch wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">On 3/19/06, <B class="gmail_sendername">Steven Adeff</B> <<A href="mailto:adeffs.mythtv@gmail.com">adeffs.mythtv@gmail.com</A>> wrote:<DIV><SPAN class="gmail_quote"></SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > 1 - Watching LiveTV or recording a channel will not always work. It will go<BR>> to a black screen and then come back to the main menu. With LiveTV trying<BR>> over and over will eventually work. When it's recording a show you have no <BR>> way of knowing if it's actually recording. This one has put me in the hurt<BR>> locker with my wife on Myth :)<BR><BR>Set the DCT connection setting to Broadcast and 200 or 400mbps. power<BR>down the computer and the cable box and repower both, this should <BR>solve the issue. as well, if channel tuning doesn't work use 6200ch<BR>(in the contrib folder) for channel changing and try the "new" method<BR>(theres a switch to enable it).</BLOCKQUOTE><DIV><BR>I'll give this a shot. Thanks for the pointer - there's not a lot of info out there for troubleshooting. </DIV><BR><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> 2 - Pixellation every 10 seconds or so. It lasts for about 1 - 2 seconds<BR> > and it is part of the recording stream so it's not a playback issue as best<BR>> as I can tell. I have verified that running my DCT-6200 direct to the TV<BR>> does NOT exhibit the pixellation, so I don't think it's related to weak <BR>> signal (I've even plugged in an amplifier to boost the signal strength).<BR><BR>This is a firewire kernel driver problem. Some firewire chipsets<BR>aren't as bad as others, but its a problem with the kernel and<BR> partially Myth, both of which are being worked on.</BLOCKQUOTE><DIV><BR>Interesting - I've tried my motherboard one (VIA chipset) and the one on my Audigy 2. Is there a recommendation anyone has to what chipset or even a specific board to buy? I'll buy whatever works at this point :) <BR><BR></DIV></DIV></BLOCKQUOTE><BR></DIV><DIV>Especially with Via-based motherboards you need to be very careful of PCI Latency settings. I was getting glitches in recordings if I tried to watch LiveTV at the same time, even with just 1 SD recording.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Re-setting the latencies, the system could then make 3 recordings while watching LiveTV without a glitch. Check the WiKi at:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><A href="http://www.mythtv.org/wiki/index.php/PCI_Latency">http://www.mythtv.org/wiki/index.php/PCI_Latency</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Also, some older Via boards had DMA problems that caused trouble for IVTV, there is some info on that on the IVTV site.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I'm not saying any of this is directly related to your problem(s), but it never hurts to have everything optimized. I'd try a latency setting of b0 hex for your IDE controller first. If your F/W controller is capable of transferring data faster than the IDE subsystem can write it to the diskyou would get your (2) symptom.</DIV></BODY></HTML>