Tonight I tried to create a series timer for a program that's scheduled at the same time as three existing series timers. I expected that, since it was a series timer, it would automatically record the next showing. Instead, it brought me to the conflict resolution screen. I took the opportunity to select a different program that I was least interested in seeing the same night, and that had the most reruns scheduled during the week, and selected "record next showing" from the menu which popped up. Instead of recording the next showing, it deleted the timer! (To be clear, this wasn't even the new timer, but a pre-existing one.)
So, I went into the guide and found that program that I wanted to be the last priority, and selected "record series", expecting it to create a timer with the lowest priority and automatically record the next showing. Of course, it brought me to the conflict resolution screen again. Selecting that program and selecting "record next showing" resulted in that timer being deleted too!
Finally, I went into the guide and selected a later showing of that program and selected "record series". This time it did indeed create the timer with the lowest priority and schedule the second showing to be recorded -- but it created the timer as "new and reruns" instead of just new.
Needless to say, I never had this problem with my 622, and I don't remember having it on my HWS before the CUI. I have to wonder if Dish ever tested the CUI on anything other than a Hopper 3, or if so, how anyone with any integrity whatsoever could release it!
So, I went into the guide and found that program that I wanted to be the last priority, and selected "record series", expecting it to create a timer with the lowest priority and automatically record the next showing. Of course, it brought me to the conflict resolution screen again. Selecting that program and selecting "record next showing" resulted in that timer being deleted too!
Finally, I went into the guide and selected a later showing of that program and selected "record series". This time it did indeed create the timer with the lowest priority and schedule the second showing to be recorded -- but it created the timer as "new and reruns" instead of just new.
Needless to say, I never had this problem with my 622, and I don't remember having it on my HWS before the CUI. I have to wonder if Dish ever tested the CUI on anything other than a Hopper 3, or if so, how anyone with any integrity whatsoever could release it!
