Hi,
I'm trying to find some replacement for vdradmin that would be a bit more reliable than the am-versions, and newer than the original vdradmin 1.96. The 1.96 has so far been working best with the auto timers if compared with the am-versions of vdradmin. The biggest problem with the am-versions of vdradmin was that I got recordings that claimed to be e.g. Alias, but what was recorded was completely something else. Other problems with auto timers was that I got a bunch of identical timers, and if I did not clean up my timers on regular basis, I got the many programs recorded multiple times.
If someone has any suggestions for a vdradmin-replacement, then they are welcome :-)
Regards,
René
Rene Hertell wrote:
If someone has any suggestions for a vdradmin-replacement, then they are welcome :-)
I don't have a suggestion, but some questions first: Which vdr version are you using? Which was the latest vdradmin version you have been using?
I'm running vdr-1.3.37 here with vdradmin-0.97-am3.3. It is stable, the recodings are fine and autotimer works as it should.
The latest stable verison can be found here: http://andreas.vdr-developer.org/download/vdradmin-0.97-am3.4.2.tar.bz2
The one that is working with >=1.3.38 is still an RC, but you can give it a try. The stable version will probably come this week: http://andreas.vdr-developer.org/download/vdradmin-am-3.4.3rc.tar.bz2
André
André Weidemann wrote:
I don't have a suggestion, but some questions first: Which vdr version are you using?
When i had those problems, I was running vdr 1.3.37
Which was the latest vdradmin version you have been using?
0.97-am3.4.2
I'm running vdr-1.3.37 here with vdradmin-0.97-am3.3. It is stable, the recodings are fine and autotimer works as it should.
It's strange.. I had soo much trouble with the autotimer, especially when I gout multiple entrys showing up for the same recording, and wrong titles for recordings i don't even had a timer or autotimer for..
http://andreas.vdr-developer.org/download/vdradmin-am-3.4.3rc.tar.bz2
Is there any changelog for this release-candidate?
Regards,
René
Rene Hertell wrote:
Is there any changelog for this release-candidate?
The changelog can be found here: http://www.vdrportal.de/board/thread.php?threadid=42457
If vdradmin is causing so many problems, maybe you can post them there and get some help...
André
André Weidemann writes:
If vdradmin is causing so many problems, maybe you can post them there and get some help...
Well, these problems are well known. They might not appear with the epg data received by the vdradmin's author, so we just have to fix them ourselves.
First - NO_EVENTID = 1 to the config file, and then, if you get lots of duplicates (which I get with an earlier version of vdradmin) fix the broken updating of autotimers in the source code (by disabling it).
yours, Jouni
On Wednesday 25 January 2006 10:10, Jouni Karvo wrote:
André Weidemann writes:
If vdradmin is causing so many problems, maybe you can post them there and get some help...
Well, these problems are well known. They might not appear with the epg data received by the vdradmin's author, so we just have to fix them ourselves.
First - NO_EVENTID = 1 to the config file, and then, if you get lots of duplicates (which I get with an earlier version of vdradmin) fix the broken updating of autotimers in the source code (by disabling it).
yours, Jouni
How can I "fix the broken updating of autotimers in the source code (by disabling it)"? I'm not aware of such a problem/fix. Maybe you can post the fix here and I will include it if it's worth?
Regards, Andreas
Jouni Karvo wrote:
Well, these problems are well known. They might not appear with the epg data received by the vdradmin's author, so we just have to fix them ourselves.
I assume that this is because the Finnish epg-data is messed up?
For example. I have C.S.I as an autotimer. Today I got two entrys for upcoming Sunday (both for the same channel). One that starts at 22:34 and ends at 23:40 (which is correct), and an other that starts at 22:05 and ends at 23:40 (which is wrong). I have set up the autotimer to start 1 (one) minute before the actual program starts (here in Finland no program starts on time except for News)
Here is the current schedule for that time frame that the second timer uses:
22:00 - 22:15 Kymmenen Uutiset (News) 22:15 - 22:25 Viikon sää (weather forcast) 22:25 - 22:35 Tulosruutu (Sports) 22:35 - 23:30 C.S.I. Miami
Somehow there is no logic in this. The second timer starts more or less in the middle of the news..
First - NO_EVENTID = 1 to the config file, and then, if you get lots of duplicates (which I get with an earlier version of vdradmin) fix the broken updating of autotimers in the source code (by disabling it).
I tried to tweak the no_eventid = 1 also, but I got more than 10 entrys for the same recording...
What part of the vdradmin-script did you tweak? How reliable was it?
Regards,
René
hi
Rene Hertell writes:
I tried to tweak the no_eventid = 1 also, but I got more than 10 entrys for the same recording...
What part of the vdradmin-script did you tweak? How reliable was it?
yes, this is exactly the thing you need to tweak in the vdradmin script.
I do not have my patch at hand, but it should be easy to find. There is a place in the code where vdradmin "updates" the autotimers. In practice this means that it - moves the recording to start earlier than it should start - then creates a new timer later to the actual time where it should be
This goes on and the number of timers grows. Just disabling this "update" will cure your symptoms.
For A Mair - I have sent it to you earlier. I know now how to fix it for me, so why should I care.
yours, Jouni
Jouni Karvo wrote:
I do not have my patch at hand, but it should be easy to find. There is a place in the code where vdradmin "updates" the autotimers. In practice this means that it
- moves the recording to start earlier than it should start
- then creates a new timer later to the actual time where it should be
This goes on and the number of timers grows. Just disabling this "update" will cure your symptoms.
I guess that you are talking about a subfunction in the CheckTimers sub? Or did you disable the whole CheckTimers sub?
René
Rene Hertell writes:
I guess that you are talking about a subfunction in the CheckTimers sub? Or did you disable the whole CheckTimers sub?
Just disable the check for autotimers without eventid. It has a complicated if () condition which is supposed to check the start time (and perhaps the end time - I do not remember) of the event. If I remember correctly, this if () thing appears there twice.
yours, Jouni
Jouni Karvo wrote:
Just disable the check for autotimers without eventid. It has a complicated if () condition which is supposed to check the start time (and perhaps the end time - I do not remember) of the event. If I remember correctly, this if () thing appears there twice.
Argh.. :-( My eyes are already bleeding... Can't figure out where that failing if() condition resides..
I guess that I'll skip vdradmin and try the epg-search plugin till there will be a new version fixes this this bug..
René
Rene Hertell wrote:
Hi,
I'm trying to find some replacement for vdradmin that would be a bit more reliable than the am-versions, and newer than the original vdradmin 1.96. The 1.96 has so far been working best with the auto timers if compared with the am-versions of vdradmin. The biggest problem with the am-versions of vdradmin was that I got recordings that claimed to be e.g. Alias, but what was recorded was completely something else. Other problems with auto timers was that I got a bunch of identical timers, and if I did not clean up my timers on regular basis, I got the many programs recorded multiple times.
If someone has any suggestions for a vdradmin-replacement, then they are welcome :-)
If you 'only' need something for automatic recording and can live without a web-frontend then you may try Master-Timer.
http://mt.citd.de/master-timer-0.6.3b.tar.bz2
As long as the EPG-Data is good you can use the 'done' functionality to remove Timers for reruns after the recording was successful.
Master-Timer reaches it's 5th birthday (and VDR it's 6th) in about a month and i can say that at least for myself it has always been reliable. :-)
Bis denn
On Mon, Jan 23, 2006 at 09:10:48PM +0100, Matthias Schniedermeyer wrote:
If you 'only' need something for automatic recording and can live without a web-frontend then you may try Master-Timer.
http://mt.citd.de/master-timer-0.6.3b.tar.bz2
As long as the EPG-Data is good you can use the 'done' functionality to remove Timers for reruns after the recording was successful.
That's a really nice tool, and deepblack is also a solution for not so good epg :)
My only problem is that i have "only" two cards ;)
Gregoire Favre wrote:
On Mon, Jan 23, 2006 at 09:10:48PM +0100, Matthias Schniedermeyer wrote:
If you 'only' need something for automatic recording and can live without a web-frontend then you may try Master-Timer.
http://mt.citd.de/master-timer-0.6.3b.tar.bz2
As long as the EPG-Data is good you can use the 'done' functionality to remove Timers for reruns after the recording was successful.
That's a really nice tool, and deepblack is also a solution for not so good epg :)
Is there something that i missed? I can't see how a blacklist can help with bad data.
My only problem is that i have "only" two cards ;)
Same problem here, buth with 3 complete systems. And i also have a/the problem with storage-space. :-)
Bis denn
On Mon, Jan 23, 2006 at 11:01:21PM +0100, Matthias Schniedermeyer wrote:
Is there something that i missed? I can't see how a blacklist can help with bad data.
As the process_summary.pl don't have any effect here, I have written some scripts to deal with my reccording, some have good title and good subtitle which are perfect for done, but some have title, no subtitle but a description which is good enough to write it in deepblack.
I don't know if it's me who have missed something, for example how to deal with process_summary.pl ? In that case, I would really enjoy to know about it :)
Thank,
Gregoire Favre wrote:
On Mon, Jan 23, 2006 at 11:01:21PM +0100, Matthias Schniedermeyer wrote:
Is there something that i missed? I can't see how a blacklist can help with bad data.
As the process_summary.pl don't have any effect here.
1.3.<current> VDR?
Send a few info.vdrs then i can test them. The code wasn't tested on real files. :-)
I have written some scripts to deal with my reccording, some have good title and good subtitle which are perfect for done, but some have title, no subtitle but a description which is good enough to write it in deepblack.
I've something similar implemented in Master-Timer, but only for a few specific channels. If there is NO subtitle but a description then MD5 the description and put it into the subtitle.
This is equivalent to your method of putting the description into deepblack. (Except that e.g. case-changes will generate another MD5 but deepblack is case-insensitive)
But if i change the MD5-generation a bit and activate it for all channels it may be the solution for you. -> Kill subtitle if the subtitle equals the title (e.g. Pro 7) -> Convert the description to lowercase -> Strip whitespaces and punctuation from the description then MD5 it and put it into the subtitle. This is a bit more robust against 'subtle' changes in the text which would make it 'binary different' otherwise.
OTOH MD5-Sums as subtitles aren't exactly good for the WAF. :-)
Hmm. I guess a 'generate MD5 sums for bad subtitles'-config-option is appropriate. :-)
I don't know if it's me who have missed something, for example how to deal with process_summary.pl ? In that case, I would really enjoy to know about it :)
It may be that my info.vdr-code doesn't function properly. :-)
Bis denn
Rene Hertell wrote:
Hi,
I'm trying to find some replacement for vdradmin that would be a bit more reliable than the am-versions, and newer than the original vdradmin 1.96. The 1.96 has so far been working best with the auto timers if compared with the am-versions of vdradmin. The biggest problem with the am-versions of vdradmin was that I got recordings that claimed to be e.g. Alias, but what was recorded was completely something else. Other problems with auto timers was that I got a bunch of identical timers, and if I did not clean up my timers on regular basis, I got the many programs recorded multiple times.
If someone has any suggestions for a vdradmin-replacement, then they are welcome :-)
I also do not have a suggestion but can confirm similar programs. I have to delete scheduled timers for Enterpise (on sat.1, broadcasted sundays) on monday and tuesday every week. Does anyone else also has these problems or does even know how to solve them? I'm curently using vdr-1.3.40 and vdradmin-0.97-am3.4.2 with the patch provided by Dave P vdr@pickles.me.uk here on the list.
So long,
-
Andreas Mair -
André Weidemann -
Gregoire Favre -
Jouni Karvo -
Matthias Schniedermeyer -
Patrick Cernko -
Rene Hertell