If RID is the last number in the list, vdr won't collect epg data if
this number is anything but 0 for atsc channels.
On 1/9/2011 11:28 PM, Theunis Potgieter wrote:
On 10 January 2011 00:02, Klaus Schmidinger wrote:
On 09.01.2011 21:04, Timothy D. Lenz wrote:
Using vdr-1.7.15. 3 of the loca
OK, now the conf has been changed. First time it happened within 30sec.
this time it took much longer.
On 1/9/2011 3:02 PM, Klaus Schmidinger wrote:
On 09.01.2011 21:04, Timothy D. Lenz wrote:
Using vdr-1.7.15. 3 of the local networks have duplicate transmitters. 1
is a bit too weak get right
First time I tried it, I started vdr, went into vdradmin from a browser
and the new channels where not there. Check the conf and it was as I
posted with only the numbers. I checked the log and it said nothing
about deleting channels, only changing pids which it does all the time.
It's never hap
On 10 January 2011 00:02, Klaus Schmidinger wrote:
>
> On 09.01.2011 21:04, Timothy D. Lenz wrote:
> > Using vdr-1.7.15. 3 of the local networks have duplicate transmitters. 1
> > is a bit too weak get right now and because of a bug in atsc, I can't
> > rescan right now (crashes vdr, reported in a
On 09.01.2011 21:04, Timothy D. Lenz wrote:
> Using vdr-1.7.15. 3 of the local networks have duplicate transmitters. 1
> is a bit too weak get right now and because of a bug in atsc, I can't
> rescan right now (crashes vdr, reported in another post). I pulled the
> entries for the secondary transmi
Using vdr-1.7.15. 3 of the local networks have duplicate transmitters. 1
is a bit too weak get right now and because of a bug in atsc, I can't
rescan right now (crashes vdr, reported in another post). I pulled the
entries for the secondary transmitters for two of the networks from the
last scan
