[mythtv] Using original network identifiers in the "temporary" range to identify UK DTT multiplexes

Rune Petersen rune at megahurts.dk
Tue Nov 15 01:12:19 UTC 2016

Hi Roger,

I have not looked at the mapping, but I have a minor thing.

The temporary range is from 0xff01-0xffff (255 values) according to:


On 14/11/16 15:55, Roger James wrote:
> Hi,
> After struggling with reconciling table version numbers in the UK DTT network, I
> am having a rethink. The versioning problem arises because the UK DTT network
> uses a single original network identifier. This identifier does not identify a
> group of transmitters carrying the same multiple, but the UK network as a
> virtual whole. However the DTG (the outfit that manages UK DTT) dishes out
> ranges of transport stream IDs and service IDs for individual multiplex
> operators to use. These ranges are defined in this document
> http://www.digitaluk.co.uk/__data/assets/pdf_file/0008/87371/UKDTT_DVBID_Allocation_v1_1.pdf.
> It shows that a multiplex identifier can be extracted from these IDs.
> I am thinking of mapping this identifier into the "temporary" range (0xFF00 -
> 0xFFFF) of original network identifiers and using this replacement original
> network identifier within the dvb facing side of the EIT code. Hopefully this
> will allow me to limit the UK specific part to a very small area of the code.
> Comments anyone?
> Do you think it will work?
> If it does not work I will have to revert to my original plan to maintain
> separate version structures, which is a RPITA (or RPITB if you are in US).
> Roger
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

More information about the mythtv-dev mailing list