said by nunya:
SDV, IMO, is still very Beta. Yes, it's being implemented - like it or not.
Being that one of your boxes "timed out", and all three boxes shit the bed at the same time, I'm more apt to believe that it's a carrier or return path issue. E.G., the STB can't let the node "know" that you are still watching that program. The channel times out, and all you see is the last image.
The STB return is on 19 MHz, and I checked the power levels on all three boxes. They are showing about 34-35 dBmV at each box. Tech thought that was pretty good... maybe a hair low, but he then went in the truck and looked at the noise on the node... and there was nothing that could have interrupted communication... it was pretty clean overall.
I will say that I have had some difficulty in the past with On Demand... when I select a program, it will search and search and come up empty handed... like it's looking for something it can't find. not sure if that is directly related to my issue, but he did think that may be a piece of this issue.
The only portion you have control over is the amplifier in your house. Some amps that claim to be "digital ready" only pass the upstream return, they don't actually boost the upstream return signal. As far as return path is concerned it's just a passive device.
Check the specs on your particular amp. Make sure it's truly bi-directional.
It has 0.0 forward gain, and 0.0 reverse gain, so it simply repeats in and out what it's sent with no loss.
Tech said they set up a sling box in the headend, hoping to catch a freeze event, and then take it from there. he said that ironically, the head end was watching a SDV channel last night, and they shut off the TV but forgot to shut off the cable box. They came in this mornning... box was frozen on a picture with no audio... just like my problem. They investigated and learned that 360 minutes is the timeout... but are not sure how often the STB needs to communicate with the headend to keep the stream going.
And if that is the reason... why is my return not able to communicate with the headend to keep the stream, but a quick channel change instantly fixes the problem?!?