[Skates]

I'm having a weird problem the past two or three weeks. All of my timers are set up as standard timers. They're just set to record a given show weekly and I'm not using any of the features for "new episodes" or "all episodes".

Now, the 622 is starting to mark some timers as "incorrect event" and X-ing them out. But when I check, I find that its the correct episode in the correct time slot, and I have to restore the event.

Any idea what's going on here?

 

[kmcnamara]

I've noticed that too. Fortunately, I haven't missed any recordings because of it (I've manually overridden the incorrect event thing). OTOH, it could just be an invalid error message and the recording would fire anyway.

 

[Ron Barry]

Need More Info Skates so we it can be reproduced.

1) Your timer is a weekly timer?
2) What programs are you seeing this on?
3) Does it happen 100% of the time.
4) Single or Dual Mode.

Cheers,

Ron

 

[Skates]

Need More Info Skates so we it can be reproduced.

1) Your timer is a weekly timer?

Yes - only happens on weekly timers.

2) What programs are you seeing this on?

I'll give two examples - Numbers and L&O:Criminal Intent

3) Does it happen 100% of the time.

On those programs, yes...seems once the issue starts, it continues each week.

4) Single or Dual Mode.

Single mode.

 

[Ron Barry]

is Numbers or L&O OTA or Dish HD locals or on SD?

I will set up a timer and see if it happens in for me... As for having any idea what is going on... Don't know.. I don't use weekly timers.. Only New and All and Dish Pass.

 

[Skates]

is Numbers or L&O OTA or Dish HD locals or on SD?

SD? What's that?

That's a great question - I should have thought to mention it - Numbers is CBS HD (mine is set to record from 148, channel 9484). L&O is OTA.

 

[lujan]

I've noticed this as well on a couple of my M-F timers. The only thing I can guess about what is causing this is when the show doesn't show on one of those days (like say Wednesday). It seems to screw up the rest of the week or the same day the following week. When this happens I just delete the current timer and create a new one.

 

[Skates]

That's very interesting. It definitely could have happened that way. Maybe it's a fixable bug. I just don't really have any way of knowing whether I can trace it to a s/w update because I kinda noticed the problem gradually.

What I've been doing is just reviewing my timers ahead a few days and restoring them...I did delete a timer and re-create, but I've been so busy lately that I can't remember which one it was now or whether it solved the problem - I really gotta start writing this down

 

[Bradtothebone]

I've noticed this as well on a couple of my M-F timers.

Hey, watch the language - this is a family site!

Brad

 

[lujan]

Hey, watch the language - this is a family site!

Brad

:lol: :lol: :lol:

 

[BillJ]

I've had this happen a few times. Never been able to find a cause or common trait. So far I've spotted it in advance and fixed it before I missed a recording.

 

[Mando]

I'm having the exact same scenario here.

I have a weekly timer to record ER off the OTA HD NBC feed (04-001) here in LA, CA. @ 10pm. I have to manually "restore" the "incorrect event" every week.

It's quite frustrating that I have to look up the "to-do" list to see if my show is going to be recorded.

Anyone figured out why this is happening?

Question - isn't ER one of those "-1 minute before" shows that starts @ 9:59pm on the guide? On my ReplayTV DVR, this was the case. I'm wondering if this is related. This is a tactic used so that single-stream DVR can't record anything at 9:30pm (if a 1/2 hour show) or 9pm (if an hour show), without causing a "conflict."

 

[lujan]

I've had the same problem with one of my daily shows that I record during the day. This has been happening for several weeks now. Maybe we need to delete all timers and then do a cold re-boot and then re-create all of the timers? Do you think this might fix it? I'm waiting for the next update before I move the heavy TV out of the way to do the cold reboot.

 

[Ron Barry]

Mando,

Any reason to create a All Episode Timer rather than weekly? I think that would provide a good workaround and it will not record duplicate shows.

By the way... I created a weekly timer and was able to recreate the issue.

Have not looked at if weekly timers and All or New timers result in a different number of timer events. That might be a reason to create a weekly over a All or new timer but other than that I am not sure what the benefit would be.

 

[Postman]

I've had the same problem trying to set a timer to record channel 205 at the same time every night. If I fail to check every few days, the programs are marked incorrect event.

 

[bobl]

I've had this problem for a long time and I know what it is. This happens when a program is scheduled for a time slot which is immediately after the last program in the guide. For example, let's say you have a program slotted to record at 10:00PM in eight days. The guide is now filled up to the point just before this start of the program. I've noticed that the daily schedule will show the timeslot but not with the correct program. Instead it will say something like missing event (can't recall the exact wording). The next day when the guide downloads the information for the program everything looks normal except the program is marked as being skipped due to the previous day's initial tagging of the time period. This seems to happen regardless of how the program is recorded as long as it's not a one-time event which can't be scheduled until it's actually in the guide. This is a bug in the 622 software which needs to be fixed. The program in the daily schedule must be manually restored so that it records properly.