1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

amount rewind at the end of FF 1x more than in the past

Discussion in 'DIRECTV HD DVR/Receiver Discussion' started by rajeshh, Aug 17, 2009.

  1. rajeshh

    rajeshh Godfather

    263
    0
    Sep 11, 2007
    I have posted this in one of the issues thread a while back, but am making a thread of its own because football season is around and I am hoping this gets fixed before then ( and confirmation that I am not the only one seeing this).

    So for about some months now, when I FF 1X, and hit play, it backs up more than it did last year for example. I use this a lot to go between plays of a recorded baseball or football game, and its annoying now because if I stop at exactly where I would last year, it backs up 2-3 seconds more than I would like.

    Anyone else see this?
     
  2. calidelphia

    calidelphia Godfather

    264
    0
    Feb 17, 2007
    I was logging on to start this very same thread.

    I wish it didn't autocorrect FF1 at all...

    For a while it was just a stutter or 1 second back. Now after counting the seconds, it's about 4 1/2. Way too much. It's very irritating trying to FF between pitches in a baseball game. This will also annoy the hell out of me during football season.

    They need to axe this immediately. If you can't stop where you want on FF1, you probably have a vision problem.
     
  3. ddockery

    ddockery Cool Member

    16
    0
    May 15, 2008
    I just noticed this between pitches as well. Very annoying.
     
  4. Doug Brott

    Doug Brott Lifetime Achiever DBSTalk Club

    28,939
    72
    Jul 12, 2006
    Los Angeles
    I'm not sure of this .. As far as I know, the autocorrect is the same that it always has been.
     
  5. calidelphia

    calidelphia Godfather

    264
    0
    Feb 17, 2007
    Doug, I remember back when autocorrect was first implemented. A bunch of us whined that FF1 jumped back too far. About six months later it was changed.
     
  6. calidelphia

    calidelphia Godfather

    264
    0
    Feb 17, 2007
  7. Doug Brott

    Doug Brott Lifetime Achiever DBSTalk Club

    28,939
    72
    Jul 12, 2006
    Los Angeles
    Perhaps "always" wasn't really the term I was shooting for here .. :grin:

    I don't think that this feature has been tweaked since it was initially stabilized .. how's that? :)
     
  8. e500

    e500 New Member

    8
    0
    Aug 31, 2007
    I agree with the first two posts. It definitely backs up too much and is irritating for me also. They did fix it some months ago to where it backed up very little. Now whether intentionally or not they have changed it to where it backs up even more than I ever remember it doing so before. In my opinion, at 1x FF it shouldn't back up at all.
     
  9. reber1b

    reber1b Legend

    169
    1
    Jun 14, 2007
    I too agree with OP. I wish we could get D* to remove the auto-correct altogether for 1x -- it's so frustrating to deal with that I sometimes think my head will explode.
     
  10. RACJ2

    RACJ2 Hall Of Fame

    3,872
    5
    Aug 2, 2008
    Yes, I experience that as well. This isn't a fix, but a workaround I use. When you use FF1, instead of pressing <Play>, press <Pause>, then <Play>. It seems to only rewind about a second that way. So it stops at the right spot, but still causes you to wait a couple seconds while you do the extra step.
     
  11. Scott Kocourek

    Scott Kocourek Well-Known Member

    9,491
    523
    Jun 13, 2009
    I agree it would be nice if the auto correct would be removed for 1X, but I would also like to see them back off the auto correct on the other speeds too. Always seems to jump back farther than I can get used to.
     
  12. rajeshh

    rajeshh Godfather

    263
    0
    Sep 11, 2007
  13. RoyGBiv

    RoyGBiv Icon

    702
    6
    Jul 24, 2007
    I, too, am not a fan of autocorrect for FF1 but the post above using pause as an intermediate step is the way around it (for now). That method using pause instead of play when stopping FF works to prevent autocorrect for any FF speed. I use it a lot. My recollection is that this technique, i.e. pause canceling autocorrect, was the way TiVo implemented autocorrect, and a few NRs ago, D* changed to the same way.

    SMK
     
  14. bigwad

    bigwad Godfather

    382
    0
    Oct 19, 2006
    I agree, the 1x should not have an autocorrect. I remember it being that way before, but has since changed. I'm not sure why it would autocorrect at such a slow speed anyway. And we should not have to push 2 buttons for such a simple thing.
     
  15. reber1b

    reber1b Legend

    169
    1
    Jun 14, 2007
    RACJ2, thanks for the tip, I tried it last night, and I think it'll work for me. I wonder if it would work in a macro on a universal remote.
     
  16. The Merg

    The Merg 1*

    10,289
    35
    Jun 24, 2007
    Northern VA
    No reason it shouldn't.

    - Merg
     
  17. RACJ2

    RACJ2 Hall Of Fame

    3,872
    5
    Aug 2, 2008
    Your welcome and thanks for your idea. I'll have to see if a macro will work.
     
  18. calidelphia

    calidelphia Godfather

    264
    0
    Feb 17, 2007
    Except for the fact that some of us have HRs with brutally slow UIs that don't see all button presses. Sequences on my Harmony One are useless with this box.:(
     
  19. RACJ2

    RACJ2 Hall Of Fame

    3,872
    5
    Aug 2, 2008
    I was able to set up a macro for the <Pause> then <Play> and it works perfect. Thanks again!

    Also, I was able to set this up on my Harmony as well. After reading other posts about Harmony remotes and sequences, I learned something. My 659 can do macros, they just call them sequences. I think this feature may have been added on one of the software updates I downloaded, since I first got my Harmony remote.
     
  20. TomCat

    TomCat Broadcast Engineer

    4,153
    101
    Aug 31, 2002
    Agreed. I'm bumping this to hopefully help get it on their radar.

    How about fixing this, DTV? We would have to be asleep, mentally challenged, and blind drunk to need this amount of autocorrect. Stop worrying about "UI polishing" and "faster restarts" and concentrate on the nuts and bolts features we all depend on every day to NOT CHANGE to some ridiculous new setting.

    While no change may have been made to it, the fact remains that it is way too large now compared to what it was, so possibly some other change precipitated this, which is not an excuse not to fix it.
     

Share This Page