Exception java.lang.IllegalArgumentException: new child is null

[ericberendsen]

Exception java.lang.IllegalArgumentException: new child is null

[EricBerendsen]

Thanks for reporting this. There is an issue in the frequency_list_descriptor in the NIT. It has coding_type 0, which is is not defined in EN 300 468 V1.16.1. When trying to display the centre_frequency in a formatted way DVB inspector depends on the coding_type, and 0 caused a problem. Now fixed, for 0 it does not try to format the value, and also small adjustments for other types.

This is fixed view for coding_type==0;

and this is what formatted view looks like for a valid DVB-T2 stream from NL;

Would be interesting to see what the other new multiplexes have as value.

You can find a snapshot build at the bottom of this page, under artifacts, snapshot; https://github.com/EricBerendsen/dvbinspector/actions/runs/756702133

[jan-adam]

Thank you for the quick reply!

I inspected all multiplexes, results below.

• 4 nationwide DVB-T muxes have coding_type: 0x3
• 1 local/private DVB-T mux has no frequency_list_descriptor
• 1 nationwide DVB-T2 mux (discussed in this issue) has coding_type: 0x0
• 1 local/private DVB-T2 mux has no frequency_list_descriptor

According to plans, the migration to DVB-T2/HEVC will continue until June 2022.

Coming back to the issue, I wonder what the broadcaster would say. I will ask on his own internet forum, there should be an answer in a few days. Then we will also close this issue.

Thanks again for the awesome software: DVB Inspector! 😄

[jan-adam]

The coding_type has been changed to 0x3 in the transmitter configuration, so the broadcast is now compliant with EN 300 468 V1.16.1.