PDA

View Full Version : DMA: Montgomery, AL


DishGeek75
12-14-07, 09:23 AM
Good morning!

I've had this problem since 9-18-07 and since it's been almost 3 months with no resolution (or information about it) I decided to post incase there are others that could give me some info on how to push this along or if some engineer at Dish would love to figure this out....

Basically, it is just like many other OTA problems.... It's the guide info.

I have 5 local OTA channels that are supposed to have guide info, all do, one does not. All of the sub channels have guide info except the sub channel for the primary channel that doesn't.

WCOV is the local Fox affiliate and I've called the engineer and he stated they didn't change anything like the TSID or anything on the PSIP. The only thing that did happen on their end was the PSIP had an update applied that required a reboot and he said there was a little trouble getting it to boot up all the way, but said they got it back online and I believe him since I have guide info for my locals dish provides.

Dish on the other hand.... Can't tell me anything. I've emailed their tech support and was asked to provide information about my receiver and that it usually takes a software update to correct such things. Now, of all of the threads I've read about guide issues with OTA, I've never seen where it took a software update. I fail to see why it would. Since the receiver is the convergence point of both pieces of info, such as the guide info from Dish, and the actual programming and TSID and such info from OTA, I fail to see how a software update will fix one channel while there is proof that the piece of code responsible for providing guide info for OTA depending on matching the TSID info from the guide is working since I have OTA guide info for all my other local OTA channels. It doesn't make sense to me and that's why I'm fairly sure it won't be resolved anytime soon unless I get someone with the now how to correct it.

A little further background.

I chatted with a few others with Dish that are local on the avsforum for our area and there is only one of the four (including me) that gets guide info, but he hasn't rescanned his channels in a long time, so it seems to me he has matching info that enables him to get the guide for WCOV. I've come across a post while searching on Google about this where someone that apparently was using MythTV and a dvb-s tuner card to receive pirated tv, and was able to change the TSID of the OTA feed info he was getting to match the TSID of the dish guide and made his map down correctly. So, this tells me it's pretty simple, but Dish with all the red tape, takes too long to fix a very simple problem. I wish that on my 722, you had the option of changing the TSID as well as the name of the stations in the local scan in order to make them match, kind of an advanced setting, you know?

Thanks in advance for any help that is provided!

tomtb
12-17-07, 07:38 PM
Good morning!

I've had this problem since 9-18-07 and since it's been almost 3 months with no resolution (or information about it) I decided to post incase there are others that could give me some info on how to push this along or if some engineer at Dish would love to figure this out....

Basically, it is just like many other OTA problems.... It's the guide info.

I have 5 local OTA channels that are supposed to have guide info, all do, one does not. All of the sub channels have guide info except the sub channel for the primary channel that doesn't.

WCOV is the local Fox affiliate and I've called the engineer and he stated they didn't change anything like the TSID or anything on the PSIP. The only thing that did happen on their end was the PSIP had an update applied that required a reboot and he said there was a little trouble getting it to boot up all the way, but said they got it back online and I believe him since I have guide info for my locals dish provides.

Dish on the other hand.... Can't tell me anything. I've emailed their tech support and was asked to provide information about my receiver and that it usually takes a software update to correct such things. Now, of all of the threads I've read about guide issues with OTA, I've never seen where it took a software update. I fail to see why it would. Since the receiver is the convergence point of both pieces of info, such as the guide info from Dish, and the actual programming and TSID and such info from OTA, I fail to see how a software update will fix one channel while there is proof that the piece of code responsible for providing guide info for OTA depending on matching the TSID info from the guide is working since I have OTA guide info for all my other local OTA channels. It doesn't make sense to me and that's why I'm fairly sure it won't be resolved anytime soon unless I get someone with the now how to correct it.

A little further background.

