Separate names with a comma.
Discussion in 'DIRECTV HD DVR/Receiver Discussion' started by Stuart Sweet, Oct 22, 2009.
Once you have it for a few days let us know if you still feel this way.
you should be able to expect persistence this time ..
The speed improvement is more than what comes with a reset. I've reset many times in the past w/o significant speed improvement. But, with the latest release I see a consistent speedup.
I await the blue eyes on my HRs.
Just out of curiousity, did the skip-to-end finally end with this update?
I believe that this particular problem really does not happen much anymore.
Faster guide, but about as fast as last weeks CE? Notice less key bounce in RF.
Only if this update fixed it...
I'll go to a friends house that has an HR after this update wends its way East to here to see how things have changed.
The last update made it much worse that it ever used to be. I even have it happening if I Slip forward a few time, then let it play for few seconds and then try the slip again... Moves right to the end of the show.
Then there is yelling... and the Fast Reverse and skipping to 15 minute blocks... and then more slipping forward.
I don't know if others were getting this but I hadn't had it happen for months and then lots after the last "update".
The skip to end problem is real, and a major bug. It seems to be similar the problem with slow response to the remote.
I also find that the HR21 (under 034C) sometimes loses track of where you have paused, if you leave a program and later return.
Both problems seem to come and go over time. Worse when the box is sluggish or when Double Play is being used.
All your points are valid.....but since you don't have 0368 yet, and this thread is about that version....perhaps you might withhold judgement until you receive it.
It may not resolve all the issues, but the top ones reported within 34C seem to be well addressed.
I share your desire to get the HR21 units operating well.
It's a good thing we're talking about 0x368 then
I read the prior posts to indicate this was not a wide-spread issue and, therefore, not addressed in the new NR.
I may be wrong, but I am never in doubt.
I don't use the DLB function either and I have no noise from any of my HRs.
I have one of my 20-700s in my bedroom in an open faced cabinet and I do see an orange flicker coming from the Ethernet port, but I've never heard any noise coming from it. I just use it for DOD tho. And the 20-700 is "owned" and has a new internal drive in it.
I do not use it and do have noise.
What kind of HR?
As has been reported many many times in the past, on the manual recording setup page, the direct channel selection function using the remote number pad is completely broken.
It should work the same way direct num-pad channel selection works everywhere else, such as in the guide and in the channel favorites setup screen..... pressing 1-2-3 should jump to channel 123.... not channel 30, then channel 100, then channel 200, then channel 300, then channel 1000, as it does now in the manual recording setup page.
Also, the recording start time on the manual record setup page defaults to 5 minutes past the next half hour mark, which makes no sense whatsoever. It should probably default to the next half hour mark.
These two bugs in some of the most basic of the DVR's functionality should have been caught and fixed years ago and they should really stop being released into NR after NR after NR, given that they have been reported many times dating back before multiple past national software releases.
Who is setting the priorities for these software releases??? If there are resources to make cosmetic GUI changes, why aren't long standing bugs like this being addressed? It's time to start setting proper priorities.
IMO, lunatics (or marketing personnel) are setting the priorities, and a lot of the coders are idiots. Oops, that's not a real "issue."
Like anything else, they fix what they can fix, and don't fix what they can't. I'm sure there are some issues that deserve higher priority than others, but at the same time some problems are harder to fix than others, and that has no correlation to the wish list, unfortunately. IOW, just because something remains a problem doesn't mean there isn't effort expended trying to fix it. How much effort is not really revealed.
It is not realistic to assume that what is fixed or not or what features are added or not are based solely on priorities, and it is also unrealistic to measure success or failure and assume that reflects the priority strategy. Luck and skill have a lot to do with it also. Like it or not, how the platform actually evolves is very much up to chance, regardless of the priority list. If we were all to vote on a priority list, I'm sure it would likely mirror what the code team captains have in mind pretty closely, but what really happens depends on skill and luck much more than it does strategy. IOW, we're all on the same page here. We all want the same things, but that doesn't mean we will get them, or get them as soon as we would like.
"Bugs" are by definition unexpected problems, meaning they have to try to fix them after the fact. You throw a coder or two at a particular problem, and if he fixes it, great. If he is beating his head against the wall (possibly literally) after a period of time and not able to make headway, you put him on something else and throw another coder at the original problem. Some problems never get fixed; never find a coder who can figure them out.
Features are not cleanup issues like bugs. They are strategized plans. What happens in that case is expected, and the success rate is therefore higher. If everyone had tried their hand at fixing a particular bug and have had no luck, it makes sense to put them on new features instead, IMHO. How quickly bugs are fixed is basically a budgetary issue (how big a team you can muster to attack them). Unfortunately, adding features sometimes has unexpected consequences (as does fixing bugs) of creating new bugs. If it were easy, anyone could do it, and it would be done already.
People in hell would like some icewater, too. Odds are not good for that.