10 Messages
DVR click forward will jump to the beginning of the recording
I've having the same problem as here: https://forums.xfinity.com/conversations/x1/dvr-jumps-back-to-beginning-of-recording/65ada133ed17eb490b57132a and https://forums.xfinity.com/conversations/x1/dvr-click-forward-will-jump-to-the-beginning-of-the-recording-corrected/6551773920a91817c99111c9. Note that there are literally over 1,000 people who are following that thread. They want the problem fixed. It is terrible. It makes the product you sell unusable. I never had this problem with TiVo and now you don't support TiVo. It is like you are begging us to try a different service.
XfinityBillie
Official Employee
•
3K Messages
26 days ago
4
0
fishfix
Contributor
•
17 Messages
19 days ago
I too have this problem. FF and goes to the beginning of recording. Today for the first time it went to the end of the Eagles recording ruining the entire point of recording. The delay incurred when fast forwarding is excruciating. Most of the time the fast-forward problem is with football games. Thousands of people with the same problem thousands of people paying a king ransom and not receiving good service.
1
0
fishfix
Contributor
•
17 Messages
18 days ago
Did it again tonight with the lions Ninners game. Right to the beginning when fast forward hit. Also will not do slow motion. It just freezes and pixelated. So sad that I can’t get what I pay for. Shame on you Comcast. Oops I forgot you have no shame.
3
0
user_778dlz
1 Message
3 days ago
We have been having this issue for weeks now with no resolution! We are extremely frustrated with no resolution that we are considering switching providers!
1
0
user_63b4s9
10 Messages
3 days ago
We still don't have a resolution. I am a retired software engineer. This is a bug. This is clearly a bug. Since it happens intermittently it is a very hard bug to find. But it is a bug that is not impossible to find and fix with enough effort. My guess is the program has a variable that represents the current time. For example if you have been watching the program for five minutes and you press a button it holds that "five minute" number in memory (most likely the number of milliseconds since the program started). Somehow that number is lost and gets reset to zero. The bug is intermittent but not that difficult to reproduce. A test engineer could watch a program (especially one that is currently recording) and then press the fast forward button every few seconds. Do this enough times and it will happen. Meanwhile, inside the code they should be tracing the various values. As soon as the button is pressed it should log these numbers. As soon as it comes out of fast-forward it should log the numbers. Most of the time the numbers will make sense. But when the bug happens the numbers won't. The developers should be able to figure out what is going on and how to fix it.
The support staff needs to work with the QA/Engineering staff to fix this bug. Is this even registered as a bug? Even highly sophisticated software companies (like Google) have known bugs (that you can see on the forums). We are getting nothing here but underpaid help staff suggesting things we've already tried. (Or bots that are much worse.)
0
0