[mythtv] Channel scan produces bogus transponder data
Stuart Auchterlonie
stuarta at squashedfrog.net
Wed Nov 15 15:10:44 UTC 2006
On Wed, Nov 15, 2006 at 08:25:56AM +0100, Tino Keitel wrote:
>
> From my database:
>
> 10 1 775 8468 714000000 0 NULL NULL NULL qpsk 8 auto a auto 0 auto n auto dvb 7 2006-09-26 20:44:59
>
> Janne Grunau's transponder entry:
>
> 10 1 775 8468 714000000 a NULL NULL NULL NULL 8 1/2 8 1/8 0 qam_16 n 2/3 dvb 7 2006-09-26 20:44:59
>
>
> 11 1 775 8468 714000000 0 0 auto v auto 8 auto a auto 0 auto n auto dvb 7 2006-11-15 07:52:49
>
> Could somebody give me some insights regarding this?
At a bare minimum the result from rescanning is wrong. there should
not be a polarity on a dvb-t multiplex.
>
> 1. Why did the old dtv_multiplex entry stopped to work somewhere after
> 11619?
>
> 2. Why does my entry look so much different compared with Jannes?
> Shouldn't thy look the same? He said that he also used the channel scan
> for this.
A lot of this is dependent on your card and drivers.
Some cards can lock onto mux happily given just the frequency,
sometimes they need more information given.
AUTO|auto means that the driver should just try to work it out
itself, so using Janne's more specific information obviously
let the card lock better.
>
> 3. Why does the new entry contains different, but still broken data?
>
That is an interesting question. I'd like to see the output from
mythtv-setup --verbose channel,record,siparser
when scanning for the channels....
Stuart
More information about the mythtv-dev
mailing list