[DoVi_Scripts] Multi-Function Scripts for Dolby Vision processing and a lot more...

[Atari1971]

Sorry, I don't see the link

[Kuler087]

Click on the word ''Resolve (https://www.youtube.com/watch?v=FVSh3oGqfXY)''.

[Atari1971]

Thank You Very Much

[ac777103]

I've run 6-2 on a rip of the UK UHD of Terminator 2 and in the graph the mastering display info says "ul - ul". What does this signify?

[Kuler087]

This movie is missing the HDR10 mastering display information.

[B0b]

I keep getting the same error. Can someone tell me what I don't have configured correctly?

11/21/2024/19:44:51.410000000 cuda: NVIDIA GeForce RTX 4090: compute 8.9, cores 16384*2625MHz, memory 24563MB
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Test_full_hdr_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Reading generate config file...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 177768 frames
Done.
Error: expected value at line 21 column 36
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .

[Kuler087]

avisynth+?
madvr beta?
lav filters?

[B0b]

I have avisynth+ installed and it opens notepad everytime I run the script. If I don't associate it with notepad I receive an error running the script that avs isn't associated with anything. I adjusted the video lav filter per the video. Madvr was included in your installation, so I didn't replace it. Do I need to overwrite what was in the installation files?

[Kuler087]

Madvr was included in your installation, so I didn't replace it. Do I need to overwrite what was in the installation files?
only the files are included, you have to click on the madvr install bat

[B0b]

I did run the install bat file. I've uninstalled/reinstalled multiple times. I have something not set up correctly. I even wiped my drive and reverted to Win 10 after seeing your post about issues with the Dolby Vision tools and Win 11. If I run a 30 second clip, the script works properly. If I run a 30 minute clip, the script can't find the xml file or I get this:
Measuring video file "E:\Test_30_min_hdr.mkv"...
Metadata:
Mastering display luminance: 0/0, gamut: 0 0, 0 0, 0 0, 0 0
MaxCLL: 0, MaxFALL: 0 nits

For some reason, measurement didn't produce a "complete" file.
Reading generate config file...
Parsing madVR measurement file...
Error: The system cannot find the file specified. (os error 2)
The system cannot find the file specified.
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
madvr failed to make the scene cuts
Press any key to continue . . .

[Kuler087]

For some reason, measurement didn't produce a "complete" file.

https://forum.doom9.org/showthread.php?p=2010062#post2010062

[Black Ops]

Is it possible to modify MaxMDL (Maximum Mastering Display Luminance) without having to re-encode?

[Kuler087]

I think ffmpeg can do it but i dont know the cli

[Andy22]

For the Ugoos AM6B in LLDV mode, playing CMv4.0 files from streamed content, is it advised to remove 4.0 via the dovi_tools or is the default CMv2.9 fallback working fine?

Just confused, since AM6B guide states "When using LLDV mode, these devices only decode CMv2.9 metadata" yet CMv4.0 is backwards compatible, so not sure what actually happens in the LLDV case on this device?

[Kuler087]

No need to remove anything. It will fallback to the cmv2.9 bloc.

[Black Ops]

In your Dolby compatible devices spreadsheet, you mention "Fake TV Led". What is it exactly thats fake about it? Is this only applicable to Dolby vision and not standard HDR10/HDR10+?

[Kuler087]

It means the device is processing the RPU metadata even when doing TV-LED. This is a bug that @CPM found and fixed for any device that can install the coreelec builds. Even the latest Firestick TV and Google Chromecast has this bug.

In LLDV, the player processes the RPU metadata and does the tone mapping.
In TV-LED, the player is supposed to send the RPU metadata untouched to the display and the TV does the tonemapping.

see this video of the TV-LED RGB signal captured:
https://www.youtube.com/watch?v=z8sgHR78Rdw

[ac777103]

Is there a way to upgrade P7 MEL rips via any of the workflows, that takes account of the embedded RPU data to add CM v4?

[Kuler087]

Yes, but only if you can get the original CMv4.0 RPU from WEB streaming services. You also have to make sure that both sources have exactly the same L1/L2 metadata. Like this: https://slow.pics/c/djXrowII
Once you have done all the checks, you can use workflow 2-3 to transfer cmv4.0 levels to the original P7 cmv2.9 RPU.

in other words, you can't transfer generated levels to an original RPU.

[Atari1971]

Good evening. I replaced the .bat "3.0.3_mkv" with 3.0.4. Since then, I've only had serial "file not found" errors... :confused:

Example :

Donate: https://www.paypal.com/donate/?hosted_button_id=6ML5KUZG9XGB6 Date: 25/11/2024 22:32
Contact: R3S3T_9999@proton.me Version: 3.0.4_MKV
Tutorials: https://www.youtube.com/playlist?list=PLFGpkrmX_eOL2Dre1ZyIJP2uMtcQYH8ql


_____ __ ___ _____ _ _
| __ \ \ \ / (_) / ____| (_) | |
| | | | __\ \ / / _ | (___ ___ _ __ _ _ __ | |_ ___
| | | |/ _ \ \/ / | | \___ \ / __| '__| | '_ \| __/ __|
| |__| | (_) \ / | | ____) | (__| | | | |_) | |_\__ \
|_____/ \___/ \/ |_| |_____/ \___|_| |_| .__/ \__|___/
-Author: RESET_9999--------------------------|__|-----------



1) MODE.I= INJECT / EDIT / EXTRACT / INFO / VALIDATE
2) MODE.F= VERIFY SYNC / REMOVER / TRANSFER LEVELS
3) MODE.H= DoVi MAKER from HDR10 (Dolby Algo or MadVR or HDR10+)
4) MODE.7= DoVi Profile 7 Input (MKV/BDMV)
5) MODE.B= DoVi MKV Batch Muxer
6) MODE.P= Plotter (DoVi/HDR10/HLG/SDR)
7) MODE.S= Screenshots & Player
8) MODE.E= Encoders (video and audio)
9) MODE.M= MORE

