29 replies to this topic

[el bandido]

There are about 4 satellite companies in North America. Canada has 2, and the United States has two.
Canada has Shaw, and Bell, with Bell sometimes being called BEV. The United States has DishNetwork and Direct TV. None of these 4 satellite providers uses encryption that can be seen on any fta receiver. In other words, you have to buy their receivers to use their satellite services.
 

In 2006, DishNetwork had a few channels that were open or unencrypted. Today, everything Dish has is encrypted except for a few  DishNetwork channels that advertise DishNetwork.
 

I guess it has been a year or longer since I scanned a DishNetwork satellite with a fta receiver, but I remember the channel names not displaying correctly the last time I scanned them. Several years ago, the channel names would display correctly on enigma2 receivers when a DishNetwork satellite was scanned. The channel names would display along with the epg.
 

If there is a problem the 2006 DishNet "fix" is causing, then IMO, it should be removed because any DishNet fix from 2006 can no longer be used. I will try to setup a DishNetwork satellite later today, and see what the channels scan as. The DishNetrok satellites are circular polarized, and everything else for North America that is fta in the ku band is linear. So I will need to change a lnb and re-aim a satellite dish to check DishNetwork.

[nautilus7]

Thanks for the detailed info.

 

Regards.

[EnoSat]

I have also see the same thing with a transponder at 16E (one of the transponder carrying the arena sport channels, not remember which exactly and I can't receive 16E now).

Yes, same problem (timing SDT_table) with scan 16E/11595H and 16E/11512H

Edited by EnoSat, 19 December 2021 - 20:01.

[MCelliotG]

It is a no brainer at this point that the fix is right in front of our eyes. And it's such a shame for everyone of us that it took 15 years for this known issue to be reported and investigated.
Indeed this seems to fix most naming issues on 13E, 16E and even on tps where not all channel names are displayed correctly ie 39E etc.

[el bandido]

The attached screencap is the DishNetwork satellite at 118.7w. Yes, a couple of channels lost their names on this satellite when the scan.cpp file was changed today, but who wants to watch this? I say change it since it helps other services that are actually useful.
 

Attached Files

•  dishnet-118.7_20211219201027.jpg   63.76KB   4 downloads

[nautilus7]

So they still transmit 0x46 tables only for pid 0x0011 (SDT)... 

[el bandido]

Went from this:
< File created on Sunday, December 19, 2021 at 18:59:54 >
< 'DVB-S 11711R / 19998 / 7/8' > Tp# 1
< (1)MBCM />  1:0:1:290:2BD:1001:AE6ADBF:0:0:0:
< (2)ANTEN />  1:0:1:2665:2BD:1001:AE6ADBF:0:0:0:
< (3)SPRT+ />  1:0:1:2666:2BD:1001:AE6ADBF:0:0:0:
< (4)EASY   (Radio #1) />  1:0:2:2669:2BD:1001:AE6ADBF:0:0:0:
< (5)TVPI />  1:0:1:26A5:2BD:1001:AE6ADBF:0:0:0:
< (6)GWFSH />  1:0:1:26D6:2BD:1001:AE6ADBF:0:0:0:
< (7)ETNEW />  1:0:1:26D9:2BD:1001:AE6ADBF:0:0:0:
< (8)ETGLB />  1:0:1:26DA:2BD:1001:AE6ADBF:0:0:0:
< (9)ETDRA />  1:0:1:26DB:2BD:1001:AE6ADBF:0:0:0:
< (10)YOYO />  1:0:1:26E8:2BD:1001:AE6ADBF:0:0:0:

To This:
< File created on Sunday, December 19, 2021 at 19:57:12 >
< 'DVB-S 11711R / 19999 / AUTO' > Tp# 1
< (1)11711V SID 0x290 />  1:0:1:290:2BD:0:AE6ADBF:0:0:0:
< (2)11711V SID 0x2665 />  1:0:1:2665:2BD:0:AE6ADBF:0:0:0:
< (3)11711V SID 0x2666 />  1:0:1:2666:2BD:0:AE6ADBF:0:0:0:
< (4)11711V SID 0x2669   (Radio #1) />  1:0:2:2669:2BD:0:AE6ADBF:0:0:0:
< (5)11711V SID 0x26a5 />  1:0:1:26A5:2BD:0:AE6ADBF:0:0:0:
< (6)11711V SID 0x26d6 />  1:0:1:26D6:2BD:0:AE6ADBF:0:0:0:
< (7)11711V SID 0x26d9 />  1:0:1:26D9:2BD:0:AE6ADBF:0:0:0:
< (8)11711V SID 0x26da />  1:0:1:26DA:2BD:0:AE6ADBF:0:0:0:
< (9)11711V SID 0x26db />  1:0:1:26DB:2BD:0:AE6ADBF:0:0:0:
< (10)11711V SID 0x26e8 />  1:0:1:26E8:2BD:0:AE6ADBF:0:0:0:

 

[nautilus7]

Thanks for the report.

 

On the other hand RAI names are scanned just fine now.

Edited by nautilus7, 20 December 2021 - 22:17.

[MCelliotG]

So, will a condition placed in scan.cpp will cover both cases?
Since I won't have access to my satellite equipment until December 23rd, can someone report if 16E and 39E issues are fixed as well?

[jpuigs]

And it's such a shame for everyone of us that it took 15 years for this known issue to be reported and investigated.
Indeed this seems to fix most naming issues on 13E, 16E and even on tps where not all channel names are displayed correctly ie 39E etc.

 

 

7 Years ago somebody already reported it, but he got replies like "are you sure your dish ponits to correct satellite...?"

 

https://forums.openp...ng-10992-on-13e

 

 

 

On the other hand RAI names are scanned just fine now.

 

Yes, I've been unable to receive HotBird signals for several weeks, and now I see the issue has been corrected.

 

Thanks,