[NFLnut]

I've noticed a new problem with pausing on 0x254 .. when you PAUSE and then resume, either hitting PAUSE again or PLAY it jumps back 3-4 seconds. This was a problem up until about 8 months ago with FFx1 but finally after much user protestation, they fixed that.

NOW, ONCE AGAIN, it is impossible to get to a particular spot of a recording or LIVE TV using PAUSE or FFx1, which is a REAL problem when trying to watch football!

Could we FIX THIS DirecTV?!!! What's the use of having a PAUSE function that essentially becomes nothing more than a Instant replay button?!

I swear .. after over two years with this boat anchor, they STILL haven't gotten things right! The ONLY good news is that I will have the opportunity to get an HD DirecTiVo in a little over a year. THANK GOD!!

 

[pacjag]

Yeah, I've noticed this recently also.

 

[kocuba]

I have been noticing this also lately. Also notice it does the same thing when I do the 30 sec skip. While I'm not upset about it as you are I agree that it is something that should not be happening. Atleast in my mind.

 

[Stuart Sweet]

I have noticed this as well but I'm actually ok with it. When I'm paused it's just as likely to be in the middle of a word so it's ok for the playback to back up a little bit to give me some context as I start back up.

 

[deltafowler]

Auto-correct coming out of pause makes no sense whatsoever.
Dump it.

 

[Flyrx7]

I have been noticing this also lately. Also notice it does the same thing when I do the 30 sec skip. While I'm not upset about it as you are I agree that it is something that should not be happening. Atleast in my mind.

While the autocorrect out of pause doesn't bother me that much, I actually kind of prefer it, but the autorcorrect after the 30 sec slip drives me crazy!
It makes trying to watch a recorded football game rather bothersome, always showing a little spoiler on each play, then correcting back 3-5 seconds where I get to see it again.

Autocorrect should at least be an option we can switch on/off, or not be used with a single click of slip. That, and a single click of slip/skip should be set to 25 seconds to match the NFL play clock!

Regards,
Frank

 

[NFLnut]

Well .. it bothers me BIG time for several reasons, but the biggest is that simply .. PAUSE should NOT jump back or autocorrect!

I swear .. the HR20 looked so promising on paper, but after 2+ years, it's basically a failure! It can't even do BASIC FUNCTIONS properly!

DirecTV: PLEASE do SOMETHING about this! If I wanted jump-back or autocorrect on PAUSE, I would press TWO buttons! This makes it VERY difficult to navigate a football game!

 

[Flyrx7]

If I wanted jump-back or autocorrect on PAUSE, I would press TWO buttons! This makes it VERY difficult to navigate a football game!

I may be missing something, but how are you using the pause function so much during a game that is causing you this grief? Just curious.

Frank

 

[NFLnut]

I may be missing something, but how are you using the pause function so much during a game that is causing you this grief? Just curious.

Frank

I am a 14 year Sunday Ticket subscriber. I watch/switch between several games on a couple of DVRs. When I PAUSE, I want the game to resume EXACTLY where I paused at, not the play before!

Also, my SD DirecTiVos do not sync up exactly with the HR20, so I have to pause the HR20 for a second or two so that the TV's in the rest of the house that are on the SD TiVos, are at the same spot (otherwise, I end up with annoying echoes coming from other parts of the house). It is IMPOSSIBLE to do this with PAUSE effectively becoming a delayed JUMP-BACK button!

The bottom line AGAIN is: PAUSE should **NOT** autocorrect!! DirecTV .. FIX IT!

 

[Rich]

Yeah, I've noticed this recently also.

This is nothing new. It's been obvious on the baseball games most of the season and it seems to be more than a couple seconds.

Rich

 

[mscog]

I am a 14 year Sunday Ticket subscriber. I watch/switch between several games on a couple of DVRs. When I PAUSE, I want the game to resume EXACTLY where I paused at, not the play before!

Also, my SD DirecTiVos do not sync up exactly with the HR20, so I have to pause the HR20 for a second or two so that the TV's in the rest of the house that are on the SD TiVos, are at the same spot (otherwise, I end up with annoying echoes coming from other parts of the house). It is IMPOSSIBLE to do this with PAUSE effectively becoming a delayed JUMP-BACK button!

The bottom line AGAIN is: PAUSE should **NOT** autocorrect!! DirecTV .. FIX IT!

They might of did this to help people like me who use closed-captioning. It takes a couple of seconds for CC to start up again after a pause, this way you do not miss anything that is being said after a pause. Maybe they should make this a menu option so you can turn it on or off.

 

[DBSNewbie]

This "back-up" after the initial pause appears to be a byproduct of the fast forward to live TV feature that was implemented a few software versions ago.