Choice? [1,2,3,4,5,6,7,8,9]?6

=========================
- SELECT A WORKFLOW -
=========================

1) Workflow.1= Measure Letterbox
2) Workflow.2= Measure MadVR HDR (can batch)
3) Workflow.3= Measure DoVi Level 1 (can batch)
4) Workflow.4= Measure DoVi Level 1,2,3,8 (can batch)
5) Workflow.5= Measure DoVi Level 4,5,6
6) Workflow.6= Measure HDR10plus
7) Workflow.7= Measure Bitrate
8) Workflow.8= Measure Audio waveform
9) Workflow.9= Go back to Main Menu

Choice? [1,2,3,4,5,6,7,8,9]?1


=====================
- MEASURE LETTERBOX -
=====================

------------------------------------------------
-- this script measure a video file letterbox
-- Auto mode might not be 100 accurate
-- Tip: zoom 400 in avspmod
------------------------------------------------

Drag and drop a video file and press enter...
E:\Mulan.mkv
Manual or Auto measurement? (manual=m auto=a default=m) and press enter...
a
Measuring the letterbox...
Le fichier spécifié est introuvable.
Le fichier spécifié est introuvable.
Le fichier spécifié est introuvable.
Le fichier spécifié est introuvable.

Measurements(this may not be accurate):
left border:
right border:
top border:
bottom border:

Deleting TEMP folder...
done, press enter to measure another video !
Appuyez sur une touche pour continuer...

[Kuler087]

I dont know but nothing changed in that workflow from 3.0.3 to 3.0.4

_____ __ ___ _____ _ _
| __ \ \ \ / (_) / ____| (_) | |
| | | | __\ \ / / _ | (___ ___ _ __ _ _ __ | |_ ___
| | | |/ _ \ \/ / | | \___ \ / __| '__| | '_ \| __/ __|
| |__| | (_) \ / | | ____) | (__| | | | |_) | |_\__ \
|_____/ \___/ \/ |_| |_____/ \___|_| |_| .__/ \__|___/
-Author: RESET_9999--------------------------|__|-----------



