If there's been a deep discussion about this, forgive me, but let's go deeeeeep into this one gang!! No comments are unwelcome!! Milo, brott, tibber, and I were having a discussion the other day and I think it's time that everyone starts talking, thinking, and brainstorming about this one as a big group. Milo's survey points to watching "Live TV" as being a potential place where the unexpected seems to occur the most. Sometimes minor things and sometimes major things. Anywhere from total lockups, trickplay issues, audio drops and crackling, pixilating, to even stranger phenomenons like finding pixilation in a recording when you previously watched the live broadcast and everything was fine. Only God knows what other possible little issues people have seen surrounding "Live TV" non-trickplayed. Over the years I used to have 2 tivo's (1 hughes sd-dvr80 and 1 HR10-250) plus I currently have another Hughes SD-DVR80 and ALL of them occasionally suffered from "audio studdering" now and then. Recordings for me never suffered, just live tv. The simple answer for me, without ever reading a forum thread about it back then, was to simply hit the tivo's 6 second back button one time and all my audio problems would magically disappear. It became a habit for me which I still have. So then last night tibber and I got to talking in chat about this a little more with a couple other guys and tibber mentioned something I didn't know since i don't have 2 receivers side by side anymore .... He said that when you switch channel on HR20, you are watching "truely live tv", but if you trickplay back and then forward, then your suddenly NOT watching live tv anymore (and let's leave out that 30 sec slip bug because that's not what we're talking about here) .... this proven (he said) by comparing the broadcast to a H20 non-dvr. So now we have 3 types of watchable tv. "Truely Live TV" "End of Buffered Live TV" "Buffered TV" In the 5 weeks I've had the HR20, I've watched a LOT of live tv on it, but I still find myself addicted to that 6 sec back (and pause button too) so I'm rarely watching "truely live tv" even when I fast forward back to what i thought was live tv .... what I now call "buffered tv" and "end of buffered live tv"!!! Maybe I just got the luck of the draw and got a great receiver, could very well be because i have rarely had problems, but I CAN SAY that the few times I've had to reboot from lockups or whatnot .... The receiver was in fact watching "truely live tv". Then I got to thinking... None my tivo's EVER showed "truely live tv"!!! They always had a built in buffer as my broadcast was always about 2 seconds or so behind my old non-dvr's. I know this because I had 4 tv's (3 receivers and an ota feed) in my old living room FOR YEARS and I often had all of them going. Theory Time!!! Could a lot of the HR20's problems be tied right to this one .... dare i say .... BOTTLENECK of trying to do to much work all at the same time simply to get your DVR's and your NON-DVR's playing a perfectly simulcasted broadcast? If there was a built-in predefined full-time 2 second buffer, could this help the processor and memory to keep up with what it needs to do to deliver us a perfect seamless signal/decryption full-time? Wouldn't this senario allow for one set of functions to be running full-time as opposed to (speculating here, don't sue me if this isn't the case) possibly different sets of functions as we switch from "truely live tv" over the "end of buffered tv" ... because if this is the case, any programmer knows software jumps take more processor time the further away the functions are from each other inside the code? The object here is "efficiency". The more efficient the receiver runs, the more stable it can run AND the better our chances get for more complex tasks being implemented like for example ....dare I say .... DLB? Is it purely fixable code bugs that are the problem? Is the processor starved for speed? Is there not enough memory in the unit? Are there too many memory leaks? Remember guys, I'm brainstorming and theorizing. Feel free to correct me and/or build upon me. Any takers?