Opened 17 years ago
Closed 16 years ago
#2372 closed defect (fixed)
Unsupported service descriptor on Echostar Satellites
Reported by: | Owned by: | danielk | |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | dvb | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Im unable to scan any of the exhostar satellites. logs included. let me know if you need anything else.
Attachments (7)
Change History (26)
Changed 17 years ago by
Attachment: | Echostar3_full_existing_tp_scan.log added |
---|
Changed 17 years ago by
Attachment: | Echostar3_single8PSK_and_singleQPSK_scan.log added |
---|
comment:1 Changed 17 years ago by
Owner: | changed from Isaac Richards to Stuart Auchterlonie |
---|
comment:2 follow-up: 3 Changed 17 years ago by
Priority: | major → minor |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Version: | → 0.20 |
comment:3 Changed 17 years ago by
Replying to stuarta: yes, all transports are detected and inserted into the DB, but scanning those transports finds 0 channels. No channels are added to the database.
because these satellites carry few FTA channels, for the purpose of getting a full log I had the "FTA Only" Unchecked and all channels should be inserted, but none were.
As to be more specific, I can not. I don't know anything about the specifics of DVB transmissions etc. That's why I provided the logs. I'll be more then happy to help out if you tell me what to do. All I know is that with 0.19, scanning was not a problem and with svn and now 0.20 it has been for a long while.
Another problem is that with 0.20 I can't even tune to any channels on these satellites. All I get is a paritial lock (LMs, if I recall correctly), but that's another issue I was gonna open a ticket for with the appropriate log.
comment:4 follow-up: 7 Changed 17 years ago by
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Summary: | Unable to scan echostar (dish network) satellites → Unsupported service descriptor on Echostar Satellites |
Looks like echostar are marking all their channels with a service descriptor we don't currently support (0x9a)
Can you confirm if the following channels are tv or radio channels
USA, HIST, BET, BRAVO, FUSE, MTV2 et al...
comment:5 Changed 17 years ago by
Milestone: | 0.21 → 0.20 |
---|
From the 0.19 dtv_private types tables
| networkid | private_value | | 4100 | 1,145,154 | | 4101 | 1,145,154 | | 4102 | 1,145,154 | | 4103 | 1,145,154 | | 4104 | 1,145,154 | | 4105 | 1,145,154 | | 4106 | 1,145,154 | | 4107 | 1,145,154 | | 4098 | 1,145,154 |
so we're missing a few tv types. Patch coming soon...
Changed 17 years ago by
Attachment: | ticket2372-add-echostar-tvtype-descriptors.diff added |
---|
add echostar tv service descriptors....
comment:6 follow-up: 8 Changed 17 years ago by
Can you try with the attached patch. Should allow you to scan and find channels.
comment:7 Changed 17 years ago by
Replying to stuarta:
Looks like echostar are marking all their channels with a service descriptor we don't currently support (0x9a)
Can you confirm if the following channels are tv or radio channels
USA, HIST, BET, BRAVO, FUSE, MTV2 et al...
as far as I know, all these are encrypted TV services on another echostar satellite @ 119W. Let me know if you need a dvbsnoop dump or somthing.
comment:8 Changed 17 years ago by
Replying to stuarta:
Can you try with the attached patch. Should allow you to scan and find channels.
i applied the patch. here are the results: Full frequency scan: found all transports, then went on to scanning each one of them. While scanning each transport, it found info about other transports and reinserted them into DB then looked for channels. Found 0 channels on each transport. Intersting enough, somwhere in the process it inserted one additional transport with freq = 0 and networkid=4100 (which is another echostar satellite at 119W) and for that transport it found channels and inserted them into DB
same thing happens with "Full transport scan" or "Single Transport Scan"
comment:9 Changed 17 years ago by
22:51 -!- cythrault [n=cythraul@…] has joined #mythtv 22:51 < cythrault> i'm trying to figure out if I should open a ticket about channel scanning on dvb-s, some channels are not seen as tv or radio service
due to their service_type being 0x86, 0x89 and 0x96 instead of 0x01...
stuarta: three additional service types. he gaver no further deatils
Changed 17 years ago by
Attachment: | dvbsnoop-bev.txt added |
---|
a snoop of the provider showing service type 0x86, 0x89 & 0x96
Changed 17 years ago by
Attachment: | ticket2372-add-nimiq-tvtype-descriptors.diff added |
---|
A patch against 11188 to include echostar & nimiq service types
Changed 17 years ago by
Attachment: | ticket2372-add-nimiq-tvtype-descriptors.2.diff added |
---|
A patch against 11188 to include echostar & nimiq service types (corrected)
comment:10 follow-up: 11 Changed 17 years ago by
Thanks Janne for adding the info, I was not sure if it was related to this issue. Also, thanks for dyzio from dvbn who proposed the patch.
Also, while dvbsnooping to update this ticket, I noticed some other service types being used on Nimiq for DTV: 0x81, 0x85, 0x8a, 0x8d, 0x8f & 0x90. I'm not sure how you want to handle all these…
Changed 17 years ago by
Attachment: | ticket2372-add-nimiq-tvtype-descriptors.3.diff added |
---|
A patch against 11188 to include echostar & nimiq service types (final? -- please delete the two others :)
comment:11 follow-up: 12 Changed 17 years ago by
Replying to cythrault@gmail.com:
Also, while dvbsnooping to update this ticket, I noticed some other service types being used on Nimiq for DTV: 0x81, 0x85, 0x8a, 0x8d, 0x8f & 0x90. I'm not sure how you want to handle all these…
Can you confirm that all of these service types are TV services, since if they are radio channels they need to be handled slightly differently.
After you have found these channels you are able to tune to them and they work?
comment:12 follow-up: 13 Changed 17 years ago by
I confirm that these are DTV and they tune correctly after scanning them.
comment:13 Changed 17 years ago by
I forgot to enter my email in the last reply... sorry for the mess.
comment:14 Changed 17 years ago by
comment:15 Changed 17 years ago by
comment:16 Changed 17 years ago by
Milestone: | 0.20 → 0.21 |
---|---|
Version: | 0.20 → head |
comment:17 Changed 17 years ago by
Component: | mythtv → dvb |
---|
comment:18 Changed 16 years ago by
Milestone: | 0.21 → unknown |
---|---|
Owner: | changed from Stuart Auchterlonie to danielk |
Status: | reopened → new |
I'll verify the Echostar scan for FTA channels. (NASA and a couple others are FTA).
comment:19 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
The echostar descriptors were added a long time ago.
Channel Scan does not work with the NASA channel or the few other FTA channels. But that is a separate issue, and a low priority one since the NASA channel is really the only valuable FTA channel on the EchoStar? satellites.
From the log files, the transports have been scanned correctly and all the channels on those tranports are found as well.
However all those channels are encrypted, so if you have FTA only set when scanning you won't have any channels inserted.
You will also have to be more specific. "Unable to scan echostar..." doesn't actually tell me anything about what you think is going wrong.