Before, when playback would resume at the exact point you paused at, you would actually be 3 - 4 seconds behind "Live TV" when you fast forwarded to the end of the buffer.

That presented a problem for those who would have the same program on different TVs. (A Super Bowl Party, for example) where the game is showing all throughout the house. If one wanted to pause or rewind, it would then be impossible to catch up and be in sync with the rest of the TVs. (without having to clear the buffer by changing channels and switching back)

So, I guess D* decided to go with the lesser of two evils (in their estimation) and opted to go with the capability for the buffer to catch up to "live", and as a result, created this new problem.

 

[mrpull]

It has been years since i studied video compression and it may not even be valid for MPEG4, but I'm guessing it is jumping to the closest "key frame". Key frames have all the information to generate the entire picture. Non-key frames are built using the key frame + the differences since the last key frame... thus saving space by representing the unchanged data fewer times.

I cant describe it well.... see: this

Again, this is just speculation, but it gives a plausible technical reason for it skipping to a "random" frame. It also could be part of the reason why FF isn't as smooth as it used to be.

mr.

 

[NFLnut]

It has been years since i studied video compression and it may not even be valid for MPEG4, but I'm guessing it is jumping to the closest "key frame". Key frames have all the information to generate the entire picture. Non-key frames are built using the key frame + the differences since the last key frame... thus saving space by representing the unchanged data fewer times.

I cant describe it well.... see: this

Again, this is just speculation, but it gives a plausible technical reason for it skipping to a "random" frame. It also could be part of the reason why FF isn't as smooth as it used to be.

mr.

That makes sense and I also have noticed "issues" with FF of late.

Still .. the PAUSE issue I have described (jumping back) needs to be FIXED!

 

[paulman182]

It has been years since i studied video compression and it may not even be valid for MPEG4, but I'm guessing it is jumping to the closest "key frame". Key frames have all the information to generate the entire picture. Non-key frames are built using the key frame + the differences since the last key frame... thus saving space by representing the unchanged data fewer times.

I cant describe it well.... see: this

Again, this is just speculation, but it gives a plausible technical reason for it skipping to a "random" frame. It also could be part of the reason why FF isn't as smooth as it used to be.

mr.

That is a plausible theory, but I don't remember seeing this until recently, and I have recorded from the MPEG4 movie channels since they went online. Maybe I just didn't notice it until now.

It is a big irritation for me on whatever programming I'm watching.

 

[Steve]

Ya, as I recently posted here, there may be so much compression on NFL games that key frames are relatively scarce. Just a theory. /steve

 

[bonscott87]

Hmmm, I always thought it was a feature actually. First time it happened to me a while ago I couldn't figure out what was happening and I started thinking it was pretty cool because sometimes if I have it paused for a long time I would often back up a few seconds anyway to remind myself what was happening and here the DVR was doing that for me automatically. I like it actually.

 

[billsharpe]

Hmmm, I always thought it was a feature actually. First time it happened to me a while ago I couldn't figure out what was happening and I started thinking it was pretty cool because sometimes if I have it paused for a long time I would often back up a few seconds anyway to remind myself what was happening and here the DVR was doing that for me automatically. I like it actually.

I agree with you.

I watch a lot of college football and switch a lot between games, generally at commercial breaks.

I've found the PIP feature of my Sony Bravia great for watching two games at once, one through the HD receiver and one with an OTA antenna connected to the Bravia. Of course the OTA on the Bravia will only pick up my local stations, but last Saturday I could watch CBS and NBC plus switch to FOX for Dodger updates.

 

[Halo]

The pause/jump back bug only happens when Live in the buffer. Even 10 seconds back in the buffer the Pause/Unpause will work correctly. This bug never happened until they tried to fix the end-of-buffer audio problems in the past.
Fix something, break something else.

Mpeg isn't an excuse for the kludge. All frames are available after decoding. If you look at how the R15 does Frame-Reverse/ Frame-Advance it doesn't skip frames at all. The HR-2X version of Frame-Revers jumps ahead, then back 40 or so frames at a time. The R15 coders know how to correctly task the decoder to rebuild the frame buffer. That's apparently too complicated for the HR-2X guys and they only use I-frames.

 

[mikeinthekeys]

FWIW, I prefer no jump back on pause. I listen to internet radio audio of MLB games when the only HD coverage is the opposing team. It used to be fairly easy to synch up the audio with the game, but now much more difficult. In case you haven't noticed, this only happens when you are at the LIVE position. If you delay all your DVRs for 10 to 30 seconds, it is much easier to synch everything. After the first pause, the jump back DOES NOT occur and it works as you would expect a Pause to work... starts exactly where you stopped. Hope this helps.