I have been testing vdradmin-0.97-am3.4.2rc3 from vdrportal.de and have come across a bug that I can not explain. When I check the "Timers" page, it shows the recording light on several timers scheduled throughout the week. For example, today is Sunday, but the timer page says that the timers scheduled on Wednesday and Friday are currently running. Has anyone else noticed this problem?
Best Regards,
Hi,
which VDR version are you using? I guess it's >=1.3.24. In this case VDRAdmin uses the status flags returned by "lstt". So it might be a bug in VDR. I once had a wrong "recording" identification, but failed to reproduce it. So if it's reproduceable for you, I think Klaus would like to know if it's also the case with vanilla VDR (without patches/plugins).
Kind regards, Andreas
On Sunday 06 November 2005 09:42, C.Y.M wrote:
I have been testing vdradmin-0.97-am3.4.2rc3 from vdrportal.de and have come across a bug that I can not explain. When I check the "Timers" page, it shows the recording light on several timers scheduled throughout the week. For example, today is Sunday, but the timer page says that the timers scheduled on Wednesday and Friday are currently running. Has anyone else noticed this problem?
Best Regards,
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
I've forgotten one thing: could you please send "lstt" to the VDR port and check what the timer status (the value in front of the first ":") is.
On Monday 07 November 2005 11:49, Andreas Mair wrote:
Hi,
which VDR version are you using? I guess it's >=1.3.24. In this case VDRAdmin uses the status flags returned by "lstt". So it might be a bug in VDR. I once had a wrong "recording" identification, but failed to reproduce it. So if it's reproduceable for you, I think Klaus would like to know if it's also the case with vanilla VDR (without patches/plugins).
Kind regards, Andreas
On Sunday 06 November 2005 09:42, C.Y.M wrote:
I have been testing vdradmin-0.97-am3.4.2rc3 from vdrportal.de and have come across a bug that I can not explain. When I check the "Timers" page, it shows the recording light on several timers scheduled throughout the week. For example, today is Sunday, but the timer page says that the timers scheduled on Wednesday and Friday are currently running. Has anyone else noticed this problem?
Best Regards,
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
I have seen this many times too. I used to use vdradmin and it's autotimers until got frustrated on the number of wrong recordings.
This applies too on single recordings created with vdradmin.
All recent VDR (patched with subtitles, many plugins) versions have had this.
BR, Jarmo
Andreas Mair wrote:
Hi,
which VDR version are you using? I guess it's >=1.3.24. In this case VDRAdmin uses the status flags returned by "lstt". So it might be a bug in VDR. I once had a wrong "recording" identification, but failed to reproduce it. So if it's reproduceable for you, I think Klaus would like to know if it's also the case with vanilla VDR (without patches/plugins).
Kind regards, Andreas
On Sunday 06 November 2005 09:42, C.Y.M wrote:
I have been testing vdradmin-0.97-am3.4.2rc3 from vdrportal.de and have come across a bug that I can not explain. When I check the "Timers" page, it shows the recording light on several timers scheduled throughout the week. For example, today is Sunday, but the timer page says that the timers scheduled on Wednesday and Friday are currently running. Has anyone else noticed this problem?
Best Regards,
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Mon, 2005-11-07 at 13:08 +0200, Jarmo Järvenpää wrote:
I have seen this many times too. I used to use vdradmin and it's autotimers until got frustrated on the number of wrong recordings.
This applies too on single recordings created with vdradmin.
All recent VDR (patched with subtitles, many plugins) versions have had this.
Seconded, same problems witnessed here. I haven't tried am3.4.2rc* yet.