Here are some considerations on the images posted by RESET_9999 (which I continue to thank)
Let's start by looking at the pictures on the PLEX forum (
HERE)
The peculiar behavior of the red and blue channels immediately catches the eye. In the Single Layer version, if you look at the region of the histogram lights there is no information relating to the two previous channels with the result that the green color predominates in the image (giving this greenish halo)
Now let's move on to Netflix and RESET_9999 images.

The behavior of blue is almost identical. Green and red (mostly red) tend to shift towards midtones making the image appear "more saturated"
Now let's move on to the X700 which plays a DV Dual Track Dual Layer file and the Shield which instead plays one of my files (dvhe.07.06 Single Track Dual Layer).

Do you notice any similarities with Netflix images?
I see the same behavior as before and in any case totally different from the images on the PLEX forum.
Clearly the analysis is not valid because each test should be carried out with the same camera, the same TV, the same player, etc ... but ... but ...
Different devices give a different "footprint" to the videos they play.
Perhaps what RESET_9999 has noticed is simply the normal behavior of the Shield.
And if Netflix videos are displayed in the same way as mine, then Netflix is also using streams with the wrong colors ...
smartrobot wrote: Fri Mar 06, 2020 4:35 am
FFMPEG output warnings
Code: Select all
[NULL @ 0x5568201f5c80] Invalid NAL unit 36, skipping.
[NULL @ 0x5568201f6e40] Invalid NAL unit 36, skipping.
yusesope output
Code: Select all
___@little-server:~/src$ python3 bl_el_rpu_builder.py -tbw 4 -bl ~/BL.hevc -el ~/EL.hevc -o ~/Out.hvec
Exception in thread Thread-1:LYSIS: 86.8% BL_EL_RPU WRITING: 86.0%
Traceback (most recent call last):
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "bl_el_rpu_builder.py", line 175, in run
self.read()
File "bl_el_rpu_builder.py", line 163, in read
self.get_nal_info(mm,length,global_offset)
File "bl_el_rpu_builder.py", line 138, in get_nal_info
nal_type = self.get_nal_type(mmap_obj[(nal_offset + 3):(nal_offset + 5)])
File "bl_el_rpu_builder.py", line 128, in get_nal_type
nuh_layer_id = b_stream.read('uint:6')
File "/home/nick/.local/lib/python3.6/site-packages/bitstring.py", line 3902, in read
value, self._pos = self._readtoken(name, self._pos, length)
File "/home/nick/.local/lib/python3.6/site-packages/bitstring.py", line 2016, in _readtoken
"Tried to read {0} bits when only {1} available.".format(int(length), self.length - pos))
bitstring.ReadError: Reading off the end of the data. Tried to read 6 bits when only 1 available.
Exception in thread Thread-2:LYSIS: 92.4% BL_EL_RPU WRITING: 91.3%
Traceback (most recent call last):
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "bl_el_rpu_builder.py", line 175, in run
self.read()
File "bl_el_rpu_builder.py", line 163, in read
self.get_nal_info(mm,length,global_offset)
File "bl_el_rpu_builder.py", line 138, in get_nal_info
nal_type = self.get_nal_type(mmap_obj[(nal_offset + 3):(nal_offset + 5)])
File "bl_el_rpu_builder.py", line 128, in get_nal_type
nuh_layer_id = b_stream.read('uint:6')
File "~/.local/lib/python3.6/site-packages/bitstring.py", line 3902, in read
value, self._pos = self._readtoken(name, self._pos, length)
File "~/.local/lib/python3.6/site-packages/bitstring.py", line 2016, in _readtoken
"Tried to read {0} bits when only {1} available.".format(int(length), self.length - pos))
bitstring.ReadError: Reading off the end of the data. Tried to read 6 bits when only 1 available.
BL ANALYSIS: 99.3% EL ANALYSIS: 99.3% BL_EL_RPU WRITING: 99.3%
There appear to be incorrect NAL units in your stream (as ffmpeg has pointed out to you).
If you analyze a stream like this with my program, you will surely get errors: it is a very simple tool that does not have the ability to handle unexpected errors.
The tool expects to receive a perfect stream ...