search

oe-alliance / AutoBouquetsMaker

Automatically build and update bouquets from the DVB stream.
GNU General Public License v3.0
23 stars 59 forks source link

Channel is missing when doing a channelscan #157

Closed ghost closed 3 years ago

ghost commented 4 years ago

Hi, I'm doing a DVB-C channelscan, but the channellist misses one channel. When doing a channelscan with TransEdit the LCN is filled in with channelnumber 613 which is correct. How can I get this missing channel with AutoBouquetsMaker?

ghost commented 4 years ago

I also tried the cableplugin from the feed, and this one finds channel 613 without problems.

However, I need AutoBouquetsMaker as the cablescan plugin doesn't work with my SAT>IP server like AutoBouquetsMaker does.

Can you please fix this issue?

Thanks!

AbuBaniaz commented 4 years ago

Enable debug logs in image. Enable extra debug in ABM. Run ABM just for that provider and then upload debug log. If you have IPTV, delete any sensitive details.

If you can get a stream recording of the raw data on the home transponder, even better. About 60seconds worth is long enough.

ghost commented 4 years ago

I can use TransEdit for this purpose?

ghost commented 4 years ago

Here's the debug log:

[file removed]

ghost commented 4 years ago

As workaround for now I do a channelscan for the first network ID and then insert one channel from the other netwerk ID to the first netwerk ID. However, I hope you can fix this issue very soon, so this workaround isn't needed anymore. ;-)

AbuBaniaz commented 4 years ago

Can you please confirm the recording you provided earlier was on the home transponder/frequency for the NetID?

In response to the earlier question, yes Transedit is fine.

ghost commented 4 years ago

Hi, yes recording was done from the home frequency of the Network ID.

ghost commented 4 years ago

I also tried dvbsnoop on my Enigma2 receiver with option -s ts -tsraw -b > capture.ts when tuning the home frequency. and get this: Error (122 ): DMX_SET_PES_FILTER failed: Operation not supported Is this correct or can I try another command with dvbsnoop? Actually I'm hoping the debug logs of both Net ID's can help you.

AbuBaniaz commented 4 years ago

ABM reads tables, it does not interrogate frequencies

One of the ABM developers said the recording was on the incorrect frequency and that you are using old NetID. It is also possible that the the encryption flag is wrong.

If you receiver is capable, you could try getting a recording with this: https://github.com/oe-alliance/AutoBouquetsMaker/tree/tools/scripts%20and%20tools/Stream%20recording

ghost commented 4 years ago

I will try the tool, but the recording was taken from the correct frequency of 164MHz as I live in former UPC area. UPC has merged with Ziggo several years ago, but the home frequency didn't change until today. Otherwise I didn't have signal, right? ;-) My cable provider uses the NetID for other purposes. NetID 4444 is for FTA channels and NetID 5555 for people with a subscription for encrypted channels including the FTA ones. I use NetID 4444 because of the correct LCN and order of the FTA channels. The cables_nl.xml of ABM is incomplete. Therefor I uploaded an updated version which you can use.

ghost commented 4 years ago

If you can get a stream recording of the raw data on the home transponder, even better. About 60seconds worth is long enough.

Succes! With an USB tuner I was able to record the complete TS stream from the home frequency at 164 MHz. Please search for PSI -> NIT -> Network ID 4444 -> Transport Stream 2051 at 834.75 MHz. The LCN is 613 which is correct. Also the service visible flag and encryption flag is correct as far as I can see.

But why doesn't it show up in my channellist of ABM like the cablescan plugin does?

[file removed]

Please also update the cables_nl.xml file on your server, see attachment. Ziggo has 2 separated home frequencies and has taken over former cable operator UPC some years ago, but they still kept those home frequencies (164.00 MHz for former UPC and 474.00 MHz for former Ziggo). UPC is now also completed in this file with Network ID 4444 and 5555. Thank you!

[file removed]

AbuBaniaz commented 4 years ago

This is the response from one of our developers

As I am not aan Ziggo customer, it is difficult for me to test.
I understand he is using an 'old' netid for Ziggo (4444).
The ts file for that netid is recorded on the wrong frequency. This file does not contain the correct information.
As far as I understand Ziggo has now 1 netid (5555) for all their networks, also the old UPC networks.
When he is using this netid and that 1 channel 613 is missing, we need a recording of the home channel freq we are using for netid 5555.
Then I can have a look at it.

As I understand he only wants the FTA channels. It is possible that Ziggo has the subscription flag on 613, but free to watch.

Please get a recording of 474000

ghost commented 4 years ago

How can I contact the developer directly? It's very difficult to communicate this way. As Ziggo customer I know all the details. ;-) The developer has it wrong. Ziggo has multiple NetID's which can be used. Ziggo has 2 home frequencies (164 and 474 MHz) as I told before depending on in which area you are. See next post for proof ;-)

