right dwarren2, but what has caused it to be worse since the days when Dish added several HD channels per transponder (and more SD channels, as well, because even the SD streams are really long, as well) is the sheer size of the stream. The time it takes to encode all that data and merge it onto a stream before it can be sent to uplink and the time it takes for stream to cycle so that the STB has all the data necessary before it can spit out the video, audio, for the requested sat channel (USA, TNT, etc.), the encryption key, program data, etc. It's a really long stream these days, and that is the major cause of the delay. The up and down route of RF sat transmissions (such as old analog TV/radio) is only a few seconds like 2 - 3 seconds of delay. But, if it is a digital stream, who knows how long the delay will be. It's the tyranny of THE STREAM. For Dish, the question becomes this: should we keep the clock on the money and just not be concerned about the stream not being in synch, or do we synch the clock (being set LATER than real time) with the stream so that SATELLITE streams reach the downlink so that recordings don't end or start early. But that would make the OTA timers fire LATE and end late because the OTA RF has a much shorter distance to travel and often has a much SMALLER stream than Dish sat streams, and people may find that upsetting. Consider, however, that Dish MUST be sending the data that keeps the clock accurate EARLIER than real time because it really is on the money at our donwlink end, and the only way that cam be is if Dish sends the synch just a few seconds BEFORE real time so that it is perfect at our end.