-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sky Deutschland #283
Comments
Before we update the sections, the channel order needs to be correct. Here is a log: Example file: |
Yeah that doesn't seem right to me. forgot above lol it is there... |
I have looked for this a long time. Can't find LCN on any of the transponders. So how are the boxes tuning? Do these Sky DE boxes even put the channels in an order? |
Looking at this video it does seem so |
Yes, but to correctly order the channels we need to find where that LCN data is stored on the transport stream (if at all). On all the transport streams I have seen that carry Sky DE channels that datais either not available or hidden in some non conventional place. We really need an expert in SI tables to look at this, e.g. @LraiZer |
Not sure it's worth the hassle mate . |
No LCN listed there, and it must come from the transport stream, so unless someone knows where it is hidden, it is unlikely it will ever be fixed. |
OpenTV LCN is normally hidden HERE |
In the past I spent a lot of time looking. Maybe it is only list on one transponder. If someone has one of these boxes maybe the home transponder is listed in the setup, like on Sky UK boxes. |
It is the first time I have seen a list from their website, I was always redirected to the UK site. Some of the channels on that list do not show up in the debug log. Probably because they are by another provider. Is there an easy way to see the log with lines starting on each service name instead of having multiple services on one line? |
On here it shows the lcn, maybe we can make an custom lcn with the details here . |
ABM uses data on the satellite, not websites. |
Someone has confirmed that the channel list on link in first comment is correct. A raw stream recording of the frequency ABM uses for Sky DE is uploaded on link below. Obtained using a Zgemma H9S SE. Not checked as I don't have Transedit anymore.
|
So maybe test this, and ask dad for the lcn.. ;) Follow the paper trail, to an app-level configuration file on the stream containing the dvb:URL 12031 H 27500 9/10 QPSK 19.2e GFD Service (0xdad) dvbsnoop -n 10 0x08ae >/tmp/bingo.txt stream targetUri: 100=142=dvb://85.B.8E;1;1 STB lamedb5: |
Thanks. How did you export the data in this format please?
|
|
|
dvbsnoop -b -n 100 0x08ae >/tmp/bingo.txt The data already contains CR/LF, so just output the data as binary data with above command and open with notepad to view. There is all sort of junk in there along with lcn data, like some other useful data such as bouquet names etc. but whether this data is of any use other than looking at it, may remain a mystery how to reliably parse this lot. |
I would guess from the data, that it is assigned as Serien? or is it a channelID? |
So somehow we need the dvbreader.c to output this data. |
Looks like a different ETag for many different data files. ETag: "1a5-600aaef11d8ef" data is currently sliced across section 2,3,4,5 of 58 sections on table_id_extension 85. Table_ID: 158 (0x9e) [= User private] table_id_extension: 85 (0x0055) Section_number: 2 (0x02) Last_section_number: 58 (0x3a) Specific "User_Defined-decoding" would be needed to be coded from scratch in a reader. |
Sorry for opening a can of worms. |
So can't a new protocol be coded for this in the python reader code that uses current read_ts function in the dvbreader..c code which is already coded to dump the required sections header info and content data? Just read all sections first, concatenate the sections content data sequentially 0 to last_section. Then usie the ETag as a delimer to determine each config file beginning and end data. |
The read_ts project was never finished. We need to see what that outputs. It is so long ago I really can't remember what is was supposed to do. |
Maybe the read_ts code could eventually be recoded and turned into the skyq config reader for this? Had another quick look at the data, to see what is hidden and to work out how we put back together. So looks like we have to read section 0 first to get the filenames in the order they are sent, then read the rest of the sections sequentially to get the .txt file data which is followed by the .headers file data. Q-skyTVServiceGenres.txt ETag: "5cdafe0c12960-7a" For example in data bellow:
Would give us the two files: Q-TVServicesGenresLabels.txt contents would be: Q-TVServicesGenresLabels.txt.headers contents would be: Etag comes after its related data. First part of Etag "a1-" is the hex value of content-length, ie a1=161 |
Had a little look at this some more, but don't know if anyone else is looking into this also, so just sharing where i am at. Still looking at working out how to parse the data reliably. Parsing filenames still looks tricky, but there is some more new parsing info now in the debug notes. I've made a little config dump tool to read the stream data. It can be used instead of this dvbsnoop binary dump command, as the data output is more or less the same. The config dump tool outputs only the required sections content data, and in correct order.
|
Hi, thanks for your work on this. |
Most work by @yannydodo12 Some channels not being found still. Official chanenl list: https://www.sky.de/hilfe/abonnement/programm/senderliste-sky-satellitenreceiver #283
Hi can the sat_192_sky_deutschland.xml be updated now that we can use the normal bouquets.
I did try update it myself lol but doesn't seem to work right..
I think this is the new line up.
https://www.sky.de/hilfe/s/article/senderliste-sky-satellitenreceiver
Thanks
The text was updated successfully, but these errors were encountered: