[vdr] Re: timer bug: Usage of channel ID inconsitend

[Alexander Wetzel <alexander.wetzel@web.de>]

On Sunday 07 September 2003 16:21, you wrote:
> Alexander Wetzel wrote:
> > 1.) Created a copy of ARD with NID=1
> >
> > ARD2:11836:h:S19.2E:27500:101:102:104:0:28106:1:0.0
>
> I assume the '.' between the last to '0' is just a typo...
>

Shame on me. While reprodincing the error I introduced a typo in 
channels.conf. (I really had a '.' instead of a ':' for ARD2)

Nevertheless the problem occured first with ":" and still does.

> > 2) Started VDR from command line (without pugins)
> > Sep  7 14:55:00 vdr vdr[1878]: VDR version 1.2.2 started
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/setup.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/sources.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/diseqc.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/channels.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/timers.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/svdrphosts.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/ca.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/remote.conf
> > Sep  7 14:55:00 vdr vdr[1878]: loading /video/keymacros.conf
> > Sep  7 14:55:00 vdr vdr[1878]: found 2 video devices
> > Sep  7 14:55:00 vdr vdr[1878]: setting primary device to 1
> > Sep  7 14:55:00 vdr vdr[1878]: SVDRP listening on port 2001
> > Sep  7 14:55:00 vdr vdr[1878]: switching to channel 1
> >
> > 2.) Created a timer with the OSD. New entry in timers.conf:
> > Sep  7 14:56:46 vdr vdr[1878]: timer 10 added (active)
> >
> > Entry in timers.conf: 1:S19.2E-1-0-28106:8:1456:1756:50:99:a:
> >
> > 3.) Closed all OSD windows and opend again the timer window. Timer is
> > listed
> >
> > 4.) restarted vdr
> > Sep  7 14:59:19 vdr vdr[1878]: caught signal 2
> > Sep  7 14:59:19 vdr vdr[1878]: saved setup to /video/setup.conf
> > Sep  7 14:59:20 vdr vdr[1878]: exiting
> > Sep  7 14:59:46 vdr vdr[1895]: VDR version 1.2.2 started
> > Sep  7 14:59:46 vdr vdr[1895]: loading /video/setup.conf
> > Sep  7 14:59:46 vdr vdr[1895]: loading /video/sources.conf
> > Sep  7 14:59:46 vdr vdr[1895]: loading /video/diseqc.conf
> > Sep  7 14:59:46 vdr vdr[1895]: loading /video/channels.conf
> > Sep  7 14:59:46 vdr vdr[1895]: loading /video/timers.conf
> > Sep  7 14:59:47 vdr vdr[1895]: loading /video/svdrphosts.conf
> > Sep  7 14:59:47 vdr vdr[1895]: loading /video/ca.conf
> > Sep  7 14:59:47 vdr vdr[1895]: loading /video/remote.conf
> > Sep  7 14:59:47 vdr vdr[1895]: loading /video/keymacros.conf
> > Sep  7 14:59:47 vdr vdr[1895]: found 2 video devices
> > Sep  7 14:59:47 vdr vdr[1895]: setting primary device to 1
> > Sep  7 14:59:47 vdr vdr[1895]: SVDRP listening on port 2001
> > Sep  7 14:59:47 vdr vdr[1895]: switching to channel 1
>
> At this point newer developer versions log this:
>
> Sep  7 16:14:14 video vdr[863]: loading /video/timers.conf
> Sep  7 16:14:14 video vdr[863]: ERROR: channel S19.2E-1-0-28106 not defined
> Sep  7 16:14:14 video vdr[863]: ERROR: error in /video/timers.conf, line 22
>
> > 5.) Reopend OSD/timers. timer gone
>
> Newer developer versions don't get that far, due to the above error.
>
> The problem here is that you have used an invalid combination of NID and
> TID. If NID is not 0, TID must not be 0, too, because that's an invalid
> TID.
>
> Use a TID other than 0 and it works.
>
> Klaus


So we are back at 'scan'. It not only sets a NID for VDR output, it also 
forgets the 'TID'. Here's the according output from scan:
ARD - Das Erste:11836:h:S19.2E:27500:101:102:104:0:28106:1:0:0

Nevertheless it's funny VDR first accept the timer and also process them as 
long as VDR was not restarted since timer creation. Wouldn't it better if the 
timer creation fails or maybe even the in vdr 1.2.5pre introduced check on 
the config files would detect the error?











-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.