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

ViP622/ViP722 - L6.15 Software Experiences/Bugs Discussion

Discussion in 'ViP612/622/722/722K DVR Support Forum' started by Rob Glasser, Sep 19, 2008.

  1. Dec 21, 2008 #61 of 122
    P Smith

    P Smith Mr. FixAnything

    21,598
    143
    Jul 25, 2002
    W.Mdtrn Sea
    That's offtopic question. Usually in a week.
     
  2. Dec 21, 2008 #62 of 122
    DAG

    DAG Legend

    224
    0
    Feb 7, 2006
    L6.15 Software Experiences/Bugs Discussion

    :lol: Off topic...hahaha.
     
  3. Dec 21, 2008 #63 of 122
    Grandude

    Grandude RichardParker II

    938
    12
    Oct 21, 2004
    My gut feeling was correct. Hard reboot did not fix the failure to autotune feature.
    Deleting and creating a new autotune for that channel did not fix the problem either.
     
  4. Dec 21, 2008 #64 of 122
    Henry

    Henry Retired Member

    3,588
    64
    Nov 15, 2007
    Pine, CO
    Mods ... is this really off topic? The title says Discussion, right?

    BTW ... I'm still waiting for L6.15, too.
     
  5. Dec 21, 2008 #65 of 122
    phrelin

    phrelin Hall Of Fame DBSTalk Club

    14,943
    294
    Jan 18, 2007
    Northern...
    Well it does say "L6.15 Software Experiences/Bugs Discussion" and if you haven't experienced it yet that's something to discuss. I've experienced it, and based on my experience so far, you are better off than I am.
     
  6. Dec 21, 2008 #66 of 122
    plainsman

    plainsman AllStar

    57
    0
    Nov 16, 2006
    I've been seeing a rash of jerky video when watching HD - I was reluctant to call it a new bug as I was playing back recordings made w/ 6.14 but I'm now running w/ 6.15 and ...

    I was watching a football game - live via component video outputs on my 622, and w/o any inputs from me, the sound dropped for < 1 second [toslink from 622 to my receiver] and the video became stuttered ... jerky -- don't know how better to describe it.

    after the initial drop, the sound was fine - the picture remained stuttered.

    tuning away and then back to the channel 'fixed' it but I've had cases where that didn't clear the problem.

    This has been a problem for me in other releases and it was gone for a good long time but now seems back - a step backwards.
     
  7. Dec 21, 2008 #67 of 122
    moman19

    moman19 Icon

    710
    1
    Oct 22, 2004
    I too, have experienced this twice on my 622 since the 6.15 update. One time I was watching an OTA HD event (PBS) thru the DVR. I recall seeing this issue long ago with an early release and I sure hope it hasn't somehow been re-introduced.

    Sometimes hitting the BACK or LIVE buttons can clear it up. If they fail to clear things up, your only recourse may be a cold restart.
     
  8. Dec 21, 2008 #68 of 122
    kstuart

    kstuart Icon

    643
    0
    Apr 25, 2002
    The only time I ever had that sort of problem, it was fixed by a power plug hard reboot.

    Almost all reports from San Francisco DMA show no problems with L615. Of course, there are now problems in Saint Louis DMA.

    I find that these threads - especially the audio ones - have lots of posts from people who have the same problem with the software - such as the Saint Louis people - mixed with a few people who a) have defective receivers, b) need a power plug hard reboot, c) need a cooling fan on the left side.
     
  9. Dec 21, 2008 #69 of 122
    Cokeswigga

    Cokeswigga Legend

    167
    0
    Jan 25, 2005
    Ever since my 622 took the L6.15 download, my HDMI connection stopped working.

    However, after I reboot the recceiver (by pressing and holding the power button, the HDMI connection will work)
     
  10. Dec 22, 2008 #70 of 122
    TheGrove

    TheGrove AllStar

    180
    7
    Jan 9, 2007
    FWIW, I'm still on 6.14 and this has happened to me twice.
     
  11. Dec 22, 2008 #71 of 122
    plainsman

    plainsman AllStar

    57
    0
    Nov 16, 2006
    a couple of points -

    1) a 'power plug hard reboot' isn't a fix - it is a very vestigial tail(tale!) leftover from the DVR days where that was the only option for most problems. With the man-years of subsequent DVR development a power-cord reboot should not be needed.

    likewise, needing a user-supplied cooling fan ... is a fix which should have been engineered into DVRs from the 500 -on. These boxes really shouldn't need user-tinkering to run. most consumer-electronics products are engineered to be idiot-proof ... the 622's manual reflects this -- it's very good.

    My best guess is there's some sharp-pencil accountant wringing out the costs on these boxes ... resulting in the early / sub-standard HDMI connector and the ongoing lack of a good cooling fan.

    B) this thread is called "ViP622/ViP722 - L6.15 Software Experiences/Bugs Discussion" ... not "one user's idea of only-real-bugs". More to the point, the value in this thread is to group all the uncertain/flaky/bogus ... and genuinely bad 622 behaviors into one spot.

    Part of bug triage is to wade thru them all, finding the common problems and prioritizing them. if we only allow one user's idea of what makes a valid bug, then that's the only thing which gets action. Echostar probably knows more about how their receivers work than we in the peanut gallery and will better sift the bugs from this sea of noise.

    My job is just to give them one more data point to sift. If I give enough accurate details, maybe my problem will see some action.

    iii) Re: jerky video -- my best guess is that this may be resulting from repeatedly hitting a bad block on the disk ... I recently deleted some old recordings, in addition to getting 6.15 ... last time this reared its ugly head I remember thinking I should keep that jerky recording and see if the problem disappears ... it did.

    if bad block remapping can't be handled on the fly, in real-time w/o interrupting the video stream, maybe it could be done once -- marking it unavailable -- suffer one jerk/glitch, and then resume normal video ...

    [ next time this happens I'm going to listen very closely to the hard drive and try to hear if it's repeatedly seek/retry/seek/retry-ing ... ]

    my .002 ...

    -PM.
     
  12. Dec 22, 2008 #72 of 122
    Grandude

    Grandude RichardParker II

    938
    12
    Oct 21, 2004
    Since 615 broke the autotune feature when the receiver is off I have a workaround (fix) for it. I create a second autotune a minute or two after the first one. The first one turns the receiver on and the second one does the tuning.
     
  13. Dec 22, 2008 #73 of 122
    Ron Barry

    Ron Barry 622 Tips & Trick Keeper

    9,881
    0
    Dec 10, 2002
    No this is not off topic. This thread should be used for all conversation relating to L6.15. As for when it will fully rollout. It differs between ever release and some releases do not fully roll out if they feel it does not make things better.

    Rollouts can take up to 3 weeks thought most seem to run a week to two from my experience. All one can do is place the box into standby and if the box does not have shows to record and it is targeted for a update it will get the update.
     
  14. Dec 22, 2008 #74 of 122
    Henry

    Henry Retired Member

    3,588
    64
    Nov 15, 2007
    Pine, CO

    Thank you, Ron ... I appreciate the courtesy.

    Based on past experience, I'm assuming the roll-out has been slowed down. That's unfortunate for me since my 622 seems to run OK no matter what software version it's working under. Whatever the problems are with L6.15, I hope they correct them quickly. I realize that some folks view these releases with great trepidation, but I (knock on wood) have found new capabilities and improved performance in all of them.

    I'll be patient. I usually get the upgrades within four days of release. That delay has come and gone.

    Again, thanks for clarifying.
     
  15. Dec 22, 2008 #75 of 122
    phrelin

    phrelin Hall Of Fame DBSTalk Club

    14,943
    294
    Jan 18, 2007
    Northern...
    The power plug reboot on my ViP722 fixed the "new" scheduling problem (except for Leno which has been an ongoing problem, something to do with the way the show's coded I guess).
    Actually, it appears that for most in San Francisco and St. Louis and North Carolina and the several other DMA's involved, the disruptive Fox and (probably) the ABC audio dropout problems have been fixed with L6.15. That particular audio dropout problem clearly caused the dolby on A/V receivers to switch off/on which was totally disruptive of dialog flow and when one skipped back and replayed the dropout it moved syllables a fact moman19 brought to my attention. (For whatever reason, these dropouts occur in the relative same area on my ViP612 and do change syllables but don't switch the dolby off/on and therefore are 'ignorable".)

    With that said, during the extended time period June-December that the Fox/ABC problem was being worked on, I (and others) realized we were getting less frequent dropouts on CBS and NBC. These dropouts did not turn my dolby off/on. In my case, at least, when skipped back and replayed they sometimes disappeared, sometimes they don't move syllables, and sometimes they move syllables. Whatever L6.15 did, it appears it may have exacerbated the problem on NBC in St. Louis on some boxes and not others. In San Francisco I still occasionally hear these dropouts on CBS, even after I did a hard reboot. And I hear them on my ViP612.

    The truth of the matter is I may have been getting these HD/5.1 audio dropouts on CBS and other locals (and perhaps even the occasional cable channel show) from the first day I got my 722. My brain was not trained to listen for them and I really do have to listen for them (except for my recording this past Saturday of "The Bucket List" on HBO which may never happen again after the hard reboot). I know that there are occasional video glitches which my brain mostly chooses to ignore, so I'm hoping I can retrain it to ignore the occasional audio dropout.
     
  16. Dec 22, 2008 #76 of 122
    Farmer Dave

    Farmer Dave Cool Member

    23
    0
    Oct 7, 2004
    You can also disable the "inactivity standby" and leave the receiver on all the time.
     
  17. Dec 22, 2008 #77 of 122
    Ron Barry

    Ron Barry 622 Tips & Trick Keeper

    9,881
    0
    Dec 10, 2002
    Good work around guys!
     
  18. Dec 22, 2008 #78 of 122
    AVJohnnie

    AVJohnnie Icon

    509
    0
    Jul 27, 2004
    This is a new one (at least for me). Tonight I had a 2+ hour scheduled recording suddenly stop after recording just 12 minutes of the program. The timer event log says “Event Stopped by User 2”. This receiver is running in single mode. There were no other conflicting timers. Wonder if this might be related to the other L6.15 timer/event anomalies that are being talked about?
     
  19. Dec 22, 2008 #79 of 122
    Grandude

    Grandude RichardParker II

    938
    12
    Oct 21, 2004
    True, but then I would have to reprogram my Harmony remotes.:grin: Oh, and my wife who is programmed to turn things off.
     
  20. Dec 24, 2008 #80 of 122
    rexa

    rexa AllStar

    70
    0
    Aug 7, 2008
    Is anyone else seeing ERROR boxes?

    I get this occasionally since 6.15. Watching some program with no problems like audio or video glitches and suddenly the program goes black and there is a box (sort of like the signal lost box) but it just says ERROR and then says to hit up or down channel. I do, and it changes to the next channel. If I quickly hit up/down it fixes the problem and restarts the failed program.

    I don't remember ever seeing this before 6.15 and now I see it randomly. Had it about three times in the last day.

    It is very annoying for several reasons. First it eats a chunk of the program. Not sure what would happen if I was recording the program. Second, ERROR tells me nothing. The software must have detected something wrong but is not willing to give me any clue what the ERROR was. Third, it suggests I click the channel up/down which has always fixed it for me. If the software thinks that's a good idea, why the hell can't it just do something like that itself before telling me there was an ERROR.

    Arrgh! Anyone else seeing this?

    I've got a 622.
     

Share This Page