Recording Service Refresh

[jsather]

Hi-

I placed an entry into the RECORDING_SCHEDULE table and started waiting on the recording (35 minutes before the show was supposed to start). It didn't happen. I restarted the service and it started recording. Is the Recording Service not refreshing itself? Another thread indicated that it refreshed every 10 minutes or so. Is this true or do I need to restart the service everytime I add an entry? Is there a way to adjust the refresh rate?

Thanks,
Joel

[sub]

If you use the exposed ScheduleHelper API for creating the recording, then the recording service will pick it up immediately, otherwise I'm not sure.

[jorm]

try to add/access everything via subs interfaces. That way if he changes something you get it automatically.

[jsather]

I'll try using the API to add to the schedule. I was going through the code from the CDKScheduler and noticed that it seemed to do quite a few things against the table directly.

Does the ScheduleHelper API actually know where to find the database or do I need to instantiate something first and setup the pointer?

Thanks

[jsather]

Never mind about all this. I figured out what was probably causing the problem. I had WinSQL open while I was trying to get the schedule to take. It was blocking access to the database file from the scheduler.

-Joel

[KingArgyle]

I typically recommend using the Plugin API where at all possible. The main reason that the CDK Scheduler does a lot of querying of the database on it's own is because there was no quick and easy way to get some of the information that was needed. In order to keep memory usage down, and to provide as quick a look up as possible for a narrow set, it is necessary to do your own API work. Also, prior to this last release of GBPVR there was a big bug with the ScheduleHelper and the LoadRecordings method. If you had over 65 recordings scheduled, GBPVR wouldn't load any more records.

So, if the GBPVR plugin API does what you need, then use that, you'll have less problems if Sub changes the underlying database structure than if you read the database directly.

[jrockintuitive]

There is going to be a time when I regret making calls directly to the DB instead of using the API, but since I might have to change something that is recorded to conflict and vice-vers I could not use the API directly. If two programs overlap, the API will make the first recorded and the second in conflict... or the opposite (I forget). I needed more control.
Also I don't think there is a way to retrieve capture sources for a particular channel.

Nonetheless, if you can use the API, then you should.