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.
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?
I should have also mentioned that this is *not* a problem with the latest "stable" release of vdradmin (vdradmin-0.97-am3.4.1). I only see the problem with the latest release candidates. I will check lstt and send back.
Best Regards,
C.Y.M wrote:
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.
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?
I should have also mentioned that this is *not* a problem with the latest "stable" release of vdradmin (vdradmin-0.97-am3.4.1). I only see the problem with the latest release candidates. I will check lstt and send back.
I do not see any problems with the lstt output. Is there something specific I need to be searching for?
Regards,
Hi,
On Monday 07 November 2005 12:56, C.Y.M wrote:
C.Y.M wrote:
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.
What do you mean when you're talking about "wrong recordings"? Did VDRAdmin program wrong timers or do you mean the blinking "Rec".
This applies too on single recordings created with vdradmin.
All recent VDR (patched with subtitles, many plugins) versions have had this.
Again: what did they have?
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?
I should have also mentioned that this is *not* a problem with the latest "stable" release of vdradmin (vdradmin-0.97-am3.4.1). I only see the problem with the latest release candidates. I will check lstt and send back.
Since v3.4.2rc VDRAdmin uses the timer status flag as reported by VDR.
I do not see any problems with the lstt output. Is there something specific I need to be searching for?
Can you please send the output to me via PM?
Regards, Andreas
Hi,
another thing that came to my mind: are you talking about repeating timers that are really recording at that moment? In that case every shown repetition of that timer will have a blinking "Rec". This will be fixed soon.
Regards, Andreas
On Tuesday 08 November 2005 15:50, Andreas Mair wrote:
Hi,
On Monday 07 November 2005 12:56, C.Y.M wrote:
C.Y.M wrote:
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.
What do you mean when you're talking about "wrong recordings"? Did VDRAdmin program wrong timers or do you mean the blinking "Rec".
This applies too on single recordings created with vdradmin.
All recent VDR (patched with subtitles, many plugins) versions have had this.
Again: what did they have?
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?
I should have also mentioned that this is *not* a problem with the latest "stable" release of vdradmin (vdradmin-0.97-am3.4.1). I only see the problem with the latest release candidates. I will check lstt and send back.
Since v3.4.2rc VDRAdmin uses the timer status flag as reported by VDR.
I do not see any problems with the lstt output. Is there something specific I need to be searching for?
Can you please send the output to me via PM?
Regards, Andreas
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Andreas Mair wrote:
Hi,
another thing that came to my mind: are you talking about repeating timers that are really recording at that moment? In that case every shown repetition of that timer will have a blinking "Rec". This will be fixed soon.
Nothing is currently recording at the time. But, the blinking "Rec" light is active on several timers throughout the week. This reminds of a similar problem I have had with the Timeline plugin. People with more than one DVB card do not see this problem.
Since v3.4.2rc VDRAdmin uses the timer status flag as reported by VDR.
Ah, ok. Now I understand why it is different. I think the Timeline plugin utilizes the same flag.
I do not see any problems with the lstt output. Is there something specific I need to be searching for?
Can you please send the output to me via PM?
yes.
Hi,
On Tuesday 08 November 2005 22:38, C.Y.M wrote:
Andreas Mair wrote:
Hi,
another thing that came to my mind: are you talking about repeating timers that are really recording at that moment? In that case every shown repetition of that timer will have a blinking "Rec". This will be fixed soon.
Nothing is currently recording at the time. But, the blinking "Rec" light is active on several timers throughout the week. This reminds of a similar problem I have had with the Timeline plugin. People with more than one DVB card do not see this problem.
I don't use the Timeline plugin and my VDR box has two DVB-S cards but I once had a wrong status flag in "lstt". Unfortunately I had not been able to reproduce it later :(
Since v3.4.2rc VDRAdmin uses the timer status flag as reported by VDR.
Ah, ok. Now I understand why it is different. I think the Timeline plugin utilizes the same flag.
I don't use the Timeline plugin.
Regards, Andreas
On Tue, 2005-11-08 at 15:50 +0100, Andreas Mair wrote:
Hi,
On Monday 07 November 2005 12:56, C.Y.M wrote:
C.Y.M wrote:
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.
What do you mean when you're talking about "wrong recordings"? Did VDRAdmin program wrong timers or do you mean the blinking "Rec".
In my case, a simple one-time recording done from vdradmin has sometimes (enough for me to stop setting timers from it) behaved so that when the timer is set, it looks correct right after the creation. But after some time (in the order of day or two) passes, it has changed to something entirely different, and a completely wrong program has been recorded unless I've noticed the change and had a chance to fix it manually. I don't have better details right now, sorry.
I'm not at all sure if this is a vdradmin-only thing as there has been several issues with the EPG of some Finnish channels in vdr too, though. But I *think* it has occurred more often with vdradmin than with timers set directly from vdr. Will try to keep an eye on it.
Hi,
On Tuesday 08 November 2005 21:58, Ville Skyttä wrote:
On Tue, 2005-11-08 at 15:50 +0100, Andreas Mair wrote:
Hi,
On Monday 07 November 2005 12:56, C.Y.M wrote:
C.Y.M wrote:
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.
What do you mean when you're talking about "wrong recordings"? Did VDRAdmin program wrong timers or do you mean the blinking "Rec".
In my case, a simple one-time recording done from vdradmin has sometimes (enough for me to stop setting timers from it) behaved so that when the timer is set, it looks correct right after the creation. But after some time (in the order of day or two) passes, it has changed to something entirely different, and a completely wrong program has been recorded unless I've noticed the change and had a chance to fix it manually. I don't have better details right now, sorry.
Did you have "AutoTimer Checking" set to "Transmission Identification"? In this case VDRAdmin will check the EPG ID and will record the event having that EPG ID. If the EPG ID is changed for events by the broadcasting company different events will be recorded. Can you please check if that's the case?
I'm not at all sure if this is a vdradmin-only thing as there has been several issues with the EPG of some Finnish channels in vdr too, though. But I *think* it has occurred more often with vdradmin than with timers set directly from vdr. Will try to keep an eye on it.
It also happened with timers programmed in VDR? Don't know why.
Regards, Andreas
Andreas Mair wrote:
Did you have "AutoTimer Checking" set to "Transmission Identification"? In this case VDRAdmin will check the EPG ID and will record the event having that EPG ID. If the EPG ID is changed for events by the broadcasting company different events will be recorded. Can you please check if that's the case?
I have used this option, but I find that the EPG was correct, the program had not moved - but I'm not sure what's the EPG ID or how to check it.
BR, Jarmo
Hi Jarmo,
On Wednesday 09 November 2005 10:14, Jarmo Järvenpää wrote:
Andreas Mair wrote:
Did you have "AutoTimer Checking" set to "Transmission Identification"? In this case VDRAdmin will check the EPG ID and will record the event having that EPG ID. If the EPG ID is changed for events by the broadcasting company different events will be recorded. Can you please check if that's the case?
I have used this option, but I find that the EPG was correct, the program had not moved - but I'm not sure what's the EPG ID or how to check it.
In timer_list point your mouse to the timer's title. It should be a link. In the status bar you can read the epg_id. Or you click the link and the popup will show the epg_id in the URL bar.
Regards, Andreas
On Wed, 2005-11-09 at 08:55 +0100, Andreas Mair wrote:
Hi,
On Tuesday 08 November 2005 21:58, Ville Skyttä wrote:
In my case, a simple one-time recording done from vdradmin has sometimes (enough for me to stop setting timers from it) behaved so that when the timer is set, it looks correct right after the creation. But after some time (in the order of day or two) passes, it has changed to something entirely different, and a completely wrong program has been recorded unless I've noticed the change and had a chance to fix it manually. I don't have better details right now, sorry.
Did you have "AutoTimer Checking" set to "Transmission Identification"?
Yes, that seems to be the default, and I don't remember ever changing it.
In this case VDRAdmin will check the EPG ID and will record the event having that EPG ID. If the EPG ID is changed for events by the broadcasting company different events will be recorded. Can you please check if that's the case?
Could be, makes sense. I'm currently running vdr with "-E-" to see if it prevents the duplicates, so I don't have an epg.data available where I could check. Later, maybe...
On Wed 2005-11-09 16:57, Ville Skyttä wrote
In my case, a simple one-time recording done from
vdradmin has sometimes
(enough for me to stop setting timers from it) behaved so
that when the
timer is set, it looks correct right after the creation.
But after some
time (in the order of day or two) passes, it has changed
to something
entirely different, and a completely wrong program has
been recorded
unless I've noticed the change and had a chance to fix it
manually. I
don't have better details right now, sorry.
Did you have "AutoTimer Checking" set to "Transmission
Identification"?
Yes, that seems to be the default, and I don't remember ever changing it.
In this case VDRAdmin will check the EPG ID and will record
the event having
that EPG ID. If the EPG ID is changed for events by the
broadcasting
company different events will be recorded. Can you please check if that's the case?
Could be, makes sense. I'm currently running vdr with "-E-" to see if it prevents the duplicates, so I don't have an epg.data available where I could check. Later, maybe...
I have noticed that especially in Finnland on channel "Nelonen" the EPG data is corrupted. That is there are missing program information, faulty times, double or even tripple instances of the same program with same or slightly different timings. This ofcourse means that someone should get in contact with "Nelonen" to inform them about these things. To do that it would be nice to have some utility that could be collecting EPG info on selected channel(s) to back up these "accusations" :)
My EPG bugfix level is set to 0.
// Kartsa
Hi,
With wrong recordings I mean recordings with a correct name but time different than intended.
For example, last sunday there was a 2-hour movie shown, made a timer (date, channel and time were correct) and checked the recording status on monday - length of recording was 14 minutes and start time was 5 hours after the movie had ended.
Also, there has been recordings with a correct time but with wrong program name. This was ok, at least recordings were made but the ones with wrong starting time and length :-/
Application versions which I've used and problem has been there; VDR versions at least from 1.3.28 --> vdradmin-0.97-am3.4 Plugins: vdr-epgsearch-0.9.7 vdr-femon-0.9.4 vdr-mp3-0.9.13 vdr-osdteletext-0.5.1 vdr-subtitles-0.3.8 vdr-dxr3-0.2.3
BR, Jarmo
Andreas Mair wrote:
Hi,
On Monday 07 November 2005 12:56, C.Y.M wrote:
C.Y.M wrote:
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.
What do you mean when you're talking about "wrong recordings"? Did VDRAdmin program wrong timers or do you mean the blinking "Rec".
This applies too on single recordings created with vdradmin.
All recent VDR (patched with subtitles, many plugins) versions have had this.
Again: what did they have?
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?
I should have also mentioned that this is *not* a problem with the latest "stable" release of vdradmin (vdradmin-0.97-am3.4.1). I only see the problem with the latest release candidates. I will check lstt and send back.
Since v3.4.2rc VDRAdmin uses the timer status flag as reported by VDR.
I do not see any problems with the lstt output. Is there something specific I need to be searching for?
Can you please send the output to me via PM?
Regards, Andreas
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
On Wednesday 09 November 2005 10:09, Jarmo Järvenpää wrote:
Hi,
With wrong recordings I mean recordings with a correct name but time different than intended.
For example, last sunday there was a 2-hour movie shown, made a timer (date, channel and time were correct) and checked the recording status on monday - length of recording was 14 minutes and start time was 5 hours after the movie had ended.
Also, there has been recordings with a correct time but with wrong program name. This was ok, at least recordings were made but the ones with wrong starting time and length :-/
And that's only the case when programming timers using VDRAdmin?
Did you have "AutoTimer Checking" set to "Transmission Identification"? In this case VDRAdmin will check the EPG ID and will record the event having that EPG ID. If the EPG ID is changed for events by the broadcasting company different events will be recorded. Can you please check if that's the case?
Regards, Andreas
Application versions which I've used and problem has been there; VDR versions at least from 1.3.28 --> vdradmin-0.97-am3.4 Plugins: vdr-epgsearch-0.9.7 vdr-femon-0.9.4 vdr-mp3-0.9.13 vdr-osdteletext-0.5.1 vdr-subtitles-0.3.8 vdr-dxr3-0.2.3
BR, Jarmo
Andreas Mair wrote:
Hi,
On Monday 07 November 2005 12:56, C.Y.M wrote:
C.Y.M wrote:
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.
What do you mean when you're talking about "wrong recordings"? Did VDRAdmin program wrong timers or do you mean the blinking "Rec".
This applies too on single recordings created with vdradmin.
All recent VDR (patched with subtitles, many plugins) versions have had this.
Again: what did they have?
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?
I should have also mentioned that this is *not* a problem with the latest "stable" release of vdradmin (vdradmin-0.97-am3.4.1). I only see the problem with the latest release candidates. I will check lstt and send back.
Since v3.4.2rc VDRAdmin uses the timer status flag as reported by VDR.
I do not see any problems with the lstt output. Is there something specific I need to be searching for?
Can you please send the output to me via PM?
Regards, Andreas
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
Andreas Mair wrote:
Also, there has been recordings with a correct time but with wrong program name. This was ok, at least recordings were made but the ones with wrong starting time and length :-/
And that's only the case when programming timers using VDRAdmin?
Indeed yes. With VDR's timer recordings or with the epgsearch's autorecordings there has been no 'wrong' recordings.
Did you have "AutoTimer Checking" set to "Transmission Identification"? In this case VDRAdmin will check the EPG ID and will record the event having that EPG ID. If the EPG ID is changed for events by the broadcasting company different events will be recorded. Can you please check if that's the case?
I'll create timer now and see if it changes.
BR, Jarmo
-
Andreas Mair -
C.Y.M -
Jarmo Järvenpää -
Kartsa -
Ville Skyttä