1) MODE.I= INJECT / EDIT / EXTRACT / INFO / VALIDATE
2) MODE.F= VERIFY SYNC / REMOVER / TRANSFER LEVELS
3) MODE.H= DoVi MAKER from HDR10 (Dolby Algo or MadVR or HDR10+)
4) MODE.7= DoVi Profile 7 Input (MKV/BDMV)
5) MODE.B= DoVi MKV Batch Muxer
6) MODE.P= Plotter (DoVi/HDR10/HLG/SDR)
7) MODE.S= Screenshots & Player
8) MODE.E= Encoders (video and audio)
9) MODE.M= MORE

Choice? [1,2,3,4,5,6,7,8,9]?6

=========================
- SELECT A WORKFLOW -
=========================

1) Workflow.1= Measure Letterbox
2) Workflow.2= Measure MadVR HDR (can batch)
3) Workflow.3= Measure DoVi Level 1 (can batch)
4) Workflow.4= Measure DoVi Level 1,2,3,8 (can batch)
5) Workflow.5= Measure DoVi Level 4,5,6
6) Workflow.6= Measure HDR10plus
7) Workflow.7= Measure Bitrate
8) Workflow.8= Measure Audio waveform
9) Workflow.9= Go back to Main Menu

Choice? [1,2,3,4,5,6,7,8,9]?1


=====================
- MEASURE LETTERBOX -
=====================

------------------------------------------------
-- this script measure a video file letterbox
-- Auto mode might not be 100 accurate
-- Tip: zoom 400 in avspmod
------------------------------------------------

Drag and drop a video file and press enter...
D:\Alien.Romulus.2024.HDR12.mkv
Manual or Auto measurement? (manual=m auto=a default=m) and press enter...
a
Measuring the letterbox...

Measurements(this may not be accurate):
left border: 0
right border: 0
top border: 276
bottom border: 276

Deleting TEMP folder...
done, press enter to measure another video !

[Atari1971]

Good evening.

I have just transcribed the film "spider-man" HDR10 into Dolby Vision. I transcoded the mkv file to prores. I opened it with Davinci Resolve and analyzed in Dolby and exported to xml. I then use dovi_script to generate the dolby vision.

I get this flat outline. Is there something I did wrong:scared:? :thanks:

[DMD]

Maybe of create the scenes in DaVinci, in the Timeline section.

https://i.slow.pics/BeiV9tqP.webp

[Atari1971]

yes I will try

[lemaireus]

I'm new to Dolby Vision. I would much appreciate it if I can get help with the following, presumably elementary questions.

My target is to preserve my UHD blu ray collection in a relatively compact format, in the mkv container, while preserving the Dolby Vision parameters as close to the UHD BD as possible. Device playback compatibility is not a concern.

1. Does the Dolby Vision enhancement layer (EL) also contain the RPU? If yes, then would it make sense for me to extract only the EL, leaving the RPU alone, and injecting that EL back into the transcoded video?
2. If the Dolby Vision enhancement layer (EL) does not contain the RPU, does it make sense for me to extract both the RPU and the EL and then inject them both into the encoded video?
3. If my concern is quality and not compatibility, then should I keep DV profile 7.6 without conversion or do I gain something by converting the RPU to profile 8.1?

I have scoured through the forums but have not run into posts that answer these questions specifically. The most helpful videos on the subject on YouTube are, of course, RESET_9999's (Kuler's YouTube avatar) and I have seen those. For example, https://youtu.be/iKUf2GpqoeU?si=ZmsoHSkFbK82Jdib has been very helpful in clarifying the terminology and the functions of the EL. Being new to DV, however, I am looking for a specific answer to the question:

Should I extract and inject both RPU and EL, or only one of those?

[Incidentally, in my PC-and-Denon AVR-centred home theatre setup with LG C4 OLED display, I use MPC-HC for playback, using its MPC video renderer, which passes through Dolby Vision metadata to the display.]

