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

722k Timer issue

Discussion in 'ViP612/622/722/722K DVR Support Forum' started by FastNOC, Mar 14, 2010.

  1. FastNOC

    FastNOC Godfather

    410
    1
    Sep 11, 2007
    For some bizarre reason, ALL of my timers appear to be on vacation.

    None of them show any pending events. i have 85 timers, and record multiple shows every day. I can manually go back into the guide and ONE BY ONE set them to record, but i'm hoping there's an easier way to re-search the guide to track the timers.

    I rebooted hoping it was a glitch, but so far I can't figure it out.

    Thoughts?
     
  2. bobl

    bobl Legend

    136
    0
    Jan 17, 2004
    Maybe you've lost your program guide information? If so, do a check switch and your receiver will download a new guide.
     
  3. harsh

    harsh Beware the Attack Basset

    21,192
    182
    Jun 14, 2003
    Salem, OR
    Note also that several shows are winding down for the season. This is heralded by the spinning up of DWTS each spring.
     
  4. FastNOC

    FastNOC Godfather

    410
    1
    Sep 11, 2007
    you're not understanding.

    i have a timer for 'friends'. normally i records 3 to 4 episodes a day, and skips 5 or so due to conflicts.

    if i go into the timer, it shows zero upcoming events. if I EDIT the timer, and go from say, all episodes to new episodes, all the skipped recordings show. if i edit again and go back to 'all episodes' then they all show up again. but i HAVE to edit EVERY timer for it to pick up the upcoming events again.

    samewith all 84 timers.
     
  5. CABill

    CABill Hall Of Fame

    2,114
    2
    Mar 20, 2005
    I can't recall the exact details, and it was probably not even a ViP, BUT, I recall testing number of timers and number of events previously. At a minimum, the number of each were limited to something less than what they are now. Once the receiver (probably was a 942) hit a timer that had so many events that the max number of events was exceeded, it stopped processing that timer and all other timers. I don't even recall the max number of events now, but if your Priority 1 timer is a DishPASS for anything with "LAW" or "CSI" and there is some marathon this weekend, it *MIGHT* stop automatically entering events for existing timers (unless you do them manually). If you step through the 84 timers, does one have some huge number of events?

    EXTREME Longshot!
     
  6. russ9

    russ9 Godfather

    391
    3
    Jan 28, 2004
    I have numerous timers that show the same thing, the show up in the timer list with no date/times shown, and don't show up at all in the guide. Editing the timer does not seem to do any good, I am having to delete them.

    Updates: No new issues, all the "corrupted timers" have remained so. While I initially believed this to be related to the DST time change, I now am leaning towards the "too many timers" scenario. I did notice one other clue for a corrupted timer - if I go to edit, the only options available are All and New Program - Daily, Weekly etc. are grayed out. The end result is still deleting and creating new timers.
     
  7. articos

    articos Mentor

    45
    0
    Oct 10, 2006
    This has started happening on my 622, as well. Recently added timers show up in the timer list, and when I set them to record it shows up in the to do list as well as in the guide. But after the nightly reboot, these timers show with no upcoming events, and don't show in the guide, even for single occurrence timers. (Shows in the timer list, nowhere else, and won't record.) Strange. Only way to fix is to delete and re-add. Older timers aren't affected by this bug. They show up as normal. Also had a weird glitch with a single timer that was a record once on a specific date that I went to change the lead-in time in options, and it asked if I wanted to change just the one event, or all events of this timer, even though it wasn't a repeating timer.

    Something's strange. Thought it was the box starting to go, which it might be, but this seems like a new software glitch in addition.
     

Share This Page