Nine playing funny buggers causing Autotimer to stop early

[dRdoS7]

Hi,

Have Autotimers to record Cricket involving Aussies. Works fine.

I was watching the first session, and noticed that the second innings was not recording. When I checked, it had started, but finished early.

I looked at the EPG, and saw this:

Because it's no longer Cricket, the timer was stopped.

I think some thing similar this has occurred in the past, but that had resulted in 2 (or even 3) recordings, instead of one.

dRdoS7

[netmask]

I wonder if you can simply do a auto time recording on a station with no name so this might not happen?

[dRdoS7]

Hi,

I wonder if you can simply do a auto time recording on a station with no name so this might not happen?

In the words of Pauline: "Please explain".

The AT did record the first session twice after all, I didn't see the 2nd version recording as it was on the next page. The first started OK at 13:28, the 2nd started at 17:45. Like any good couple they finished together.

dRdoS7

[prl]

I'm not sure what AutoTimer can be expected to do to get around the network putting bad data in the EPG.

Take it up with the network. I'm sure they'll be very sympathetic. /snark

[prl]

...

I wonder if you can simply do a auto time recording on a station with no name so this might not happen?

In the words of Pauline: "Please explain".
...

I can't work out what netmask is suggesting, either.

[Gully]

...

I wonder if you can simply do a auto time recording on a station with no name so this might not happen?

In the words of Pauline: "Please explain".
...

I can't work out what netmask is suggesting, either.

I have a feeling he means an auto timer that creates a timer any time it finds no information in the EPG.

I think even if you could it would be a nightmare as the results would be so unpredictable (take C31 in Melbourne for a start) and give you lots of timers to either manage or check the results of.

[dRdoS7]

Hi,

I'm not sure what AutoTimer can be expected to do to get around the network putting bad data in the EPG.

Take it up with the network. I'm sure they'll be very sympathetic. /snark

I don't know what AT could do either, maybe ignore such late updates, and the Cricket is the only time I've seen this.

Anyway, it's posted in case some one else has the same.

Will your work on CRIDs help in any way?

I didn't realise the EPG was kept this up to date. When I checked the timer info it looked as if was a late change.

I have EPGRefresh set to start at 03:30, latest at 20:00, I thought it only did one scan.

Thanks,

dRdoS7

[netmask]

What I had in mind was no so much an auto timer but simply a timer to record Nine from say 7pm to Midnight or whatever the time period for the game.

[dRdoS7]

Hi,

What I had in mind was no so much an auto timer but simply a timer to record Nine from say 7pm to Midnight or whatever the time period for the game.

OK, got it. Trying to avoid manual timers. Just have to pay close attention to 9 & Cricket: it's almost like they don't want people to record it!

I changed the AT setting "Skip Poll during records" to "ON", see if that prevents both types of happenings.

dRdoS7

[prl]

Hi,

I'm not sure what AutoTimer can be expected to do to get around the network putting bad data in the EPG.
...
Will your work on CRIDs help in any way?
...

If they put in "No Information" in the event name, I'm not sure you could expect there to be anything useful in the CRID. They're just as dependent on the broadcaster doing the right thing as anything else in the EPG.