v1.2.9: recurring recording time display incorrect (cosmetic)

[dturland]

Ok, now that GBPVR is practically perfect, I thought it time to report the final longstanding bug:

To reproduce, create a recording with Recording Type: "Record Season (all in this daily timeslot, this channel)"

Now view the recording details in Recording| Recurring, the details will be shown as:
"Daily, between X - Y"

Where X is 90 minutes too early and Y is 30 minutes too late. (bad waf)

The recordings are actually correct, although I haven't checked pre and post padding.

This recording type, "all in this daily timeslot, this channel" is very useful for daily soaps on channels without any EPG. I schedule the generation of a fake XML EPG with 1 hour program slots but if this fails then I know the recordings will continue (good waf) even if the TV guide shows nada.
Correction: should be "hope the recordings will continue"; not reckless enough to find out.

This is purely cosmetic but if it's a quick fix that would be great.

Cheers

David

[martint123]

I think this is as intended.

AFAIR it is done this way so that programs that might start a little early or late will be recorded. If the window for "this timeslot" was exact, then you might miss recordings.

I think there is a tweak in config.xml AllowableTimeslotVariance that if you felt really brave, you could reduce

Martin

[dturland]

Hi Martin,

I could understand it including the pre and post padding in the recording times but 90 minutes and 30 minutes either side!; pretty sure that's unintentional

cheers

David

[martint123]

No, I still think it is as intended.

It isn't the length of recording - it is the times it looks for the recording starting in the EPG. So with the defaults, if it finds "show name" starting +/- 90 minutes from when you first said you wanted it recording, then it will record the show - using EPG start/finish times + padding.

Martin

[dturland]

Hi Martin,
Apologies; I did not realise there was any parsing of the EPG in the 'all in this daily timeslot' recording type and thought it just recorded that timeslot daily.

So now your reply makes sense and is indeed correct, sorry again :o

I do indeed have a AllowableTimeslotVariance and it is set to

<AllowableTimeslotVariance>90</AllowableTimeslotVariance>

Setting this to something like 5 gives good waf for my situation, ymmv

cheers

David

[dturland]

<kid> Bwah!!!!! you know more stuff about stuff and your c2duo is quicker than mine</kid>

[martint123]

Setting this to something like 5 gives good waf for my situation, ymmv

I still reckon you're living dangerously - if it starts 6 mins early or late you will miss it. I can't see any downside to 90 minutes - what problem does it cause?

[martint123]

<kid> Bwah!!!!! you know more stuff about stuff and your c2duo is quicker than mine</kid>

I'm an old git, you pick this stuff up as you go along

[dturland]

Hi Martin,
bwah continued; and you have gritstone....

Moving on; I autogenerate the EPG which hold the 'daily' programs so I know these will always be at the same time.
Hence all I am interested in is how it is presented and having the "between X-Y" looking similar to expected times gives least chance of confusion, again ymmv.

I may delve deeper into this "config dot exe emm ell" you speak of. Mind you last time I edited it our house was flooded, no really !

cheers

David

[dturland]

Hi Sub,

Having played with AllowableTimeslotVariance it is clear that the presentation of recurring recordings is confusing for several reasons:

• The user has specified pre and post padding but these aren't shown.

• The user knows nothing about AllowableTimeslotVariance but this is shown.

• It is not obvious that the 'between' refers to start time rather than record time; certainly with the default 90 mins tolerance and a 'daily' recording probably being an hour or less.

So, in an attempt to minimise confusion, how about one of the following alternative presentations:
(assume: daily recording nominally runs 10:00 - 11:00, tolerance = 90 mins, pre = 2, post = 1 )

current: - "Daily, between 8:30 - 11:30"

1. - "Daily, 10:00 - 11:00"
   
2. - "Daily, 10:00 - 11:00 ( +/- 90 mins )"
   
3. - "Daily, start time between 8:30 - 11:30"
   
4. - "Daily, 9:58 - 11:01"
   
5. - "Daily, 9:58 - 11:01 ( +/- 90 mins )"
   
6. - "Daily, start time between 8:28 - 11:28"

I quite like '2'; there is the space for it and stripping out the '90' gives the user something obvious to search for as a config option.

'4' and onwards are interesting in that it seems needlessly complex to include the padding but at least these _are_ values the user is aware of.

I could make this a poll?

Cheers

David
'think of the husbands!'