some db help please...

[sub]

The oid column is generated automatically by the database each time a new programme is inserted. unique_identifier is the show identifier generated by zap2it, but will only be available for zap2it users.

[sub]

3. In GB-PVR config, from each of my two tuners I update the EPG

The Channels and Source Channels are populated
The TV Guide is repopulated

*** Is there a way to automate the update of EPG on each of the tuners?

You'd can run "gbpvr.exe -OnlyUpdateEPG" and it'll update the EPG for each capture source.

7. The big question. How do I tell GB-PVR to look for shows that match the Reoccurring scheduled show? On a two week EPG it should give me a couple of status 0 entries for each status 4 Reoccuring Show (assuming no reruns)

GB-PVR automatically schedules any reoccurring recordings after the EPG update occurs. Note there is a bug in v0.99.12 that can cause this to not happen if it was manually initiated, but there is a patch for this in the sticky survival guide thread.

[zehd]

You'd can run "gbpvr.exe -OnlyUpdateEPG" and it'll update the EPG for each capture source.

GB-PVR automatically schedules any reoccurring recordings after the EPG update occurs. Note there is a bug in v0.99.12 that can cause this to not happen if it was manually initiated, but there is a patch for this in the sticky survival guide thread.

Ahhhh a patch. cool

[zehd]

You'd can run "gbpvr.exe -OnlyUpdateEPG" and it'll update the EPG for each capture source.

That works, thank you...

I have updated with the patch...

But when I finally have a reoccurring schedule in the database, I can not initiate a re-schedule of reoccurring recordings after the EPG update occurs.

Of course if I manually input a reoccurring event, as soon as I accept it, there are a couple of pending events... (2 events in two weeks)

I am also confused about the difference in manual (as initiated with the command line above) , a right-click of the tray icon and select "Update EPG" and wait until EPG time, let GB-PVR refresh automatically...

I would really like to be able to tweak the db and then re-schedule the events, real time, rather than wait for the epg update...

[sub]

But when I finally have a reoccurring schedule in the database, I can not initiate a re-schedule of reoccurring recordings after the EPG update occurs.

Its hard to guess without knowing exactly what you write to the database. If its tried to process any reoccurring recordings, you should see "RecordingFactor.ScheduleSeasonRecordings(channel_oid, filename)" messages in the logs - one for each season recording.

Of course if I manually input a reoccurring event, as soon as I accept it, there are a couple of pending events... (2 events in two weeks)

I would really like to be able to tweak the db and then re-schedule the events, real time, rather than wait for the epg update...

When a season recording is created by the app, it also immediately tells the system to find and schedule all the episode matches it finds. There is no way for you to initiate this process, other than letting an EPG update complete (manual or automated).

[zehd]

Its hard to guess without knowing exactly what you write to the database. If its tried to process any reoccurring recordings, you should see "RecordingFactor.ScheduleSeasonRecordings(channel_oid, filename)" messages in the logs - one for each season recording.

When a season recording is created by the app, it also immediately tells the system to find and schedule all the episode matches it finds. There is no way for you to initiate this process, other than letting an EPG update complete (manual or automated).

I'll watch the logs for that...

[zehd]

What does this mean?

Code:

2007-04-22 10:16:24.203 VERBOSE [1] about to save listings 2007-04-22 10:16:25.609 VERBOSE [1] RecordingFactor.ScheduleSeasonRecordings(25, Greys Anatomy *) 2007-04-22 10:16:25.609 VERBOSE [1] getValue() loading new key/value into cache: /settings/AvoidDuplicateRecordingsIfPossible 2007-04-22 10:16:25.609 VERBOSE [1] getValue: /settings/AvoidDuplicateRecordingsIfPossible : true 2007-04-22 10:16:25.609 VERBOSE [1] RecordingFactory.loadSchedule() 2007-04-22 10:16:25.609 VERBOSE [1] getValue cached value: /settings/AutoRemoveMissingRecordings : false 2007-04-22 10:16:25.625 VERBOSE [1] getPreviousEpisodesIdentifiers() 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP552080.0187 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP552080.0188 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP848731.0009 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP877293.0002 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: MV061365.0000 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP632108.0004 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP560454.0027 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP754279.0017 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP732798.0005 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP466293.0060 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP410411.0029 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP700820.0031 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP700818.0018 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: EP730224.0002 2007-04-22 10:16:25.625 VERBOSE [1] Recently had recording: MV149140.0000

