I have come up with a couple of things that people can do on their HR34s that seem to show that this unit is not built with the same design philosophy as any of the other DVRs, and that it is built more like two units, an RVU DVR server and an RVU client all in one box, and that what we are really interacting with on the HR34 is a RVU client. EXAMPLE 1 This first example that anyone can easily re-create will show that any tuner on HR 34 can be used as a foreground tuner for the HR34 "client", therefore making all tuners on the HR34 RVU capable tuners. (if any tuner can be used by the HR34, then any tuner also has to be able to be used by any outboard RVU client) First turn on the unit and tune to channel A and have it begin recording whatever is on. Now go into the guide and have it record channel B, channel C, channel D, and channel E. Now while viewing live TV type in channel F and hit enter. This will prompt a conflict screen and it will show you that you have four tuners unassigned and one tuner is listed as my location and the name of each program being recorded with those tuners currently going on. Now exit that screen. Then type in channel B and hit enter and allow the unit to change channels. Now once again type in channel F to bring up the conflict screen and you'll see that my location has moved to channel B with all the other channels now showing as unassigned. You have changed the foreground tuner from channel A to channel B. Now hit exit again, tune to channel C, then to channel F once again to bring up the conflict screen and you notice that the foreground tuner is now changed to channel C. You can repeat this process twice more and move the foreground tuner to channel D and channel E showing that any and all tuners can be a foreground tuner on the HR34. If you really want to have some fun you can actually use the same process with double-play engaged and you will notice how you can move the foreground and the background tuner around to any and all different tuners using the same processes. This appears to be prime evidence that the HR34 was built as two units since no two tuners are tied only to the HR34, however, the HR34 client can only be using any two tuners at a time for its own purposes. EXAMPLE 2 Making the live buffer go completely away, even while the HR34 is on and being used. This example will shows that the HR34 does not always have a tuner designated as a foreground tuner. Turn on your unit and tune it to channel A. This channel will now be the foreground tuner and is writing the live buffer. Now go into your playlist, choose a recording and start playback. Now go into the guide and start recording's on channel B channel C channel D channel E and channel F. (you may see the conflict screen, and if so, simply choose the my location tuner for the final recording.) Now go into the guide one more time and try starting a recording on channel G. This will bring up a conflict screen and you will see that no tuner is assigned to anything, and that all tuners are listed as unassigned. The RVU DVR server seems to have taken all the tuners which it seems to see as nothing more than resources and assigned them all the task of recording programs because none of them were actively being used to view live TV by any client. This means that there is no foreground tuner on the HR34 client at the moment and therefore no live buffers are being written at the moment. Keep watching the program you've been watching that was previously recorded until after all the recordings that you set are finished. (you can speed this up by going to the playlist and simply stopping all the recordings) Now simply hit the exit key on the recording you're currently watching and it will dump you to a live tuner/channel and you will notice that there is absolutely no buffer of any kind on the HR 34 for the live tuner. (you may want to wait for 5 or ten minutes between stopping all recordings and exiting the playback of the previously recorded program. That will make it easier to see no buffer is there, since you will know it should easily show a long span of green in the playbar.) This seems to provide evidence that until the HR 34 client again requested a tuner to be used that resource wasn't assigned to the HR34 client and therefore wasn't writing a live buffer. These examples put together seem to provide a lot of evidence of how this unit was designed and why you won't always see a live buffer coming out of standby even when you don't have any outboard clients hooked up to it because the HR 34 itself also acts like in many ways, if not in all ways, just like any other RVU client probably will based on what we have all heard about the Samsung tvs that can act as a RVU client. These examples also seem to show that that process of writing a live buffer doesn't start anew on an HR34 if it is at any point stopped without an HR34 client requesting a new foreground tuner. I'd say that makes sense, because it has no way of knowing which tuner will get assigned to the HR34 client foreground tuner because it has no idea when you will interact with it again in a way that will cause it to need a tuner again.