Split timer issue

[ccs]

You can work around for now by turning off the split programme detection in the recording options, the problem won't occur.

This just backs up why the ServiceReference class has to go. The bug is the direct result of the class being a really bad idea.

Can confirm that instant record is working ok in 5.3.032

ps "split programme detection" only works if you select the 1st segment of the programme, I guess selecting the 2nd segment in the epg doesn't really make sense, but......

 

[simonc]

Hmm, fair point. Would you want it to search backwards as well as forwards? Might make sense.

 

[ccs]

Hmm, fair point. Would you want it to search backwards as well as forwards? Might make sense.

Not bothered, really, I just thought I'd see what happened. I guess, depending on what the epg is showing, you might not notice it's split.

What happens if autotimer finds a match?

EDIT: It creates two separate timers, as it would normally.

Debug log looks ok as well.

<  9693.4552> 15:02:27.4659 [eEPGCache] lookup events with 'Godzilla' as title (case sensitive)
<  9693.4774> 15:02:27.4882 [RecordTimer] [AutoTimer] Try to add new timer based on AutoTimer Godzilla.
<  9693.4776> 15:02:27.4884 [RecordTimer] [AutoTimer] Timer start on: Sun May 24 15:43:00 2020
<  9693.4787> 15:02:27.4895 [eDVBFrontend0] opening frontend
<  9693.4798> 15:02:27.4906 [eDVBFrontend1] opening frontend
<  9693.4814> 15:02:27.4922 [eDVBFrontend2] opening frontend
<  9693.4849> 15:02:27.4957 [TimerSanityCheck] conflict not found!
<  9693.4852> 15:02:27.4960 [Timer] Record RecordTimerEntry(name=Godzilla, begin=Sun May 24 15:43:00 2020, serviceref=1:0:19:4540:4089:233A:EEEE0000:0:0:0:, justplay=0, isAutoTimer=True)
<  9693.5095> 15:02:27.5203 [RecordTimer] [AutoTimer] Try to add new timer based on AutoTimer Godzilla.
<  9693.5096> 15:02:27.5204 [RecordTimer] [AutoTimer] Timer start on: Sun May 24 16:48:00 2020
<  9693.5153> 15:02:27.5260 [TimerSanityCheck] conflict not found!
<  9693.5156> 15:02:27.5263 [Timer] Record RecordTimerEntry(name=Godzilla, begin=Sun May 24 16:48:00 2020, serviceref=1:0:19:4540:4089:233A:EEEE0000:0:0:0:, justplay=0, isAutoTimer=True)

 

[abu baniaz]

Posts moved to separate thread from bug report

 

[birdman]

Hmm, fair point. Would you want it to search backwards as well as forwards? Might make sense.

Yes, it would. You might only see the second part on a visual scan if the first part is on the (not visible) previous screen.
It's happened to me before now.

 

[adm]

What happens if autotimer finds a match?

EDIT: It creates two separate timers, as it would normally.

It doesn't necessarily work with autotimers! I have autotimers set by default to "require description to be unique" and as both parts (separated by news) have the same description only the first part is recorded.
Going to the EPG selecting the first part of a film, then pressing record button the options of timer and autotimer appear. Both parts will be recorded if timer is selected and only the first part will be recorded if autotimer is selected.

This is a problem when trying to avoid repeats when recording a series that has news splitting the program.

 

[simonc]

Hmm, I didn't really consider AutoTimer, what with it being a plugin. Could be a bit tricky as other distros use the same source code

 

[ccs]

It doesn't necessarily work with autotimers! I have autotimers set by default to "require description to be unique" and as both parts (separated by news) have the same description only the first part is recorded.
Going to the EPG selecting the first part of a film, then pressing record button the options of timer and autotimer appear. Both parts will be recorded if timer is selected and only the first part will be recorded if autotimer is selected.

This is a problem when trying to avoid repeats when recording a series that has news splitting the program.

I think autotimer sets up its own timers, and doesn't go anywhere near the new "split timers".

My example worked (as it always has) because the time-span included both parts, and 2 timers were created.
Reducing the time-span to exclude the 2nd part results in a timer for only the first part.

Split timer creates just a single timer for the whole programme.

 

[birdman]

This is a problem when trying to avoid repeats when recording a series that has news splitting the program.

Something I usually have set too.
Although I can't think of anything I'd set an AutoTimer for that would ever be split by the News.

Perhaps the AT code could have a "set one combined timer if you find two matches with < given-configurable-gap between them" option? The default being a 0-gap, which means no-combining.

 

[adm]

Although I can't think of anything I'd set an AutoTimer for that would ever be split by the News.

It’s not just news but those pointless 1 minute "celebrity/Hollywood/film” updates inserted during a programme, and some of which are flagged in the EPG.

 

[spanner123]

I think autotimer sets up its own timers, and doesn't go anywhere near the new "split timers".

My example worked (as it always has) because the time-span included both parts, and 2 timers were created.
Reducing the time-span to exclude the 2nd part results in a timer for only the first part.

Split timer creates just a single timer for the whole programme.

It does create a single timer but includes the unwanted bit in-between also.

 

[ccs]

It does create a single timer but includes the unwanted bit in-between also.

Hardly an issue, surely.
And if you prefer, you can disable the feature, but then you'll have 2 recordings to mess about with.

I always used to create a single timer with an extended finish time, now it does it automatically.

 

[simonc]

It does create a single timer but includes the unwanted bit in-between also.

Yes, that's the intention of the feature - it's so that you don't have to check whether the programme is split by some silly entertainment news. Imagine it as an extended advert break. Given that the most common duration of these interruptions is 5 minutes, you'd record almost as much padding if doing 2 separate recordings! AFAIK, there's no way to pause and resume a recording, and even if you did, you'd still want padding either side; I doubt the channels that do this stick to an exacting schedule.

 

[birdman]

I always used to create a single timer with an extended finish time, now it does it automatically.

But, as was noted in #6, this will not happen if you have set an AT that is checking for unique descriptions. Which is what I often set to avoid recording the same thing twice when it is repeated soon after.

 

[ccs]

But, as was noted in #6, this will not happen if you have set an AT that is checking for unique descriptions. Which is what I often set to avoid recording the same thing twice when it is repeated soon after.

I know - I was referring to a timer, not an autotimer, so why repeat what we already know?

 

[abu baniaz]

The code changes are to Timeredit py only. Autotimer is a separate process and has not been touched.

 

[birdman]

I know - I was referring to a timer, not an autotimer, so why repeat what we already know?

In case someone reading through thought it was fixed everywhere.