I chatted with a few others with Dish that are local on the avsforum for our area and there is only one of the four (including me) that gets guide info, but he hasn't rescanned his channels in a long time, so it seems to me he has matching info that enables him to get the guide for WCOV. I've come across a post while searching on Google about this where someone that apparently was using MythTV and a dvb-s tuner card to receive pirated tv, and was able to change the TSID of the OTA feed info he was getting to match the TSID of the dish guide and made his map down correctly. So, this tells me it's pretty simple, but Dish with all the red tape, takes too long to fix a very simple problem. I wish that on my 722, you had the option of changing the TSID as well as the name of the stations in the local scan in order to make them match, kind of an advanced setting, you know?

Thanks in advance for any help that is provided!

I live in Montgomery and have the same problem. It is very frustrating.

Ron Barry
12-18-07, 11:52 AM
"PSIP had an update"

This to me sounds like it might be the source of when the issue was introduced. Remember there is two side of the coin. It is very common for the source to make an update and something in the stream changes resulting in loss of guide data. This is the crux of why OTA is very fragile.

Well to me is sounds like the there might be a problem that was introduced when the update occurred. I would suggest having the engineer at your local station take a look at the stream and see if he sees anything that the update might have effected. If this worked before the update and know does not work then the fix might lie on his end.

And welcome guys to DBSTalk!

DishGeek75
12-18-07, 12:09 PM
"PSIP had an update"

This to me sounds like it might be the source of when the issue was introduced. Remember there is two side of the coin. It is very common for the source to make an update and something in the stream changes resulting in loss of guide data. This is the crux of why OTA is very fragile.

Well to me is sounds like the there might be a problem that was introduced when the update occurred. I would suggest having the engineer at your local station take a look at the stream and see if he sees anything that the update might have effected. If this worked before the update and know does not work then the fix might lie on his end.

And welcome guys to DBSTalk!

Thanks for the reply Ron!

I do understand what you are talking about and understand how both sides are needed to get it working....

When I talked to the WCOV engineer, he didn't want to really hear that it may be on his end... That's why I tried to pressure Dish to contact him and see since Dish actually gets the data from the PSIP. I figured they would see exactly what the data is and why it isn't working correctly, but It has fallen on deaf ears. I also understand it may take Dish a little while to work through their other trouble tickets, but after three months you think they would of at least taken a few minutes and checked the PSIP stream from WCOV to see if it's that simple and fix it quick. But I guess it depends on how you prioritize such issues with the smallest being last or first. I really don't know how Dish tech support goes through their workload so I won't hazard a guess, but It just makes sense that small little problems like this wouldn't take three months. I guess what really bugs me is no return communication letting me know if anything has indeed been done.

I've been a customer for growing on 9 years and have always had around an $80 bill and upgraded to HD and really enjoy Dish's programming and enjoy the fact I am able to get my local OTA. I feel it isn't as compressed that way. At least I can tell the difference between Dish and my OTA.

Forgive me.... I talk alot.....:)

DishGeek75
12-18-07, 12:12 PM
I live in Montgomery and have the same problem. It is very frustrating.

Hey Tomtb!

I believe I briefly talked to you on the AVS forums about this.....

Ron Barry
12-18-07, 12:17 PM
You have a few PMs DishGeek.. ;)

tomtb
12-21-07, 10:36 PM
Hey Tomtb!

I believe I briefly talked to you on the AVS forums about this.....

Yes, thanks for your reply.

DishGeek75
01-05-08, 03:23 PM
Hey tomtb,

A quick update, I have guide data for WCOV now after talking with Dish for a while now and trying several things, and I need to ask you if you do?

If you don't, let me know and I'll post what I did to make it happen.

I'm not sure if I performed a procedure that was a partial help considering the Dish engineers have been calling and talking to the WCOV engineer and made any changes or if what I did fixed it without their help. That's why I need to know if you still have this problem.

UPDATE: Here's the link on AVS with details of what I did....
http://www.avsforum.com/avs-vb/showthread.php?p=12704264#post12704264