Tvheadend

Could you compare the missing autorec episode with others ? The detail in EPG window might help to determine the diferences.

If "Record all" is set, then the rerun mechanism is completely off. Do you see 'rerun' dates in the 'Rerun of' column in the upcoming recordings grid?

If you turn off/on the autorec, is the event correctly included?

It's not easy to debug such things. It may help, if you can pack the whole settings directory (which includes the EPG database) and give me the URL to the packed file to do an analysis why autorec code ommits this event. I'm perexg on IRC, so send me a PM.

I have SD and can't reproduce the Strictly problem, but I can reproduce the Coast to Coast issue, assuming you are talking about S01E03 on Fri 6th Oct 02:00 on Spike which is dup of Tuesday 3rd on channel 5.

@Jaroslav I think the dvr_entry_create_by_autorec is dropping the dup since episode is the same. I already had a small local patch in that area to do logging (below), but my patch also forced preferring earlier showing so is slightly different logic to master which schedules the first it found which in my case was frequently the +1 channel. Perhaps the check in master should also check start time is equal?

dvr: Autorecord "(null)": Not scheduling "Tony Robinson: Coast To Coast" on channel Channel 5 HD because identical dup start: 1507251600 and de start: 1507053600 channel: Spike                                                                                                                                             

Robert E: I tested things with your data and if I turn the autorec on/off then all episodes are queued correctly. Perhaps, someone deleted the upcomming DVR entry? (there should be 'delete entry' lines in log)

@Em: Yes, it seems that the condition is not perfect. Perhaps, we should add the channel check instead start time in the second part of the condition, too.

I'm not sure. Looks like that existing check is from 2012 (103de71f).

I think that check is probably there for Astra 28.2 since UK gets ~15 regional channels called BBC1 and maybe another 15 regional channels called ITV1, and similar numbers for HD counterparts and timeshift (+1 hour) channels. So all the ITV1 show mostly the same programmes at the same times but sometimes have an extra programme in the schedule or replace some programme with "regional interest" programme or a different film.

I think even people who say "record all" don't expect every regional channel to be recorded at the same start time since it will tie up the tuners, but it's reasonable to expect it to record on a different channel at a different time.

But if a channel check is added then presumably the upcoming tab will suddenly list (say) 14 other showings at the same time and then another 14 on timeshift +1 channel and then the "max schedules" check later on.

I run with a modified version since I kept getting channel 5+1 hour scheduled instead of channel 5, but not yet submitted it:

if (e->start >= de->de_start && strcmp(dae->dae_owner...

Perhaps the check (to work for Original Poster) should be:

(de->de_bcast == e || (de->de_bcast && de->de_bcast->episode == e->episode)) && e->start == de->de_start

I manually fixed the Strictly recordings by doing a "Record program" action on the Thursday episode. The Autorec for Strictly is several years old.
The "Coast to coast" schedule is as I found it last Saturday. As you can see, only one of recording is made of each episode. I created the Autorecords on Saturday, clean and new.

@Jaroslav: I did some basic testing with e->start==de->de_start and it seems to schedule ok. This was done using OTA (not SD) since my test env hasn't got SD listings for next week and it takes a long time to d/l.

So a "record all" where DVB-T and DVB-S are separate channels (not merged) gave recordings for Spike (DVB-T) and not Spike (DVB-S) for the identical start time of Tue@02:00; which I think is the correct response for "record all" since they are the same episode at the same time; and the S01E03 is recorded once on Channel 5 and on a different day on Spike.

I haven't tested actual recording, just that it scheduled.

Robert E are you able to patch and compile? If so, I can give you a debug line to add which may indicate why it is not scheduling that one single episode of Strictly since that's a different issue to the Coast.

By the way, when I changed Duplicate handling, I noticed a line in the dvr/autorec directory
"record": 1,
and it went back to "record": 0, when I selected "record all" again.

Could you do the same with the Strictly rule? Thanks.

Strictly is now being selected just great. I suspect it had a bad recording number in the SD stream on Saturday.

Deleted the old "upcoming recordings" and changed "all: record if different episode"

Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry 9cdca2622d54936f5bca6c6ba215ee1c "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-03 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry 760e925cdc5005735ecf02e465f14b95 "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-04 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry d37231c3b6f56bde3a6468de4561ec7d "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-05 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry c7e94434e9802ae765bf1a90d47e8c47 "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-06 18:54:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry cdc47b5e0847e894c0c9f8c4441bd7f4 "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-09 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry 151b9e902c393a311a40ec20c7e787bc "Strictly Come Dancing" on "BBC One HD" starting at 2017-10-07 19:29:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:46:37 sat tvheadend[28399]: dvr: entry 2f43963f3f45f21925896e02ae6b82f5 "Strictly Come Dancing" on "BBC One HD" starting at 2017-10-08 20:09:30, scheduled for recording by "10.29.1.69" 

This is what happened when I had a manually created recording and changed the Duplicate handling before:

Oct  3 17:44:17 sat tvheadend[28399]: dvr: entry 01799a63f038660cac5c425209a5fa52 "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-03 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:44:17 sat tvheadend[28399]: dvr: entry 241ed706a4aeecd6ec3a8371bde4d32e "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-04 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:44:17 sat tvheadend[28399]: dvr: Autorecord "": Not scheduling "Strictly Come Dancing: It Takes Two" on channel "BBC Two HD" because dup on "BBC Two HD" start: 1507224600 and de start: 1507224600 (e: 2017-10-05;19:30:00(+0200) de: 2017-10-05;19:30:00(+0200))
Oct  3 17:44:17 sat tvheadend[28399]: dvr: entry 09a2a3d5a4a49895e7c6093d1ea2cb42 "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-06 18:54:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:44:17 sat tvheadend[28399]: dvr: entry c8ea49304bdc0b9a60fa890143309ab3 "Strictly Come Dancing: It Takes Two" on "BBC Two HD" starting at 2017-10-09 19:24:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:44:17 sat tvheadend[28399]: dvr: entry 37d7e4624ab682573812c623d670d490 "Strictly Come Dancing" on "BBC One HD" starting at 2017-10-07 19:29:30, scheduled for recording by "10.29.1.69" 
Oct  3 17:44:17 sat tvheadend[28399]: dvr: entry a041f4d9ced24b824fd3950a13770c2d "Strictly Come Dancing" on "BBC One HD" starting at 2017-10-08 20:09:30, scheduled for recording by "10.29.1.69"