Klaus,
Yes I do still have the issue, I reverted back to 2.20 for now as table
0 functionality is critical for me. I also didn't have luck with the
Astrometa DVB-T2 receiver on either current or 2.20, without a udev
script to copy frontend1 over frontend0, which then works fine. Ugly
but it works.
Thanks for the reminder - I'll see if I can test with other versions.
Richard
On 23/11/2022 16:05, Klaus Schmidinger wrote:
I just dug up this old message.
@Richard: do you still have this problem?
If so, could you try VDR versions between 2.2.0 and 2.6.1 to narrow
down when the problem appeared?
Klaus
On 17.07.22 18:09, Richard F wrote:
On 16.07.22 14:07, Richard F wrote:
>/I've just updated to VDR V2.61 after a long time on V2.2, using
the same config and the epgtableid0 (2.4.0) plug-in. />//>/The
issue I'm seeing is that when VDR is restarted, it doesn't seem to
be reading/respecting the epg.data file. />/... /
Is this the only EPG handler you have installed, or are there others?
If so, make sure this one is installed FIRST.
Klaus
Actually after more testing it seems the table 0 EPG entries are
always being overwritten after EPG scans, not just at startup.
The only EPG handler I have is XMLTV using SVDRP: once a day a
script clears the existing EPG then inserts new entries in table 0
The correct table 0 entries can be seen in VDR for a while, then
get overwritten after automatic scans.
I do need both types, as some channels / programmes don't have
current data in XMLTV, only DVB.
My command line is:
/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P
streamdev-server -P epgsearch -v 1 -l /var/log/epgsearch.log -m
/usr/local/bin/sendEmail.pl -P epgtableid0 -P vnsiserver -P
vdrmanager -P dummydevice -r /usr/local/bin/vdr-auto -u vdr --vfat
-v /mnt/lvm0/TV
There are quotes missing:
/usr/bin/vdr -c /etc/vdr -E /mnt/lvm0/TV/epg.data -l 2 --no-kbd -P
streamdev-server -P "epgsearch -v 1 -l /var/log/epgsearch.log -m
/usr/local/bin/sendEmail.pl" -P epgtableid0 -P vnsiserver -P
vdrmanager -P dummydevice -r /usr/local/bin/vdr-auto -u vdr --vfat
-v /mnt/lvm0/TV
Klaus
I should have explained - earlier I quoted the command line reported
by the kernel. It's actually created by runvdr.extreme.
So the plugins are recognised, the same way they were in 2.20 -
here's an excerpt of the startup
Jul 17 14:39:00 ha-server vdr[8699]: [8699] frontend 0/0 provides
DVB-T with QPSK,QAM16,QAM64 ("Conexant CX22702 DVB-T")
Jul 17 14:39:00 ha-server vdr[8699]: [8699] frontend 1/0 provides
DVB-T,DVB-T2,DVB-C with QPSK,QAM16,QAM32,QAM64,QAM128,QAM256
("Silicon Labs Si2168")
Jul 17 14:39:00 ha-server vdr[8699]: [8699] found 2 DVB devices
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin:
streamdev-server (0.6.3): VDR Streaming Server
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin:
epgsearch (2.4.1): search the EPG for repeats and more
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin:
epgtableid0 (2.4.0): EPG handler for events with table id 0x00
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin:
vnsiserver (1.8.0): VDR-Network-Streaming-Interface (VNSI) Server
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin:
vdrmanager (0.15): VDR-Manager plugin
Jul 17 14:39:00 ha-server vdr[8699]: [8699] initializing plugin:
dummydevice (2.0.0): Output device that does nothing
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
