06-17-2012 09:37:27 PM
I have two issues with the way Uverse resolves recording conflicts.
First, when I am watching live TV and select that I want it to be recorded, I want to be alerted to conflicts that would occur during the entire course of the show, not just at that moment.
I was watching the NBA Finals and decided I wanted to record it since I need to take a break. Uverse correctly warned me that too many shows were being recorded and I selected one to stop recording. The Final started recording.
When I went to watch the Finals later, it was cut off mid-way, stopping at 7 PM. Another show had started recording at 7 PM as per original schedule. When I selected that I wanted to record the live TV, Uverse knew that there would be a conflict at 7 PM, but did not bother to tell me so I could resolve it.
When I had a TiVo, it would tell me all of the conflicts and I could resolve them. Almost every time when I selected I wanted to record live TV, that was more important to me than the scheduled recordings.
Second, when I am watching live TV and a scheduled show needs to be recorded, Uverse stops live TV and tells me to pick a show to stop recording to fix it. During that time, my live TV stops. Depending on how fast I move, I can miss a couple of minutes of live TV, which is a lot at the end of a sports event.
Again, my TiVo would warn me ahead of time, not interrupting my live TV, and let me correct it before the new recording needed to start. If I wasn't watching, then it timed out and switched over to the scheduled recording. I'd like Uverse to do the same.
Losing recordings of live sports events is important enough to me that I will eventually cancel service if AT&T can't copy TiVo better.
06-19-2012 10:05:53 AM
The DVRs used to alert that there was a schedule conflict at the time when a recording is scheduled. I don't know when that feature changed. What I have done, just to make sure that my scheduled recordings are scheduled is to go to the scheduled tab in the menu. There you will see any conflicts that may have come up. This is not suggested as a fix for your question but is a workaround. Hopefully an update will be rolled out soon that will include notification of recording conflicts.