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
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
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
On 17.07.22 13:23, 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
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
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
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.
It's starting an EPG scan and seems to be overwriting table 0
