Help with updateEPG.bat? Seems to run in a loop, unpredictable

[aberson]

Hi folks

I'm having some problems with my update EPG. I'm running 1.4.7 and things have been pretty stable for a while, but frequently my guide data doesn't update right.


my updateepg looks like this:

[INDENT]
append a log entry to a txt file (so i can see when updateepg is being run)
mc2xml (the new version from just a few weeks ago)
nircmd to mute the speakers
ultraxml
nircmd to unmute
pvrx2.exe --OnlyUpdateEPG[/INDENT]


1. Is the last line required? Or will PVRX2 eventually figure out that the XML has been updated?


2. I have my EPG Updates in the config screen set to run at 4am. So why is my epgupdate log file showing the following runs:

[INDENT]Sun 08/15/2010 4:00:49.08
Sun 08/15/2010 18:32:22.82
Sun 08/15/2010 18:33:17.07
Sun 08/15/2010 18:39:57.01
Sun 08/15/2010 19:05:13.03
Mon 08/16/2010 4:04:45.45
Mon 08/16/2010 4:57:10.94
Wed 08/18/2010 4:06:06.76
Wed 08/18/2010 21:14:47.99
Thu 08/19/2010 4:06:04.79 [/INDENT]


My assumption is this has something to do with mc2xml failing and/or UltraXML hanging, GPPVR never seeing the new XML, and then trying to run the update again.


I wonder if I should empty my updateepg.bat and use windows scheduler to run the EPG updates instead of GBPBR, and just let GBPVR "discover" the updated XML every morning at 445am after running the empty updateEPG.bat


I also tried adding some "taskkill" lines at the beginning of the .bat so that if UltraXML was hung from the last time, it would kill it before trying to run it again.


I'm going to keep poking around with this, but any ideas are appreciated.

Thanks!
Adam

[johnsonx42]

No, you should not have pvrx2.exe --OnlyUpdateEPG in that file. PVRX2 loads the new EPG as soon as the UpdateEPG.bat completes.

Remove that and see if your problems go away. If not, please post logs after your next auto epg update.

[sub]

'pvrx2.exe --OnlyUpdateEPG' causes UpdateEPG.bat to run, which calls 'pvrx2.exe --OnlyUpdateEPG' causing UpdateEPG.bat to run, which calls 'pvrx2.exe --OnlyUpdateEPG' causing UpdateEPG.bat to run, which calls 'pvrx2.exe --OnlyUpdateEPG' causing UpdateEPG.bat to run, which calls 'pvrx2.exe --OnlyUpdateEPG' causing UpdateEPG.bat to run, which calls 'pvrx2.exe --OnlyUpdateEPG' causing UpdateEPG.bat to run etc...

You definitely shouldnt have that last line in your batch file.

[aberson]

ok thanks Sub... I expected that was part of the problem, and experimentally rem'd it out a few days ago, but it hadn't totally solved my problem so I wasn't sure anymore. I guess that explains the looping, but perhaps not the other problems.


I originally crafted my updateEPG based on the EPG wiki documentation (http://gbpvr.com/pmwiki/pmwiki.php/Manual/EPG ). In looking at it now, I see the fine print does say to leave out the last line if you're running it from within GBPVR.... so my bad.

wonder how I've been able to limp things along for almost a year like this



So, if I go the windows task-scheduler route, then I should leave the --OnlyUpdateEPG in there? Or, does it make better sense to let GBPVR just run an empty updateepg.bat on its own schedule, scheduled for 1 hr after windows actually does the updating?

I suppose the point of the --onlyupdateepg is because you're never sure how long the guide update might take?

[sub]

So, if I go the windows task-scheduler route, then I should leave the --OnlyUpdateEPG in there? Or, does it make better sense to let GBPVR just run an empty updateepg.bat on its own schedule, scheduled for 1 hr after windows actually does the updating?

I suppose the point of the --onlyupdateepg is because you're never sure how long the guide update might take?

Personally I dont think you should need -onlyupdatepg at all. It was only added because a couple of people wanted a way to trigger an epg update from outside the application. I would expect most people would never need this.

If it exists, UpdateEPG.bat is called by the application prior to updating the epg. If you wanted to run an xmltv grabber to update xmltv files, like mc2xml, then this is a good place to run it. You shouldnt have to fluff around with the windows task scheduler etc.