Where is the recently had recordings coming from?

[zehd]

So I purge the PREVIOUS_EPISODES table and try again. this is all I got...

Code:

2007-04-23 05:46:37.031 VERBOSE [1] about to save listings 2007-04-23 05:46:37.375 VERBOSE [1] RecordingFactor.ScheduleSeasonRecordings(25, Greys Anatomy *) 2007-04-23 05:46:37.375 VERBOSE [1] getValue() loading new key/value into cache: /settings/AvoidDuplicateRecordingsIfPossible 2007-04-23 05:46:37.375 VERBOSE [1] getValue: /settings/AvoidDuplicateRecordingsIfPossible : true 2007-04-23 05:46:37.375 VERBOSE [1] RecordingFactory.loadSchedule() 2007-04-23 05:46:37.375 VERBOSE [1] getValue cached value: /settings/AutoRemoveMissingRecordings : false 2007-04-23 05:46:37.375 VERBOSE [1] getPreviousEpisodesIdentifiers() 2007-04-23 05:46:37.437 VERBOSE [1] RecordingFactory.getExtrasForGroup(1)

[sub]

So I purge the PREVIOUS_EPISODES table and try again. this is all I got...

Code:

2007-04-23 05:46:37.031 VERBOSE [1] about to save listings 2007-04-23 05:46:37.375 VERBOSE [1] RecordingFactor.ScheduleSeasonRecordings(25, Greys Anatomy *) 2007-04-23 05:46:37.375 VERBOSE [1] getValue() loading new key/value into cache: /settings/AvoidDuplicateRecordingsIfPossible 2007-04-23 05:46:37.375 VERBOSE [1] getValue: /settings/AvoidDuplicateRecordingsIfPossible : true 2007-04-23 05:46:37.375 VERBOSE [1] RecordingFactory.loadSchedule() 2007-04-23 05:46:37.375 VERBOSE [1] getValue cached value: /settings/AutoRemoveMissingRecordings : false 2007-04-23 05:46:37.375 VERBOSE [1] getPreviousEpisodesIdentifiers() 2007-04-23 05:46:37.437 VERBOSE [1] RecordingFactory.getExtrasForGroup(1)

Yep, thats doing its thing. In this case its not finding any shows that exactly match "Greys Anatomy *". I dont know if the "*" thing is your problem. From memory thats some xmltv tool?

[zehd]

Yep, thats doing its thing. In this case its not finding any shows that exactly match "Greys Anatomy *". I dont know if the "*" thing is your problem. From memory thats some xmltv tool?

Yep the * is added by XMLTV and when scheduled manually, GB-PVR finds the occurrances.

One of the beautiful things about our time difference, is I have plenty of time to poke around. While I was recreating the situations and zipping logs, I discovered that if I hand input the data using the SQLite Database Browser, and then update the EPG, it does it's thing.

Now, I think I'm having trouble inputing the datatypes, and it's probably the date...

I would imagine that you don't usually look at sqlite queries in batch file form, but here's the input string...

sqlite3 "C:\Program Files\devnz\gbpvr\gbpvr.db3" "INSERT INTO RECORDING_SCHEDULE (programme_oid,capture_source_oid,status,filename,recording_type,recording_group,manual_start_time,manual_end_time,manual_channel_oid,quality_level,pre_pad_minutes,post_pad_minutes,priority,conversion_profile) VALUES (9585,1,4,'Greys Anatomy *',5,1,'0001-01-01 00:00:00.0000000','0001-01-01 00:00:00.0000000',25,1,2,2,1,null);"

As per the docs, if there's a column list, and then you skip one of the columns, then the default is used, in this case the autonumber OID.

This loads straight into the database and looks identical to a manully scheduled record, or hand input record, yet something must be different, like string instead of integer, or string instead of date type.

Ever seen this