SOLVED: NL-Lijbrandt muxes?
Added by ruud - almost 13 years ago
Hi, today switched dbv-c provider (from ziggo to lijbrandt).
Because Lijbrandt is not avialable 'on location' button (list), I add a mux manual with information from lijbrandt website:
Frequency 304000
Symbolrate: 6875000
Constellation: QAM64 (not from lijbrandt site, but this one is working)
FEC: auto (also not from lijbrandt site)
after adding a second (bogus) mux, it starts scanning the first mux and finds 13 services (radio and tv channels): these work correct.
Muxes awaiting initial scan = 0.
I have 'Autodetect muxes' enabled.
What is supposed to happen next? What I would expect is that it will autodetect other muxes and scan these for additional services, but it doesn't do that: leaving me with one mux and 13 services....
Any help is highly appreciated as this renders my current setup (almost) useless
not sure if I am missing something, used google but also to no avail....
thanks in advance,
Ruud.
HTS Tvheadend git-0664329
Edit: just re-enabled ziggo again, and within 5 econds it automatically adds all muxes and scans for services.... so tvheadend should not be the problem, perhaps a problem with settings from lijbrandt?
Anyone with more insight or tips and tricks?
Replies (13)
RE: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
Which lijbrandt area are you in?
I suspect you need to do something with the NIT-o setting to get the correct list of the other muxes.
This manual suggest the following network IDs:
Netwerk-id: Almere/Meppel 8200, Rijssen/Holten/Enter 7461, Dordrecht 3300, Leeuwarden 8900
http://www.lijbrandt.nl/pdf/handleiding/DVBCInstelling.pdf
Or these:
Plaats en omgeving Netwerk ID:
Omgeving Amsterdam, Hoofddorp: 1000
Omgeving Arnhem, Hilversum, Utrecht, Veenendaal: 3900
Omgeving Deventer, Haaksbergen: 7461
Omgeving Dordrecht: 3300
Omgeving Eindhoven: 5600
Omgeving Leeuwarden: 8900
Omgeving Lelystad: 8200
Voor Amsterdam - Oostelijk havengebied gelden tijdelijk een andere frequentie en netwerk-id:
- Frequency: 311,25Mhz (invullen als 311250)
http://www.lijbrandt.nl/support/tv_en_radio
Hein
(using a simple lijbrandt dvb-c google query)
RE: NL-Lijbrandt muxes? - Added by ruud - almost 13 years ago
Hoi Hein,
that is the site where I got the initial mux information from
I am in Utrecht area so I filled in the NIT 3900.
The manual entered mux works okay (picture and sound on all 13 found services), problem is that tvheadend does not automagically detect additional muxes...
any other thoughts or pointers?
Thanks in advance,
Ruud.
RE: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
Make a mux dump and then use dvbsnoop or an other transport stream analysis tool to see what information you can find in the NIT tables (both actual and others). Tvheadend is using that information to find the other muxes.
Maybe this tool is easier to use the dvbsnoop : http://www.digitalekabeltelevisie.nl/dvb_inspector/
Hein
RE: NL-Lijbrandt muxes? - Added by ruud - almost 13 years ago
Hi,
just saved a couple of minutes (mux-dump on) and ran the file through dvbsnoop.
search for NIT and the below part is relevant. Unfortunately for me this is all way over my head
I can sent you a link to the recorded file...
-------------
Guess table from table id...
NIT-decoding....
Table_ID: 65 (0x41) [= Network Information Table (NIT) - other network]
section_syntax_indicator: 1 (0x01)
reserved_1: 1 (0x01)
reserved_2: 2 (0x02)
Section_length: 3571 (0x0df3)
Network_ID: 11840 (0x2e40) [= --> please lookup at http://www.dvb.org]
reserved_3: 0 (0x00)
Version_number: 4 (0x04)
current_next_indicator: 1 (0x01) [= valid now]
Section_number: 232 (0xe8)
Last_Section_number: 3 (0x03)
reserved_4: 6 (0x06)
Network_descriptor_length: 3648 (0x0e40)
MPEG-DescriptorTag: 24 (0x18) [= NPT_endpoint_descriptor]
descriptor_length: 0 (0x00)
MPEG-DescriptorTag: 60 (0x3c) [= ITU-T.Rec.H.222.0|ISO/IEC13818-1 Reserved]
descriptor_length: 0 (0x00)
DVB-DescriptorTag: 171 (0xab) [= User defined/ATSC reserved]
descriptor_length: 5 (0x05)
Descriptor-data:
0000: 80 1d bb a7 4d ....M
DVB-DescriptorTag: 165 (0xa5) [= User defined/ATSC reserved]
descriptor_length: 24 (0x18)
Descriptor-data:
0000: e9 8e 80 71 4d ed 81 03 de 85 77 f0 08 1f a4 fc ...qM.....w.....
0010: 9c d0 0b 3e 40 1f 7f b9 ...>@...
DVB-DescriptorTag: 156 (0x9c) [= User defined/ATSC reserved]
descriptor_length: 41 (0x29)
Descriptor-data:
0000: 52 b8 dc 8b 1b 5f b0 bd e7 dd f8 32 2b 67 a0 15 R...._.....2+g..
0010: 8a f2 36 cb 8f 54 6d ea 7b 00 22 00 73 48 c2 be ..6..Tm.{.".sH..
0020: e2 a6 0b e0 4b 89 f1 c7 3d ....K...=
MPEG-DescriptorTag: 3 (0x03) [= audio_stream_descriptor]
descriptor_length: 20 (0x14)
free_format_flag: 1 (0x01)
ID: 1 (0x01)
layer: 3 (0x03)
variable_rate_audio_indicator: 1 (0x01)
reserved_1: 0 (0x00)
MPEG-DescriptorTag: 44 (0x2c) [= FlexMuxTiming_descriptor]
descriptor_length: 190 (0xbe)
FCR_ES_ID: 21670 (0x54a6)
FCRResolution: 4188020738 (0xf9a02002) [= (cycles/s)]
FCRLength: 8 (0x08)
FCRRateLength: 2 (0x02)
MPEG-DescriptorTag: 51 (0x33) [= ITU-T.Rec.H.222.0|ISO/IEC13818-1 Reserved]
descriptor_length: 123 (0x7b)
----> ERROR: unimplemented descriptor (mpeg context), Report!
Descriptor-data:
0000: c9 72 06 59 5b cd 02 07 da 82 00 1c 80 2a 22 7d .r.Y[........*"}
0010: be e0 06 80 0e 45 80 38 f6 17 9d eb fe 39 b5 fc .....E.8.....9..
0020: 4b 95 64 e1 69 4b 4a 6f 4e 00 ce 1a 08 1f 98 00 K.d.iKJoN.......
0030: fa 0f 00 77 fc 80 95 ff 58 de 54 10 3e 4a 28 03 ...w....X.T.>J(.
0040: 6e c2 45 84 93 5b 9c 5e ee 3f e3 21 52 9f e0 db n.E..[.^.?.!R...
0050: 3b 25 c1 76 c5 43 9b 68 fa 02 07 eb 00 3f 00 30 ;%.v.C.h.....?.0
0060: 00 50 00 d3 80 06 60 0b bb d1 42 80 1f 65 fb 7f .P....`...B..e..
ETC.
RE: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
Run it through dvbinspector ... That is graphical and can most likely give you some more details .
And ... See this as a nice puzzle and use google as your textbook to learn more about this puzzle.
Hein
SOLVED: NL-Lijbrandt muxes? - Added by ruud - almost 13 years ago
Hoi Hein,
thanks for the challenge 'never to old to learn' LOL.
this is what I learned:
mux, frequency:
#1, 304000Mhz
#2, 312000Mhz
#3, 320000Mhz
#4, 328000Mhz
#5, 336000Mhz
#6, 344000Mhz
#7, 352000Mhz
#8, 360000Mhz
all with:
Symbolrate 6875000
Constellation: QAM-64
FEC: None
NIT: 3900 (Utrecht area)
it finds 86 services.
best part is that these are all unencrypted! this makes my setup easier (no CI / Oscam etc.) and.... on my tv's I can receive digital TV without the need for a smartcard reader / CI card (extra costs).
Worst part is that all services are SDTV, if you want HDTV you have got to go the IPTV route (next 'project')
Thanks, and I hope that this info is usefull for somebody
EDIT: Question still remains why auto discovery didn't work....
RE: SOLVED: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
Good that you got all your channels ...
But ... Did you runyour mux dump through dvbinspector?
Did you make the mux dump from tvheadend? Could you maybe post a 1min dump here?
And abou iptv .. I assume you are already reading the lijbrandt iptv thread on tweakers?
Hein
RE: SOLVED: NL-Lijbrandt muxes? - Added by ruud - almost 13 years ago
Hoi Hein,
the mux info came from dvbinspector it was all in the muxdump generated bij tvheadend.
Haven't looked into the IPTV info yet, just invistigated how I can use my ClearOS server as 'end-point' in stead of the device from Lijbrandt.
Any issues with Lijbrandt and IPTV that I should know off (before reading the complete tweakers thread :)?
muxdump attached.
regards,
Ruud.
EDIT: attaching didn't work so you can download it via this link: https://xceed.no-ip.org/mp/_dev_dvb_adapter0_Philips_TDA10023_DVB_C304000000.dump1.ts (ignore the certificate error)
RE: SOLVED: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
Start with the start message of that thread on tweakers .... And make sure that you have a seperate network card in your server that can attach to the iptv lan of lijbrandt and make sure your dhcp request on that network impersonate a amino device (all this is in that thread)
I wil have a look later to night at that dump ...
Hein
RE: SOLVED: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
when you tried the " audo detect muxes" option ... did you have something populated in the NITo field? Lijbrandt is not using NITo but NITa .. so you do not need to set the NITo option for Lijbrandt.
Could you try to remove all the muxes, remove the NITo setting and then manually add the 304KHz mux ... and then activate the auto mux discovery?
Hein
RE: SOLVED: NL-Lijbrandt muxes? - Added by ruud - almost 13 years ago
Hoi Hein,
I had 3900 filled in so not empty.
will try tomorrow, tonight the server is running full-time recordings (fingers crossed)
is there an easy way to save my current config (channels numbers etc.)? Put quiet some work in tuning that to my liking, retesting will mean doing that again (and if I can avoid that...)
thanks, will report back!
Ruud.
RE: SOLVED: NL-Lijbrandt muxes? - Added by Hein Rigolo almost 13 years ago
shutdown tvheadend and then make a copy of the .hts directory under the user that is running tvheadend (most likely also hts). Then restart tvheadend again and make the changes and see what is happening. If everything works .. then you can decide for your self if you want your old backup back and remove the NITo ID.
Hein
RE: SOLVED: NL-Lijbrandt muxes? - Added by ruud - almost 13 years ago
Hoi Hein,
erased everything, cleared the NIT-o field, manually added the first mux, and it worked: all other muxes started populating the mux list!
So I guess the programming logic would be: that if in the initial mux a NIT-a record exists, the NIT-o variable should be 'skipped'.
yesterday ordered an additional network card for my server, so that the IPTV fun can begin
Thanks for helping out!
regards,
Ruud.