DTMB terrestrial television

DTMB is a terrestrial television transmission system defined by GB 20600, with its specific framing, coding and modulation required before service media can be recovered.

DTMB, Digital Terrestrial Multimedia Broadcasting, is a terrestrial transmission system defined by GB 20600. ITU’s terrestrial-system material identifies its distinct transmission arrangement.

It is not another name for DVB-T, nor a video codec that a media server selects after receiving any digital RF signal.

Framing and modulation need a compatible receiver

The standard addresses how data is framed, coded and modulated for transmission. Its single-carrier/multicarrier arrangements and synchronization structure need their own receiver support.

Linux’s frontend parameter documentation provides examples of relevant DTMB mode and guard identifiers:

Identifier family Role
C1 / C3780 Applicable transmission-mode distinctions
PN-related guard identifiers Defined synchronization/framing-related selections
Delivery-system declaration Whether the frontend exposes the required system

Those API names describe an implementation contract. They are not a complete dump of the DTMB specification or proof that every tuner implementing the API supports it.

A guard or framing identifier taken from another terrestrial system should not be silently assumed to have the same meaning.

A media decoder is a later resource

Consider an original compatibility exercise:

{
  "frontendDeliverySystems": ["DVB-T", "DVB-T2"],
  "requestedDeliverySystem": "DTMB",
  "clientVideoDecoderAvailable": true
}

The frontend’s declared set does not include the requested system. The positive client-decoder flag cannot recover missing RF data.

The object is readable teaching data, not a native query or a real product capability report.

In the reverse case, a compatible receiver can recover a programme whose audio or video still needs another decoder or preparation route. These conditions have different positions in the chain.

The standard label does not supply every service property

The recovered transport and selected service establish the actual encoded components. The transmission standard’s scope should not be expanded into a universal resolution, bitrate or codec for every programme.

For an Emby source, hardware/driver/backend support must first expose a usable service. Playback then depends on the supplied media and the chosen client.

See Also

References