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

L3.60 software experiences/bugs

Discussion in 'ViP612/622/722/722K DVR Support Forum' started by Ron Barry, Jul 26, 2006.

Thread Status:
Not open for further replies.
  1. Jul 29, 2006 #41 of 163
    knealy

    knealy Legend

    120
    0
    Jul 5, 2002
    After 360 release I notice that I can now extend recordings beyond the default record time and it functions properly.

    Video stuttering is still present on occasion.
     
  2. Jul 29, 2006 #42 of 163
    Mike D-CO5

    Mike D-CO5 Hall Of Fame

    3,099
    0
    Mar 11, 2003


    IF I hit 6 then 9 on the menu to try to go into the locals menu it will usually reboot immediately . Sometimes it won't even go fully into the locals sub menu and it will reboot like it did last night. Sometimes it will go to scan and then reboot.

    IF it has just rebooted then it is clear to go into the locals menu to do a scan etc. I wasn't even on an ota channel when I did the reboot. I was watching a recorded show and it rebooted. I notice this happens a lot more as the day gets later when it reboots if I try to go into the locals menu . Last night it happened at 11:30 pm . Just now I tried to reproduce it and it didn't happen at 3:20pm. I will try later tonight and see what happens.

    By the way all my ota timers are manual timers as I don't get guide data for my area . They are also set as daily timers.
     
  3. Jul 29, 2006 #43 of 163
    Mark Lamutt

    Mark Lamutt Your Neighborhood Liasion

    12,527
    1
    Mar 23, 2002
    John - really stupid question from me here (the one that's supposed to know all of this stuff)...how do you know which version of 622 you have? I'm not seeing any problems at all with editing timers and then doing anything in the locals menu. No crashes, resets, or anything at all amiss with mine.
     
  4. Jul 29, 2006 #44 of 163
    Mark Lamutt

    Mark Lamutt Your Neighborhood Liasion

    12,527
    1
    Mar 23, 2002
    Some of the DishHD locals have CC at this point, but not all. Still working them over with the other ones, though. I'm most concerned about the sync issue, and am hoping now that (knocking on wood bigtime) most of the video jitter problems have been worked out that CC can make it onto their radar, along with the upcoming features that I can't talk about at all at the moment.
     
  5. Jul 29, 2006 #45 of 163
    boylehome

    boylehome Hall Of Fame/Supporter

    2,143
    0
    Jul 16, 2004
    Mark,

    The version letter is found at the end of the number sequence on a label located on the back of the receiver in the area where the phone line input is located. Not long after the release of the 622 someone discovered the letter and it seems to have changed on a monthly basis with receivers released. I think F is the latest and G should be showing up if not already out.

    From your post and Ron's, I'm beginning to think I just have three strange receivers.

    John
     
  6. Jul 29, 2006 #46 of 163
    wje

    wje Godfather

    471
    0
    Mar 8, 2006
    New England
    I wouldn't rush into that if I were you. I just left D*, mostly for the same reasons! Check out some of the HR10-250 discussions on Tivocommunity. You'll see many of the same gripes there. Its OTA tuner in particular is a piece of junk.

    As for the update, I haven't seen any problems. Then again, I didn't have any problems before, except for the PIP/shared mode reset issue, which was easily avoidable. All in all, I've been MUCH happier with the 622 than with D*'s HR10-250.
     
  7. Jul 29, 2006 #47 of 163
    Mark Lamutt

    Mark Lamutt Your Neighborhood Liasion

    12,527
    1
    Mar 23, 2002
    That would explain it then, as this one that I have now is a version C. What is your bootstrap version? Mine's RBDD
     
  8. Jul 29, 2006 #48 of 163
    boylehome

    boylehome Hall Of Fame/Supporter

    2,143
    0
    Jul 16, 2004
    All my receivers are 1710 RBDD. I never had the "C" but I did have an "A" which was the first receiver where the bug was present in February or March. My signature has all the receiver data.
     
  9. Jul 29, 2006 #49 of 163
    High def mon

    High def mon Cool Member

    16
    0
    Aug 7, 2004
    Received L3.60 last night. Nothing has changed.
    Was having problems with 004 (check switch screen) during pip swap.
    I'll keep this forum apprised.
     
  10. Jul 29, 2006 #50 of 163
    Doggfather

    Doggfather AllStar

    72
    0
    Apr 19, 2004
    well it didnt fix my hdmi which 359 killed... sooo its time for me to request a new receiver from them. I waited patiently and i had enough now. ;0 New receiver time... I am not getting what i paid for... Digital HD...

    -Dogg
     
  11. Jul 30, 2006 #51 of 163
    Ron Barry

    Ron Barry 622 Tips & Trick Keeper

    9,881
    0
    Dec 10, 2002
    My new version looks like it is a C model. I basically repeated your steps with no luck. I will try downstairs. Does this only happen when you update an OTA timer or also with Dish HD. Almost wonder in your case could you get it to happen with no OTA channels in the picture.

    I wonder if the issues that you and Mike is seeing are releated to your OTA feeds. Possible something in one of the channels the 622 is having trouble with. Wonder if it is a case where the 622 needs to be more robust in handling suspect data. I will try to reproduct this one tomorrow.
     
  12. Jul 30, 2006 #52 of 163
    boylehome

    boylehome Hall Of Fame/Supporter

    2,143
    0
    Jul 16, 2004
    Ron,

    This happens with both OTA timers and Dish HD. I have one Dish SD that I can change, it is affected as well.

    These are good questions. I don't think that it is related to my OTA feeds, but who knows? Say it was realted to the feeds, then why is my version E unaffected by the bug?

    If I didn't have timers that I didn't want to lose (programs that are off for the summer but due to return in the fall) I would be willing to clear all of them and clear all the OTA channels then then test by creating Dish SD timers then going into local channels, Dish HD channels then going into local channels, and lastly OTA timers then going into local channels. Again I really thought that this bug was fixed until L360.

    At this point I feel that version C and E are exempt form the bug. Is there another administrator/moderator out there with a version B, D, or F that could test this?

    John
     
  13. Jul 30, 2006 #53 of 163
    Mike D-CO5

    Mike D-CO5 Hall Of Fame

    3,099
    0
    Mar 11, 2003
    Like I said earlier , I wasn't even watching an ota channel when I attempted to go into the locals menu and it rebooted. I also tried several times last night at different times to repeat the reboot and no go. I can't pin point what makes it reboot . Sometimes it happens late at night and other times it doesn't. But usually when I need to go into the locals menu I get a reboot.:confused:
     
  14. Jul 30, 2006 #54 of 163
    boylehome

    boylehome Hall Of Fame/Supporter

    2,143
    0
    Jul 16, 2004
    Mike if have read my posts you see that it happens with mine when I do something to the timers then go into the Local Channels (ota channel). If I modify a timer in the morning but then need to reacquire a Local Channel due to some problem in the evening. Hours later, when I go into Local Channels it will still cause the reset because a timer was tampered with.

    Can you look on the label located on the back of your 622 and look for the letter that is at the end of a sequence of number on a label located near the phone plug input and tell us what that letter is?

    Try this, then report on what happens. Do a power button reset. Once the 622 is up and running again, go directly into the Local Channels and attempt a Scan. If it causes a reset I would conclude that the problem is isolated to the channel acquiring process and the OTA tuner. I would then check your OTA connections including grounds, then do the test again. If it still resets, call Dish and request a replacement receiver. If it works fine then there is some process that is being performed before that is causing the trigger which is a software issue.
     
  15. Jul 30, 2006 #55 of 163
    Ron Barry

    Ron Barry 622 Tips & Trick Keeper

    9,881
    0
    Dec 10, 2002
    You make a good point on why it is not effected on E. One thing you do mention is having to reaquire a station due to a problem in the evening. Does this happen a lot. With my OTA channels I have not had to go into the local configuration screen for months.

    I will check the box I have downstairs and see what version it is. If it is not a C or E I will try to do your tests downstairs to see if I can get it to happen.

    How often do you guys access the local configuration screen? I usually just set it once and that is it.
     
  16. Jul 30, 2006 #56 of 163
    boylehome

    boylehome Hall Of Fame/Supporter

    2,143
    0
    Jul 16, 2004
    Here in good old DMA 130, yes it happens a lot. It is necessary as a station will start broadcasting corrupted data. The 622 is rigid and will not work with bad channel mapping. It isn't always necessary to actually reacquire the channel as it is still there, but doing an Add Channel is a good indicator to identify what kind of problem the station is having so I can report it to them.

    For the reasons stated above, plus there are rumors that a LP station may begin broadcasting in digital, quite a few times so to identify problems and check for new channels. Maybe once a week.
     
  17. Jul 30, 2006 #57 of 163
    pbrown

    pbrown Legend

    179
    0
    May 23, 2002
    I have had video stutter on both recorded and live programming since 360 came out. I don't think they quite have it down, but it has gotten a little better. Actually, I think this release may be a little worse for me in terms of stutter.
     
  18. Jul 30, 2006 #58 of 163
    lionsrule

    lionsrule Godfather

    449
    0
    Nov 25, 2003
    3.60 is the DEVIL.....maybe


    As I've said before, I lost nearly all local HD ota stuff. I had another 622 (unused/never hooked up) boxed up and ready to send back to dish (from a different issue). Well, not being one to shy away from experimenting, I decided to test it for OTA issues before sending it back to dish tomorrow....and guess what...all of my OTA's are rock solid!!!

    This brings up several issues. First, because this other 622 has not been activated since 3.60 existed, it is running on 3.59. Therefore, I really have no way of knowing whether is a software conflict problem or the OTA tuner in my original box going to crap. Your guess is good as mine. I guess I'll know after I activate the replacement box and get 3.60 in it. Anyone know if 3.60 is in WIDE RELEASE??
     
  19. Jul 30, 2006 #59 of 163
    lionsrule

    lionsrule Godfather

    449
    0
    Nov 25, 2003
    Just got done forcing my replacement 622 to get 3.60....and.....

    NO PROBLEMS WITH OTA's!!!!


    All signs point toward hardware problem with prev. 622?

    Who cares, I'm good to go now
     
  20. Jul 30, 2006 #60 of 163
    Ron Barry

    Ron Barry 622 Tips & Trick Keeper

    9,881
    0
    Dec 10, 2002
    Well if previous HD DVR are any indication, Usually there are not enough unit in the field to warrent a roll out and it goes WIDE on day one. However, It does take while to get to all the receivers.

    I could be wrong here, but I have not seen any indication of a stagged release.
     
Thread Status:
Not open for further replies.

Share This Page