If you take a look at the image I posted a few entries back, you'll see that there is no AM/PM problem.
The image doesn't load for most of us... requires a membership to esnips i guess.

No problems with any timers I had set this evening. I set my timers from the guide.

Hey Gary, nope it is definitely not an AM/PM problem. In fact, I have had these weekly timers set for ... well ... weeks! It just started tonight, everything was fine last night.

If it continues, I'll give *Choice a call tomorrow afternoon. It is too late now.

If anyone hears anything about why this is occurring, please post! Thanks.

I'm in the same boat and just got off the phone with SC. They basically have no answer for this. I know, you're all shocked.

Besides the fact that the girl is a Flames fan, my only complaint is that "Your box shouldn't do that" doesn't really help me out. Anyway, her best advice was for her to do a factory reset on my box, citing that since the CC download, extra crap could basically be confusing the box and starting over from scratch might help. I decided not to go quite that far yet, but (on her recommendation) to do an "AC reset" which is basically unplugging it for a few seconds...all is OK for now, although 20 minutes will not tell the story.

Interestingly enough, she was also of the opinion that the power-button reset (sorry, don't recall the actual name for it) is basically useless on the 530...can't say I disagree...

Upon explaining to her that my timers that were up against each other (say, 7-8pm on one channel, then 8-9pm on another) worked for the last six months, she said "they shouldn't", as this consititutes an overlap conflict....is it just me or is this insane? ...So I should cut off the last (or first) minute of every recording so the fancy computer that is my DSR530 can figure out to change the channel while recording. AAAAhhhhhhh!!!!!!!

So ya....I'll keep you posted...

I had the conflict a day or so back when a 6-7 PM show conflicted with a 7-8 PM show right at 7 PM.
Aren't we approching the DST exit time?
I wonder if there is something funny in the guide data all of a sudden.

While code bugs are certainly possible, with it all occuring together, there must be some external trigger and guide data is all I can figure.

Maybe it will go away like the last freaky behavior that was caused by changes in the control stream.

I don't think we ever did hear the root cause, it just went away.

Maybe it's Halloween spookiness?

I'm in the same boat and just got off the phone with SC. They basically have no answer for this. I know, you're all shocked.

Besides the fact that the girl is a Flames fan, my only complaint is that "Your box shouldn't do that" doesn't really help me out.

Well, that is disheartening.

I tested again this morning and the same error keeps occurring.

What doesn't make sense, is that these are weekly timers that have existed since early to mid September. Nothing has changed.

I was hoping that *Choice was just flagging their guide incorrectly, but since not everyone is having this issue, that can't be the reason.

I am tired of hearing that a factory reset will cure all. It doesn't. It has never cured anything for me, in fact.

And as for the *Choice tech saying that you shouldn't be able to have a 7 - 8 pm timer and then an 8 - 9 pm timer because they overlap, WTF? I do not set my timers manually. The guide sets them up for me and the guide states the times in that manner.

Uh. I am so sick of this.

Interestingly, single event timers work fine and do not conflict. I can tape from 7-7:30, 8-9pm, 9-10 pm, etc. and they will all record. But, I can't ask the machine to do this on a weekly basis.

:o

Chalk up another one for the time conflicts.

My Sunday nigtht and Monday night timers have various back to back shows. They have been set up the same way for weeks with no problems. Now they're all reporting conflicts. I have missed some shows and had one two hour timer record an HD channel for 12 hours (until I cleared the message).

When I called SC on Monday they had no knowledge of such a problem. I'll see what they have to say today. This is nuts!!!

Same here, timers that have worked well for weeks now have a conflict. Recorded 10+ hours last night 'till I shut them off this morning.

I had the conflict a day or so back when a 6-7 PM show conflicted with a 7-8 PM show right at 7 PM.
Aren't we approching the DST exit time?
I wonder if there is something funny in the guide data all of a sudden.

While code bugs are certainly possible, with it all occuring together, there must be some external trigger and guide data is all I can figure.

Maybe it will go away like the last freaky behavior that was caused by changes in the control stream.

I don't think we ever did hear the root cause, it just went away.

Maybe it's Halloween spookiness?

ARR, I'm thinking this is likely...everything else in my settings/timers has been static for months, the guide data (and the occasional one-off timer recording) is the only thing changing...

I had the conflict a day or so back when a 6-7 PM show conflicted with a 7-8 PM show right at 7 PM.
Aren't we approching the DST exit time?

Ohmigosh! That would make perfect sense! My timers were set for next Monday, after the daylight savings time change. In the past, I have always had to go in and change them all.

Well, that makes me feel better and slightly dumb. :rolleyes:

I agree with ARR as well. I've had 2 conflicts that didn't make sense until now. I'm sure it has to do with DST.

Ohmigosh! That would make perfect sense! My timers were set for next Monday, after the daylight savings time change. In the past, I have always had to go in and change them all.

Well, that makes me feel better and slightly dumb. :rolleyes:

It looks like there is a new DST bug. I am seeing numerous conflicts for next week.

The best way I found to get around this is to change the "Record" timer to a "Tune To" timer. Next Sunday change them back to "Record Timers" and adjust the times if they need it.

I don't think DST is the issue. Why would exiting DST next weekend impact only some timers from last friday and saturday (in my case)? Besides, having one timer end at the same time another begins has never been an issue for me before. Also, the change in DST should only change the system time, not the timers.

...or I could be wrong...or *C could just be clueless...

Anyway, I guess we will just be loft to daeal with the fallout ourselves...

I have deleted any weekly timers that will fall after we change our clocks for standard time and will redo the weekly timers after the time change. I have yet to have any timer conflicts, but I guess only time will tell.

I don't think DST is the issue. Why would exiting DST next weekend impact only some timers from last friday and saturday (in my case)? Besides, having one timer end at the same time another begins has never been an issue for me before. Also, the change in DST should only change the system time, not the timers.

I'm really not sure. I can't imagine why it would affect a Friday timer. It may affect Saturday if it goes beyond midnight.

I do remember, though, that I always had to change my timer back (or forward) one hour after DST because the DSR would not make the change for me.

Anyways, I am HOPING this is the problem. If not, we are in for it. :eek:

I am going to go with single event timers all this week, reprogram weekly timers when Sunday comes around and see what happens. :eek:

The image doesn't load for most of us... requires a membership to esnips i guess.Oh, I didn't know that. Well if you go to esnips you can find it by keying DSR530 into the SEARCH field.

http://esnips.com

There is still something strange going on. Even if the DST kicks in, the times that are in conflict are almost 24 hours apart.

Saturday at 1:00 AM to Saturday at 2:00 AM
Saturday at 11:30 PM to Sunday at 1:03 AM

2 AM Saturday to 11:30 PM Saturday is quite a distance apart.

GAWD...some people have just got nothing else better to do excect..."Complain":rolleyes:

I know others have had this problem but I have to say this is a first for me. I got home from work yesterday and turned on the receiver to set up some recordings I wanted to do that night and found there were 2 separate recordings that I have no idea how they got there. One was for 30 minutes and the other was for 2 and a half hours!? I asked everyone in the house kids, dog, cat, and no one recorded these programs. Who would - one was for "Maury" for cryin' out loud! Other than this peculiar thing that just, well, happened . . . I really haven't had too many issues with this recent download. I've only had to do a couple of soft resets when I couldn't get the guide to work but other than that it's been great.

GAWD...some people have just got nothing else better to do excect..."Complain":rolleyes:Hmm, I guess people who like to COMPLAIN about others complaining should not participate in threads entitled:

DSR530 Code CC Fixes, Features & Bugs

Who would - one was for "Maury" for cryin' out loud! I got home from work one day last week and noticed that the program "So NoTORIous" was recorded. I thought it was some fluke with the schedule because I would never record something like that. Tori Spelling? I don't think so.

However, now that you mention the machine is also recording shows at random, it explains that one!

Reminds me of the TIVO story, maybe folklore, the units 'learn' what you like to watch and try and record shows it thinks you'll like, so some unsuspecting sole accidently watched Will & Grace and the Tivo promptly filled his hard drive with Gay Porn!