Showtime HD & HBO HD - 110 - 148 Bitrates, Errors and More
Over the past several days I had an unusual opportunity to be in a position where we had a several modified 6000s in the same location that could pick up 110 and 148. This allowed capture of the same exact showing of HBO-HD and SHO-HD off 148 and 110 at the same time for the first (that I am aware of) apples to apples comparison of the two.
As anyone who has viewed these threads should know, the bit-rates of the same movie at different times on Dish can be different - thus even though you compare the same movie, it still can yield different results.
House Arrest on HBO-HD from start to finish:
11.09 Mbps Video on 110
11.87 Mbps Video on 148
Not a surprise as that is around where the 2 average.
Teaching Mrs. Tingle on SHO-HD from start to finish:
8.49 Mbps Video on 110
12.83 Mbps Video on 148
Again, confirming what I basically knew - but in dramatic fashion.
HERE IS THE SHOCKER......
We know that Showtime has problems on Dish and usually it will cause a mux issue resulting in an error and a glitch - time gap - even using a 942. On the 6000 it often results in an audio/video desynch on the composite outputs of the unit.
What I (and I suspect) no one knew up until yesterday, was the glitch occurs ON BOTH SATELLITES AT THE SAME TIME. I have a glitch on Teaching Mrs. Tingle AT EXACTLY THE SAME TIME ON BOTH BIRDS and the logs from Mpeg2repair are virtually identical with the errors.
As I do not know the flow chart of the downlink and up-link at Dish, its hard to make a firm conclusion, but I can speculate with somewhat certainty now that this is not happening at the dish up-link as its happening at the same time on 110 and 148.
Given the large bitrate difference in 110 and 148, I have to assume these are on different paths at Dish. It apprears to be happening more in their downlink and plant distribution of the source material.
Thus, could Dish have a problem in their Showtime Downlink Motorola/GI 4400MD that is the root of these glitches we have come to know and love? This would explain why its at the same place on both birds - even if being feed to different encoders for 110 and 148?
Over the past several days I had an unusual opportunity to be in a position where we had a several modified 6000s in the same location that could pick up 110 and 148. This allowed capture of the same exact showing of HBO-HD and SHO-HD off 148 and 110 at the same time for the first (that I am aware of) apples to apples comparison of the two.
As anyone who has viewed these threads should know, the bit-rates of the same movie at different times on Dish can be different - thus even though you compare the same movie, it still can yield different results.
House Arrest on HBO-HD from start to finish:
11.09 Mbps Video on 110
11.87 Mbps Video on 148
Not a surprise as that is around where the 2 average.
Teaching Mrs. Tingle on SHO-HD from start to finish:
8.49 Mbps Video on 110
12.83 Mbps Video on 148
Again, confirming what I basically knew - but in dramatic fashion.
HERE IS THE SHOCKER......
We know that Showtime has problems on Dish and usually it will cause a mux issue resulting in an error and a glitch - time gap - even using a 942. On the 6000 it often results in an audio/video desynch on the composite outputs of the unit.
What I (and I suspect) no one knew up until yesterday, was the glitch occurs ON BOTH SATELLITES AT THE SAME TIME. I have a glitch on Teaching Mrs. Tingle AT EXACTLY THE SAME TIME ON BOTH BIRDS and the logs from Mpeg2repair are virtually identical with the errors.
As I do not know the flow chart of the downlink and up-link at Dish, its hard to make a firm conclusion, but I can speculate with somewhat certainty now that this is not happening at the dish up-link as its happening at the same time on 110 and 148.
Given the large bitrate difference in 110 and 148, I have to assume these are on different paths at Dish. It apprears to be happening more in their downlink and plant distribution of the source material.
Thus, could Dish have a problem in their Showtime Downlink Motorola/GI 4400MD that is the root of these glitches we have come to know and love? This would explain why its at the same place on both birds - even if being feed to different encoders for 110 and 148?
Last edited: