XRecord and duplicates

[KingArgyle]

What was really odd in your log file is the number of times that the Recording Schedule was requested to reload. It looked like everytime it was requested to reload it lost one of your scheduled recordings.

Your GBPVRRecordingService log should look something like this:

Code:

11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking The Apprentice: Martha Stewart 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: The Apprentice: Martha Stewart 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking The Apprentice 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: The Apprentice 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Dr. 90210 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Dr. 90210 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking JAG 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: JAG 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Dr. 90210 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Dr. 90210 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking The West Wing 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: The West Wing 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Desperate Housewives 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Desperate Housewives 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Las Vegas 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Las Vegas 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Dr. 90210 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Dr. 90210 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.093 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.093 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking My Name Is Earl 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: My Name Is Earl 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking The Office 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: The Office 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking The Victoria's Secret Fashion Show 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: The Victoria's Secret Fashion Show 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking JAG 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: JAG 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking E-Ring 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: E-Ring 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking The Apprentice: Martha Stewart 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: The Apprentice: Martha Stewart 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Joey 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Joey 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking The Apprentice 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: The Apprentice 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Frasier 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Frasier 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Dr. 90210 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Dr. 90210 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Days of our Lives 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Days of our Lives 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking JAG 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: JAG 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Alias 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Maximum Exposure 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Maximum Exposure 11/30/2005 5:22:59 PM.109 VERBOSE [23] - checking Stargate Atlantis 11/30/2005 5:22:59 PM.109 VERBOSE [23] pending: Stargate Atlantis

however if you take a look at your log...you get muliple calls to the request to reload the schedule, and each time it removes a schedule recording from the pending status.

Have you tried commenting out the zapimport and see if the recordings stay? That is the only thing I can think of that you have different in your system than I do in mine. I don't run the ZapImport program.

[spyder40]

I took out the zapimport but the problem is still happening. The log is still showing the calls to the request to reload the schedule and nuking the pending recordings. Any other ideas?

[KingArgyle]

I don't think this is an issue with CDK Scheduler or the PriorityRecordings.exe file that does the actual scheduling as everything seems alright from the list below.

Code:

12/1/2005 10:37:14 AM.707 INFO [29] Running PostUpdateEPG.bat 12/1/2005 10:37:24 AM.271 VERBOSE [552] received request to reload schedule 12/1/2005 10:37:24 AM.401 VERBOSE [21] flushDatabaseConnections() 12/1/2005 10:37:24 AM.441 VERBOSE [21] processing request to reload schedule 12/1/2005 10:37:24 AM.942 VERBOSE [21] RecordingFactory.loadSchedule() 12/1/2005 10:37:24 AM.942 VERBOSE [21] getValue cached value: /settings/AutoRemoveMissingRecordings : true 12/1/2005 10:37:24 AM.942 VERBOSE [21] getDatabaseConnection() creating new connection 12/1/2005 10:37:24 AM.952 VERBOSE [21] checking pending recordings 12/1/2005 10:37:24 AM.952 VERBOSE [21] - checking G:\Recorded TV\GoldenEye\GoldenEye_20051126_20002300.mpg 12/1/2005 10:37:24 AM.952 VERBOSE [21] - checking G:\Recorded TV\60 Minutes\60 Minutes_20051127_19002000.mpg 12/1/2005 10:37:24 AM.952 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:37:24 AM.952 VERBOSE [21] pending: The Three Stooges . . . 12/1/2005 10:37:24 AM.962 VERBOSE [21] pending: The Three Stooges 12/1/2005 10:37:24 AM.962 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:37:24 AM.962 VERBOSE [21] pending: The Three Stooges

PriorityRecordings finishes scheduling at 10:37AM, and the problems start happening about 12 minutes later.

Code:

12/1/2005 10:49:46 AM.077 VERBOSE [673] received request to reload schedule 12/1/2005 10:49:46 AM.167 VERBOSE [21] flushDatabaseConnections() 12/1/2005 10:49:46 AM.197 VERBOSE [21] processing request to reload schedule 12/1/2005 10:49:46 AM.678 VERBOSE [673] received request to reload schedule 12/1/2005 10:49:46 AM.698 VERBOSE [21] RecordingFactory.loadSchedule() 12/1/2005 10:49:46 AM.698 VERBOSE [21] getValue cached value: /settings/AutoRemoveMissingRecordings : true 12/1/2005 10:49:46 AM.708 VERBOSE [21] getDatabaseConnection() creating new connection 12/1/2005 10:49:46 AM.718 VERBOSE [21] checking pending recordings 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking G:\Recorded TV\GoldenEye\GoldenEye_20051126_20002300.mpg 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking G:\Recorded TV\60 Minutes\60 Minutes_20051127_19002000.mpg 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] pending: The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] - checking The Three Stooges 12/1/2005 10:49:46 AM.718 VERBOSE [21] pending: The Three Stooges

That pattern repeats until there are no more pending Three Stooges. If you can remember what happened 12 minutes after updating the guide. It's that process that seems to be causing the problems. This might be something that Sub can shed some light on.

[spyder40]

I just ran priorityrecordings and the shows got scheduled. Next I turned off the MVP and ran some errands. I just returned and they're gone again so it has to be something that is getting run on a regular basis since they disappear regardless of the time of day. Strange... Should I post a link to this thread in the support section so Sub can take a look?

[KingArgyle]

Yeah, I would post a link. Maybe Sub has an idea of what is going on.

Do you have any recordings setup to be scheduled by the built in GBPVR scheduler???

[spyder40]

Cool, I'll post the link but with sub getting some new hardware to play with plus the bugs he's working on this shouldn't be a high priority on his list. I think I'll make a copy of the directory, remove gbpvr, and reinstall fresh with xrecord as the only plugin and see if it still happens. After trying xrecord I haven't used the builtin scheduler for eons.

[spyder40]

KingArgyle,

This thread looks similar and would have started about that time...

http://forums.nextpvr.com/showthread.php?t=10225

[KingArgyle]

It might be similar, but not positive. CDK Scheduler enters all it's recordings as one time recordings in GBPVR. So from GBPVR it looks like they are one time recording entries. The thread you linked to describes the issue as happening with reoccuring recordings scheduled within GBPVR.

Again, they do sound similar, but not exactly the same.

I'm going to try later tonight and see if I can duplicate the problem on my test system with .95.11 installed. I'll just schedule some recordings and then check about 12 or 30 minutes later to see what the logs say.

This will be a generic install with no additional plugins installed (i.e. no XRecord) just CDK Scheduler.

[spyder40]

I should have time to try the same tomorrow only with xrecord as the only installed plugin.

[KingArgyle]

Alright, installed GBPVR 95.11 on my development machine, and scheduled some recordings with CDK Scheduler. Started up GBPVR and let it sit for about 20 minutes or so, and no problems. I did not have any additional plugins installed, just a base install.

I'd proceed with a clean install, just install XRecord, and schedule your programs and see if the error occurs. If everything is fine, then start re-installing plugins and utilities as necessary, keeping an eye on the log after each of the plugins are added. That unfortunately is going to be the only way to track down what is causing the problem.