P7 to P5

[arvinlau88-droid]

Hi, dovi.script is a really interesting tool,hanks for sharing!

I used dovi.script 3.1.0, DEE 5.2.1, and the script encode_dvmezz_to_dv5.py from https://justpaste.it/enibt to encode a Dolby Vision Profile 7 video to Profile 5. However, the RPU metadata of the resulting Profile 5 file has lost all L4, L5, L6 and L8 information. Using the dee 5.2.1 default config file ，have the same result. Where’s the problem : (

The Profile 7 to Profile 8 work is perfectly.

[R3S3t9999]

L4 is always re-calculated at re-encoding.
L5 will be changed if you crop
L6 is useless and not restored
L8 changed? not possible

[arvinlau88-droid]

Thanks for your reply.
Sorry, i checked with 6-4 and 6-5:
1.L4 may have been inconsistent after re-encoding, which led me to mistakenly think the segment involving L8 prompts in the test demo was behaving incorrectly.
2.L5 is lost, but this is just a test demo , L5 isn’t needed here. I can add L5 globally, but i can’t do it in certain fragments.
3.For dynamic metadata, L6 isn’t needed.
4.L8 is the same in P7、P8 and P5.
So how can I make the L4 of the P5 output same with the P7?

[R3S3t9999]

L4 is a metadata that is calculated automatically by Dolby and depends on your L5. You could restore the original with workflow 2-3, but I wouldn't do that, especially if you crop or downscale since a new L4 will be calculated based on the new L5 crop.

L5 is not lost. The script will edit the original L5 only if you crop or downscale. If you dont, L5 will remain the same.

L6 too I believe, is edited only if you crop; otherwise, the original values are transferred.

[arvinlau88-droid]

L4 is a metadata that is calculated automatically by Dolby and depends on your L5. You could restore the original with workflow 2-3, but I wouldn't do that, especially if you crop or downscale since a new L4 will be calculated based on the new L5 crop.L4 是 Dolby 自动计算的元数据，取决于你的 L5。你可以用工作流程 2-3 恢复原来的，但我不建议这么做，尤其是如果你裁剪或缩放，因为新的 L4 会基于新的 L5 裁剪计算。

L5 is not lost. The script will edit the original L5 only if you crop or downscale. If you dont, L5 will remain the same.L5 并没有丢失。脚本只有在裁剪或缩放时才会编辑原始的 L5。如果不这样做，L5 会保持不变。

L6 too I believe, is edited only if you crop; otherwise, the original values are transferred.我记得 L6 也是，只有裁剪才会被编辑;否则，原始数值被转移。

https://drive.google.com/file/d/1zyB1x1iUP2_ZWKeFSwa34qUzJZTLrW4o/view?usp=drive_link，just this test demo，free to give it a try if you have time，no worries if you don’t. ：）

It should be an issue with either the Dolby Dee or the P5 decode py script.I'm interested in decode to P5; in fact, decode to P8 works really well, and it's also faster than decode to P5.

[R3S3t9999]

There is no issue. As I said, L5 is only modified when you crop. I’ve encoded many movies to Profile 5 and I always verify the metadata. The file you linked is my homemade FEL test file, and I know that L5 is preserved when converting it to Profile 5 because I tested this a long time ago.

The script just converts the RPU to XML as it is, then the DEE uses that xml to encode P5 or P7.

[arvinlau88-droid]

There is no issue. As I said, L5 is only modified when you crop. I’ve encoded many movies to Profile 5 and I always verify the metadata. The file you linked is my homemade FEL test file, and I know that L5 is preserved when converting it to Profile 5 because I tested this a long time ago.没有问题。正如我说的，L5 只有裁剪时才会被修改。我已经把很多电影编码成 Profile 5，并且总是核实元数据。你链接的文件是我自制的 FEL 测试文件，我知道转换成配置文件 5 时 L5 会被保留，因为我很久以前测试过。

The script just converts the RPU to XML as it is, then the DEE uses that xml to encode P5 or P7.脚本只是将 RPU 原样转换成 XML，然后 DEE 用这个 XML 编码 P5 或 P7。

Thanks a lot.

so strange: P7 cmv2.9 to P5 ,L5 is preserved . P7 cmv4.0 to P5,lost L5.

i will install a new winsystem,reconfigure software environment and retry decode to P5.I really have no idea where the problem is. Something must be wrong.Decoding P7 to P5 is successful, but with incomplete metadata, and the script fails when decoding P8 to P5.

[R3S3t9999]

I just tried with cmv4.0 file, and L5 is not lost.
Only L6 maxcll/fall is discarded and L4 is rewritten, which is intended.

[arvinlau88-droid]

I just tried with cmv4.0 file, and L5 is not lost. Only L6 maxcll/fall is discarded and L4 is rewritten, which is intended.

Thanks for your patience and help – hoping reinstallation and reconfiguration can resolve my problem. :))