[mythtv] Some DVB remarks

[Daniel Kristjansson]

On Sat, 2005-09-24 at 14:03 +0200, Rudy Zijlstra wrote:
> Dear,
> 
> I've last night upgraded my test DVB-C system to svn current.
> 
> I am in the Netherlands, which is DVB country. No ATSC to be found for 
> thousends of miles around...

> 2005-09-25 10:29:22.851 desired_program(20701) pid(0xdd0)
> 2005-09-25 10:29:22.852 pmt_pid(0xdd0)
> 2005-09-25 10:29:22.854 PAT for output stream
> 2005-09-25 10:29:22.855 Program Association Table
>  PSIP prefix(0x0) tableID(0x0) length(13) extension(0xcf)
>       version(25) current(1) section(0) last_section(0)
>          tsid: 207
>  programCount: 1
>   program number 1 has PID 0x dd0   data  0x0 0x1 0x237 0x208
> 
> 2005-09-25 10:29:22.856 DVBSM(0)::AddPIDFilter(0xdd0):
> 2005-09-25 10:29:22.915 PSIP packet has Adaptation Field Control, not 
> ATSC compiant
> 2005-09-25 10:29:23.088 DummyRec: Restart! Frames seen 220
> 2005-09-25 10:29:23.117 PSIP packet has Adaptation Field Control, not 
> ATSC compiant
> 2005-09-25 10:29:23.320 PSIP packet has Adaptation Field Control, not 
> ATSC compiant
> 
> When it starts complaining about "not ATSC compliant" i can wait for 
> minutes (i've let it go on in this for over 10 minutes) without getting 
> video displayed.

The "PSIP packet has..." is not related to the problem, it looks
like the signal monitor finds what it is looking for. But it also
looks like it is kept running too long, it has to be shut down
before DVB recording is started.

Can you try the latest tuning patch here:
   http://svn.mythtv.org/trac/ticket/339


Those Scanning problems are best left to someone in DVB land, this
is the scanning logic that works in England and Germany. But if the
frequency was messed up, then it may be your drivers, there was a
post a couple days ago about a fix for one of the DVB cards that
was returning the wrong frequency.

-- Daniel