90% of my DISH Channels have NO EPG >> EpgGrabber: no channel found for networkid (2 Viewers)

[gemx]

Sorry, totally forgot about this thread.
Since i can't test this and i don't really get the picture about what's wrong - ASiDiE or perhaps someone else - could you give me some more details about what's wrong or how scanning SHOULD be working in this case?

 

[ASiDiE]

As far as I can tell, the tables we are reading either have the wrong information or have dual sets of information and the tv server is choosing one of them. Each Sat that is owned by dish network has it's very own Network ID.

61.5W = 4098 (0x1002)
72.0W = 4101 (0x1005)
77.0W = 4099 (0x1003)
110.0W = 4102 ((0x1006)
118.0W = 4097 (0x1001)
119.0W = 4100 (0x1004)
121.0W = 4106 (0x100a)
129.0W = 4104 (0x1008)
148.0W = 4105 (0x1009)

Let's take channel 121 for example.

I have been using ts reader and going in like 10 times and it's pretty random. It seems like half the time I get the correct values (the first one) and then the other half I get the values not even for my transponder. It looks like this is all being created in the SDT 0x0011 Table and the EIT 0x0012 table. The only table that seems to be right is the NIT 0x0010 table. Maybe this is the table that all these values should be pulled from instead of the SDT table (I think that's the one)

Channel 121
On Table_ID: 0x46 (another mux)
Service Name: HISTI
Provider Name: History Channel International
Transport Stream ID: 201 (0x00c9) 110.0W 12.224 R 20000 7/8 QPSK, DVB-S

Channel 121
On Table_ID: 0x46 (another mux)
Service Name: HISTI
Provider Name:
Transport Stream ID: 911 (0x038f) 72.0W 12.370 R 20000 5/6 QPSK, DVB-S

Here are the values under the NIT table for 12224 transponder:

Network Name: EchoStar 110 West
Network ID: 4102 (0x1006)
Transport Stream ID: 201 (0x00c9)
Original Network ID: 4102 (0x1006)
DVB-S Orbital Position: 110.0W
Frequency: 12.224 GHz
Modulation: QPSK, DVB-S
Polarity: RHCP
Symbol Rate: 20000 MSps
FEC: 7/8
Current Network: True
Descriptor: Service List Descriptor
Service: 121 (HISTI) user defined (0x9a)
Service: 151 (VS.) user defined (0x9a)
Service: 157 (OVATN) user defined (0x9a)
Service: 187 (HMC) user defined (0x9a)
Service: 196 (CURNT) user defined (0x9a)
Service: 199 (CHILR) user defined (0x9a)
Service: 271 (FTRAE) user defined (0x9a)
Service: 272 (FTRAW) user defined (0x9a)
Service: 344 (EMYST) user defined (0x9a)
Service: 402 (NBATV) user defined (0x9a)
Service: 560 (NBATV) user defined (0x9a)
Service: 825 (AZTCA) user defined (0x9a)
Service: 828 (UNVSW) user defined (0x9a)
Service: 830 (FTRAE) user defined (0x9a)
Service: 831 (FTRAW) user defined (0x9a)
Service: 862 (PELIC) user defined (0x9a)
Service: 863 (PCLAS) user defined (0x9a)
Service: 9590 (HMC) user defined (0x9a)
Service: 9591 (HMC) user defined (0x9a)
Service: 9592 (HMC) user defined (0x9a)
Service: 9593 (HMC) user defined (0x9a)
Service: 9594 (HMC) user defined (0x9a)
Service: 9595 (HMC) user defined (0x9a)
Service: 9596 (HMC) user defined (0x9a)
Service: 31500 (KFUG) user defined (0x90)
Service: 31510 (DLSV) user defined (0x88)

There is also a PAT PID 0x0000 Table that would give us the same thing.

