<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 16 April 2013 22:22, Edward Peckham <span dir="ltr"><<a href="mailto:edward@peckham.me.uk" target="_blank">edward@peckham.me.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Simon,<br>
<br>
I feel your pain.<br>
<div class="im"><br>
On Tuesday 16 Apr 2013 18:41:19 Simon Waldman wrote:<br>
><br>
> All has worked for some years. Since I upgraded to 0.26, I've been getting<br>
> quite a lot of failed (0-byte) recordings - perhaps 30% of all recordings<br>
> fail. These only ever happen on the Nova-TD stick. They *seem* to happen<br>
> more on one multiplex than others, but they are not restricted to that<br>
> multiplex (and the favouring of that one that could be random chance / my<br>
> imagination).<br>
</div>My Nova TD stopped being reliable when I upgraded to 0.25. Do you know what<br>
you were on before the 0.26 upgrade?<br>
<div class="im"><br>
> I've tried deleting each of the dual tuners in turn to see if one of them is<br>
> dud. No use. I've tried putting up the various timeouts and tuning delays,<br>
> no use. I've tried changing Fast Tuning between "Live TV Only" and<br>
> "Always", but it made no difference.<br>
</div>I've failed to find a working magic incantation myself. I have found that<br>
tuning with tzap always works, but unfortunately strace does not decode the<br>
structures passed to the v4l frontend ioctl() call, so I've not seen if<br>
there's any difference in how mythbackend does the tune.<br>
<br>
Ed<br></blockquote><div><br></div><div>I was getting the same with my Nova TD tuner. What fixed it for me was ensuring EIT was only enabled on one of it's dual tuners, if it was enabled on both, then recordings failed, but just on one and its been perfect since. Apart from when it disappears completely and the Linux system can't see it at all until I have rebooted 10 times!!<br>
<br></div><div>Cheers<br><br>Martin<br></div></div></div></div>