[mythtv-users] tuning timeout with dvb-s hd h264

David Watkins watkinshome at gmail.com
Mon Feb 19 09:24:07 UTC 2007


On 19/02/07, Andrew Lyon <andrew.lyon at gmail.com> wrote:
> On 2/18/07, David Watkins <watkinshome at gmail.com> wrote:
> > On 18/02/07, Andrew Lyon <andrew.lyon at gmail.com> wrote:
> > > Hi,
> > >
> > > When I try to tune to a dvb-s hd h264 channel (bbc hd) myth rarely
> > > locks on first time, but if i try again it locks and playback starts,
> > > I think it just times out the first time, is there a timeout value for
> > > dvb-s cards? or better yet a channel specific timeout value?
> > >
> > > Ive looked but all ive found is timeout values for atsc, not dvb-s.
> > >
> >
> > Don't know about dvb-s but for my dvb-t card I set the following
> > timeouts to enable me to record the BBC HD stuff (with the default
> > values I got zero byte recordings).  I set the timeouts high and
> > intended to gradually reduce them to find out what the actual limit
> > was - never got round to doing that yet though!
> >
> > (In mythtv-setup)
> >
> > Signal Timeout to 2000ms
> > Tuning Timeout to 4000ms
> > DVB Tuning Delay to 1000ms
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
>
> The current values are:
>
> Signal Timeout: 60000 msec
> Tuning Timeout: 62500 msec
>
> Are msec and ms the same scale?

I would have though so, normally meaning milliseconds (1/1000 s)
However, 60000 milliseconds is a minute, which seems a bit excessive
so I'm wondering if that msec actually means micro-seconds?  60000
microseconds is 60ms which is short compared to what I'm using.  Maybe
a bit of experimentation might be worthwhile?

> I dont see a tuning delay at all.

Maybe that's a difference between dvb-s and dvb-t, or maybe we're on
different mythtv versions?  I'm running an oldish 0.20 fixes from SVN,
using a Hauppauge USB DVB-T module.


More information about the mythtv-users mailing list