[Kuler087]

1. Does the Dolby Vision enhancement layer (EL) also contain the RPU? If yes, then would it make sense for me to extract only the EL, leaving the RPU alone, and injecting that EL back into the transcoded video?
2. If the Dolby Vision enhancement layer (EL) does not contain the RPU, does it make sense for me to extract both the RPU and the EL and then inject them both into the encoded video?
yes the EL contains the RPU dynamic metadata.
If it's MEL you can discard the EL, convert the RPU to P8.1 and inject it.
If it's FEL, you have to bake the EL into the BL and then you can convert the RPU to P8.1 and inject it.

All of this is automated in workflow 8-2-1 and the encoding settings can be configured at lines 140-165.
https://www.youtube.com/watch?v=8BvXqw_cGJE

If my concern is quality and not compatibility, then should I keep DV profile 7.6 without conversion or do I gain something by converting the RPU to profile 8.1?
when you bake fel to P8.1, the DV will be the same (minus 12 bit but your TV is 10bit so it doesn't matter)

I use MPC-HC for playback, using its MPC video renderer, which passes through Dolby Vision metadata to the display
it doesn't pass the DV metadata to the display. It's only useful for profile 5 DV because it can tone map the colorspace to HDR10 but the dynamic metadata are always ignored.
The only players on PC that can process the metadata are the Windows native player and the Energy player. Windows player only supports P8 P5 MP4 DV and lossy audio, while Energy player supports P5 P8 MKV with lossless audio.
Both players do not send metadata to the display; they process the metadata themselves (LLDV, aka player-led) and send a decoded/tone-mapped HDR10 image to the display.

https://apps.microsoft.com/detail/9p9zh5fl1bfk?hl=en-US&gl=US
https://www.youtube.com/watch?v=bXS5I1GlRSM

[lemaireus]

Much, much gratitude, Kuler, for your crystal clear, helpful replies. I shall take a day or so to let the information you have shared sink in, then run through some workflows in accordance with your suggestions, and thereafter share information about the results I get, or any potential issues I run into, here on the forum.

You are not only a treasure trove of information but also so helpful that learning from you is a pleasure. Thank you very, very much.

[Hellboy.]

If it's FEL, you have to bake the EL into the BL and then you can convert the RPU to P8.1 and inject it.

You know if HandBrake do this when convert a movie that have FEL?
Or if anyone who uses HandBrake knows?
Thanks.

[Kuler087]

I'd be very surprised if it did.
It would be easy to verify. Take one of the known movies that FEL restores the 4000nits master and measure the handbrake encode HDR brightness with my script workflow 6-2 and compare the brightness with the original HDR10 baselayer.

example: https://slow.pics/c/mtU0824c

[lemaireus]

All of this is automated in workflow 8-2-1 and the encoding settings can be configured at lines 140-165.
https://www.youtube.com/watch?v=8BvXqw_cGJE

There is no doubt that DoVi scripts is one of most fully featured audio video encoders currently available, and without a doubt the single best application for Dolby Vision. However, if one is encoding three to four movies per day, typing in the settings each time can become time consuming and tedious. I'm sure the GUI will eventually streamline a lot of that work and that there are many alongside me who are waiting for a fully-featured GUI that is currently in the works.

[MPC-HC] doesn't pass the DV metadata to the display. It's only useful for profile 5 DV because it can tone map the colorspace to HDR10 but the dynamic metadata are always ignored.

I'm surprised because MPC-HC claims support for Dolby Vision ["MPCVR also supports Dolby Vision" https://github.com/clsid2/mpc-hc/releases]. It even provides the passthrough option in settings:

https://i.postimg.cc/85zCQLTL/Screenshot-2024-12-03-205735-2.jpg

Checking that passthrough option in MPC-HC does trigger HDR each time I play a DV video, but playing a DV file in MPC-HC does not trigger DV on my LG C4 so your observation is correct. I can only wonder what purpose the setting above might serve.

Energy Media Player seems terrific. Its HDR/DV processing definitely appears better than that of the MPC video renderer. I guess Energy will soon become my default media player once I have figured out all the settings. I have checked out the Energy player only on my HDR-capable (not DV-capable) Samsung monitor attached to my PC, not on the LG TV thus far. Thank you for suggesting this player.

when you bake fel to P8.1, the DV will be the same (minus 12 bit but your TV is 10bit so it doesn't matter)

I would not wish to encode my entire library all over again each time a new set of hardware and software options becomes available. So I am sticking to keeping DV profile 7.6 in my encodes, with the belief that 12-bit TVs might become mainstream at some stage. Also, I suppose it is reasonable to hope that players such as Energy might be able to offer support for profile 7 in the not too distant future, or is that beyond the scope of reverse engineering?

Once again, many thanks!

[Kuler087]

However, if one is encoding three to four movies per day, typing in the settings each time can become time consuming and tedious.
Well if you use different settings for each movie, you can just duplicate the bat file with different settings..

I'm surprised because MPC-HC claims support for Dolby Vision ["MPCVR also supports Dolby Vision" https://github.com/clsid2/mpc-hc/releases]. It even provides the passthrough option in settings:

It's just for Profile 5 decoding as HDR10 passthrough. I have tons of test files to find out if the RPU (dynamic metadata) is used.
https://drive.google.com/drive/u/1/folders/1yAq-jgsb8pYa92PnGZkxyEV0E3VVkhiC

Energy Media Player seems terrific. Its HDR/DV processing definitely appears better than that of the MPC video renderer. I guess Energy will soon become my default media player once I have figured out all the settings. I have checked out the Energy player only on my HDR-capable (not DV-capable) Samsung monitor attached to my PC, not on the LG TV thus far. Thank you for suggesting this player.
it has color issues though(red push with P8 and P7) but the dynamic metadata are processed according to your display edid.

real DV passthrough without certified hardware is technically possible on PC but no one has done it yet.
https://discourse.coreelec.org/t/learning-about-dolby-vision-and-coreelec-development/50998

o I am sticking to keeping DV profile 7.6 in my encodes, with the belief that 12-bit TVs might become mainstream at some stage. Also, I suppose it is reasonable to hope that players such as Energy might be able to offer support for profile 7 in the not too distant future, or is that beyond the scope of reverse engineering?

it does support P7 decoding as P8(like the shield/zidoo/ATV) but as explained in my FEL encoding tutorial, doing that is wrong for all the movies that expand brightness.
You should get the ugoos AM6B+ (with coreELEC) if you want the true DV 12bit FEL experience... CoreELEC can also be installed on the old 2nd gen firestick if you want something cheaper.
https://discourse.coreelec.org/t/ce-ng-dolby-vision-fel-for-dv-licensed-socs-s905x2-s922x-z-s905x4/50953

[lemaireus]

Well if you use different settings for each movie, you can just duplicate the bat file with different settings..

That is something I hadn't thought of; such a neat solution. That will allow me to have as many setting profiles as I might wish to use. Thank you. Nonetheless, for a not overly technologically proficient person such as myself, and one accustomed to working with GUIs (Gordian Knot in 2000s, in the era of DivX and Xvid, and later RipBot264 in 2010s-20s when x264 and x265 superseded earlier codecs) a neatly laid out, efficient GUI will likely remain the comfort food one longs for.

You should get the ugoos AM6B+ (with coreELEC) if you want the true DV 12bit FEL experience...

You are an ocean of information on Dolby Vision, Kuler. I've bookmarked this post for my next round of hardware upgrades. It'll take a while for all that you have to offer to sink into me, and once that happens, I'm sure I'll be able to get a lot more out of my hardware than I have been able to thus far.

Now that DV is pretty much the default HDR option on UHD BDs, I hope one or the other code writers for one of the players makes a DV passthrough option available so that the DV-capable displays actually do the job that they are supposed to. At the moment, there is a lot of activity among software writers about DV but we are still to get to a settled stage at which streamlined, user friendly, fully functional applications are available for DV encoding and playback. DoVi scripts comes across as the most well developed package of the lot and a GUI will certainly round it off as the most comprehensive package. Thank you very much for all the work that you have put in.

[dkangel]

Hello
Can you tell me if it's a big problem and if i have just to modify L5 to correct it?
Thank you

https://image.noelshack.com/minis/2024/49/7/1733650368-sans-titre.png (https://www.noelshack.com/2024-49-7-1733650368-sans-titre.jpg)

[Kuler087]

it's not a big problem but you can modify it if you want.

L5 is used only on the TV's internal player, all the HDMI devices ignore it.

[dkangel]

thanks for your answer, i will correct it in the same time i convert mel to P8
thanks again

[Black Ops]

Is there any way to compare a HDR10 and HDR10+ version of a movie to see if the dynamic metadata is making any difference

Ive generated hdr10+ metadata via resolve and injected it via the script. But im wondering if im seeing a placebo effect when the movie in question has MaxMDL of 1000 which my samsung qn90c uses (Doesnt Use MaxCLL, Only MaxDML). The movie in question is around 600 nits max so well within the 1000+ capability of my TV so im wondering if the TV is doing any tonemapping at all

I can however see a reduction in peak highlight brightness when i watch movies with MAXDML of 4000 nits like pacific rim. The highlights were clearly muted but im not sure if its the case for 1000MaxMDL movies.

Whats the best way, if any, to determine this?

[Kuler087]

You can make the json out of sync and see if brightness varies between the shots.
resync it in workflow 1

[Black Ops]

Apologies, how would i check the shots? Im currently using my firestick to playback each video to spot a difference

[Kuler087]

you play the OOS HDR10plus video and look for brightness variation between the shots. If nothing is visible, it means your TV is not doing any tone mapping.

[en6ads]

Sorry if these questions have been answered before, noob here:
1. Does workflow (3)(1) create a DV 8.1 Cmv4.0 file from HDR10+? The instructions state HDR10, not HDR10+. Workflow (3)(2) appears to be for HDR10+, but says "not recommended"
2. If I convert a HDR10+ movie to DV 8.1 Cmv4.0, does this in any way reduce or alter the picture quality when decoding an encoding?
2. If a movie has BT.2020 color primaries, but 'Display P3' Mastering display color primaries, should I choose BT.2020 or P3?

Edit: I'm trying to decide whether to use Dolby VS10 to dynamically convert HDR10+ only movies (such as Alien, Dawn of the Dead), or use this tool to make a new file that is DV. But if there's any degradation whatsoever, I don't want that.
Thank you.

[Kuler087]

1- Yes 3-1 works for any HDR input: HDR10, HDR10+, HLG, DVP5... 3-2 is not recommended (but a LOT faster) because 3-1 uses the official DV algo and is more accurate.

2- No, The dolby vision metadata generation(using official tools like in 3-1) is non-destructive. All it does is tell your TV about the content brightness.

3- All the movies/TV shows are in a bt2020 container regardless of the mastering monitor. The value you have to match in 3-1 is the mastering display info, so P3 in that case.

I'm trying to decide whether to use Dolby VS10 to dynamically convert HDR10+ only movies (such as Alien, Dawn of the Dead), or use this tool to make a new file that is DV. But if there's any degradation whatsoever, I don't want that.
converting HDR10plus to DV can be destructive because they are both different algos that calculate the metadata differently.

[en6ads]

2- No, The dolby vision metadata generation(using official tools like in 3-1) is non-destructive.

converting HDR10plus to DV can be destructive because they are both different algos that calculate the metadata differently.

Thank you for the quick reply!
I'm a bit confused with the above: So If I convert HDR10+ dynamic metadata to DV using (3-1), that's non-destructive? But if I use Dolby VS10 engine, or whatever method CPM uses, that method of conversion could be destructive?

[Kuler087]

right. 3-1 doesnt care if your input has HDR10plus, it uses the official Dolby CM_Analyze to generate proper metadata.

Using the VS10 engine, do you mean with the CoreElec CPM build that can convert HDR10plus to DV on the fly? yes this can be destructive and it's the same method used in workflow 3-2.
if you mean just a straight HDR10 to DV using VS10 without using the HDR10plus metadata, yes that's even worse.

[en6ads]

Much appreciated, thank you!

Using the VS10 engine, do you mean with the CoreElec CPM build that can convert HDR10plus to DV on the fly? yes this can be destructive and it's the same method used in workflow 3-2.
if you mean just a straight HDR10 to DV using VS10 without using the HDR10plus metadata, yes that's even worse.

Yes, I'm referring to watching HDR10+ only movies [Alien, Dawn of the Dead, etc] on an LG OLED TV with dynamic metadata included using an Ugoos AMB6+ with CoreElec.

Is the best way to create a new DV file using (3-1) workflow to ensure dynamic metadata is used? I would prefer the best quality conversion that is possible.

Thanks again for creating these scripts!

[Kuler087]

The best quality possible is with official Dolby tools. So workflow 3-1 but it can be VERY slow so you might want to look into Davinci Resolve (same official DV algo as 3-1)
https://www.youtube.com/watch?v=FVSh3oGqfXY

[en6ads]

The best quality possible is with official Dolby tools. So workflow 3-1 but it can be VERY slow so you might want to look into Davinci Resolve (same official DV algo as 3-1)
https://www.youtube.com/watch?v=FVSh3oGqfXY

I just completed Alien Director's Cut (1979) using workflow 3-1 and it took 4 hours (I have AMD, no cuda cores).

Amazing!

I went from:
51,249,835,141 bytes; "SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible"

to:
51,201,998,479 bytes; "Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile A, HDR10+ Profile A compatible"

The file is about 45MB smaller, and it is now profile 8.1 with the HDR10+ still in there.

This is way better than using CPM dynamic conversion.

There's only a few HDR10+ with no DV movies. I only own 2, so will be doing the same to the other - Dawn of the Dead (1978).

I have no need for CPM now, however I do like to look at the dynamic data, levels etc in the skin that the regular dailies skin does not provide.

Thanks again for your work in creating these scripts!

[Kuler087]

using workflow 3-1 and it took 4 hours (I have AMD, no cuda cores).
That's surprising, especially with AMD hardware but you will notice that some movies take a lot more time. Speed is really inconsistent with CM-Analyze(3-1) on Windows.

For reference, the processing speed is always the same in Resolve and it takes about 1h30 per movie on my end (RTX3070 + i9 13900ks).
I only use 3-1 when I batch-generate DV for Amazon TV shows.

[en6ads]

That's surprising, especially with AMD hardware but you will notice that some movies take a lot more time. Speed is really inconsistent with CM-Analyze(3-1) on Windows.

Dawn of the Dead (1978) Cannes Cut, 200805 frames, (3-1) took 2hr50:48 total time. That's on a 7840HS @ 55w.

[en6ads]

Feature request:

FEL to baked profile 8.1 as an option in workflow (4). I know this can be done using workflow 8-2-1 and then multiplex back with MKVToolNix.

I would love to see a fully auto option - so you provide the P7FEL file in option (4), and it returns a FEL baked P8.1 file many hours later with no additional extra steps, without having to open MKVToolNix.

Perhaps even a batch option to scan your library for FEL files, then automatically create FEL baked P8.1 for each [this would take weeks, but in serverland, who cares?]. Wow, this would negate the need for a CoreElec Ugoos FEL player. Then we can go back to our Shields ;).

Love your work, thank you.

[Kuler087]

8-2-1 can already mux the encoded file without any extra step (unless you're using a very old version of the script ?).
2-7 can quickly scan your library and display all the info you need

I'll think about adding batch mode in 8-2-1...

Then we can go back to our Shields
Shield has color issues with P8 P7 DV. you should encode to P5 with 8-2-6 (support FEL baking too)