Saw that, interesting…
If they used your work, that’s interesting, because they didn’t help you…
This is really interesting, maybe this work is not as a grey area as I thought it was.
2 Likes
Never saw the difference between passing through DV data vs passing through Dolby audio data which is done without checking the chip version myself…
They did provide input and answer questions on what they had done when asked. May have preferred more details in some of the answers - but they were clear on where the line was. I can’t complain there
A quote from the first post:
What are FEL and MEL?
In Profile 7 video, the enhancement layer may be ‘full’ (FEL) or ‘minimum’ (MEL). FEL includes a video stream which modifies every pixel of the base layer. MEL is equivalent to Profile 8.1. FEL requires sophisticated decoder hardware and support for it seems to have been dropped in newer kernels and Android versions. Software is available which can merge a FEL into the base layer to produce a Profile 8.1 video.
Question: how can the FEL layer of a Profile 7 FEL video (12 bits) be merged into a profile 8.1 video without quality loss?? I always thought that profile 8.1 is 10 bits.
Where it says that it can (convert P7 FEL to P8.1) without quality loss?
The conversion is done for devices that cannot display DV P7 FEL but can display DV P8.1. Quality loss is then not of primary importance.
It was my interpretation of the last sentence: “Software is available which can merge a FEL into the base layer to produce a Profile 8.1 video.” No remark is added that this results in information lost.
For me, basic DV understanding of P7-FEL and P8.1 combined with common sense makes any such remark unnecessary; if there is no quality loss who’d give a fuq about FEL 
One way you can merge the P7 FEL into P8 is by using DoVi_Scripts to encode “bake” the FEL layer to P8 (using DoViBaker + x265/NVenc). Since I never did it I am not sure how much quality is lost. @R3S3T_9999 can further clarify since he developed the great DoVi_Scripts.
FEL to MEL is easy done by dovitool.
It discard the FEL data and use only the RPU.
The TV will use these info with base layer to produce DV 8.1 quality.
I am not sure about the purpose of all this work except selling more devices. Like the 4k is not compatible with it is just nonsense, it’s just not wanted to sell even more devices.
I did not see any code but I am sure the use CE code like to merge dual layer to single layer as CE ist the first Kodi implementation supporting such dual layer streams. This is the bad side of open source…
5 Likes
Well it requires re-encoding so there is ‘‘loss’’ but depending on how good one is with the x265.exe settings, it’s possible to encode something that is transparent to the source. Obviously the FEL+BL merged encode is 10bit but that doesn’t matter because there’s no 12bit TV on the market.
2 Likes
Pretty sure CE couldn’t play it, but wouldn’t it be possible to encode the FEL+BL merged result into a 12-bit 422 format to actually get the best result?
Yes, dovi_baker output is 16bit RGB and 100% lossless.
x265.exe supports 12bit encoding but nothing can play the file.
FEL baked 12 bit x265 encode (420 though) sample
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Format Range@L5.1@High
HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 25 s 609 ms
Bit rate : 39.4 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Display aspect ratio : 2.39:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 12 bits
I have tried this build and an episode of a Dolby Vision encoded show looked amazing on the LG C8.
@doppingkoala you are a genius to go that far with this proprietary format. Thank you for your work.
I’ve ran into trouble with some episodes of another show, that plays fine with the normal Omega 21.1.1 in HDR backward compatibility. With this experimental Dolby Vision build, the audio goes mute every few seconds, and the Dolby Vision logo is redisplayed by the TV every few seconds. I can give you a short sample but I can’t seem to find a way to send private messages here, and posting publicly such files are not safe.
1 Like
You must have a minimum number of posts (don’t know how many 
before you get the option to send private messages…
Any chance the file that doesn’t work is 25 Hz or 29.97…Hz and CE isn’t outputting the HDMI at the native framerate?
@doppingkoala You are right, the file is indeed 25 Hz. I think it is outputted at 50 Hz.
[cplayer] ● Video --vid=1 (hevc 3840x1920 25 fps) [default]
[cplayer] ● Audio --aid=1 --alang=en (eac3 6ch 48000 Hz) [default]
Try enabling the 3840x2160 25Z mode in whitelist setting.
If that doesn’t work will likely need a sample of the file (or another that you are willing to share with the same issue). Also try entering
echo 2 > /sys/module/amvideo/parameters/dv_injection_log_level
and then posting a dmesg log with that file playing on the chance the log shows something useful
Nothing is whitelisted, so it means every mode is available?
Last time I’ve tried again, the audio didn’t skip, but there were broken frames every couple of seconds.
EDIT: File removed, as it is not needed any more.