[kstuart]

I am posting this both to ask for confirmations from others, and also to warn people about this bug. I am also curious as to how many other models (besides my own 622) are affected. I would guess that 612, 622 and 722 all have the same timer code, but it is possible that the bug dates back to the 522.

Here is the bug:

If a DVR Mon-Fri timer is pre-empted in the schedule, then it will not
record due to "incorrect event", which is right.

If a new timer is created for the new (pre-empting) event, then that
will not record due to "duplicate event", which is wrong and a bug. What is worst about this is that there is no warning when you are creating the timer. If you create a timer, and it will not record due to priority, a popup message immediately appears informing you about that. However, in this case, no message appears whatsoever, just the red X in the schedule, with the xplanation "duplicate event".

---

This was brought to my attention because it comes up quite a bit at the moment due to the Olympics. If you have a pre-existing weekly or M-F DVR timer for an NBC (or CNBC or MSNBC) program, during these Olympic weeks, it will come up as "incorrect event" which is right. But if you then create a DVR timer for the Olympics event, it won't record due to "duplicate event" which is wrong.

Let me know if you have seen this before, and if so, what model DVR. I have reported this to Dish, and it would undoubtedly be helpful for them to read any other reports about it.

 

[SaltiDawg]

...

If a new timer is created for the new (pre-empting) event, then that
will not record due to "duplicate event", which is wrong and a bug. ...

New timers, without extraordinary effort by the user, are assigned the lowest of all existing priorities and will not record if in conflict with any previously existing timer.
This is not a bug.

 

[dbconsultant]

We saw the same thing happen last Friday. Had a timer set up for the opening ceremonies of the Olympics and had it at the top of the priority list. No other timers set during the time that the opening ceremonies were going to record. The event for the opening ceremonies showed that it would not record because it was a duplicate event that would record on channel 004 yet that is the channel this timer was for! Confirmed that I didn't have the timer set up twice but could not get the event to restore. Deleted the timer, put in a new one for the same channel and then it looked ok and was scheduled as it should be. The night before, I went in and checked and the event once again showed that it would be skipped as a duplicate event. I was able to restore it but this is really frustrating. Saw the same thing happen with one of the Little League events. Now I feel like I have to check everything on a daily basis to make sure that all will tape as they are supposed to.

 

[kstuart]

New timers, without extraordinary effort by the user, are assigned the lowest of all existing priorities and will not record if in conflict with any previously existing timer.
This is not a bug.

If there is a Priority Conflict, then a popup message tells you that, and gives you two choices.

Also, in the schedule, it will give the reason " Event skipped by priority ". In this case, as I stated, it gives the reason as " Event skipped duplicate event ".