Weekly recordings adopt next week's date and title!

[RatAtAt]

My PVR-9200T again (latest software installed)

I have 2 recordings from yesterday 30th Nov which are annotated as being from 7/12, and have
titles which do not occur until 7th Dec schedule (i.e. they are not titles from 30th Nov). They are
numbered 13 and 16 in my list of recordings, and intermediate recording have correct dates etc.

This (at least the date part) used to be a problem on the PVR-8000T until a software update fixed it.

If anyone else is getting this please report it to Humax - weight of comment should get some action :roll:

In my opinion, the titles should not be set at the end on recording, but a few minutes after the start
(to allow for manual padding at both ends of the recording, especially as Chan 4 is always 1 min early)

[radicalengineer]

Agreed, Channel 4 and Five program timing is really annoying since if you start recording early you get the wrong title ie the previous show.....
Cant comment about the other title problems.

RadicalEngineer

[Kitman]

This happened to me yesterday:

I have weekly timers set for Coronation Street http://www.hummy.org.uk/invison/style_emoticons/<#EMO_DIR#>/oops.gif so for Monday it's ITV1 from 19.28-20.02 and 20.28-21.02 to include padding.

Last night went into recorded list to select that night's recordings only to find them dated 12/12 rather than 7/12. This was for both timer settings. Because they're padded, the naming issue does not apply (original firmware).

This could confuse a stupid person, or even an intelligent one!

I will do as you suggest, RatAtAt, and report to Humax.

[RatAtAt]

Originally posted by Kitman
This happened to me yesterday:

I have weekly timers set for Coronation Street http://www.hummy.org.uk/invison/style_emoticons/<#EMO_DIR#>/oops.gif so for Monday it's ITV1 from 19.28-20.02 and 20.28-21.02 to include padding.

Last night went into recorded list to select that night's recordings only to find them dated 12/12 rather than 7/12. This was for both timer settings. Because they're padded, the naming issue does not apply (original firmware).

This could confuse a stupid person, or even an intelligent one!

I will do as you suggest, RatAtAt, and report to Humax.

Thank you - it's not just me then :!: (although I guess you meant "12/12 rather than 5/12" not "7/12" :?:

Anyway, I haven't figured any pattern to predict under what circumstances this happens - has anyone :?:

[Kitman]

Originally posted by RatAtAt
Thank you - it's not just me then :!: (although I guess you meant "12/12 rather than 5/12" not "7/12" :?:

You're right about the 5/12 date, of course - see: I said it could confuse a stupid person! http://www.hummy.org.uk/invison/style_emoticons/<#EMO_DIR#>/biggrin.gif

[aldaweb]

I've had this also with recordings from 1/12 having date of 8/12 and have two News Quiz fom the radio dated 9/12. these are set from weekly timers though since the update I have padded the end and not seen it.

[moseygunn]

We have experienced this several times with weekly scheduled recordings (but it doesn't consistently happen - sometimes the correct date is listed, sometimes the following week i.e. the recorded program is labelled with the next scheduled recording date). Also, sometimes the correct name of the programme is shown, sometimes it loses the name and just gives the date/channel.

[peaton]

Looks like I have this date problem with daily recordings.

[aldaweb]

Originally posted by peaton
Looks like I have this date problem with daily recordings.
I've just noticed get this with daily recordings as well. First lot of daily recordings and the first two are dated correctly but the last two are dated a day ahead.

[Monkey]

I've just noticed I'm getting this with Home and Away every dat on 5 at 6pm. The first scheduled recording has the correct date but all the the others have the date 1 day in the future.

I have only padded 2 mins onto the end but nothing before.

I've tried rebooting, re-scheduling, etc.. but it keeps on doing it.

This only happens for Home and Away, nothing else. I guess the next software update may fix it ???