Network Name: EchoStar 110 West
Network ID: 4102 (0x1006)
Transport Stream ID: 201 (0x00c9)
Original Network ID: 4102 (0x1006)
DVB-S Orbital Position: 110.0W
Frequency: 12.224 GHz
Modulation: QPSK, DVB-S
Polarity: RHCP
Symbol Rate: 20000 MSps
FEC: 7/8
Current Network: True
Descriptor: Service List Descriptor
Service: 121 (HISTI) user defined (0x9a)
Service: 151 (VS.) user defined (0x9a)
Service: 157 (OVATN) user defined (0x9a)
Service: 187 (HMC) user defined (0x9a)
Service: 196 (CURNT) user defined (0x9a)
Service: 199 (CHILR) user defined (0x9a)
Service: 271 (FTRAE) user defined (0x9a)
Service: 272 (FTRAW) user defined (0x9a)
Service: 344 (EMYST) user defined (0x9a)
Service: 402 (NBATV) user defined (0x9a)
Service: 560 (NBATV) user defined (0x9a)
Service: 825 (AZTCA) user defined (0x9a)
Service: 828 (UNVSW) user defined (0x9a)
Service: 830 (FTRAE) user defined (0x9a)
Service: 831 (FTRAW) user defined (0x9a)
Service: 862 (PELIC) user defined (0x9a)
Service: 863 (PCLAS) user defined (0x9a)
Service: 9590 (HMC) user defined (0x9a)
Service: 9591 (HMC) user defined (0x9a)
Service: 9592 (HMC) user defined (0x9a)
Service: 9593 (HMC) user defined (0x9a)
Service: 9594 (HMC) user defined (0x9a)
Service: 9595 (HMC) user defined (0x9a)
Service: 9596 (HMC) user defined (0x9a)
Service: 31500 (KFUG) user defined (0x90)
Service: 31510 (DLSV) user defined (0x88)

At this point even TS Reader is doing the same thing with looking up the channels. However, it seems like dvbdream, My theatre don't seem to have a problem with this at all.

I will continue to do some research to see if I find out how they are doing it in the other programs.

I did notice something from all this testing and it may or may not matter. In my transponder file, I am telling it to use ,78 for the FEC number. You can see in my log file that it is seeing it "InnerFecRate:Rate7_8"

However it's always using auto "Fec:Fec_Auto 6"

I don't think this is any issue but one of the things that is different between the to is the first one (good one) is 7/8 and the other one is 5/6.

I tried over and over to get it to come up with the right values in the TV server but could not. In ts reader about every other time was either good or bad.

Here are my logs of just scanning one transponder and then some older logs and ts dump of this happening awhile back

http://www.digitaldeath.net/log911.rar
http://www.digitaldeath.net/nascan.rar

Please let me know if you need to get on my PC or you need any more logs from me.

Thanks.

 

[tourettes]

NIT == network information table
SDT == service description table
EIT == EPG

So, I would assume that we are incorrectly using SDT (that can contain different transponder information as well). NIT should be used instead.

 

[gemx]

tourettes, you are right.
Currently we are searching for PAT and SDT and then combine these infos to build a channel info structure. The NIT parser runs besides them. After PAT and SDT parsers are finished we cycle through each channel info and fill in the missing details from the NIT sections.
So, after reading this thread - this seems wrong. We should read the PAT/PMT and NIT and after that fill the missing fields with the infos from SDT instead.

 

[ASiDiE]

I am glad I could help out here.... Please let me know if you need anything else or if you have a file for me to test.... you can attach it here or e-mail it to me at asidie@gmail.com

Thanks

 

[gemx]

Hi ASiDie,
thanks for your help.
I received your email and attached the patched TsWriter.
The patch from DVBN looks good so far
Please test this version and post tswriter.log
This is also for the others who have problems with scanning - please test the attached version.

 

[ASiDiE]

Sounds good..

I am testing this out now.

Thanks.

 

[ASiDiE]

This has been tested and it all looks good. I have huge blocks of the network ID's, which for one transponder, thats what you should have.

I have attached all my logs... I think we got a winner here!

I only scanned 5 transponders.. I will do another test with both sats and all of them.

Thanks goes to Gemx and Darco!

 

[gemx]

Nice
I will wait for your results and if they are positive i commit the changes.

 

[ASiDiE]

I have done a full scan and looked through the tables... everything seems to be in order. I then tested about 20 channels to make sure they all come in... they do. Looks like these changes can be added to the latest SVN.