Tonight's episode has been changed to a repeat. Are you sure it's a repeat? It's series 10 episode 2 from 2014
It's definitely not a repeat
Thank you whoever changed it back to a 1st run
Hi there Tezza. You got in just before I was about to respond.
Yes, there has been some confusion with this series, both from what the data we have received and on our database. The 'r' flags have now been taken off tonight's episode and next Friday's.
Cheers,
Tiphanee
Thanks again
Quote from: Tezza007 on September 02, 2016, 03:24:21 PM
Tonight's episode has been changed to a repeat. Are you sure it's a repeat? It's series 10 episode 2 from 2014
Gosh, thanks for this. How long has it been back? I used to watch it - was on the list on TEDS, but when I stopped using the Toppy and copied the favourites out of TEDS I left some that I presumed will never be back. This was one of them :-(
Just made another discovery TED/S definitely doesn't work with Windows 10 :-( Just thought I'd have a look at the list again, see what else I've missed transferring over - haven't tried running it since I've upgraded this laptop to 10, get an error message :-(
It ran from 1989 to 1998 then came back in 2014 and is still in production
Quote from: Tezza007 on September 03, 2016, 09:07:11 AM
It ran from 1989 to 1998 then came back in 2014 and is still in production
Oh, I may have missed all of the ones since 2014 :-\
Quote from: csutak40 on September 05, 2016, 03:39:16 AM
Quote from: Tezza007 on September 03, 2016, 09:07:11 AM
It ran from 1989 to 1998 then came back in 2014 and is still in production
Oh, I may have missed all of the ones since 2014 :-\
They've only just started showing the 2014 series.
Quote from: simoncasey on September 05, 2016, 08:07:43 AM
They've only just started showing the 2014 series.
Oh great! So, I haven't missed anything (although I doubt I can remember what happened the last time I've watched it ;D)
Incidentally, what causes this (see attached) Not sure if this is an IceTV problem or a Beyonwiz problem
That could be because you have a long after show padding. The show itself is only 20 minutes, so if the padding is greater than that, then when it tries to work out what to use as the description, it ends up picking the show after as it takes the midpoint.
Its an issue with the BW as it doesn't differentiate between the actual show and the padding once a timer has been created. IceTV don't provide the show description as part of the timer, the BW picks that up itself from the IceTV epg.
Thank you. That makes sense.
Quote from: csutak40 on September 05, 2016, 01:20:13 PM
...
Incidentally, what causes this (see attached) Not sure if this is an IceTV problem or a Beyonwiz problem
The problem is due to the way the Beyonwiz matches the description and name (if absent) in a recording with the EPG. This can fail if the program is short reletive to the padding.
I's difficult to reconstruct exactly what's happened without the padding settings for the recording and the actual schedule times for the program, and preferably the timer log, too.
But for next week's Saturday showing of Birds of a Feather, BoaF runs 12:10-12:30, and QI runs 12:30-13:05. If they were the scheduled times for Sat 3 Sep, when the recording was made, then pre-padding must be 7 min, and post-padding must be 30 min.
That would mean that the timer ran from 12:07 to 13:00. If the name and/or description are missing from the timer when it is started they are fetched by guessing a time that should be within the time span of he program being recorded. That's done by taking the midpoint of the timer, in this case 33.5 min from the start of the timer, i.e. at 13:00:30. This is in the time span of QI, so the information for QI is fetched.
I've explained this phenomenon many times over, both here and on the Beyonwiz forum.
There is a bug registered in the Beyonwiz issue tracker that covers this:
Bug #449: Incorrect EIT and description sometimes loaded for short IceTV timers.
This is particularly a problem for short programs like a lot of the afternoon content of ABC2 and ABC3, where the midpoint of the timer can be several programs later than the program being recorded.
In this case, the bug can be worked around by decreasing padding (at either end) by a couple of minutes. That doesn't fix the general problem, though.
What puzzles me a bit, though, is that the recording name in the selection list is correct, even though the program name in right-hand information panel is wrong.