tsduck: [Q] How to tune DVB-C/B aka J.83B 256-QAM transponder over terrestrial?

tsscan --nit-scan --delivery-system DVB-C/B -f 112750000 --debug -m 256-qam -s 5900000

doesn’t lock

dvbv5-zap -vvv -c channel.conf test

where channel.conf contains the following, works:

[test]
        DELIVERY_SYSTEM = DVBC/ANNEX_B
        FREQUENCY = 112750000
        MODULATION = QAM/256

I see dvb-c/b has unsupported stuff in a bunch of places, what does that actually “mean”? Is there anything needed to support other than passing this tuning parameter to dvb-api?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (9 by maintainers)

Commits related to this issue

Most upvoted comments

there’s a nit-other that links to isdb-t channel

Currently, tsscan uses the NIT Actual only. The idea is to scan a network starting from a TS of that network. Therefore, on the initial TS, the target NIT is the actual one.

dig through the arib specs to look for dvbc specific descriptors.

AFAIK, the only ARIB specs containing signalisation are STD-B10 and STD-B21 (see bibliography) and they do not mention a cable descriptor.

The only spec I do not have access to is ARIB STD-B16 (ISDB Standard Digital Receiver for Satellite) which is not free and not available in English. Given the reference to satellite, I don’t think we could find anything about cable.

The only delivery system for which there is no signalisation is DVB-C (/A, /B, /C). So, the only case with a problem is a TS description containing a cable_delivery_system_descriptor. All the rest is addressed using other delivery descriptors.

We face only two cases:

  1. On a cable, inside one “network” (in the DVB sense), all TS use the same Annex A, B or C. In that case, in the presence of a cable_delivery_system_descriptor, we scan that TS using the same variant of DVB-C that was used to scan the initial NIT.
  2. On the same cable, several variants of A, B or C coexist. Since there is no way to signal which variant is used on which TS, I consider this case as unrealistic and unpractical because no official cable set-top box could successfully scan the network.

Therefore, I will implement solution 1. We will see how it behaves. We count on you @trollcop to provide some feedback, when you are available, because you are probably the only TSDuck user who uses it on non-/A DVB-C networks.

Damn it! Thanks a lot for finding this. Another wonderful copy/paste story…

I will fix it right away. Because this enum/string table is used everywhere, including in the definition of option --delivery-system, specifying --delivery-system DVB-C/B actually resulted in using DVB-C/A.

See the definition of option: https://github.com/tsduck/tsduck/blob/2ea222a3cb4ab6c7ce6f9fcd9a299b4f67618cee/src/libtsduck/dtv/broadcast/tsModulationArgs.cpp#L1443