[Warning: RANT contained below. You have been warned.]
Based on careful observation and experimentation, I think I have determined how a Dish Network receiver will decide which to tune, when the same channel is on two satellites in your dish configuration. Although it may seem that the answer is "random" or "based on some sort of priority list" I believe it to be more along the lines of "whichever is most likely to cause the customer to miss what they wanted to see." There are many factors that go into a customer wanting to see something, such as: is it a new episode; will it be repeated often, rarely, or never; does the network allow you to watch full episodes online. If the answers to these questions are yes, never, no - I can pretty much guarantee that the receiver will choose whichever instance of the channel currently has the weakest signal, especially if there is bad weather involved. Signal loss is much less likely on shows that you have seen before and for which the same episode will be on multiple times this week.
[OK, I exaggerate a little. But I have earned that right. I fight with technology all day for a living, I should not have to fight with it trying to enjoy my time off.]
For example, I have a 1000.4 dish for Eastern Arc. I also have a standalone "wing" dish pointed to 110 to get the SD versions of my local channels. This results in a configuration in which several channels are duplicated. For example SyFy HD is on 110tp7 and 72.7tp17. Due to storms tonight, 110tp7 has a signal strength of 3 (on 125 point scale), while 72.7tp17 has a strength of 40+. Guess which one it decided to use for the things I scheduled to record.
[OK, rant over. Almost. Here's my useful, polite suggestion to Dish software development team.]
How difficult can it be to add a simple test in the code: if there is a signal loss but the same channel exists on another satellite/transponder you have access to, at least F$&#ING TRY TO USE THE OTHER ONE, before sitting there forever with a "signal has been lost" error message.
Based on careful observation and experimentation, I think I have determined how a Dish Network receiver will decide which to tune, when the same channel is on two satellites in your dish configuration. Although it may seem that the answer is "random" or "based on some sort of priority list" I believe it to be more along the lines of "whichever is most likely to cause the customer to miss what they wanted to see." There are many factors that go into a customer wanting to see something, such as: is it a new episode; will it be repeated often, rarely, or never; does the network allow you to watch full episodes online. If the answers to these questions are yes, never, no - I can pretty much guarantee that the receiver will choose whichever instance of the channel currently has the weakest signal, especially if there is bad weather involved. Signal loss is much less likely on shows that you have seen before and for which the same episode will be on multiple times this week.
[OK, I exaggerate a little. But I have earned that right. I fight with technology all day for a living, I should not have to fight with it trying to enjoy my time off.]
For example, I have a 1000.4 dish for Eastern Arc. I also have a standalone "wing" dish pointed to 110 to get the SD versions of my local channels. This results in a configuration in which several channels are duplicated. For example SyFy HD is on 110tp7 and 72.7tp17. Due to storms tonight, 110tp7 has a signal strength of 3 (on 125 point scale), while 72.7tp17 has a strength of 40+. Guess which one it decided to use for the things I scheduled to record.
[OK, rant over. Almost. Here's my useful, polite suggestion to Dish software development team.]
How difficult can it be to add a simple test in the code: if there is a signal loss but the same channel exists on another satellite/transponder you have access to, at least F$&#ING TRY TO USE THE OTHER ONE, before sitting there forever with a "signal has been lost" error message.
Last edited:
