Re: [vdr] Freesat patch

2014-12-31 Thread VDR User
> b)  With more recent kernels (3.4 and 3.12, I think anything higher than
> 3.0)  I'm seeing regular dmesg events like so
>
> usb 1-1.2: dtv_property_legacy_params_sync: doesn't know how to handle a
> DVBv3 call to delivery system 0
>
> I'm not sure what causes this (no other errors), but it's related to the
> older DVB-T receivers. VDR is built with the same kernel/DVB as the machine
> it runs on.  Is this just a driver issue, or is there a test VDR
> could/should do based on API to avoid making the unhandled DVBv3 call ?

I would assume this question is more appropriate for the linux-media
mailing list. Driver issues are better fixed in the driver rather than
workarounds in an app imo.

-Derek

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Freesat patch

2014-12-31 Thread Klaus Schmidinger

On 31.12.2014 15:11, Richard F wrote:

Klaus / Mario - thanks for the feedback / info about filters.
I will probably stay with the filters in 2.0.6 for DVB-T and DVB-T2 as it gives 
me good functionality.
The Freeview HD EPG is quick in this config - a few minutes to get the full EPG.

A couple more questions...

a)  In later versions, the conditional

if (Setup.SetSystemTime && Setup.TimeTransponder)

was removed for the TDT PID filter. What was the reason for that?


VDR/HISTORY:

2012-12-08: Version 1.7.33

...
- Now always setting the TDT EIT filter, because otherwise when turning on 
using the
  transponder time in the Setup menu, it would only be used after the next 
restart
  of VDR (thanks to Sundararaj Reel).


b)  With more recent kernels (3.4 and 3.12, I think anything higher than 3.0)  
I'm seeing regular dmesg events like so

usb 1-1.2: dtv_property_legacy_params_sync: doesn't know how to handle a DVBv3 
call to delivery system 0

I'm not sure what causes this (no other errors), but it's related to the older 
DVB-T receivers. VDR is built with the same kernel/DVB as the machine it runs 
on.  Is this just a driver issue, or is there a test VDR could/should do based 
on API to avoid making the unhandled DVBv3 call ?  The receiver
functions well for TV reception as far as I can tell, and though I can filter 
the messages going to syslog, all these dmesg events lose the bootup info.


I'm afraid I don't know that.

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Freesat patch

2014-12-31 Thread Richard F

Klaus / Mario - thanks for the feedback / info about filters.
I will probably stay with the filters in 2.0.6 for DVB-T and DVB-T2 as 
it gives me good functionality.
The Freeview HD EPG is quick in this config - a few minutes to get the 
full EPG.


A couple more questions...

a)  In later versions, the conditional

if (Setup.SetSystemTime && Setup.TimeTransponder)

was removed for the TDT PID filter. What was the reason for that?

b)  With more recent kernels (3.4 and 3.12, I think anything higher than 
3.0)  I'm seeing regular dmesg events like so


usb 1-1.2: dtv_property_legacy_params_sync: doesn't know how to handle a DVBv3 
call to delivery system 0

I'm not sure what causes this (no other errors), but it's related to the 
older DVB-T receivers. VDR is built with the same kernel/DVB as the 
machine it runs on.  Is this just a driver issue, or is there a test VDR 
could/should do based on API to avoid making the unhandled DVBv3 call ?  
The receiver functions well for TV reception as far as I can tell, and 
though I can filter the messages going to syslog, all these dmesg events 
lose the bootup info.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Freesat patch

2014-12-27 Thread Mario Schulz
Am 27.12.2014 um 11:42 schrieb Klaus Schmidinger:

>> Does anyone know if these extra PID's are definitely required? Maybe
>> only for DVB-S/2 ?
> 
> Sorry, I don't know anything about that.

I programmed/ported a VDR Version to Topfield in 2010[*].
At that time Freesat was broadcasting their EPG using 3841/3842.
The Topfield did not have a hardware capability to filter these, so it
was necessary to write a stream parser for a recorded TS.
In addition on a standard video stream Freesat EPG came in extremely slow.
They had a specific radio transponder which was as well dedicated to
data broadcasts (11426MHz/27500/H).
Performing a recording on PID 3002/3003 revealed the full Freesat EPG
extremely fast.
When I backported the Topfield stuff into the VDR patch, the only piece
of work done has been the conversion of the Huffman tables from file
read into a header data structure to make it a bit more efficient and
eliminate the need for dynamic memory.

That has been the history.

And the situation today?
I dont think they changed 3841/3842 as this might be a problem for
installed reception equipment. But somebody would have to do a bit of
dvbsnooping to be shure.

So my guess is that it cannot be changed for DVB-S/S2 reception.

[*] https://sourceforge.net/projects/freesattotgd/

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Freesat patch

2014-12-27 Thread Klaus Schmidinger

On 26.12.2014 17:45, Richard F wrote:

The Freesat patch at http://www.vdr-wiki.de/wiki/index.php/Freesat-patch
adds the following PID filters in eit.c - cEitFilter::cEitFilter

   Set(3842, 0x4E, 0xFE);  // event info, actual(0x4E)/other(0x4F)  TS, 
present/following
   Set(3842, 0x50, 0xF0);  // event info, actual TS,  schedule(0x50)/schedule 
for future days(0x5X)
   Set(3842, 0x60, 0xF0);  // event info, other  TS,  schedule(0x60)/schedule 
for future days(0x6X)

Which eats up hardware PID filters on my older USB DVB-T receivers (Freeview 
SD), and stops them working on most transponders.  I removed them to test, 
because Klaus had removed these similar ones as long ago as 1.7.9 which was 
very helpful:

   Set(0x12, 0x50, 0xF0);  // event info, actual TS, schedule(0x50)/schedule 
for future days(0x5X)
   Set(0x12, 0x60, 0xF0);  // event info, other  TS, schedule(0x60)/schedule 
for future days(0x6X)


Just for the record: while these two filters were removed in version 1.7.9,
there was also an additional 'if (Tid >= 0x4E && Tid <= 0x6F)' added to the
'case 0x12' of the Pid handling, so that in the end the exact same data was
processed as before, just with the benefit of saving two explicit filters.


And I still receive the full 8 day EPG on Freeview, including HD channels, with 
just the PID filters defined in vanilla 2.0.6 - everything else appears OK, 
including DVB subtitles, audio description etc...

Does anyone know if these extra PID's are definitely required? Maybe only for 
DVB-S/2 ?


Sorry, I don't know anything about that.

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr