Recurring recordings not picking up all shows

[pvruser]

i remember looking through the logs some time ago and there were some comments like "recently recorded that show, skipping". how do you define the time within which you don't re-record a show? i'm assuming that's also part of the duplicate setting which i've disabled now.

[sub]

i remember looking through the logs some time ago and there were some comments like "recently recorded that show, skipping". how do you define the time within which you don't re-record a show? i'm assuming that's also part of the duplicate setting which i've disabled now.

Yes, those messages are generated by the duplicate checking. The default number of days history retained is 40 days, but you can edit the <RetainedPreviousEpisodeDays> setting in config.xml to change it.

[pvruser]

Yes, those messages are generated by the duplicate checking. The default number of days history retained is 40 days, but you can edit the <RetainedPreviousEpisodeDays> setting in config.xml to change it.

aha great! i set it to 2 days and i may try to re-enable the duplicates sometime when i can play around. i think it would be great if you had the duplicate option in the recording scheduler (for each recurring recording rather than a global system setting). i have a daily show which i cancelled now because i don't want duplicates but for the weekly shows i'd rather record duplicates just in case zap2it posts a wrong show ID.

[dennit]

it was likely Schedules Direct was returning incorrect duplicate show identifiers for some airings

Does the MC2XML data (Media Center, etc.) contain these "show identifiers," or are they only found in SD data?

[sub]

Does the MC2XML data (Media Center, etc.) contain these "show identifiers," or are they only found in SD data?

I dont think mc2xcml supplies this data.

[-stattik-]

I had the same problem with a new episode that wasn't selected to record. When I unchecked "Don't record duplicates", the show was selected but so were dozens of other actual duplicates. So the problem here was that Schedules Direct had a duplicate show identifier for the new episode that wasn't selected originally, correct?

[sub]

So the problem here was that Schedules Direct had a duplicate show identifier for the new episode that wasn't selected originally, correct?

It'll skip scheduling a recording if it as the same unique show identifier is associated with an existing Ready or Pending recording, or if a Ready recording with this show identifier was deleted recently (recently = number of days specified in <RetainedPreviousEpisodeDays> in config.xml)

[pvruser]

i found out why KINGS was not recorded... i dont update my EPG daily, usually once weekly or every 10 days. so on april 5 i got this EPG:

<programme start="20090412200000 -0400" stop="20090412210000 -0400" channel="I20359.labs.zap2it.com">
<title lang="en">Kings</title>
<sub-title lang="en">Judgment Day</sub-title>
<desc lang="en">Jack and Katrina try to get more power.</desc>
<date>20090412</date>
<category lang="en">Drama</category>
<episode-num system="dd_progid">EP01047636.0005</episode-num>
<new />
</programme>

then on april 15 i got this update:

<programme start="20090418200000 -0400" stop="20090418210000 -0400" channel="I20359.labs.zap2it.com">
<title lang="en">Kings</title>
<sub-title lang="en">Judgment Day</sub-title>
<desc lang="en">Jack and Katrina try to get more power.</desc>
<date>20090418</date>
<episode-num system="dd_progid">EP01047636.0005</episode-num>
<video>
<aspect>16:9</aspect>
<quality>HDTV</quality>
</video>
<new />
</programme>

so even though this was a new episode (which was recorded on my hardware Tivo thingy) the EPG from zap2it had the wrong ID as if it had already been recorded...

[sub]

Yep, that'd do it.