And why does the TS file not contain the correct information according to him? What's incorrect? It contains all the possible NetID's of my area. There's no signal at 474 MHz, as I'm in former UPC area, not former Ziggo area! Therefor I cannot record a stream from this frequency.

No, the subscription flag is set correctly. No difference between scanning with or without FTA channels option in ABM. NetID 4444 is for FTA channels with the correct LCN. Yes, indeed, I only want the FTA channels, but with the correct LCN and without data services, inactive channels etc. which is only possible with use of NetID 4444. Then the channels are sorted in the correct way.

In my opinion the developer should investigate the provided TS file and both debug logs I've made for both NetID 4444 and 5555.

This is all I can do. A recording of frequency 474.00 is inrelevant, as the bug occurs with frequency 164.00 MHz which is the only home frequency in my area.

So, please take a look at it and search for strange behaviour in DVB-C specifications in the logs and stream and let's try to let ABM remove the space character.

Hope to see a fix for this issue very soon. Thank you! ;-)

ghost commented 4 years ago

Please read this as well and let Google Chrome translate it to English: https://www.techconnect.nl/blog/2217/ziggo-digitaal-kijken-zonder-module/amp/

I'm using option 4 as I'm in former UPC area.

Also read this:

https://www.ziggo.nl/klantenservice/televisie-radio/digitale-tv/activeringscode-frequentie-netwerk-id-instellen#/zonder-mediabox-of-ci+-module/upc/

ghost commented 3 years ago

Thanks for updating cable_nl.xml !

peterfdej commented 3 years ago

I analysed the latest recording of 164 (4444) and it contain good data. ABM uses for cable the so called NIT scan. I noticed that the dvb NIT table for 4444 is not complete. For the transponder where Stingray Classic is broadcast, the Service_list_descriptor 0x41 is missing. Therefor the NIT scan skips this transponder, because it has no good information. When I look at the SDT table, this is more complete. It also has LCN in SDT table. Perhaps we can use for 4444 the SDT scan protocol. Try and error. :-) 4444

ghost commented 3 years ago

Great that you found the problem, thanks for analysing! What should I do next? Or will you do an update for ABM?

AbuBaniaz commented 3 years ago

Can you upload another recording of 164 MHz. 30 seconds worth. No larger than 100MB. Thanks.

ghost commented 3 years ago

Ofcourse, here it is.

[file removed]

Huevos commented 3 years ago

Change protocol to "vmuk2".

Huevos commented 3 years ago

Also, possibly "lcn2" as it looks like 0x83 is present in NIT, and just 0x41 is missing.

Anyway, try both and see what result you get.

ghost commented 3 years ago

Hi, great, that did the trick, thanks! When I set the protocol to lcn2, the issue is fixed, finally. ;-) Very easy! But what should we do with cable_nl.xml? Can we set it to lcn2 without problems for all providers including Ziggo?

AbuBaniaz commented 3 years ago

We'll have to split it as far as I am aware. We can rename the section to Ziggo too.

AbuBaniaz commented 3 years ago

The NetIDs are as follows:

1536 - Ziggo Network
3333 - HE Heerenveen B2B FTA
4444 - HE Heerenveen FTA
5555 - HE Heerenveen
6666 - HE Heerenveen B2B

43136 - HE Amsterdam
43138 - HE Lelystad
43140 - HE Heerenveen
43142 - HE Zevenaar
43144 - HE Helmond
43146 - HE Rotterdam

Please check and tidy up this file and re-upload. cable_nl_ziggo.zip

ghost commented 3 years ago

Here's the updated cable_nl_ziggo.xml. The 43xxx range are old NetIDs for Philips TV sets for LCN compatibility, but not needed for Enigma2 receivers. The current ones are 4444 and 5555. 1536 is the internal network of Ziggo and not useable.

NetID 3333 and 6666 are also old NetID's as they aren't menioned anymore when I follow the wizard for business partners to install TV. Only 4444 and 5555 are mentioned. So, we only have 2 NetID's on both frequencies. Much better ;-) I updated the file. Please upload it on your server and remove Ziggo from cable_nl.xml. Thank you!

cable_nl_ziggo.zip

Then the issue is fixed and this topic can be closed ;-) Thanks for all the help!

Huevos commented 3 years ago

How do we know this works in other regions?

ghost commented 3 years ago

Please read this again (let Chrome translate the site): https://www.techconnect.nl/blog/2217/ziggo-digitaal-kijken-zonder-module/amp/

I also checked the Ziggo wizard for random places in the country and all is now NetID 5555 or 4444.

ghost commented 3 years ago

Issue is fixed and a separated config file for Ziggo is created using LCN2 protocol.