<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> I have a combined front end / back end, nvidia graphics card, Athlon 64 X2<br> 4400, Nova T-500 dual DVB-T tuner card, 1Gb RAM. Root filesystem on a<br>
different disk to the recorded programmes.<br> <br> I was ready to junk mythtv this time last week and go back to using a normal<br> shop-bought digibox. The problems I was having were:<br> <br> - live TV jerky<br> - recorded programs playback blurred in fast pans (particularly noticable on<br>
programme credits)<br> - unreliability in recording, some tuners just wouldn't record programmes, so<br> when I came to look at the list of recorded programmes, there would be some<br> where it couldn't find the file, and there would be no picture in mythweb.<br>
Sometimes the back end process would fail for some reason and then next time<br> I looked at the recorded programmes list it would tell me that the back end<br> was not running.<br> <br> I have since upgraded to 0.21 which fixed the first two of these problems. TV<br>
quality is now excellent, both in live TV and playing back existing<br> recordings.<br> <br> However, I've just been bitten by the second problem. Only one of today's<br> recordings has actually recorded - the rest, mythtv thinks they've been<br>
recorded, but there is no file on disk.<br> <br> I have a strong signal, which is split between TV and myth box using a Y<br> connector. Normal analogue TV in this configuration is snowy, but digital is<br> ok. Signal strength reported in the OSD is 58-62% ish. I have three virtual<br>
tuners on each physical one.<br> <br> Just tried going to live TV, and it couldn't lock into the channel before the<br> timeout. I rebooted the box, and it suddenly could lock in. The box has<br> only been up since yesterday evening when I upgraded to 0.21 and then<br>
rebooted.<br> <br> Am I going to have a script a nightly reboot (windows!?) or does anyone have a<br> clue where I should start looking?<br> <br> </blockquote><div><br>hmmmm interesting, Have you read the HCL to see if you have any compatability issues with the hardware you have? I wouldn't go blaming a piece of software what appears to be working fine for others an not yourself. It might just be that the kernel drivers are not as mature as other drivers in the kernel. Ideally an wise person would have listed their hardware and asked if people have experienced issues with them.<br>
</div><br></div><br>