From: "Andreas Mair" mail@andreas.vdr-developer.org
Hi,
On Sunday 18 December 2005 22:27, Kartsa wrote:
Just updated my vdradmin to version vdradmin-0.97-am3.4.2. After the update there has been appearing recordings wich have been created by autotimers but they either have wrong name or wrong recording time.
You mean, that the recording's name does not match the autotimer's pattern?
This is excactly what I mean.
Can you please provide an example and what options you have set (search in title, subtitle and/or description)?
This is what I have in autotimers - Search string "big brother" from title - every weekday - channel subtv - no starting or ending times - priority 50 - lifetime 99 => 1:big brother:1:::0:50:99:C-0-2-97::0:1111111
and another one
- Search string "idols" from title - every weekday - channel subtv - no starting or ending times - priority 50 - lifetime 99 => 1:idols:1:::0:50:99:C-0-2-97::0:1111111
I have set 1 min before and 10 mins after boundaries
From 9 pm to 9:30 pm was Idols extra and 9:30pm to 10pm was Big brother
I ended up with two recordings 1. Idols extra beginning from 8:59pm 2. Idols extra beginning from 9:29pm
This is from the log Dec 18 20:59:01 kartzan vdr[6564]: timer 29 (5 2059-2140 'Idols Extra') start Dec 18 20:59:01 kartzan vdr[6564]: Title: 'Idols Extra' Subtitle: 'Suorassa Idols Extrassa vierailevat illan viimeiset finalistit.' Dec 18 20:59:01 kartzan vdr[6564]: record /video/Idols_Extra/2005-12-18.20:59.50.99.rec Dec 18 20:59:01 kartzan vdr[6564]: creating directory /video/Idols_Extra Dec 18 20:59:01 kartzan vdr[6564]: creating directory /video/Idols_Extra/2005-12-18.20:59.50.99.rec Dec 18 20:59:05 kartzan vdr[6564]: recording to '/video/Idols_Extra/2005-12-18.20:59.50.99.rec/001.vdr' and Dec 18 21:29:00 kartzan vdr[6564]: timer 17 (5 2129-2210 'Idols Extra') start Dec 18 21:29:00 kartzan vdr[6564]: Title: 'Big Brother: Missä he ovat nyt?' Subtitle: 'Ohjelmassa kuullaan Suomen BB-kilpailijoiden tuoreimmat kuulumiset: Mitä kukakin tahollaan tekee ja miten Big Brotheriin osallistuminen on vaikuttanut kilpailijoiden arkeen?' Dec 18 21:29:00 kartzan vdr[6564]: record /video/Idols_Extra/2005-12-18.21:29.50.99.rec Dec 18 21:29:00 kartzan vdr[6564]: creating directory /video/Idols_Extra/2005-12-18.21:29.50.99.rec Dec 18 21:29:04 kartzan vdr[6564]: recording to '/video/Idols_Extra/2005-12-18.21:29.50.99.rec/001.vdr'
As you can see the titles of the programs are quite right but the timer names are wrong and the recording is done to false directory.
The recording's start/stop time is outside the start/stop time you set in the autotimer? Can you give an example?
This recording has no autotimer entry unless you take the big brother entry as the autotimer for this one since it is named after it. Dec 18 21:59:00 kartzan vdr[6564]: timer 18 (5 2159-2240 'Big Brother: Missä he ovat nyt?') start Dec 18 21:59:00 kartzan vdr[6564]: Title: 'Yö Rakelin kanssa' Subtitle: 'Helsinkiläistä runoilijaa, kirjailijaa ja opettajaa Arno Kotroa on ti tuleerattu mm. "suomirunon uudeksi poptähdeksi". Sanovat sitä rakkaudeksi -esikoisteos sai jatkoa Musta morsian -kirjasta, ja mies on tuttu nä ky niin lehtien pal' Dec 18 21:59:00 kartzan vdr[6564]: record /video/Big_Brother:_Missä_he_ovat_nyt?/2005-12-18.21:59.50.99.rec Dec 18 21:59:00 kartzan vdr[6564]: creating directory /video/Big_Brother:_Missä_he_ovat_nyt? Dec 18 21:59:00 kartzan vdr[6564]: creating directory /video/Big_Brother:_Missä_he_ovat_nyt?/2005-12-18.21:59.50.99.rec Dec 18 21:59:04 kartzan vdr[6564]: recording to '/video/Big_Brother:_Missä_he_ovat_nyt?/2005-12-18.21:59.50.99.rec/001.vdr'
I have not yet had missing recordings but these recordings with wrong names are hard to find :) And those unattended recordings takes up disk space for nothing :(
You're talking about recordings triggered by autotimer you don't expect? Maybe you have the wrong patterns?
As you see the patterns can no meens be found from the titles :)
The funny thing is that there was no problems with the earlier version I was using (vdradmin-0.97-am3.1).
Regards, Andreas --
BR, Kartsa
Anyone ever make this patch? I tried to modify the one for .36 but it didnt like it, I had this error trying to run VDR:
*** glibc detected *** malloc(): memory corruption: 0x0a253680 ***
Anyone Successfully have SourceCaps working with .37? I have a DVB card waiting for its functionality.
Thanks!
hi,
From 9 pm to 9:30 pm was Idols extra and 9:30pm to 10pm was Big brother
I ended up with two recordings
- Idols extra beginning from 8:59pm
- Idols extra beginning from 9:29pm
I have had a similar bug, and wrote a quick and dirty solution for this (sent it to Andreas Mair also, but he probably has not had time to check it out).
If this is the same bug, then the problem is in the autotimer update code, where vdradmin first changes a recording to start the time where the time to add in the beginning is subtracted from the start time, and after this notices at some point that there is no autotimer for the correct time, and adds one to that time. VDR naturally takes the correct recording name (the program that was before in the schedule) for the one starting too early.
This happens when Event_ID is not used for autotimers.
The weird thing is that my problem was there with the earlier version...
yours, Jouni
Hi,
On Tuesday 20 December 2005 08:04, Jouni Karvo wrote:
I have had a similar bug, and wrote a quick and dirty solution for this (sent it to Andreas Mair also, but he probably has not had time to check it out).
Sorry, I can't find this patch, I even can't remember that I got one. Seems I'm getting old...
Could you please send it again?
Regards, Andreas
Hi,
I've made some changes in that part in VDRAdmin-AM v3.4.3rc2. Maybe you want to try it and report if it works better now?
You can download it at http://andreas.vdr-developer.org/en/index.html
Regards, Andreas On Tuesday 20 December 2005 08:04, Jouni Karvo wrote:
hi,
From 9 pm to 9:30 pm was Idols extra and 9:30pm to 10pm was Big brother
I ended up with two recordings
- Idols extra beginning from 8:59pm
- Idols extra beginning from 9:29pm
I have had a similar bug, and wrote a quick and dirty solution for this (sent it to Andreas Mair also, but he probably has not had time to check it out).
If this is the same bug, then the problem is in the autotimer update code, where vdradmin first changes a recording to start the time where the time to add in the beginning is subtracted from the start time, and after this notices at some point that there is no autotimer for the correct time, and adds one to that time. VDR naturally takes the correct recording name (the program that was before in the schedule) for the one starting too early.
This happens when Event_ID is not used for autotimers.
The weird thing is that my problem was there with the earlier version...
yours, Jouni
Hi,
tried this. First impression is that now it works - but it is too early to say anything definitive - have to wait at least until tomorrow.
yours, Jouni
I've noticed that in my current system if I delete all timers and start all from "scratch" it takes few days bafore it starts to appear duplicate/wrong timers. But lets give this version a try :)
\Kartsa
Hi,
tried this. First impression is that now it works - but it is too early to say anything definitive - have to wait at least until tomorrow.
yours, Jouni
hi,
I've made some changes in that part in VDRAdmin-AM v3.4.3rc2. Maybe you want to try it and report if it works better now?
After about one week of use: So far there has been one weird recording, but at least most of the problems seem fixed.
Thanks!
yours, Jouni
Hi,
I've made some changes in that part in VDRAdmin-AM v3.4.3rc2. Maybe you want to try it and report if it works better now?
After about one week of use: So far there has been one weird recording, but at least most of the problems seem fixed.
What do you mean if you're talking about "one wired recording"?
Regards, Andreas
hi,
Andreas Mair writes:
After about one week of use: So far there has been one weird recording, but at least most of the problems seem fixed.
What do you mean if you're talking about "one wired recording"?
I mean "weird". I mean something not in EPG, lasting for _hours_. Things like that sometimes happen. The timer was generated by vdradmin but possibly from an EPG bug. I did not have energy to dig deeper. I'll do that if that kind of things continue to occur. But since they are obviously so infrequent it will be more difficult.
yours, Jouni
On Tue, 14 Feb 2006, Jouni Karvo wrote:
hi,
Andreas Mair writes:
After about one week of use: So far there has been one weird recording, but at least most of the problems seem fixed.
What do you mean if you're talking about "one wired recording"?
I mean "weird". I mean something not in EPG, lasting for _hours_. Things like that sometimes happen. The timer was generated by vdradmin but possibly from an EPG bug. I did not have energy to dig deeper. I'll do that if that kind of things continue to occur. But since they are obviously so infrequent it will be more difficult.
Hi,
I almost got one whole day recording, but luckily noticed it on timers and deleted it. Lately I've been getting some timers twice and for some weird reason I've got two times timer for Galactica for saturday, while it's broadcasted only on friday and I've added that to the autotimer, ie. friday only...
So far all MTV3 recordings/timers are okay. Some subtv timers have been doupled and nelonen has these Galactica bugs and also some timers have been doupled.
Forgot now when or from which channel was this whole day timer.
Also some minor other bug, sometimes VDRadmin doesn't load whole page. It just stops in the middle. Firefox is still waiting for data, but nothing. Only loading the page again helps. This might be because my machine is abit on the slow side, P166MHz with 64 megs of ram... But still it's annoying to first wait 5-10 secs to get page loaded and then it only loads halfly.
Other than these problems, VDRadmin is very nice software. I like it alot!
Marko
On Tue, 14 Feb 2006 13:27:52 +0200 (EET) Marko Myllymaa myllymaa@niksula.hut.fi wrote:
Hi,
I almost got one whole day recording, but luckily noticed it on timers and deleted it. Lately I've been getting some timers twice and for some weird reason I've got two times timer for Galactica for saturday, while it's broadcasted only on friday and I've added that to the autotimer, ie. friday only...
So far all MTV3 recordings/timers are okay. Some subtv timers have been doupled and nelonen has these Galactica bugs and also some timers have been doupled.
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem in their EPG, but I haven't yet turned on logging in VDRAdmin to see if there's anything strange.
--Niko Mikkilä
hi,
Niko Mikkila writes:
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem
Have you set NO_EVENTID = 1 ? or something like "NO_EVENTID_ON = 4" (these options are quite essential, I do not remember whether they are available in the admin interface but at least you can manually edit the vdradmin.conf file.)
yours, Jouni
From: "Jouni Karvo" jouni.karvo@tkk.fi
Niko Mikkila writes:
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem
Have you set NO_EVENTID = 1 ? or something like "NO_EVENTID_ON = 4" (these options are quite essential, I do not remember whether they are available in the admin interface but at least you can manually edit the vdradmin.conf file.)
After updating to vdradmin-AM-3.4.2rc2 I changed back to NO_EVENTID=0 and NO_EVENTID_ON= . For now I've also had one weird timer lasting hours. As one could expect the timer was on channel Nelonen. The program was Deadwood and the timer was from about 4am to 4pm and the right timer should have been 11:20pm to 0:45 which was also there as it should. The extra long timer started almost 24 hours early. I could not see any EPG data for this and thats why I once was wondering if such a feature could be added that would save EPG data for history and debugging reasons.
Otherwise it works great and is a must for me :) I'd like to take this opportunity and thank Andreas for a great peace of programming. This is just what I need and have also been using even there have been some minor bugs.
I did miss one recording last week but then again it had nothing to do with vdradmin. It was due to the fact that HTV rearranged their channels :(
BR \Kartsa
On Tue, 14 Feb 2006 16:49:53 +0200 Jouni Karvo jouni.karvo@tkk.fi wrote:
Niko Mikkila writes:
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem
Have you set NO_EVENTID = 1 ? or something like "NO_EVENTID_ON = 4" (these options are quite essential, I do not remember whether they are available in the admin interface but at least you can manually edit the vdradmin.conf file.)
Thanks for the hint. I now set "NO_EVENTID_ON = 4" and will see what happens. Have you been using "NO_EVENTID = 1" yourself? Any problems with that? Would be nice to know what to recommend if I (or someone else) ever writes documentation for this.
Regards,
Niko Mikkilä
On Tue, 14 Feb 2006, Niko Mikkila wrote:
On Tue, 14 Feb 2006 16:49:53 +0200 Jouni Karvo jouni.karvo@tkk.fi wrote:
Niko Mikkila writes:
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem
Have you set NO_EVENTID = 1 ? or something like "NO_EVENTID_ON = 4" (these options are quite essential, I do not remember whether they are available in the admin interface but at least you can manually edit the vdradmin.conf file.)
Thanks for the hint. I now set "NO_EVENTID_ON = 4" and will see what happens. Have you been using "NO_EVENTID = 1" yourself? Any problems with that? Would be nice to know what to recommend if I (or someone
I tried "NO_EVENTID = 1" with earlier vdradmind version, but I had to turn it to 0 again. Now I didn't got double timers, but about 15 times every timer... Hopefully it works better with my current version.
Marko
hi,
Marko Myllymaa writes:
I tried "NO_EVENTID = 1" with earlier vdradmind version, but I had to turn it to 0 again. Now I didn't got double timers, but about 15 times every timer... Hopefully it works better with my current version.
Yes - the latest AM version fixed this for me.
yours, Jouni
On Wed, 15 Feb 2006, Jouni Karvo wrote:
hi,
Marko Myllymaa writes:
I tried "NO_EVENTID = 1" with earlier vdradmind version, but I had to turn it to 0 again. Now I didn't got double timers, but about 15 times every timer... Hopefully it works better with my current version.
Yes - the latest AM version fixed this for me.
I tried "NO_EVENTID_ON = 4", but I still got second galactica timer. This time also to saturday, though it should have been only on fridays.
I'm using vdradmin-am-3.4.3rc2 and vdr-1.3.23.
Is there anything I can do to track this down?
Here are corresponding timer lines for those galacticas: 32769:C-0-2-65:2006-02-17:2331:0045:99:99:Taisteluplaneetta Galactica: 32769:C-0-2-65:2006-02-18:2341:0145:99:99:Taisteluplaneetta Galactica:
First one is the correct one.
And I still have autotimer set to fridays only.
Below is some lines from vdradmind.log matching "Galactica" and from such time that false timer is programmed: 02/15/06 18:41:28: ProgTimer: Programming Timer "Taisteluplaneetta Galactica" (Channel 4, Event-ID 0, 20060218-2341 - 20060219-0145, Active 32769) 02/15/06 18:41:32: AutoTimer: Programming Timer "Taisteluplaneetta Galactica" (Event-ID 361, 20060217-2335 - 20060218-0035) 02/15/06 18:41:32: AT_ProgTimer: Programming Timer "Taisteluplaneetta Galactica" (Event-ID 361, 20060217-2331 - 20060218-0045) 02/15/06 18:41:32: ProgTimer: Programming Timer "Taisteluplaneetta Galactica" (Channel 4, Event-ID 0, 20060217-2331 - 20060218-0045, Active 32769)
I have some questions about those lines. What's the difference between ProgTimer, Autotimer and AT_ProgTimer? And when does Event-ID get value zero?
Marko
From: "Marko Myllymaa" myllymaa@niksula.hut.fi
Marko Myllymaa writes:
I tried "NO_EVENTID_ON = 4", but I still got second galactica timer. This time also to saturday, though it should have been only on fridays.
I've got "NO_EVENTID_ON = " and galactica was timered correctly on friday.
I'm using vdradmin-am-3.4.3rc2 and vdr-1.3.23.
As am I.
Is there anything I can do to track this down?
Here are corresponding timer lines for those galacticas: 32769:C-0-2-65:2006-02-17:2331:0045:99:99:Taisteluplaneetta Galactica: 32769:C-0-2-65:2006-02-18:2341:0145:99:99:Taisteluplaneetta Galactica:
First one is the correct one.
And I still have autotimer set to fridays only.
I've selected all weekdays. Usually if there are no reruns I do not bother to take the ticks off.
I'll put my vdradmind.conf here (obviously some parameters are sensored) see if there are any differences.
\Kartsa
------------------- AT_FUNC = 1 AT_LIFETIME = 99 AT_MARGIN_BEGIN = 10 AT_MARGIN_END = 10 AT_PRIORITY = 50 AT_SENDMAIL = 0 AT_TIMEOUT = 120 AT_TOOLTIP = 1 CACHE_LASTUPDATE = 1139419439 CACHE_REC_LASTUPDATE = 1139419465 CACHE_REC_TIMEOUT = 60 CACHE_TIMEOUT = 60 CHANNELS_WANTED = 1,2,3,4,5,6,7,8,9,10,12,13,14,15,16 CHANNELS_WANTED_AUTOTIMER = 0 CHANNELS_WANTED_PRG = 1 CHANNELS_WANTED_PRG2 = 0 CHANNELS_WANTED_SUMMARY = 0 CHANNELS_WANTED_TIMELINE = 0 CHANNELS_WANTED_WATCHTV = 0 EPG_DIRECT = 1 EPG_FILENAME = /video/epg.data EPGIMAGES = /video/epgimages EPG_PRUNE = 8 GUEST_ACCOUNT = 0 LANG = fi_FI LOCAL_NET = 0.0.0.0/32 LOGFILE = vdradmind.log LOGGING = 0 LOGINPAGE = 4 LOGLEVEL = 81 MAIL_PROG = /usr/bin/sendEmail MOD_GZIP = 0 NO_EVENTID = 1 NO_EVENTID_ON = PROG_SUMMARY_COLS = 3 REC_EXT = m3u REC_MIMETYPE = video/x-mpegurl RECORDINGS = 2 SKIN = bilder ST_FUNC = 1 ST_LIVE_ON = 1 ST_REC_ON = 1 ST_URL = ST_VIDEODIR = /video TEMPLATE = default TIMES = 18:00, 20:00, 21:00, 22:00 TL_TOOLTIP = 1 TM_ADD_SUMMARY = 1 TM_LIFETIME = 99 TM_MARGIN_BEGIN = 1 TM_MARGIN_END = 10 TM_PRIORITY = 50 TM_TT_LIST = 1 TM_TT_TIMELINE = 1 TV_EXT = m3u TV_MIMETYPE = video/x-mpegurl VDRCONFDIR = /video VDRVFAT = 1 VIDEODIR = /video ZEITRAHMEN = 4
On Thu, 16 Feb 2006, Kartsa wrote:
I've selected all weekdays. Usually if there are no reruns I do not bother to take the ticks off.
That's true. I've just tried that too to get rid of extra timers.
I'll put my vdradmind.conf here (obviously some parameters are sensored) see if there are any differences.
I got "NO_EVENTID = 0". I changed that to 1 and soon we'll see if it's working. Thanks.
Marko
From: "Marko Myllymaa" myllymaa@niksula.hut.fi
On Thu, 16 Feb 2006, Kartsa wrote:
I've selected all weekdays. Usually if there are no reruns I do not bother to take the ticks off.
That's true. I've just tried that too to get rid of extra timers.
I'll put my vdradmind.conf here (obviously some parameters are sensored) see if there are any differences.
I got "NO_EVENTID = 0". I changed that to 1 and soon we'll see if it's working. Thanks.
Seems like now I've got these reaaaally long timers. These are not wery desirable because of the disk space consuption :)
I've pasted two cases from my log if these could be for any help to someone.
There should be possible to see the creation of the timers and the modifications of them.
The environment is still the same. I'm using vdradmin-am-3.4.3rc2 and vdr-1.3.23
------------------------------------------- First case
I do not know which is which in EPG data so I'll paste all with the same name.
EPG data E 207 1140282000 3000 50 T American Idol S Lippuja Hollywoodiin on vielä tänään tarjolla Bostonissa. e
E 200 1140368400 3600 50 T American Idol S Hollywoodin karsintoihin selvisi 175 kilpailijaa. e
After VDR start Feb 13 18:57:30 vdr[6563]: timer 51 (5 1859-2010 'American Idol') added Here the timer is added
Just after vdrconfig contacted through SVDRP Feb 14 19:52:23 vdr[6581]: timer 32 (5 1854-2010 'American Idol') modified (active) Feb 14 19:52:35 vdr[6581]: timer 56 (5 1859-2000 'American Idol') added Here there has been a small change to starting time and another timer with the same name is created.
Just after vdrconfig contacted through SVDRP Feb 14 21:44:56 vdr[6581]: timer 32 (5 1759-2010 'American Idol') modified (active) Now the starting time is moved 1 hour earlier.
Just after vdrconfig contacted through SVDRP Feb 14 21:45:46 vdr[6581]: timer 32 (5 1729-2010 'American Idol') modified (active) Now the starting time is moved again and half an hour this time.
And this bahaviour continues until the timer starts about a day early.
Just after vdrconfig contacted through SVDRP Feb 15 00:09:26 vdr[6581]: timer 32 (5 1704-2010 'American Idol') modified (active)
After VDR start Feb 15 17:27:19 vdr[6557]: timer 31 (5 1619-2010 'American Idol') modified (active)
After VDR start Feb 15 19:27:18 vdr[6557]: timer 30 (5 1529-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 21:27:30 vdr[6557]: timer 28 (5 1439-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 21:43:55 vdr[6557]: timer 27 (5 1354-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 23:11:36 vdr[6557]: timer 27 (5 1324-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 23:16:47 vdr[6557]: timer 27 (5 1254-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 01:17:42 vdr[6557]: timer 26 (5 1204-2010 'American Idol') modified (active)
After VDR start Feb 16 17:27:17 vdr[6579]: timer 26 (5 1139-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 19:12:20 vdr[6594]: timer 25 (5 1114-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 21:28:52 vdr[6594]: timer 20 (5 1049-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 22:47:23 vdr[6567]: timer 19 (5 1024-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 17 00:47:35 vdr[6567]: timer 19 (5 0959-2010 'American Idol') modified (active)
After VDR start Feb 17 09:49:53 vdr[6563]: timer 19 (5 0559-2010 'American Idol') modified (active)
After VDR start Feb 17 15:07:16 vdr[6561]: timer 19 (5 0209-2010 'American Idol') modified (active)
After VDR start Feb 17 17:27:31 vdr[6572]: timer 18 (5 0119-2010 'American Idol') modified (active)
Just after vdrconfig contacted through SVDRP Feb 17 19:27:44 vdr[6572]: timer 16 (5 0029-2010 'American Idol') modified (active)
No apparent reason Feb 17 20:00:02 vdr[6572]: timer 15 (5 0029-2010 'American Idol') set to event Pe 17.02.2006 23:55-00:30 'Madventures II (K15)'
No apparent reason Feb 17 20:30:03 vdr[6572]: timer 13 (5 0029-2010 'American Idol') set to event La 18.02.2006 00:30-01:20 'RAW (K15)'
Just after vdrconfig contacted through SVDRP Feb 17 21:28:01 vdr[6572]: timer 12 (5 2354-2010 'American Idol') modified (active)
No apparent reason Feb 17 21:30:05 vdr[6572]: timer 12 (5 2354-2010 'American Idol') set to event La 18.02.2006 00:30-01:20 'RAW (K15)'
No apparent reason Feb 17 22:16:26 vdr[6572]: timer 11 (5 2354-2010 'American Idol') set to event La 18.02.2006 02:10-06:00 'Deittichat'
Just after vdrconfig contacted through SVDRP Feb 17 23:08:49 vdr[6572]: timer 11 (5 2309-2010 'American Idol') modified (active)
Feb 17 23:09:53 vdr[6572]: timer 11 (5 2309-2010 'American Idol') set to event La 18.02.2006 02:10-06:00 'Deittichat' Feb 17 23:09:53 vdr[6572]: switching device 1 to channel 5 Feb 17 23:09:53 vdr[6572]: timer 11 (5 2309-2010 'American Idol') start Feb 17 23:09:53 vdr[6572]: Title: 'Deittichat' Subtitle: 'Löytyykö Se Oikea ruudun takaa? Sovi treffit tekstiviestitse!' Feb 17 23:09:53 vdr[6572]: record /video/American_Idol/2006-02-17.23:09.50.99.rec Feb 17 23:09:53 vdr[6572]: creating directory /video/American_Idol Feb 17 23:09:53 vdr[6572]: creating directory /video/American_Idol/2006-02-17.23:09.50.99.rec Feb 17 23:09:57 vdr[6572]: recording to '/video/American_Idol/2006-02-17.23:09.50.99.rec/001.vdr' Feb 17 23:09:57 vdr[7445]: file writer thread started (pid=7445, tid=655370) Feb 17 23:09:57 vdr[7446]: recording thread started (pid=7446, tid=671755)
--------------------------- And another case
And again the EPG data first
E 201 1140372000 3000 50 T Summerland S Derrickin ystävät löytävät komerosta vanhan alastonkuvan Avasta. Kun kuva päätyy lasten vanhempien käsiin, Derrickin ystävät kaikkoavat nope asti. Bradin hämmentyy rakkauselämässään, kun hän löytää Sarahin toisen pojan kainalosta juuri kun e
In this one a similar behaviour can be seen as in the first one.
After VDR start Feb 13 18:57:30 vdr[6563]: timer 52 (5 1959-2110 'Summerland') added
Just after vdrconfig contacted through SVDRP Feb 14 19:52:23 vdr[6581]: timer 43 (5 1959-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 14 21:44:56 vdr[6581]: timer 43 (5 1859-2210 'Summerland') modified (active) poistetaan tässä välissä yksi tallenne Feb 14 21:45:09 vdr[6581]: timer 56 (5 1959-2100 'Summerland') added
Just after vdrconfig contacted through SVDRP Feb 14 21:45:46 vdr[6581]: timer 43 (5 1829-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 00:09:26 vdr[6581]: timer 43 (5 1739-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 17:27:19 vdr[6557]: timer 42 (5 1649-2210 'Summerland') modified (active)
After VDR start Feb 15 19:27:18 vdr[6557]: timer 41 (5 1559-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 21:27:30 vdr[6557]: timer 39 (5 1509-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 21:43:55 vdr[6557]: timer 38 (5 1419-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 23:11:36 vdr[6557]: timer 38 (5 1354-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 15 23:16:47 vdr[6557]: timer 38 (5 1304-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 01:17:42 vdr[6557]: timer 37 (5 1234-2210 'Summerland') modified (active)
After VDR start Feb 16 17:27:17 vdr[6579]: timer 37 (5 1144-2210 'Summerland') modified (active)
After VDR start Feb 16 19:12:20 vdr[6594]: timer 36 (5 1114-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 21:28:53 vdr[6594]: timer 31 (5 1049-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 16 22:47:23 vdr[6567]: timer 30 (5 1024-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 17 00:47:35 vdr[6567]: timer 30 (5 0959-2210 'Summerland') modified (active)
After VDR start Feb 17 09:49:54 vdr[6563]: timer 30 (5 0559-2210 'Summerland') modified (active)
After VDR start Feb 17 15:07:16 vdr[6561]: timer 30 (5 0224-2210 'Summerland') modified (active)
After VDR start Feb 17 17:27:31 vdr[6572]: timer 29 (5 0159-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 17 19:27:44 vdr[6572]: timer 27 (5 0114-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 17 21:28:01 vdr[6572]: timer 23 (5 2339-2210 'Summerland') modified (active)
Just after vdrconfig contacted through SVDRP Feb 17 23:08:49 vdr[6572]: timer 22 (5 2249-2210 'Summerland') modified (active)
\Kartsa
From: "Kartsa" kari@kniivila.com From: "Marko Myllymaa" myllymaa@niksula.hut.fi
On Thu, 16 Feb 2006, Kartsa wrote:
I've selected all weekdays. Usually if there are no reruns I do not bother to take the ticks off.
That's true. I've just tried that too to get rid of extra timers.
I'll put my vdradmind.conf here (obviously some parameters are sensored) see if there are any differences.
I got "NO_EVENTID = 0". I changed that to 1 and soon we'll see if it's working. Thanks.
Addition to my resent post just after I sent it I noticed yet again a log entry for the second case
Just after vdrconfig contacted through SVDRP Feb 18 00:26:45 kartzan vdr[6572]: timer 20 (5 2159-2210 'Summerland') modified (active) This seems like totally different program and only for eleven minutes that is. A zero length program would end up as 11 min program in my configuration because of the 1 min pretime and 10 min after time. :)
The right time for summerland would be 19.2 at 8pm.
\Kartsa
Niko Mikkila wrote:
On Tue, 14 Feb 2006 13:27:52 +0200 (EET) Marko Myllymaa myllymaa@niksula.hut.fi wrote:
Hi,
I almost got one whole day recording, but luckily noticed it on timers and deleted it. Lately I've been getting some timers twice and for some weird reason I've got two times timer for Galactica for saturday, while it's broadcasted only on friday and I've added that to the autotimer, ie. friday only...
So far all MTV3 recordings/timers are okay. Some subtv timers have been doupled and nelonen has these Galactica bugs and also some timers have been doupled.
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem in their EPG, but I haven't yet turned on logging in VDRAdmin to see if there's anything strange.
It would be a good debug tool if either VDR or vdradmin stores the EPG data (history data not just the new data) for later usage. Of course the file would be large but that would be a good tool when reporting to the broadcast companies if their EPG is not correct.
Br, Pasi
From: "Pasi Juppo" pasi.juppo@iki.fi
Niko Mikkila wrote:
On Tue, 14 Feb 2006 13:27:52 +0200 (EET) Marko Myllymaa myllymaa@niksula.hut.fi wrote:
Hi,
I almost got one whole day recording, but luckily noticed it on timers and deleted it. Lately I've been getting some timers twice and for some weird reason I've got two times timer for Galactica for saturday, while it's broadcasted only on friday and I've added that to the autotimer, ie. friday only...
So far all MTV3 recordings/timers are okay. Some subtv timers have been doupled and nelonen has these Galactica bugs and also some timers have been doupled.
I have the same problem with all my autotimers for Nelonen. I get the correct timer and then incorrect ones later or a bit earlier the same day and for the few days after the correct date. Smells like a problem in their EPG, but I haven't yet turned on logging in VDRAdmin to see if there's anything strange.
It would be a good debug tool if either VDR or vdradmin stores the EPG data (history data not just the new data) for later usage. Of course the file would be large but that would be a good tool when reporting to the broadcast companies if their EPG is not correct.
I think it should be VDR that would create the history file. Its VDR that creates the file and removes entrys from it, isn't it. It could also be some kind of setting for how old data would be stored and possibly for which channels. The problem I think would be how to present the history data because of possible changes in the EPG data itself. There could be an error in the data for many days and in some point it would be corrected and possibly corrected again. How should these changes be in the history file for it to be easily read. Ofcourse the data may not be corrected at all and that would also be seen in the history data.
Another question is that should this data be browseable in OSD or only through telnet or ssh (or maybe vdradmin).
\Kartsa
hi,
Kartsa writes:
From: "Pasi Juppo" pasi.juppo@iki.fi
It would be a good debug tool if either VDR or vdradmin stores the EPG data (history data not just the new data) for later usage. Of course the file would be large but that would be a good tool when reporting to the broadcast companies if their EPG is not correct.
I think it should be VDR that would create the history file. Its VDR that creates the file and removes entrys from it, isn't it. It could also be some kind of setting for how old data would be stored and possibly for which channels. The problem I think would be how to present the history data because of possible changes in the EPG data itself. There could be an error in the data for many days and in some point it would be corrected and
How about using a cvs repository? The problem would be of course then _when_ to make a check-in. Perhaps a diff with the current epg.data and the latest check-out would be made and if it differs, a new check-in would be made...
EPG data repository would be for debugging anyway, so I do not really know about user interfacing.
yours, Jouni
From: Jouni Karvo [mailto:jouni.karvo@tkk.fi] Kartsa writes:
From: "Pasi Juppo" pasi.juppo@iki.fi
It would be a good debug tool if either VDR or vdradmin
stores the EPG
data (history data not just the new data) for later
usage. Of course the
file would be large but that would be a good tool when
reporting to the
broadcast companies if their EPG is not correct.
I think it should be VDR that would create the history
file. Its VDR that
creates the file and removes entrys from it, isn't it. It
could also be some
kind of setting for how old data would be stored and
possibly for which
channels. The problem I think would be how to present the
history data
because of possible changes in the EPG data itself. There
could be an error
in the data for many days and in some point it would be
corrected and
How about using a cvs repository? The problem would be of course then _when_ to make a check-in. Perhaps a diff with the current epg.data and the latest check-out would be made and if it differs, a new check-in would be made...
EPG data repository would be for debugging anyway, so I do not really know about user interfacing.
Well the user interface was just a thought and no means necessary property. Propably a simple text file could be enough where would be all occurrences of EPG data. If it would change both old and new version would be stored possibly with a timestamp of when the data was seen. And as Jouni wrote it would be for debugging anyway and therefore a simple textfile could be enough. If diff would be used would the history data be only for changes and no other. If so one could not find those errors where EPG data would be error free and the reason for problem lies elsewhere.
\Kartsa
-
Andreas Mair -
Dave -
Jouni Karvo -
Kartsa -
Marko Myllymaa -
Niko Mikkila -
Pasi Juppo