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

[Kuler087]

Drag-and-drop batch scripts designed for effortless management of HDR/Dolby Vision files,
ensuring a user-friendly and easy-to-use experience.

https://github.com/R3S3t9999/DoVi_Scripts

Installation tutorial for newbies: https://youtu.be/wb9191cExF8

https://i.ibb.co/Z6scm8fx/Do-Vi-Scripts-animated-gif.gif
https://images2.imgbox.com/bc/b7/cx8CGyxP_o.png

MUXING BEHAVIOR AND SCRIPT FOLDER:

The script's behavior for muxing (MKV, MP4, or TS) is determined by the filename of the .bat file. If you decide to remove these tags, the default muxing mode will be MKV but muxing can be completely disabled at line 55

I advise against using the script on your OS drive as it may result in certain functions being disabled or not functioning correctly. Furthermore, remuxing large files will slowdown the Windows operating system.

The script default settings can be edited if you open the bat file in Notepad++ (https://notepad-plus-plus.org/)

To ensure optimal performance, make sure that your path and script folder (containing both tools and the .bat file) adhere to the following format: It's preferable not to include special characters or spaces in the path.
DO NOT LAUNCH THE BAT FILE WITH ADMIN RIGHTS, DRAG AND DROP WILL NOT WORK!

https://i.ibb.co/p1rp5K0/Capture-d-cran-2024-02-13-084631.jpg

SCRIPTS MODES

MODE.I (1) =
INJECTOR/INJECTOR/EDITOR/EXTRACTOR


Can do all the extracting, parsing, injecting, and editing of two input sources. (P8/P5/P7 injection/edition)
Can get info(fel or mel, profile, l1/l2/l5) from any DV source as well as extract and edit any source.
One static HDR base layer input and one dynamic HDR file input (MKV/MP4/HEVC/TS/M2TS/RPU/XML/JSON HDR10+).
Can easily resynchronize RPUs, edit parameters like L5/L6, convert the profile to P8. (P8 hybrid maker)
see P8 hybrid maker tutorial: https://www.youtube.com/watch?v=hVWZpat34oc
see Resolve DV generation tutorial: https://www.youtube.com/watch?v=FVSh3oGqfXY
Can Resync HDR10plus and Dolby Vision (any profile)
Can use external json files and batch process files
Can validate metadata with Official Dolby Metafier
Can convert RPU to XML
Can disable DV tone mapping (reset L1 L2 L8)
can batch remove cmv4.0

EXAMPLES:
Edit a single file (https://s10.gifyu.com/images/S5l93.gif)
inject HDR10plus and DV in one shot (json must be in sync) (https://s12.gifyu.com/images/S5l9H.gif)
json edit (https://s12.gifyu.com/images/S5l9x.gif)
Batch edit (https://s12.gifyu.com/images/S5l9K.gif)
batch inject (https://s12.gifyu.com/images/S5l9N.gif)



MODE.F (2) =
REMOVER/TRANSFER/VERIFY



Can verify the dynamic metadata (DV/HDR10plus) synchronization with the base layer.
see tutorial: https://www.youtube.com/watch?v=lIO_ZfT-LnY
Can overwrite/remove Level 2 trims
can transfer any metadata level to another rpu
can transfer scene cuts from one rpu to another
Can remove hdr10plus or DV
Can export EDL timecodes for Resolve
Can export Level 5 aspect ratio config file
Can find scene cut difference between two sources.
Can batch info your whole library



MODE.H (3) =
GENERATOR


Can convert any HDR10plus/HDR10/HLG source to shot-by-shot or frame-by-frame DoVi. CMV4.0 metadata, no fake static crap
Official Dolby cm_analyze.exe (best) or hdr10plus to dv or madvr to dv
see batch generate DV tutorial: https://www.youtube.com/watch?v=jBqbG5XM54g
can use an external shot list
Cmv4.0 L1 analysis can be tuned (line 95)
Support DV-P5 / HDR10 / HLG input
can batch generate DV with external files for L5/ MD, and original shot list
Shot list source is selected in this order:

1- any external file with the same filename as the input (rpu, json, text)
2- internal RPU (in case of original rpu that has no shot, add ''IGNORERPU'' in the input filename.)
3- internal hdr10plus
4- if no dynamic metadata is found, it uses madvr to generate a shot list

MODE.7 (4) =
PROFILE 7


Can process any Profile 7 source(BD or Rip) to Single-layer Profile 8 or Profile 7 single-track dual-layers.

see tutorial: https://www.youtube.com/watch?v=sBUL2gjhqEE

MODE.B (5) =
BATCH MUXER


Can batch mux any DV source to TS or MP4

MKV/MP4 to TS

MKV/TS to MP4


MODE.P (6) =
PLOTTER


Can batch plot DoVi Level 1,2,3,4,5,6,8 and hdr10, hdr10plus, HLG, P5BL, video bitrate and audio channels

EXAMPLES (https://drive.google.com/drive/u/1/folders/154fBNllwOHL4Lckc7wDV8QKFJwFxnDt-)
see tutorial: https://www.youtube.com/watch?v=KHXvjtHNdB8

MODE.S (7) =
SCREENSHOTS


can export 16bits RGB real HDR screenshots (FEL P5 HDR10 HLG SDR) fully automated frame accurate or manual modes
can export SDR screenshots from a Dolby Vision 100nits trim pass.
see tutorial: https://www.youtube.com/watch?v=ElJ1KvQMgzE
can play FEL + BL or Profile 5 DV in HDR10 or SDR with madVR+MPC (if your pc can handle it)
can export HDR heatmap and gamut visualization (FEL P5 HDR10 HLG SDR)
can tonemap to SDR or HDR PQ (default = PQ)

EXAMPLES (https://docs.google.com/spreadsheets/d/15i0a84uiBtWiHZ5CXZZ7wygLFXwYOd84/edit?gid=1226038728#gid=1226038728)

frame-accurate screenshot maker tutorial: https://www.youtube.com/watch?v=SA-i1tZssIo
MANUAL SCREENSHOT EXAMPLE (https://s10.gifyu.com/images/S5l9w.gif)
Can create DV metadata or FEL video comparisons like this:
Metadata: https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf
FEL: https://drive.google.com/drive/u/0/folders/1FS42T95TOSpoy4xtwUBIQmziCe_R_IKe

MODE.E (8) =
VIDEO/AUDIO ENCODERS


can convert audio (DDP 7.1 / Add silent or encoded core to TrueHD)
see tutorial (convert to ddp): https://www.youtube.com/watch?v=m5_Bt2yGPhE
see tutorial (add core): https://www.youtube.com/watch?v=X8CImPBh_DI
can encode bake fel to HDR10/P8 with dovibaker+x265 or NVenc
see tutorial: https://www.youtube.com/watch?v=8BvXqw_cGJE
can encode any HDR10/HLG/FELP7/P5 source to HDR or SDR (x265 or NVenc or prores)
can encode DV to SDR using official Level-2 100nits trim pass (Official Dolby cm_offline.exe)
can encode P7/P8 to profile 5 DV (requires DEE.exe)
can encode to profile 5 DV (requires DEE.exe)
can encode to profile 7 DV MEL or FEL without mapping or 600/1000nits mapping for the BL(requires DEE.exe)



MODE.M (9) =
MIXED


Can fix video framerate bitstream, color range
Can automatically find frame difference between two sources
can find bd playlist
can make 5 min samples. timestamp configurable at line: 109
can quickly find a video framecount (useful when creating a shotlist in 3-1)
Can tonemap pgs subtitles to different brightness
can edit HDR10 metadata


DIRECT MODE

drag and drop a file on the bat file and it will use workflow 1
the bat file can be associated with any video/rpu file.



L5 active area and cropping:

if the base layer is 16:9 (no black bars, fullscreen): set L5 to 0

if the base layer is 16:9 but has black bars: measure the BL letterbox and adjust L5 accordingly.

if the base layer is cropped set L5 to 0


Example 1:

input= 3840x2160p with active area of 2.40 (16:9 with black bars)

L5 offsets= Left:0 Right:0 Top:280 Bottom:280

Example 2:

input= 3840x2160p with active area of 1.78 (16:9 no black bars)

L5 offsets= Left:0 Right:0 Top:0 Bottom:0

Example 3:

input= 3840x1600p (cropped)

L5 offsets= Left:0 Right:0 Top:0 Bottom:0

Downscaling and upscaling:

divide or double the L5 values.

Example:
input 3840x2160 with L5 0,0,280,280
output 1920x1080 with L5 0,0,140,140

Input filename keywords that override the script's main settings:


DONTUPSCALE : Keep original resolution in 7-2
KEEPAUDIO : Keep all the audio
DONTMUX : Disable muxing
IGNORERPU : Ignore internal rpu for shot list in 3-1
REMOVECMV4 : Force CMV4.0 removal in 1-1
KEEPPRORES : Keep prores file
FORCESDR : Force SDR tonemapping in 7-1 7-2
KEEPTRIMS : keep trims in XML injection for 1-1 and 3-1
KEEP1000 : keep 1000nits trims in XML injection for 1-1 and 3-1
KEEP600 : keep 600nits trims in XML injection for 1-1 and 3-1
JUSTINJECT : Inject without changing the DV profile in 1-1
FORCEHDR10PLUS: force hdr10plus scene cut extract when input has dv for workflow 2-3

[guest]

Are you affiliated with RESET ??

'Cause this is straight off his Github page ??

Great set of tools, this !!!!

[Kuler087]

Yes, I'm RESET_9999 :)

[speedy]

@RESET, do you have access to a S922X-J chipset device (Ugoos AM6B+) and/or have any intention of testing one?

[Kuler087]

No, I use the Sony x800m2 for FEL playback.
The new CoreElec build for the Ugoos looks interesting though. I will let other people test FEL playback a bit more but if it's really 100% stable, I might get one.

[guest]

OK, Reset,

Here's that error I mentioned in the email.

I'm using 8-2-1, and it gets thru most of the process then this:-

libavutil 58. 36.100 / 58. 36.100
libavcodec 60. 36.100 / 60. 36.100
libavformat 60. 20.100 / 60. 20.100
libavdevice 60. 4.100 / 60. 4.100
libavfilter 9. 16.100 / 9. 16.100
libswscale 7. 6.100 / 7. 6.100
libswresample 4. 13.100 / 4. 13.100
libpostproc 57. 4.100 / 57. 4.100
Unrecognized option 'vbsf'.
Error splitting the argument list: Option not found
Error: No frames parsed!
Error: No RPU found

D:\Dovi_Encodes_MP4>"D:\DoVi_Scripts\tools\NVEncC\NVEncC64.exe" --vbr 50000 --codec h265 --multipass 2pass-full --preset P7 --output-depth 10 --profile main10 --max-bitrate 160000 --vbv-bufsize 160000 --colormatrix bt2020nc
--colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "0,0" --dolby-vision-profile 8.1
--dolby-vision-rpu "D:\Dovi_Temp_MP4\temp.folder49\P8.RPU.bin" -i "D:\Dovi_Temp_MP4\temp.folder49\script.avs" -o "D:\Dovi_Encodes_MP4\removed file name.S01.E01.2010.2160p.HDR.UHD.BluRay.DD5.1.x265-10bit-HDS-001_DV_encoded.hevc"
-------------------------------------------------------------------------------------------------------------------
D:\Dovi_Encodes_MP4\removed file name.S01.E01.2010.2160p.HDR.UHD.BluRay.DD5.1.x265-10bit-HDS-001_DV_encoded.hevc
-------------------------------------------------------------------------------------------------------------------
Failed to open dovi rpu "D:\Dovi_Temp_MP4\temp.folder49\P8.RPU.bin".
Failed to open input file.

D:\Dovi_Encodes_MP4>echo off & goto :end

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?

This is a 10 minute chunk that I just converted to DV, and I thought I'd try 8-2-1.

Is it simply something I have missed installing, etc, or ??

I'm running an RTX 3050 GPU, BTW.

[Kuler087]

it looks like ffmpeg didnt like the ''vbsf'' parameter. Are you using the version included in the pack or your own version?

[guest]

It looks like the script thinks your input has DV but it doesn't?
input mediainfo or a sample please

converted file info (input):-

Format profile : Main 10@L6.1@High
HDR format : Dolby Vision, Version 1.0, Profile 8.0, dvhe.08.06, BL+RPU / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision

original file info:-

Format profile : Main 10@L6.1@High
HDR format : SMPTE ST 2086, HDR10 compatible

Like I said, I had just converted it to DV with 3-1.

[Kuler087]

sorry i edited my original response after realizing that the problem was a parameter in ffmpeg.

it looks like -vbsf is now deprecated and replaced by -bsf:v

either use the version in the tools pack or wait for the script's next version.

[guest]

sorry i edited my original response after realizing that the problem was a parameter in ffmpeg.

it looks like -vbsf is now deprecated and replaced by -bsf:v

either use the version in the tools pack or wait for the script's next version.

Interesting you mention that, 'cause that is what Google found :)

Cheers.

Update:- I changed it back to the version in the tools pack, and it looked like a different process, and NO errors...I think it was using NVencC, but MediaInfo doesn't show anything about it.

Update #2:-So I took a chance and changed all the -vbsf entries to -bsf:v, and using the latest FFmpeg, I didn't get any errors, so hopefully the process & encodes will be good to go.

Thanks

[Atlantis]

Please could someone explain for us casual users the difference between this and DDVT Tool? Do they do the same thing?

[guest]

Please could someone explain for us casual users the difference between this and DDVT Tool? Do they do the same thing?

In my humble opinion, DDVT does do the same thing, sort of.

I think it is a little harder to use the scripts, needing a cmd prompt, and copying the paths of the script & the file you want to process.

DoVi_Scripts is just a multi option menu, and you just choose the functions menu number, then simply drag the file you want to process, then there may or may not be a few more option you need to choose, then basically it does the rest itself.

But it also does a LOT of other conversions, etc, etc.

Makes a lot of other apps look pretty basic and lacking, in comparison.

It's a little involved to initially set it up, but then you're set.

[DaMacFunkin]

Hi, Updated to your latest pack, I am trying HDR to HDR DoviBake and I get this error (see screenshot), yet the file is present, can you advise please?

[Kuler087]

Does the FEL script work when you play it avspmod? Do you have an Nvidia GPU ?

[DaMacFunkin]

Hi, yes I have a Nvidia GPU that’s why I edited the config to use this.
Not sure what you mean by avspmod, please explain,

I encode HDR with Nvenc and Staxrip all the time so I’m not sure what is wrong?

[DaMacFunkin]

Hi, yes I have a Nvidia GPU that’s why I edited the config to use this.
Not sure what you mean by avspmod, please explain,

I encode HDR with Nvenc and Staxrip all the time so I’m not sure what is wrong?

Just tried to play the AB’s file with avspmod and it says invalid argument, the avs does play with media player classic, how do I fix this please?

[Kuler087]

I mean have you checked if the dovi_baker script works in avspmod?
Go into the temp folder and try to open the Avisynth script or create a new script with workflow 7-1 (manual mode)

Also, any error in the dovi_scripts window?

https://i.ibb.co/qxvYdVW/Capture-d-cran-2024-02-18-113730.png

[Kuler087]

Just tried to play the AB’s file with avspmod and it says invalid argument, the avs does play with media player classic, how do I fix this please?

Did you install avisynthplus?? if yes maybe try to reinstall it:
https://github.com/AviSynth/AviSynthPlus/releases/download/v3.7.3/AviSynthPlus_3.7.3_20230715.exe

[DaMacFunkin]

Did you install avisynthplus?? if yes maybe try to reinstall it:
https://github.com/AviSynth/AviSynthPlus/releases/download/v3.7.3/AviSynthPlus_3.7.3_20230715.exe
Hi, I uninstalled my old version of Avisynth and installed this one, I feel like I've spent all day on it, but now all of a sudden it is encoding, not very fast @ 9fps on --quality --vbr --2pass-full.
Has anybody been able to use --lookahead32 and --vbr-quality 19 with Dovibaker and Nvenc instead of 2 pass??

Thank you.

[guest]

Hi, I uninstalled my old version of Avisynth and installed this one, I feel like I've spent all day on it, but now all of a sudden it is encoding, not very fast @ 9fps on --quality --vbr --2pass-full.
Has anybody been able to use --lookahead32 and --vbr-quality 19 with Dovibaker and Nvenc instead of 2 pass??

Thank you.

AFAIK, you should be able to edit the NVenc_HDR_settings.bat (found in the Tools folder) to your hearts content.

I made a couple of changes to my liking the other day.

This may also be handy, to some:-

https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#nvencc-option-list-

https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#nvencc-option-list-

[DaMacFunkin]

Hi this completed and I'm happy with the results (Thank you Kuler087 (Reset)), also it took less than 4 hours so not too bad, I will try with the lookahead options next time I have a title that needs baking. Thank you.

[guest]

A few questions....

I am of course still learning this, and I have found a couple of things that I can't figure out.

1) When converting say a .thd, when the process if done, it's in an .mkv container, open it in MediaInfo, it's only the converted audio.
So it basically needs to be demuxed, or maybe renamed....

2) I tried to convert a Profile 5 (only) movie, with option 8-2-1, and it states that the P5 will be injected as a P8.1, these rpu's are in the temp folder (until they're not), so I copied them to play with later (yet to do that), but the processed file is a .hevc, no audio, no sub's, just the HDR10 conversion..I guess now I need to run it thru 3-1 to create a hybrid ???

3) Is there a way to save the temp folder, just in case there's something that might be needed ??

4) Also, if there are some temp or processed files from a previous job still present, and another job is started, and you don't notice, when it's almost completed, it states there are some same named files, and the process stops :( Auto renaming would be handy.

5) Also, you use FFMS2 as the decoder, is there a way to use some other decoder, eg:- L-Smash, DGindex, etc ?

6) I acquired DEE for another purpose, so I tried to map that, but it wasn't happy.

I think that's it, for now, sorry.

Cheers

[Kuler087]

1- Yes, EC3 track are encoded to an mkv container in order to preserve any delay present in input.

2- Encoder workflows don't mux by design. If you just mediainfo the hevc file, it won't show any DV info. You have to mux to mkv/ts/mp4 and then the DV flag will be present.

3- No but I could add the option in the next version

4- I've never seen that? if you start a workflow and the same temp folder already exist, it's automatically deleted before running the workflow.

5- I never had issue with ffms2 so I have no reason to use other indexers.

6- I don't like DEE... I wont touch those workflows.

[guest]

Thanks for the comments/feedback, Reset :) (replies in red)

1- Yes, EC3 track are encoded to an mkv container in order to preserve any delay present in input.
I knew there'd be a good reason.

2- Encoder workflows don't mux by design. If you just mediainfo the hevc file, it won't show any DV info. You have to mux to mkv/ts/mp4 and then the DV flag will be present.
Yep, that's pretty much what I've done.

3- No but I could add the option in the next version
I think if it was a Yes & No option in the script.

4- I've never seen that? if you start a workflow and the same temp folder already exist, it's automatically deleted before running the workflow.
Well, tbh, I don't really know what the problem is, but I've had it happen a few times when it's almost complete, it warns of an existing file, somewhere, and stops, I have generally either renamed or deleted similarly name files & folders.

5- I never had issue with ffms2 so I have no reason to use other indexers.
Had to ask, I haven't really got a problem with FFMS2. As you can see in my sig, I use RipBot264, and the dev of that is deadset against FFMS2, as he believes it drops too many frames, I can however force it to use FFMS2, (because it use to, before he found L-Smash) and have not had any issues.

6- I don't like DEE... I wont touch those workflows.
Well, I just wanted to try it, (because I had it) but if it's subpar, I actually read that somewhere else, too.

[Kuler087]

Had to ask, I haven't really got a problem with FFMS2. As you can see in my sig, I use RipBot264, and the dev of that is deadset against FFMS2, as he believes it drops too many frames, I can however force it to use FFMS2, (because it use to, before he found L-Smash) and have not had any issues.

Yes, I've heard of this issue with one version years ago but in my experience, I never had any dropped/dup frames with ffms2 and I encode about 3 movies per week and always verify them with workflow 7-2

[guest]

Hi Reset,

I have come across a dilemma (for me, that is), I have some video's (LOTR series), and they are "loaded" with DV P8.1, HDR10 & HDR10+.

My question is, I want to edit certain stuff out of each clip (eg:- the intro, previously on, and maybe end credits), would it better to extract the rpu before the editing,
and can the original unedited rpu inject properly ?? (I don't know how rpu's work)

OR just do the edits, and process it as a "new" hybrid ??

More info:- I just did a quick edit on a sample of this, and after running it thru RipBit264, it loses both the DV & HDR10+ info :(.
So it will need something injected afterwards, maybe easier just to run a Hybrid conversion.

It shouldn't matter if the HDR10+ info has gone, when you get the DV info back...correct ??

Even more info_:- Just did a quick Hybrid on the above sample, and it gets DV back, but only P8.0 (original was P8.1), (can you add a P8.1 option ??) also, I converted the AAC track to FLAC....DoVi_Scripts (or something it uses, I know you mention tsmuxer) doesn't like FLAC, there was no audio track, just video & sub's.

Might extract the rpu from the unedited sample, and see what happens trying to inject it...worth a shot.

Didn't work, got a lot of errors, this one was the first of many Error: expected ident at line 6 column 15

[Kuler087]

Hi Reset,

I have come across a dilemma (for me, that is), I have some video's (LOTR series), and they are "loaded" with DV P8.1, HDR10 & HDR10+.

My question is, I want to edit certain stuff out of each clip (eg:- the intro, previously on, and maybe end credits), would it better to extract the rpu before the editing,
and can the original unedited rpu inject properly ?? (I don't know how rpu's work)

OR just do the edits, and process it as a "new" hybrid ??



you can trim with mkvtoolnix or whatever you prefer. Just make sure your RPU start with a scene cut(0) after cutting.
see this video if you don't understand how to verify your RPU scene cuts: https://www.youtube.com/watch?v=lIO_ZfT-LnY



More info:- I just did a quick edit on a sample of this, and after running it thru RipBit264, it loses both the DV & HDR10+ info :(.
So it will need something injected afterwards, maybe easier just to run a Hybrid conversion.

It shouldn't matter if the HDR10+ info has gone, when you get the DV info back...correct ??
Even more info_:- Just did a quick Hybrid on the above sample, and it gets DV back, but only P8.0 (original was P8.1), (can you add a P8.1 option ??)

I don't know but the script cannot change that. so either your file has a problem or more likely, mediainfo is confused about your file.

also, I converted the AAC track to FLAC....DoVi_Scripts (or something it uses, I know you mention tsmuxer) doesn't like FLAC, there was no audio track, just video & sub's.



The script can only convert lossless audio to flac or pcm

Might extract the rpu from the unedited sample, and see what happens trying to inject it...worth a shot.

Didn't work, got a lot of errors, this one was the first of many[

please always post the complete log of the workflow and not just part of it but it sounds like you miss answered one of the user input question.

[guest]

you can trim with mkvtoolnix or whatever you prefer. Just make sure your RPU start with a scene cut(0) after cutting.
see this video if you don't understand how to verify your RPU scene cuts: https://www.youtube.com/watch?v=lIO_ZfT-LnY

I'll definitely check out the YT clip, I'm not sure if the way RipBot264 cuts video's, etc, could be a problem.

I don't know but the script cannot change that. so either your file has a problem or more likely, mediainfo is confused about your file.

I agree, MediaInfo can get stuff mixed up, it actually can't display codec info of a video that has been encoded with NVEnc.

The script can only convert lossless audio to flac or pcm

I have done a Hybrid run on a couple of clips that has FLAC, and it doesn't survive the process.

please always post the complete log of the workflow and not just part of it but it sounds like you miss answered one of the user input question.

Understood, I know the more info the better the diagnosis, I just need to figure out how to get the log, but I'll find it.

But yeah, I'm probably missing a lot of things.

----------------------------------------------------------------------------

I know that I have only been using this for a couple of weeks, and it just keeps amazing me what it can do :)

I know I'll have more questions, but I'll try not to bother you too much.

But whatever info you post here, will help others that want to use this.

Thanks again.

Cheers

[Kuler087]

I have done a Hybrid run on a couple of clips that has FLAC, and it doesn't survive the process.


Understood, I know the more info the better the diagnosis, I just need to figure out how to get the log, but I'll find it.

But yeah, I'm probably missing a lot of things.
s


You just copy the text from the window like this: https://justpaste.it/ejshe

this is a FLAC mkv input btw

[guest]

Me again,
Now testing with 2.0.2...some nice changes & additions :).

So first off, I have been using the mp4.bat, as that will play on my LG TV.
Then, earlier today, I grabbed the latest beta, which in only mkv, and one of the first things I noticed in 3-1 was this :-

------------------------------------------
Input tracks info:

index=1
codec_name=truehd
channel_layout=7.1
TAG:language=eng
index=2
codec_name=ac3
channel_layout=5.1(side)
TAG:language=eng
------------------------------------------

Do you want to convert the audio to DDP? (y or n default=n) if input is 7.1, a 2nd window will popup, DO NOT CLOSE IT

The mp4.bat doesn't seem to have this option, is that by design ??

-----------------------------------------------------------------------------

So anyway, I processed a short HD10+ clip thru 2.0.3, and of course got an .mkv.

And here's the MediaInfo video data on that conversion:-

MediaInfo data from DoVi_Scripts 2.0.3 BETA mkv:-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile A, HDR10+ Profile A compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 10 min 0 s
Bit rate : 43.9 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.221
Stream size : 3.07 GiB (87%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 737 cd/m2
Maximum Frame-Average Light Level : 130 cd/m2

So then I ran the above mkv thru the mp4 batcher, (5) in 2.0.1. mp4.bat, and got this:-

MediaInfo data from DoVi_Scripts 2.0.1 mp4:-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, Profile 8.0, dvhe.08.06, BL+RPU / SMPTE ST 2094 App 4, Version HDR10+ Profile A, HDR10+ Profile A compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 10 min 0 s
Bit rate : 43.9 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.221
Stream size : 3.07 GiB (86%)
Default : Yes
Alternate group : 1
Encoded date : 2024-02-22 04:35:46 UTC
Tagged date : 2024-02-22 04:36:39 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 737 cd/m2
Maximum Frame-Average Light Level : 130 cd/m2
Codec configuration box : hvcC+dvcC

[Kuler087]

probably because the script, by default use the very old mp4muxer which doesn't have a parameter to set the BL ID. Change the script MP4 version to new and mediainfo should report 8.1

:: choose the mp4muxer version for (1-1)(2-1)(3-1)(4-2) (OLD or NEW default = OLD) OLD works on (2018/2017) LG TVS but Itunes P8 hybrid wont work if you dont fix the bitstream framerate first.
set mp4_version=OLD

And the mp4 version always encodes DDP tracks unless you disable it in the settings.


:: you can completely disable ddp encoding for the all the workflows (YES or NO default = YES)
set encode_DDP=YES

[guest]

probably because the script, by default use the very old mp4muxer which doesn't have a parameter to set the BL ID. Change the script MP4 version to new and mediainfo should report 8.1

And the mp4 version always encodes DDP tracks unless you disable it in the settings.

Excellent, I will check this out tomorrow.

Hopefully changing to the newer mp4muxer won't affect the playback on my LG.

Cheers.

[Kuler087]

if it's 2019+ , the new mp4muxer should work.

[guest]

if it's 2019+ , the new mp4muxer should work.

Hmmm, I have a 55SK8500PTA, which I think is mid to late 2018...I guess there's only way to find out.

I'll let you know.

UPDATE:- Well, unfortunately P8.1 won't display DV, only HDR :(, so I guess it'll have to be P8.0 for me, but that's alright.

[benwaggoner]

Hmmm, I have a 55SK8500PTA, which I think is mid to late 2018...I guess there's only way to find out.

I'll let you know.
IIRC and FWIW, that device wouldn't have shipped with DoVi 8.1 support. Did it pick it up in an update?

I was pleasantly startled when my 2017 Z9D magically gained Dolby Vision support several years after I acquired it.

[Kuler087]

I think 2018 is the year they added Profile 8 support. The LG C7 doesn't support it but the C8 does.

[benwaggoner]

I think 2018 is the year they added Profile 8 support. The LG C7 doesn't support it but the C8 does.
News I can use. Thanks!

[guest]

News I can use. Thanks!

So just to be clear, P8.0 or P8.1 works ??

[guest]

Any chance of adding some more audio conversion options ??

eg:- aac to ec3, maybe ac3 to ec3.

[Kuler087]

aac, I'm not sure if it's supported but I think AC3 is supported if you just run a file without lossless audio in 8-1-1
I'll check it out.

[guest]

aac, I'm not sure if it's supported but I think AC3 is supported if you just run a file without lossless audio in 8-1-1
I'll check it out.

Hi,

I can confirm that ac3 is supported, and encodes to EC3. :)

However, as you mentioned, aac is not supported (yet).

no lossless audio found, skipping file.
the script has been completed, press a key to start again...

I would think that with the tools you have in the "tool pack", that this should be able to be done.

It's just a matter of the correct instructions..

Cheers.

PS:-

So I'm clearly missing something here, I just did a quick Hybrid conversion on a clip that had ac3 640kbps audio track, and I was hoping that would be converted to EC3, but it remained as an ac3. (MP4 workflow)

I converted the mp4 back to mkv (MKVToolNix) to demux the ac3 track, then used 8-1-1 to convert to EC3, then remuxed that again with MKVToolNix, then ran it thru #5 (MP4 Muxer), and there it all was.

[DaMacFunkin]

Hi,

Having problems trying to use custom settings in DoVi Baker with NVEnc, the default settings work fine as follows:

E:\Dolby-Vision-Tools>"E:\Dolby-Vision-Tools\tools\NVEncC\NVEncC64.exe" --vbr 50000 --codec h265 --multipass 2pass-full --preset P7 --output-depth 10 --profile main10 --max-bitrate 160000 --vbv-bufsize 160000 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "900,198" --dolby-vision-profile 8.1 --dolby-vision-rpu "E:\Dolby-Vision-Tools\temp.folder49\P8.RPU.bin" -i "E:\Dolby-Vision-Tools\temp.folder49\script.avs" -o "E:\Dolby-Vision-Tools\Total Recall (1990)_encoded.hevc"
--------------------------------------------------------------------------------
E:\Dolby-Vision-Tools\Total Recall (1990)_encoded.hevc
--------------------------------------------------------------------------------
Max B frames are 0 frames.
^^^As stated the above starts to encode fine.

When I copy settings that I use with HDR in Staxrip and edit the NVEnc settings it fails to run the encoder, can anybody advise what DoVi baker doesn't like about the below settings please?

E:\Dolby-Vision-Tools>"E:\Dolby-Vision-Tools\tools\NVEncC\NVEncC64.exe" --avhw --vbr 40000 --codec h265 --preset quality --output-depth 10 --profile main --level 5.1 --qp-init 1 --max-bitrate 40000 --aq --bframes 0 --ref 5 --lookahead 32 --vbr-quality 17 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "900,198" --dolby-vision-profile 8.1 --dolby-vision-rpu "E:\Dolby-Vision-Tools\temp.folder49\P8.RPU.bin" -i "E:\Dolby-Vision-Tools\temp.folder49\script.avs" -o "E:\Dolby-Vision-Tools\Total Recall (1990)_encoded.hevc"
--------------------------------------------------------------------------------
E:\Dolby-Vision-Tools\Total Recall (1990)_encoded.hevc
--------------------------------------------------------------------------------
avcuvid: error opening file "E:\Dolby-Vision-Tools\temp.folder49\script.avs": Invalid data found when processing input
failed to initialize file reader(s).
Failed to open input file.

E:\Dolby-Vision-Tools>echo off & goto :end

Thank you for any help.

[guest]

Hi,

Having problems trying to use custom settings in DoVi Baker with NVEnc, the default settings work fine as follows:

^^^As stated the above starts to encode fine.

When I copy settings that I use with HDR in Staxrip and edit the NVEnc settings it fails to run the encoder, can anybody advise what DoVi baker doesn't like about the below settings please?

Thank you for any help.

I'm pretty new to DoVi_Scripts, but if you're trying to use Staxrip settings, I'd say you're in for a world of pain !!!

I'm pretty sure that all you need to do is edit the NVenc_HDR_settings.bat file in the "tools" folder.

set settings=--vbr 50000 --codec h265 --multipass 2pass-full --preset P7 --output-depth 10 --profile main10 --max-bitrate 160000 --vbv-bufsize 160000 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers

:: do not remove the ''set settings=''

You may only need to use this:- (only guessing)

set settings=--avhw --vbr 40000 --codec h265 --preset quality --output-depth 10 --profile main --level 5.1 --qp-init 1 --max-bitrate 40000 --aq --bframes 0 --ref 5 --lookahead 32 --vbr-quality 17 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers

https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

I have changed a couple fo commands and it's worked, the rest of the settings & commands are controlled elsewhere in the app, and probably look after themselves.

[Kuler087]

Hi,

PS:-

So I'm clearly missing something here, I just did a quick Hybrid conversion on a clip that had ac3 640kbps audio track, and I was hoping that would be converted to EC3, but it remained as an ac3. (MP4 workflow)

I converted the mp4 back to mkv (MKVToolNix) to demux the ac3 track, then used 8-1-1 to convert to EC3, then remuxed that again with MKVToolNix, then ran it thru #5 (MP4 Muxer), and there it all was.

lossy audio conversion is only supported in 8-1-1. For all the other workflows, only lossless audio get converted to EAC3 and I don't think I will change this behavior.
Why do you want to convert ac3 to ec3?

PS: I added AAC support in the latest beta.




When I copy settings that I use with HDR in Staxrip and edit the NVEnc settings it fails to run the encoder, can anybody advise what DoVi baker doesn't like about the below settings please?


No idea, but try to add one custom cmd at a time until you find which one doesn't work.


PS: I found an issue (https://slow.pics/c/z5XCkMkP) when converting Profile 5 to HDR10 or SDR with avisynthplus+libplacebo, I cannot get the color right and only when I use vapoursynth+libplacebo the output is right. So if someone is converting P5 video, he should update to the latest beta right now(update your tools pack too).

I've tried in staxrip and it's exactly the same issue when you use avisynth. Sorry for not noticing earlier, I rarely convert P5 videos.

[guest]

lossy audio conversion is only supported in 8-1-1. For all the other workflows, only lossless audio get converted to EAC3 and I don't think I will change this behavior.
Why do you want to convert ac3 to ec3?

Well, one reason is that some of the series episodes have THD 7.1, and I will convert them to EC 5.1 (my TV/"home theatre" doesn't support thd or 7.1), and I just wanted them all the same....

PS: I added AAC support in the latest beta.

Is this beta mkv or mp4 ?? It's mkv, I just downloaded it, can I change this to mp4 ??
The Beta is 2.0.3, I got that a couple of days ago, or have you changed it since ??


No idea, but try to add one custom cmd at a time until you find which one doesn't work.

PS: I found an issue (https://slow.pics/c/z5XCkMkP) when converting Profile 5 to HDR10 or SDR with avisynthplus+libplacebo, I cannot get the color right and only when I use vapoursynth+libplacebo the output is right. So if someone is converting P5 video, he should update to the latest beta right now(update your tools pack too).

Is there also an update for the tool pack ?? (I actually hope not, it's another 2.6Gb rar), but if so, what has changed ?? maybe a partial update.

I've tried in staxrip and it's exactly the same issue when you use avisynth. Sorry for not noticing earlier, I rarely convert P5 videos.

I actually converted a P5 the other day, got it to P8, but like you mention, the colour is a little off.

Does DoVi_Scripts support Vapoursynth ??? (I haven't seen it anywhere).

Thanks.

[Kuler087]

Is this beta mkv or mp4 ?? It's mkv, I just downloaded it, can I change this to mp4 ??
The Beta is 2.0.3, I got that a couple of days ago, or have you changed it since ??

the scripts are all the same, you can just change the filename to TS or MP4
The last modified date is written in the right corner when you launch the script.

Is there also an update for the tool pack ?? (I actually hope not, it's another 2.6Gb rar), but if so, what has changed ?? maybe a partial update.

add these into your tools folder:
https://drive.google.com/file/d/1Sqc6dMtwZ4IpVTVZTauBXzyWFqzku18x/view?usp=drive_link

Does DoVi_Scripts support Vapoursynth ??? (I haven't seen it anywhere).
it does with the new tools and the latest beta

[Gatorman3385]

The script is crashing when I try to inject a RPU into an existing MKV. I'm not sure how to grab the logs, because it crashes when it starts injecting. Also crashing with latest BETA. Any thoughts on what I should do to track down the error? It must be my latest StaxRip encode. Other files work just fine.

[Kuler087]

you can provide a small sample.

[guest]

The script is crashing when I try to inject a RPU into an existing MKV. I'm not sure how to grab the logs, because it crashes when it starts injecting. Also crashing with latest BETA. Any thoughts on what I should do to track down the error? It must be my latest StaxRip encode. Other files work just fine.

Welcome to this thread :)

I asked about "saving the logs" just the other day, and it's pretty simple, see here for a "how to":-

https://forum.doom9.org/showthread.php?p=1998025#post1998025

I'm actually not too surprised that you're having issues with StaxRip, so many new builds & problem solving, recently.

I would strongly suggest that ANYTHING DV, should be done with DS.

FYI:- If you need to send a sample (as requested by the dev), you can cut a sample using MKVToolNix, and posting it on Mediafire (as good as any, & free)

Good Luck.

[Kuler087]

He can't do that when the script crashes. But it's all good, he sent me a sample and the problem was a typo at line 894 for Profile 7 RPU input in workflow 1-1.

fixed in the latest beta.

[guest]

He can't do that when the script crashes. But it's all good, he sent me a sample and the problem was a typo at line 894 for Profile 7 RPU input in workflow 1-1.

fixed in the latest beta.

Nice catch, typo's can ruin everything :(

I just grabbed that tools update, so I will have a play with that, it will be my first VapourSynth using app :)

So I'm guessing these will be in the full tools pack, or will you make this update available ??

Cheers, lovin' the support :)

[Kuler087]

Yes, I always update the tools pack as soon as needed to keep up with the BETA versions. And when I release the stable version, I always share separately the new tools needed so people don't have to re-download the whole pack again and again.

But there are some annoying msg now for the first 200 frames when encoding P5 videos with vapoursynth/libplacebo but the output is correct and it does the same if I do the same job in staxrip.
I'll have to check it out.


Avisynth Compat: requested frame 2 not prefetched, using slow method...

[guest]

I'm probably doing something wrong, again,

I tried 3 different AAC's in 8-1-1, of the latest BETA, and got this :-

Processing... "D:\clever\The.Lord.of.the_0_0_.aac"
ffmpeg version n6.1.1-11-g4fec1c5928-ga2cfd6062c+92 Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 13.2.0 (Rev4, Built by MSYS2 project)
configuration: --pkg-config=pkgconf --cc='ccache gcc' --cxx='ccache g++' --ld='ccache g++' --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-amf --enable-bzlib --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-cuda-llvm --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-libfdk-aac --enable-libbluray --enable-libsoxr --enable-libspeex --enable-libtwolame --enable-libwebp --enable-libxml2 --enable-gpl --enable-avisynth --enable-libxvid --enable-version3 --enable-libsrt --enable-libsvtav1 --enable-libsvthevc --enable-libsvtvp9 --enable-libkvazaar --enable-openal --enable-openssl --extra-cflags=-DLIBTWOLAME_STATIC --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv --extra-cflags=-DKVZ_STATIC_LIB --enable-nonfree --extra-cflags=-DAL_LIBTYPE_STATIC --extra-cflags='-ID:/MABS-ffmpeg/local64/include' --extra-cflags='-ID:/MABS-ffmpeg/local64/include/AL'
libavutil 58. 29.100 / 58. 29.100
libavcodec 60. 31.102 / 60. 31.102
libavformat 60. 16.100 / 60. 16.100
libavdevice 60. 3.100 / 60. 3.100
libavfilter 9. 12.100 / 9. 12.100
libswscale 7. 5.100 / 7. 5.100
libswresample 4. 12.100 / 4. 12.100
libpostproc 57. 3.100 / 57. 3.100
[aac @ 0000023bac0aa300] Estimating duration from bitrate, this may be inaccurate
Input #0, aac, from 'D:\clever\The.Lord.of.the_0_0_.aac':
Duration: 00:04:53.72, bitrate: 196 kb/s
Stream #0:0: Audio: aac (LC), 48000 Hz, 5.1, fltp, 196 kb/s
Stream mapping:
Stream #0:0 -> #0:0 (aac (native) -> eac3 (native))
Press [q] to stop, [?] for help
[eac3 @ 0000023badaf04c0] [Eval @ 0000007fd73fe8e0] Undefined constant or missing '(' in 'nk'
[eac3 @ 0000023badaf04c0] Unable to parse option value "nk"
[eac3 @ 0000023badaf04c0] Error setting option b to value nk.
[aost#0:0/eac3 @ 0000023badaaa840] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
Error while filtering: Invalid argument
[out#0/matroska @ 0000023bac0ae780] Nothing was written into output file, because at least one of its streams received no packets.
size= 0kB time=N/A bitrate=N/A speed=N/A
Conversion failed!

[Kuler087]

The problem is that the script relies on mediainfo.exe to get the bitrate and it seems it doesn't report a bitrate for a demuxed AAC track. Will make the script remux it to mka.

Should work now in the latest beta...

[guest]

The problem is that the script relies on mediainfo.exe to get the bitrate and it seems it doesn't report a bitrate for a demuxed AAC track. Will make the script remux it to mka.

Should work now in the latest beta...

Well, you've done it again, worked like a charm.

So that now leads me to the next option request (sorry)

Could you add a bitrate option(s) for ac3 & aac to EC3 conversions ??

Like maybe 640, 1024 & 1536 ??

Thanks

[guest]

I loaded the weird coloured P5 DV (only) clip and see what happens..

HDR format: Dolby Vision, Version 1.0, Profile 5, dvhe.05.06, BL+RPU

And I got this:- (truncated)

Also, please note the blue text, there is no Mastering Display option.

And, I thought there may have been some indication that Vapoursynth might have been involved with this, but there was only a reference to Avisynth.
(just thinking out loud)

------------------------------------------------
BL Mastering Display Luminance and Colors:
Profile 5 DV
------------------------------------------------

What is the Mastering Display? Choices are: 1000nits-P3= 20(default) / 1000nits-BT2020= 21 / 4000nits-P3= 7 / 4000nits-BT2020= 8 / 2000nits-P3= 30 / 2000nits-BT2020= 31


Processing: "True.Lies.1994.2160p.mkv"
reading input tracks format/id/language...
done.
Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'D:\Dovi_Temp_MP4\temp.folder77\BL.hevc'. Container format: HEVC/H.265 elementary stream
Extracting track 1 with the CodecID 'A_EAC3' to the file 'D:\Dovi_Temp_MP4\temp.folder77\True.Lies.1994.2160p.track_2_eng.ec3'. Container format: Dolby Digital Plus (E-AC-3)
Extracting track 2 with the CodecID 'S_TEXT/UTF8' to the file 'D:\Dovi_Temp_MP4\temp.folder77\True.Lies.1994.2160p.track_3_eng.srt'. Container format: SRT text subtitles
Progress: 100%
Reordering metadata... Done.
Parsing RPU file...
Exporting scenes list...
Done.
Exporting shots list from a RPU to a text file...
Indexing, please wait... 100%
Writing index... done.
Input #0, avisynth, from 'D:\Dovi_Temp_MP4\temp.folder77\script.avs':
Duration: 00:05:02.84, start: 0.000000, bitrate: 0 kb/s
Stream #0:0: Video: rawvideo (Y3[11][10] / 0xA0B3359), yuv420p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x1608, 23.98 fps, 23.98 tbr, 23.98 tbn
Stream mapping:
Stream #0:0 -> #0:0 (rawvideo (native) -> prores (prores_ks))
Press [q] to stop, [?] for help
Output #0, mov, to 'D:\Dovi_Temp_MP4\temp.folder77\True.Lies.1994.2160p_prores.422.mov':
Metadata:
encoder : Lavf60.16.100



02/26/2024/15:45:50.807000000 cm_analyze: Metadata saved to 'D:\Dovi_Temp_MP4\temp.folder77\True.Lies.1994.2160p_DV.xml'
Removing L2 trims.
Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved02/26/2024/15:45:51.160000000 metafier: Removed Trim: L2,1
02/26/2024/15:45:51.160000000 metafier: Trim to be removed (L2,27) not found in Metadata
02/26/2024/15:45:51.160000000 metafier: Removed Trim: L2,28
02/26/2024/15:45:51.160000000 metafier: Trim to be removed (L2,48) not found in Metadata
02/26/2024/15:45:51.160000000 metafier: Removed Trim: L2,49
02/26/2024/15:45:51.160000000 Metadata: WARNING List of WARNINGS:
=========================
WARNING: No L2 Trims found
WARNING: No L8 Trims found
=========================
Generate RPU from XML
Parsing XML metadata...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 7261 frames
Done.
Error: The system cannot find the file specified. (os error 2)
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 . . .

====== PROCESSING LOG ======================
Number of written frames = 9465
Number of Errors= 0
Processing finished successfully.
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
[1/2] Parsing track "D:\Dovi_Encodes_MP4\True.Lies.1994.2160p_Generated.hevc"...
[2/2] Saving output file(s) "D:\Dovi_Temp_MP4\temp.folder77\temp.mp4"...

[iso file] Missing MovieHeaderBox
[iso file] Missing MovieHeaderBox
[IsoMedia] error while opening D:\Dovi_Temp_MP4\temp.folder77\temp.mp4, error=Invalid IsoMedia File
Failed to connect filter fin PID temp.mp4 to filter mp4dmx: Invalid IsoMedia File
Blacklisting mp4dmx as output from fin and retrying connections
Filters not connected:
mp4mx (importer:file=00000278432F2290:xps_inband=auto) (ptr=0000027845473BD0)
[Importer] Error importing D:\Dovi_Temp_MP4\temp.folder77\temp.mp4
Failure while importing media: Filter not found for the desired type
Error importing D:\Dovi_Temp_MP4\temp.folder77\temp.mp4: Filter not found for the desired type

And if you're interested, I have uploaded the 5 minute sample of this DV P5 clip (880Mb).

https://www.mediafire.com/file/lxjqg461ut3mmwu/5+minute+test+DV+P5.7z/file

[Kuler087]

right, I did not update 3-1, 6-2 and 7-3 yet but it matters less for those workflows because the brightness metadata are not really affected.


Also, please note the blue text, there is no Mastering Display option.
MDL must be selected manually for P5 input because cmv2.9 doesn't have info about primaries, only cmv4.0 does in L9(the script still doesn't use it though).
Normally, if you have access to P5 web-dl you also have access to the HDR10 stream in which you can get the MDL data.

[guest]

right, I did not update 3-1, 6-2 and 7-3 yet but it matters less for those workflows because the brightness metadata are not really affected.

What does this actually refer to, as I had asked several different questions.

You didn't say anything about the audio bitrates.

MDL must be selected manually for P5 input because cmv2.9 doesn't have info about primaries, only cmv4.0 does in L9(the script still doesn't use it though).
Normally, if you have access to P5 web-dl you also have access to the HDR10 stream in which you can get the MDL data.

Actually, after I first watched that P5 DV, I acquired a non DV version by the same user, so is there any point in trying to "fix" the DV version ??

Interesting note, when I played the P5 thru my Xiaomi TV Box S 2nd Gen, it played fine, but it seems to work with DV, where the TV won't, but the Xiaomi has other issues, so I don't use it :(

Cheers.

[Kuler087]

Interesting note, when I played the P5 thru my Xiaomi TV Box S 2nd Gen, it played fine, but it seems to work with DV, where the TV won't, but the Xiaomi has other issues, so I don't use it :(

Cheers.

DV rarely needs to be generated if the original is already DV. Disney plus , iTunes and MA sometimes have DV with static metadata but its rare.


What does this actually refer to
p5 avisynth


You didn't say anything about the audio bitrates.
I'll think about something... probably just a keyword in filename.

[guest]

DV rarely needs to be generated if the original is already DV. Disney plus , iTunes and MA sometimes have DV with static metadata but its rare.

I'll have to check the details of the file before I download it, but why it was encoded to P5 is a little strange, IMO.

p5 avisynth

I thought you'd added Vapoursynth for P5..

I'll think about something... probably just a keyword in filename.

That'd be nice, thanks.

[Kuler087]

thought you'd added Vapoursynth for P5..

as i said I did not update 3-1, 6-2 and 7-3 yet but it matters less for those workflows because the brightness metadata is not really affected.

only 8-2 was updated to vapoursynth. Your question/log was about 3-1

but why it was encoded to P5 is a little strange, IMO.
what do you mean? most of the streaming services use P5.

[guest]

as i said I did not update 3-1, 6-2 and 7-3 yet but it matters less for those workflows because the brightness metadata is not really affected.

only 8-2 was updated to vapoursynth. Your question/log was about 3-1

I was just wanting to clarify, and yes it was 3-1.

what do you mean? most of the streaming services use P5.

I don't stream, I download & process, generally they are P7 or P8's, but having said that, I generally go for HDR10, but now that I've starting using DS, that might change.

Cheers.

[Kuler087]

I generally go for HDR10, but now that I've starting using DS, that might change.

Cheers.

There are so many issues with the device's implementation that make DV a big mess but generally speaking, DV has much better tone mapping than HDR10 especially for TVs under 1000nits.

[speedy]

DV rarely needs to be generated if the original is already DV. Disney plus, iTunes and MA sometimes have DV with static metadata but it's rare.
Like Poor Things that was just released today? ;-)

[Kuler087]

Like Poor Things that was just released today? ;-)

This one is not really static. It is SDR in an HDR container and DV is pretty much useless here. The Level 2 and L8 trims are just a slight increase in brightness but otherwise, it is identical to SDR. see: https://slow.pics/c/3bD4lVh4

And generating new metadata wouldn't really make a difference, it would actually be darker because of the lack of a positive lift from the original manual trims.

https://i.ibb.co/R2S1BFw/Poor-things-2023-dv-WEB-Do-Vi-L8-PLOT-100nits-trim.png

https://i.ibb.co/G9nK1J9/Poor-things-2023-hdr-WEB-HDR-plot.png

[guest]

Hi Reset,

Thought I'd try an 8-2-1 on the DV P5 video.

Got this:-

Side data:
DOVI configuration record: version: 1.0, profile: 5, level: 6, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 0
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Press [q] to stop, [?] for help
[out#0/hevc @ 000001e9ae9c5800] video:875637kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
size= 875637kB time=00:05:02.63 bitrate=23702.5kbits/s speed= 739x
Reordering metadata... Done.

D:\Dovi_Encodes_MP4>"D:\DoVi_Scripts\tools\NVEncC\NVEncC64.exe" --vbr 50000 --codec h265 --multipass 2pass-full --preset P7 --level 6.2 --output-depth 10 --profile main10
--max-bitrate 160000 --vbv-bufsize 160000 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers
--master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "201,10" --dolby-vision-profile 8.1 --dolby-vision-rpu "D:\Dovi_Temp_MP4\temp.folder49\P8.RPU.bin" -i
"D:\Dovi_Temp_MP4\temp.folder49\script.vpy" -o "D:\Dovi_Encodes_MP4\True.Lies.1994.2160p_encoded.hevc"
--------------------------------------------------------------------------------
D:\Dovi_Encodes_MP4\True.Lies.1994.2160p_encoded.hevc
--------------------------------------------------------------------------------
vpy: Failed to load vsscript.dll.
failed to initialize file reader(s).
Failed to open input file.

D:\Dovi_Encodes_MP4>echo off & goto :end

Does Vapoursynth need to be "installed", or Python cmd or something to register it ?? I have never used ANY VS stuff before.

[Kuler087]

yes, install vapoursynth R65 (which requires python 3.11)

[guest]

yes, install vapoursynth R65 (which requires python 3.11)

Well, after stuffing around blindly, I got all that done, and it all worked, and this is the log:-

Drag and drop a video and press enter...
J:\T.L.1994.2160p.WEB-DL.DDP5.1.Atmos.DV.H265-FLUX\True.Lies.1994.2160p.mkv
Do you want to crop? y or n and press enter... (default=n)
n
Indexing, please wait... 100%
Writing index... done.
ffmpeg version n6.1.1-12-g52e47d24e2-gab2173c0a5+93 Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
configuration: --pkg-config=pkgconf --cc='ccache gcc' --cxx='ccache g++' --ld='ccache g++' --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect
--enable-amf --enable-bzlib --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec
--enable-cuda-llvm --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-libfdk-aac
--enable-libbluray --enable-libsoxr --enable-libspeex --enable-libtwolame --enable-libwebp --enable-libxml2 --enable-gpl --enable-avisynth --enable-libxvid --enable-version3 --enable-libsrt
--enable-libsvtav1 --enable-libsvthevc --enable-libsvtvp9 --enable-libkvazaar --enable-openal --enable-openssl --extra-cflags=-DLIBTWOLAME_STATIC --extra-cflags=-DLIBXML_STATIC
--extra-libs=-liconv --extra-cflags=-DKVZ_STATIC_LIB --enable-nonfree --extra-cflags=-DAL_LIBTYPE_STATIC --extra-cflags='-ID:/MABS-ffmpeg/local64/include' --extra-cflags='-ID:/MABS-ffmpeg/local64/include/AL'
libavutil 58. 29.100 / 58. 29.100
libavcodec 60. 31.102 / 60. 31.102
libavformat 60. 16.100 / 60. 16.100
libavdevice 60. 3.100 / 60. 3.100
libavfilter 9. 12.100 / 9. 12.100
libswscale 7. 5.100 / 7. 5.100
libswresample 4. 12.100 / 4. 12.100
libpostproc 57. 3.100 / 57. 3.100
Input #0, matroska,webm, from 'J:\T.L.1994.2160p.WEB-DL.DDP5.1.Atmos.DV.H265-FLUX\True.Lies.1994.2160p.mkv':
Metadata:
encoder : libebml v1.4.5 + libmatroska v1.7.1
creation_time : 2024-02-22T05:26:37.000000Z
Duration: 00:05:04.72, start: 0.000000, bitrate: 24305 kb/s
Stream #0:0(eng): Video: hevc (Main 10), yuv420p10le(tv), 3840x1608 [SAR 1:1 DAR 160:67], 23.98 fps, 23.98 tbr, 1k tbn (default) (original)
Metadata:
BPS : 23685726
DURATION : 00:05:02.845000000
NUMBER_OF_FRAMES: 7261
NUMBER_OF_BYTES : 896637993
_STATISTICS_WRITING_APP: mkvmerge v82.0 ('I'm The President') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-02-22 05:26:37
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Side data:
DOVI configuration record: version: 1.0, profile: 5, level: 6, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 0
Stream #0:1(eng): Audio: eac3 (Dolby Digital Plus + Dolby Atmos), 48000 Hz, 5.1(side), fltp, 768 kb/s (default) (original)
Metadata:
BPS : 768000
DURATION : 00:05:02.848000000
NUMBER_OF_FRAMES: 9464
NUMBER_OF_BYTES : 29073408
_STATISTICS_WRITING_APP: mkvmerge v82.0 ('I'm The President') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-02-22 05:26:37
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:2(eng): Subtitle: subrip (original) (hearing impaired)
Metadata:
title : SDH
BPS : 42
DURATION : 00:04:56.263000000
NUMBER_OF_FRAMES: 64
NUMBER_OF_BYTES : 1574
_STATISTICS_WRITING_APP: mkvmerge v82.0 ('I'm The President') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-02-22 05:26:37
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Output #0, hevc, to 'pipe:':
Metadata:
encoder : Lavf60.16.100
Stream #0:0(eng): Video: hevc (Main 10), yuv420p10le(tv), 3840x1608 [SAR 1:1 DAR 160:67], q=2-31, 23.98 fps, 23.98 tbr, 23.98 tbn (default) (original)
Metadata:
BPS : 23685726
DURATION : 00:05:02.845000000
NUMBER_OF_FRAMES: 7261
NUMBER_OF_BYTES : 896637993
_STATISTICS_WRITING_APP: mkvmerge v82.0 ('I'm The President') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-02-22 05:26:37
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Side data:
DOVI configuration record: version: 1.0, profile: 5, level: 6, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 0
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Press [q] to stop, [?] for help
[out#0/hevc @ 000001c385c25840] video:875637kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
size= 875637kB time=00:05:02.63 bitrate=23702.5kbits/s speed= 722x
Reordering metadata... Done.

D:\Dovi_Encodes_MP4>"D:\DoVi_Scripts\tools\NVEncC\NVEncC64.exe" --vbr 50000 --codec h265 --multipass 2pass-full --preset P7 --level 6.2 --output-depth 10 --profile main10 --max-bitrate 160000
--vbv-bufsize 160000 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange limited --chromaloc 2 --aud --repeat-headers
--master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "201,10" --dolby-vision-profile 8.1 --dolby-vision-rpu
"D:\Dovi_Temp_MP4\temp.folder49\P8.RPU.bin" -i "D:\Dovi_Temp_MP4\temp.folder49\script.vpy" -o "D:\Dovi_Encodes_MP4\True.Lies.1994.2160p_encoded.hevc"
--------------------------------------------------------------------------------
D:\Dovi_Encodes_MP4\True.Lies.1994.2160p_encoded.hevc
--------------------------------------------------------------------------------
NVEncC (x64) 7.41 (r2681) by rigaya, Jan 22 2024 13:02:15 (VC 1929/Win)
OS Version Windows 11 x64 (22631) [UTF-8]
CPU 13th Gen Intel Core i9-13900KF [5.52GHz] (8P+16E,24C/32T)
GPU #0: NVIDIA GeForce RTX 3050 (2560 cores, 1822 MHz)[PCIe4x16][551.52]
NVENC / CUDA NVENC API 12.1, CUDA 12.4, schedule mode: auto
Input Buffers CUDA, 16 frames
Input Info VapourSynthMT r65(yv12(10bit))->p010 [AVX2], 3840x1608, 24000/1001 fps
Vpp Filters copyHtoD
Output Info H.265/HEVC main10 @ Level 6.2
3840x1608p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control VBR
Multipass 2pass-full
Bitrate 50000 kbps (Max: 160000 kbps)
Target Quality auto
Initial QP I:20 P:23 B:25
QP range I:0-63 P:0-63 B:0-63
QP Offset cb:0 cr:0
VBV buf size 160000 kbit
Split Enc Mode auto
Lookahead off
GOP length 240 frames
B frames 3 frames [ref mode: middle]
Ref frames 3 frames, MultiRef L0:auto L1:auto
AQ off
CU max / min auto / auto
VUI matrix:bt2020nc,colorprim:bt2020,transfer:smpte2084,range:limited,chromaloc:topleft
MasteringDisp G(0.265000 0.690000) B(0.150000 0.060000) R(0.680000 0.320000)
WP(0.312700 0.329000) L(1000.000000 0.000100)
MaxCLL/MaxFALL 201/10
dovi rpu D:\Dovi_Temp_MP4\temp.folder49\P8.RPU.bin
Others mv:auto aud repeat-headers

encoded 7261 frames, 31.71 fps, 33855.50 kbps, 1222.25 MB
encode time 0:03:48, CPU: 1.4%, GPU: 15.8%, VE: 72.9%, GPUClock: 1980MHz, VEClock: 1740MHz
frame type IDR 31
frame type I 31, total size 8.44 MB
frame type P 1815, total size 412.62 MB
frame type B 5415, total size 801.18 MB

D:\Dovi_Encodes_MP4>echo off & goto :end

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?

Just converted to MP4, and it looks pretty good, and it's a P8.1, which may not play on the LG.

It played :)

[Kuler087]

Just converted to MP4, and it looks pretty good, and it's a P8.1, which may not play on the LG.

It played :)

Did you try the old and new mp4 version on your TV?

Just to clarify, when you use the OLD mp4 version and if your input doesn't have lossless or subtitles, it uses a modified version of the mp4muxer that makes ''dvhe'' mp4 (compatible with C8) and that special version can specify the BL compatibility id so that's why your file says P8.1.

When there's lossless audio or subs, the script uses an old version of mp4box (because mp4muxer cannot mux lossless audio or subs), and in the process, the file loses its BL id and becomes P8.0 in mediainfo.

[guest]

Did you try the old and new mp4 version on your TV?

Just to clarify, when you use the OLD mp4 version and if your input doesn't have lossless or subtitles, it uses a modified version of the mp4muxer that makes ''dvhe'' mp4 (compatible with C8) and that special version can specify the BL compatibility id so that's why your file says P8.1.

When there's lossless audio or subs, the script uses an old version of mp4box (because mp4muxer cannot mux lossless audio or subs), and in the process, the file loses its BL id and becomes P8.0 in mediainfo.

I did fiddle around with those settings the other day, and I put them back to default settings.

There's just so much more to learn about all this, and I'm almost too old to have it sink in...information overload :(


And to test the install process, I uninstalled all the Python & Vapoursynth installs, and re-installed using, python-3.12.2-amd64.exe & VapourSynth-x64-R66-RC1.exe, and completed the 8-2-1 workflow.

[guest]

Hi Reset,

I have been doing more fiddling/testing, and noticed that if I try a conversion either .thd or .mlp to EC3, I am now getting the same error as the other day when trying .aac to EC3, here (in red):-

https://forum.doom9.org/showthread.php?p=1998223#post1998223

And .aac & .ac3 don't error., so it's kind of reversed, it seems. :(

==========================================

I have also noticed (or not noticed) there is no demuxing (audio or sub's) workflow.

So for example, if I use 8-2-1 or 8-2-3, I get a video only final file.

If I want to convert an audio file to EC3, I have to demux the original file with (I use) gMKVExtractGUI (if it's not an .mkv, I run it thru MKVToolNix, then gMKVExtractGUI).

Then using 8-1-1, that converts to an audio only file. (except for current problem mentioned above)

So now I have 2 files that need to be muxed, in my case to .mp4 for DV compatibility with my LG TV.

So now the only way I can do that (that I know of), it to mux them using MKVToolNix (I could possibly use MP4Box), and then use the DoVi MP4 muxer #5.

And after reading some fine print, I've noticed that if I mux .srt subtitles, I get a level P8.0 mp4, with no subs, I get P8.1.

==========================================

I realise that 3-1 kind of does all of the above, but sometimes you may not want to use 3-1, and because it muxes the subs, the P level is only 8.0.


So after all that BS, is there a way that you can have the DoVi MP4 muxer able to add at least one converted audio track, will save me a few steps ??

I hope you can understand what I am trying to say here, 'cause I'm confused :(

PS:- Dolby released this today:- Dolby_Vision_Professional_Tools_Windows_v5.5.0

PPS:-I just grabbed the latest Beta, and it's 60 lines bigger than the previous...there must be a few changes / additions :)

[Kuler087]

I have been doing more fiddling/testing, and noticed that if I try a conversion either .thd or .mlp to EC3,
i'll check it out, I never encode raw audio stream so its possible.

I have also noticed (or not noticed) there is no demuxing (audio or sub's) workflow.
So after all that BS, is there a way that you can have the DoVi MP4 muxer able to add at least one converted audio track, will save me a few steps ??

yes the encoder workflows dont mux and I understand how this can be a problem for the MP4 version.
p-s if you name your lossy audio and subtitle file the same as the input, and run workflow 5, it should mux them.

I might add muxing support later when i have more time.

[guest]

i'll check it out, I never encode raw audio stream so its possible.



yes the encoder workflows dont mux and I understand how this can be a problem for the MP4 version.
p-s if you name your lossy audio and subtitle file the same as the input, and run workflow 5, it should mux them.

I might add muxing support later when i have more time.

OK, thanks for the hint with the naming, I will give it a shot.

So what's different in the latest beta ?? (I know I'll possibly figure it out tomorrow (my time) but for now, it's time for bed).

Thanks again.

[Kuler087]

So what's different in the latest beta ??

2.0.3 should be released soon

changes (by memory: my pc is offline because of a power outage):
1-1 can now resync hdr10plus
2-9 now read the input framerate
8-2 now use vapoursynth
8-1 can encode lossy audio input

[guest]

2.0.3 should be released soon

changes (by memory: my pc is offline because of a power outage):
1-1 can now resync hdr10plus
2-9 now read the input framerate
8-2 now use vapoursynth
8-1 can encode lossy audio input

OK, testing time, again.

So first off was audio encoding to EC3:-

So with 8-1-1 & 2.0.2.bat, it would process .thd & .mlp, but not .aac or .ac3.

Whereas, 2.0.3 Beta (latest) is the complete opposite :(

I noticed yesterday that 8-2 uses VS for everything, I thought it was mainly for Level P5's, but as long as it works :)

[Kuler087]

try the new beta. raw thd mlp should work again...
but why do you process raw audio? you can just feed the original MKV and the script will pick the best audio according to your script language settings(default english). No need to demux.

and yes, now 8-2 use vapoursynth for everything except FEL.
The non-p5 inputs were fine with avisynth but it was easier to update to vapoursynth for all the input.

[guest]

try the new beta. raw thd mlp should work again...
but why do you process raw audio? you can just feed the original MKV and the script will pick the best audio according to your script language settings(default english). No need to demux.

and yes, now 8-2 use vapoursynth for everything except FEL.
The non-p5 inputs were fine with avisynth but it was easier to update to vapoursynth for all the input.

Yep, that worked, thanks :)

I haven't tried the "trick" you mentioned yesterday about having all the tracks named alike, for DoVi MP4 Muxer..

TBH, I have forgotten why I am processing raw audio...hang on, I just remembered...it's when the video has got some crappy bit rate audio,
and I want to "upgrade" it, and AFAIK, DS hasn't got that function, yet.

So I have to demux the audio, running it thru another app, and then mux it back.

So to re-cap, running 8-2-1 outputs a VIDEO only .hevc,

and running 8-1-1 outputs to an AUDIO only .mkv.

They need to be muxed together !

That's probably another reason I asked about demuxing, and being able to change the audio bit rate....so that DoVi_Scripts is THE "one stop shop" for all these processes.

Does that make sense ??

PS:- I just noticed this:--- You can override lossy audio input bitrate target if you add IGNOREBITRATE in the filename
is this new, in 8-1-1, latest Beta ??

Cheers.

[Kuler087]

is this new, in 8-1-1, latest Beta ??

Cheers.

it does what you wanted, it will use the bitrate you set in the settings

[guest]

Is this what you'd call SDR ??

Video
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Format settings, Slice count : 4 slices per frame
Codec ID : V_MPEG4/ISO/AVC
Duration : 5 min 0 s
Bit rate mode : Variable
Bit rate : 30.0 Mb/s
Maximum bit rate : 32.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.603
Stream size : 1.05 GiB (85%)
Language : English
Default : No
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Original source medium : Blu-ray

I ripped this BluRay, and ran workflow 8-2-5 with latest Beta, and I got this:-

[vapoursynth @ 0000016ff1e8a400] Could not get script output node.
[in#0 @ 0000016ff1e8a240] Error opening input: Generic error in an external library
Error opening input file D:\Dovi_Temp_MP4\temp.folder49\script.vpy.
Error opening input files: Generic error in an external library

However, running it with 2.0.2, 8-2-5 (avisynth), no errors.

[guest]

it does what you wanted, it will use the bitrate you set in the settings

Please tell me what line this setting is.

Also, can you please re read the previous post, as I edited it while you were replying.

[Kuler087]

Please tell me what line this setting is.

Also, can you please re read the previous post, as I edited it while you were replying.

same as before:
::choose EC3 DD+ encoding bitrate (default= 1536) 5.1 = max 1536kbps and 7.1= max 1024kbps
set DDP_bitrate=1024


8-2-5: I'll check it out.

[guest]

same as before:
::choose EC3 DD+ encoding bitrate (default= 1536) 5.1 = max 1536kbps and 7.1= max 1024kbps
set DDP_bitrate=1024


8-2-5: I'll check it out.

OK, so I do have that set to 1536, as I have disabled 7.1, as I can't really use it (as explained a few days ago), and I thought that was the setting you were talking about.

So, I have a crappy .aac audio from a tv series, (even tho it's a 4K DV video) and it has a measly bitrate of 200kbps, so what happens if I add IGNOREBITRATE to the .aac's file name ??

Yes, I was a bit puzzled that 8-2-5 worked on an earlier build, so there's been a bit of double checking along the way.

==============================

I hope I'm not being a PITA, and that the feedback, suggestions, etc, aren't too much.

Please forgive me for asking some pretty basic question's, as, as you know I have not been using this for very long, and it's your "baby", and know it like the back of your hand.
I know it can be annoying to be asked about things that just come naturally to the you, being the dev.

Regards.

[Kuler087]

it will use whatever bitrate you have set.
There is no point in increasing the bitrate though, this is intended for someone who wants to reduce bitrate. EG 768kbps to 384.

Yes, I was a bit puzzled that 8-2-5 worked on an earlier build, so there's been a bit of double checking along the way.
that's why its called BETA, when I make a change, its possible that I introduce new bug. There are so many workflow and input possible that i did not test everything yet.

EDIT: fixed in latest beta

[guest]

it will use whatever bitrate you have set.
There is no point in increasing the bitrate though, this is intended for someone who wants to reduce bitrate. EG 768kbps to 384.


that's why its called BETA, when I make a change, its possible that I introduce new bug. There are so many workflow and input possible that i did not test everything yet.

EDIT: fixed in latest beta

OK, grabbed latest BETA...

So I tried this:- The.Lord.of.the_0_0_IGNOREBITRATE.aac, which is 211kbps, after DS, it was the same, but .ec3.


Then onto 8-2-5, which was the topic of yesterday, so see here for reference:-

https://forum.doom9.org/showthread.p...40#post1998440

No errors today

Next dilemma, 8-2-5 of this :-

The Magnificent Seven_t00_chunk.mkv

produced a large .mov (video only)

So now I need the audio..how do I do that ??

Demuxed that .mkv using gMKVExtractGUI to get the audio (which was a .dts),

Audio
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Bit rate mode : Variable
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless

ran that thru 8-1-1, and that produced a .mkv container with this:-

Audio
ID : 1
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : A_EAC3
Duration : 5 min 0 s
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 62.500 FPS (768 SPF)
Bit depth : 32 bits
Compression mode : Lossy
Stream size : 55.1 MiB (100%)
Title : Dolby Digital Plus @ 1536kbps
Writing library : Lavc60.31.102 eac3
Service kind : Complete Main
Default : No
Forced : No

So now I have a .mov & a .mkv (audio), how do I mux that ??

DoVi MP4 Muxer does not support .mov , however DoVi MKV Muxer does (even tho it doesn't say that it does)

So I put both in a separate folder, named the same, and opened DoVi MKV Muxer, and got this:-

Drag and drop folder with files or a single file and press enter..."D:\Dovi_Encodes_MP4\New folder"
processing..."The Magnificent Seven_t00_chunk_HDR100.mkv"
processing..."The Magnificent Seven_t00_chunk_HDR100.mov"
mkvmerge v82.0 ('I'm The President') 64-bit
'D:\Dovi_Encodes_MP4\New folder\The Magnificent Seven_t00_chunk_HDR100.mov': Using the demultiplexer for the format 'QuickTime/MP4'.
'D:\Dovi_Encodes_MP4\New folder\The Magnificent Seven_t00_chunk_HDR100.mov' track 0: Using the output module for the format 'ProRes video'.
The file 'D:\Dovi_Encodes_MP4\The Magnificent Seven_t00_chunk_HDR100_NEW.mkv' has been opened for writing.
The cue entries (the index) are being written...
Multiplexing took 35 seconds.

But the muxed .mkv only had the video track

So then I tried the MP4 Muxer:-

Got this error, and I can't get around it:-

Drag and drop folder with files or a single file and press enter..."D:\Dovi_Encodes_MP4\New folder"
processing..."The Magnificent Seven_t00_chunk_HDR100.mkv"
reading input tracks format/id/language...
done.
Error: The ID '0' has already been used for another destination file.
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
ERROR! Can't open input file: D:\Dovi_Temp_MP4\temp.folder66\HDR.hevc
Error parsing command line!

I think there is a problem with MP4 Muxer in the latest BETA, I just tried another file, and it had other errors, but that's for another msg.

I think that's about enough, for one message.

Cheers.

[Kuler087]

8-2-5 is intended for Davinci Resolve (HDR grading). This workflow just puts the SDR video into a REC2020 HDR container without touching the brightness or gamut.
There's no point in watching HDR at 100nits so of course the script muxing doesnt support prores input, and never will. Prores is a lossless codec not meant for playback but for editing.
PS: I don't believe in the one click SDR to HDR conversions. HDR must be graded shot by shot!

-- Can encode SDR to HDR10-100nits PQ PRORES 422 HQ
-- Output should be graded in Resolve otherwise this is just 100nits SDR in an HDR container.
-- Require Vapoursynth

Audio bitrate: check the new version...

[guest]

8-2-5 is intended for Davinci Resolve (HDR grading). This workflow just puts the SDR video into a REC2020 HDR container without touching the brightness or gamut.
There's no point in watching HDR at 100nits so of course the script muxing doesnt support prores input, and never will. Prores is a lossless codec not meant for playback but for editing.
PS: I don't believe in the one click SDR to HDR conversions. HDR must be graded shot by shot!

Audio bitrate: check the new version...

OK, I did do another SDR to HDR a week or so back, and I doubt that I will go to the trouble of doing all that process in Resolve, however, I did apply a particular 3D LUT,
and it looked pretty damn good, (in preview) but I didn't process it, and haven't done any more to it, yet.

Having said that, you probably could implement a good (good enough) one click SDR to HDR conversion option, for those lazy ppl that don't want to use Resolve. Just sayin'.

I grabbed the latest BETA, it's got 4 extra lines of code, but I haven't had the opportunity to test it today.

Thanks.

UPDATE:- OK, another day, more testing :)

OK, well 8-1-1 is working, I converted that low bitrate .aac to 1536 (a bit over the top I know, but that's the setting in the .ini), when adding IGNOREBITRATE to the file name.

So expanding on that, could a custom bitrate be used in the file name, for "one off" conversions ??

------------------------------------------------------

And a little off that topic, I have been noticed a strange behavior with a lot of the workflows, when they're completed...

You get this :_

the script has been completed, press a key to start again...
Press any key to continue . . .
------------------------------------------------------
-- This script encode lossless audio to EAC3 DD+
-- Input can be a folder with files or a single file.
-- EAE folder needed for 7.1 encoding.
------------------------------------------------------
Drag and drop folder with files or a single file and press enter...

So you drag another file over, press enter, and the whole "window" disappears.

[Kuler087]

could a custom bitrate be used in the file name, for "one off" conversions
Maybe...


Having said that, you probably could implement a good (good enough) one click SDR to HDR conversion option, for those lazy ppl that don't want to use Resolve. Just sayin'.

no sorry, the web is already flooded with bad sdr to hdr upscales, I don't want to contribute...

And a little off that topic, I have been noticed a strange behavior with a lot of the workflows, when they're completed...
you have to press a key to start the workflow again. If you drop a file without pressing a key, yes the script will crash.

But there's a known issue with some workflows when there're completed that ask if you want to go back to the main menu: It could process the same file again.
It's on my todo list but I never use that function so it's not a priority to me. When I have more than one file to process I just input a folder with files instead.

[guest]

could a custom bitrate be used in the file name, for "one off" conversions

Maybe...

Any way would be nice :)


Having said that, you probably could implement a good (good enough) one click SDR to HDR conversion option, for those lazy ppl that don't want to use Resolve. Just sayin'.

no sorry, the web is already flooded with bad sdr to hdr upscales, I don't want to contribute...

Had to ask, and I agree...


And a little off that topic, I have been noticed a strange behavior with a lot of the workflows, when they're completed...
you have to press a key to start the workflow again. If you drop a file without pressing a key, yes the script will crash.

But there's a known issue with some workflows when there're completed that ask if you want to go back to the main menu: It could process the same file again.
It's on my todo list but I never use that function so it's not a priority to me. When I have more than one file to process I just input a folder with files instead.

It really only happens when I'm using the same workflow for different things, folder idea is good :)

So what's next, "proper" 2.0.3 ??

Thanks again :)

[Kuler087]

So what's next, "proper" 2.0.3 ??
Thanks again :)

I have to test every possible input in 8-2, and then I can release 2.0.3 stable. Probably be tomorrow or later today.

[guest]

I have to test every possible input in 8-2, and then I can release 2.0.3 stable. Probably be tomorrow or later today.

Awesome, so now 2.0.3 stable is out :)

I've noticed a couple of things in the "newtools2.0.3.7z"

Now there's an Avisynth folder, instead of just in the main folder.

arial.ttf ?

So other than that, simply copy & overwrite the existing contents of the tool pack ??

Thanks.

PS:- Just curious, if simply renaming a .bat (eg:- mkv to mp4, which I've done with the beta's), changes its processes, then why provide 3 variants ??

You'll have to add your doom9 address to the .bats.... Contact: R3S3T_9999@proton.me

[madey83]

@Kuler087

i have two sources:
1) HDR10 and AAC 5.1 audio [en]
2) DoVi and Dolby Digital Plus with Dolby Atmos [en]

How can i create hybrid version with better audio automatically pick up by the script?

[guest]

@Kuler087

i have two sources:
1) HDR10 and AAC 5.1 audio [en]
2) DoVi and Dolby Digital Plus with Dolby Atmos [en]

How can i create hybrid version with better audio automatically pick up by the script?

Hi madey83,

Well, once you have all the required components & tools, etc..

There is some setup settings you need to do.

It's pretty simple, open the latest .bat, and choose Menu 3 Option 1, and you will be asked a couple of questions, then away it goes.

Depending on your playback device (TV, PC, etc) will determine whether you need .mkv or .mp4 output.

Have been using this for a couple of weeks, helping Kuler along the way. It's GOOD !!!!!

[madey83]

Hi madey83,

Well, once you have all the required components & tools, etc..

There is some setup settings you need to do.

It's pretty simple, open the latest .bat, and choose Menu 3 Option 1, and you will be asked a couple of questions, then away it goes.

Depending on your playback device (TV, PC, etc) will determine whether you need .mkv or .mp4 output.

Have been using this for a couple of weeks, helping Kuler along the way. It's GOOD !!!!!

i would like to do this one

1) MODE.I= DoVi Inject/Convert/Edit/Re-sync TWO INPUTS (P8 Hybrid Maker/Injector)

and script should ask what audio choose from source or automatically choose better one.... in my case atmos

[guest]

i would like to do this one

1) MODE.I= DoVi Inject/Convert/Edit/Re-sync TWO INPUTS (P8 Hybrid Maker/Injector)

and script should ask what audio choose from source or automatically choose better one.... in my case atmos

I haven't used that one, yet.

Well, the choice is yours, you will need to do a bit of trial & error until you get the exact result you're after....

There are a LOT of settings you can "play" with, when you "edit" the .bat, you will see them, LOT's of them.

[Kuler087]

So other than that, simply copy & overwrite the existing contents of the tool pack ??

yes

then why provide 3 variants ??

because most of the new users don't read instructions and don't know about it.


@Kuler087

i have two sources:
1) HDR10 and AAC 5.1 audio [en]
2) DoVi and Dolby Digital Plus with Dolby Atmos [en]

How can i create hybrid version with better audio automatically pick up by the script?


unfortunately the script takes the audio from the BL input and I don't think I will change that. So just make sure your BL input has the right audio/subs track before running 1-1
You can also disable muxing and mux with any audio you want after the workflow

[guest]

Quote:
So other than that, simply copy & overwrite the existing contents of the tool pack ??

yes

I just checked to see if you'd actually provided an updated complete tools pack, (as well as simply the extra's required), and was happy to see that it was .7z :)

Nice.

[Kuler087]

, and was happy to see that it was .7z :)

Nice.
yes :)

[CineManiac]

Hello, supporter and lurker here

I'm wondering if there's a way to input an L5 config somehow into Resolve's Output Blanking? So, I don't have to go scene by scene and override the blanking for variable ARs in Resolve.

Thank you for your work updating and improving on your scripts regularly. :)

[Kuler087]

Hello, supporter and lurker here

I'm wondering if there's a way to input an L5 config somehow into Resolve's Output Blanking? So, I don't have to go scene by scene and override the blanking for variable ARs in Resolve.

Thank you for your work updating and improving on your scripts regularly. :)

Workflow 2-9 can make an EDL file that you can import in Resolve. Youtube tutorial about it: https://www.youtube.com/watch?v=KVx01kCLLS8

But after importing the scene cuts in Resolve, if you planned to import an original XML DV metadata with dynamic L5, It won't work. AFAIK, if you import your xml, only the first shot will get metadata.

[CineManiac]

Workflow 2-9 can make an EDL file that you can import in Resolve. Youtube tutorial about it: https://www.youtube.com/watch?v=KVx01kCLLS8

But after importing the scene cuts in Resolve, if you planned to import an original XML DV metadata with dynamic L5, It won't work. AFAIK, if you import your xml, only the first shot will get metadata.

Oh I see. I am aware of importing the EDL so thank you, but it seems I would be unable to import variable output blanking so we just have to go scene by scene.

Thank you again for clarifying.

[guest]

Hi Reset,

I did a 3-1 with the latest everything, and I'm not sure if this is important, or what it means:-

Input #0, avisynth, from 'D:\Dovi_Temp_MP4\temp.folder77\script.avs':
Duration: 00:58:48.07, start: 0.000000, bitrate: N/A
Stream #0:0: Video: rawvideo (Y3[11][10] / 0xA0B3359), yuv420p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x2160, 23.98 fps, 23.98 tbr, 23.98 tbn
Stream mapping:
Stream #0:0 -> #0:0 (rawvideo (native) -> prores (prores_ks))
Press [q] to stop, [?] for help
Output #0, mov, to 'D:\Dovi_Temp_MP4\temp.folder77\Game of Thrones S01 E01_prores.422.mov':
Metadata:
encoder : Lavf60.16.100
Stream #0:0: Video: prores (HQ) (apch / 0x68637061), yuv422p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x2160, q=2-31, 200 kb/s, 23.98 fps, 24k tbn
Metadata:
encoder : Lavc60.31.102 prores_ks
[out#0/mov @ 0000013ad8ed2600] video:34326861kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.002049%
frame=84589 fps= 71 q=-0.0 Lsize=34327565kB time=00:58:48.02 bitrate=79707.9kbits/s speed=2.98x
Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved
03/05/2024/16:51:51.728000000 CPU: INFO 13th Gen Intel(R) Core(TM) i9-13900KF (GenuineIntel) [ mmx sse sse2 sse3 ssse3 sse41 sse42 avx avx2 fma ]
03/05/2024/16:51:51.755000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:51.813000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:51.899000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:51.937000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:51.956000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:51.995000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:52.109000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:52.204000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:52.365000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
03/05/2024/16:51:52.459000000 cm_analyze: INFO Shot cut detection is disabled when shot list is used
03/05/2024/16:51:52.460000000 cm_analyze: INFO Source: 'file:///D:/Dovi_Temp_MP4/temp.folder77/Game of Thrones S01 E01_prores.422.mov'
03/05/2024/16:51:52.460000000 cm_analyze: INFO Master Display: 1000-nit, BT.2020, D65, ST.2084, Full
03/05/2024/16:51:52.460000000 cm_analyze: INFO Src Info: '3840x2160x3 u16 interleaved 422 le tight 0-84588 23.976fps top_left pq ycbcr_bt2020 video bt2020'
03/05/2024/16:51:52.460000000 cm_analyze: INFO Frames: 0 - 84588
03/05/2024/16:51:52.460000000 cm_analyze: INFO Frame rate: 24000/1001
03/05/2024/16:51:52.460000000 cm_analyze: INFO Algorithm Version: 4
03/05/2024/16:51:52.460000000 cm_analyze: INFO XML Version: 4.0.2

I'm going to have to change what drives I do this on, NVME's preferably, doing in on old "spinner's" takes forever :(

[Kuler087]

Yes I've noticed the warning when using the latest CM-Analyze, I don't think it matters. The output is the same as before.

[pancserzso]

Hi, thanks for these scripts. I have two questions:

1. Can you tell me what do I need to run to convert a P7 mkv file to a P8 mkv?
2. Do I need to use MakeMKV to crate the source MKV from a BDMV folder, or I can use mkvmerge with the biggest m2ts file in STREAM? Is there any difference, other than the chapters?

[Kuler087]

Hi, thanks for these scripts. I have two questions:

1. Can you tell me what do I need to run to convert a P7 mkv file to a P8 mkv?
2. Do I need to use MakeMKV to crate the source MKV from a BDMV folder, or I can use mkvmerge with the biggest m2ts file in STREAM? Is there any difference, other than the chapters?

Hi,

For any P7 source(mkv or bdmv) to Profile 8, use workflow 4-1.
For BDMV input, you should input the main playlist file and not the largest M2ts.

see tutorial: https://www.youtube.com/watch?v=sBUL2gjhqEE

[pancserzso]

Hi,

For any P7 source(mkv or bdmv) to Profile 8, use workflow 4-1.
For BDMV input, you should input the main playlist file and not the largest M2ts.

see tutorial: https://www.youtube.com/watch?v=sBUL2gjhqEE

Thanks a lot, video is perfect! About CM4, if my TV supports it (LG G2), then I should use rem_cmv4=NO right?

[Kuler087]

You should not remove cmv4.0 unless maybe if you use the AppleTV 4K with Infuse (non-beta).
Cmv4.0 has superior tone mapping to the old cmv2.9 algo

[giyo279]

Any thoughts on NVENC vs x265 for dovi_baking? I know encoding settings can get pretty advanced, but are the default HDR_settings set for mostly transparent encodes?

[Kuler087]

I'm no HEVC encode setting expert but as far as I can tell, if you use x265 with the script default settings, it should produce something transparent but depending on how much FEL adds, you might end up with a file larger than your source.
For NVENC, I don't know but from the quick tests I did, it seems to produce decent quality.

[CineManiac]

Hey, have you had a chance to check if the Infuse beta implementation of cmv4.0 has the same issues as the Plex version on ATV?

[Kuler087]

Not yet, I have to get in the beta test group first but I'll definitely check it out.

[CineManiac]

Oh man, I'll have to re-inject everything with cmv4

[Kuler087]

Oh man, I'll have to re-inject everything with cmv4

haha, yes but it's worth it.

[Gatorman3385]

It seems my madVR install is broken. I've tried running "install.bat" as admin. 6-2 gives me the error,

Connecting LAV Video Decoder to madVR failed.

MPC-HC has stop using madVR as well. Any thoghts?

[Kuler087]

Yes, it happened to me on 3 different PCs a couple of days ago, and I don't understand how this is possible. It must be a Windows update that broke something, idk...
Re-download the tool pack and overwrite the madvr folder, which should fix it.

[Gatorman3385]

Yes, it happened to me on 3 different PCs a couple of days ago, and I don't understand how this is possible. It must be a Windows update that broke something, idk...
Re-download the tool pack and overwrite the madvr folder, which should fix it.

That worked. Thanks.

[pancserzso]

I'm using a M1 mac and the only way to run the scripts is through a Windows ARM install in UTM, +1 more layer inside Windows to do the CPU emulation. The files can also only be shared by a loopback network share, which is super super slow, about 12 MB/s only!

The native SSD under macOS on the other hand is super fast, a 100 GB demux only takes a few seconds.

So I've spend a few hours trying to understand what's the heart of P7 -> P8 conversion.

Do I understand it correctly that it's basically these 3 commands?


ffmpeg -i $MKVFILE -c:v copy -bsf:v hevc_mp4toannexb -f hevc - | dovi_tool demux -

dovi_tool -m 2 mux --bl BL.hevc --el EL.hevc --discard -o P8.hevc

mkvmerge --output $MKVFILE-P8.mkv --compression 0:none --default-duration 0:24000/1001p P8.hevc --no-video --compression 1:none $MKVFILE


And do I understand it correctly that the last command can be simplified into:

mkvmerge --output $MKVFILE-P8mod.mkv P8.hevc --no-video $MKVFILE


Is this correct?

[Kuler087]

Seems right but you should have a look at @nekno script for MAC

https://github.com/nekno/DV7toDV8

[guest]

Yes I've noticed the warning when using the latest CM-Analyze, I don't think it matters. The output is the same as before.

Can confirm that this IS the case :)

v5.4.1 does not display those WARNINGS.

v5.5.0 does :(

[guest]

Has something changed with the audio conversions ??

I was sure that I had set it that when I encode audio, regardless of it's original bitrate, to would come out either as 1024 or 1536, but it's unchanged, keeping it's original bitrate.

I'll have to dig deeper.

EDIT:- I just figured it out, I wasn't adding the IGNOREBITRATE in the file name https://www.cosgan.de/images/smilie/konfus/a080.gif

Forgive me if I've asked this before (I have a very short term memory, sometimes).

I thought that 3-1 would encode any audio to EC3 at the bitrate set in the .bat.

[speedy]

You should not remove cmv4.0 unless maybe if you use the AppleTV 4K with Infuse (non-beta).
Cmv4.0 has superior tone mapping to the old cmv2.9 algo

Hey, have you had a chance to check if the Infuse beta implementation of cmv4.0 has the same issues as the Plex version on ATV?

Not yet, I have to get in the beta test group first but I'll definitely check it out.

Oh man, I'll have to re-inject everything with cmv4

haha, yes but it's worth it.

Infuse 7.7.2 beta support for CMv4 has been great in my early testing. The only downside is that I'm now likely going to want to go back through a number of my favorite releases and convert re-inject CMv4 metadata :scared:

[Kuler087]

Hey, have you had a chance to check if the Infuse beta implementation of cmv4.0 has the same issues as the Plex version on ATV?

Ha this sucks, the beta group is not available to users with monthly subscriptions :(

I'll have to wait for a public release because there's no way I buy a year subs of something I might never use.

https://i.ibb.co/Ws6BKK5/Capture-d-cran-2024-03-06-114710.png

@@ speedy did you test if the color bars cmv4.0 pattern looks as bad as on PLEX ?
https://slow.pics/c/VGBhNeQU

https://drive.google.com/file/d/1tv6bF-Pj8SCJjQGXz__11dKfo-vDTMgF/view?usp=drive_link

[pancserzso]

Seems right but you should have a look at @nekno script for MAC

https://github.com/nekno/DV7toDV8

Thanks for checking it, I started with nekno script, however the differences confused me.


it does the following:

mkvextract "$mkvFile" tracks 0:"$BL_EL_RPU_HEVC"
dovi_tool demux --el-only "$BL_EL_RPU_HEVC" -e "$DV7_EL_RPU_HEVC"
dovi_tool --edit-config "$jsonFile convert --discard "$BL_EL_RPU_HEVC" -o "$DV8_BL_RPU_HEVC"
dovi_tool extract-rpu "$DV8_BL_RPU_HEVC" -o "$DV8_RPU_BIN"
mkvmerge -o "$mkvBase.DV8.mkv" -D "$mkvFile" "$DV8_BL_RPU_HEVC" --track-order 1:0


It does demux + convert + extract-rpu, which I don't really understand.

[Kuler087]

yeah thats a waste of time. your ffmpeg pipe to dovitool approach is better

[pancserzso]

Thanks! I think the DoVi_Scripts demux + mux approach can be simplified into one command, then it's half the processing time, isn't it? Or you made it like this for special use cases which need the results from demux?

[Kuler087]

Thanks! I think the DoVi_Scripts demux + mux approach can be simplified into one command, then it's half the processing time, isn't it? Or you made it like this for special use cases which need the results from demux?

my script (MKV version) already use the ffmpeg pipe to dovi_tool approach unless you decide to set the following to NO:

set mux_all_audio=NO
set mux_all_sub=NO

I don't know why nekno script doesn't do that as well.


https://i.ibb.co/6NKVCdn/Windows-Terminal-HS9rxegi3p.gif

[pancserzso]

No, I mean your script has this in 2 lines:


"%ffmpeg_path%" -i "%filepath%%filename%%fileext%" -c:v copy -bsf:v hevc_mp4toannexb -f hevc - | "%dovi_tool_path%" demux - & set HDR="%TEMP%BL.hevc"& set EL="%TEMP%EL.hevc"& goto :nodemux



"%dovi_tool_path%" %dropH% %remove.4.0% -m 2 mux --bl %HDR% --el %EL% --discard -o "%output_path%%filename%_P8.hevc"


I believe these two could be a simple command, doesn't it?

[Kuler087]

i dont think you can demux and mux at the same time?? Tell me how please if its possible

[pancserzso]

i dont think you can demux and mux at the same time?? Tell me how please if its possible

I just asked quietvoid:
https://github.com/quietvoid/dovi_tool/discussions/290#discussioncomment-8697502

[Kuler087]

thanks, I'll look into it.

[speedy]

Ha this sucks, the beta group is not available to users with monthly subscriptions :(

I'll have to wait for a public release because there's no way I buy a year subs of something I might never use.

https://i.ibb.co/Ws6BKK5/Capture-d-cran-2024-03-06-114710.png

@@ speedy did you test if the color bars cmv4.0 pattern looks as bad as on PLEX ?
https://slow.pics/c/VGBhNeQU

https://drive.google.com/file/d/1tv6bF-Pj8SCJjQGXz__11dKfo-vDTMgF/view?usp=drive_link
Yes, I tested color bars with the CMv4 pattern on Infuse 7.7.2b1, and they look great: https://youtu.be/D4WJow-iOA0 (the steps are more visible IRL on the gradient than in the video)

I'd recommend throwing out those results that tested Dolby Vision with Plex on Apple TV. Plex for Apple TV doesn't have any support for Dolby Vision and instead just triggers the Apple TV to switch to Dolby Vision but then only plays back the HDR10 base layer, which is problematic for obvious reasons. This is well documented (https://www.reddit.com/r/PleX/comments/13cedvi/is_fake_dolby_vision_on_apple_tv_fixed_somethings/), and the Plex team continues to ignore it. It would be much better if they just triggered HDR10 instead so the Base Layer could be played back as intended.

[Kuler087]

I'd recommend throwing out those results that tested Dolby Vision with Plex on Apple TV. Plex for Apple TV doesn't have any support for Dolby Vision and instead just triggers the Apple TV to switch to Dolby Vision but then only plays back the HDR10 base layer,.

That is not true. All my results with plex are accurate otherwise all of my target brightness results would be the same

And I tested the RPU reaction before doing any test, see for yourself: https://drive.google.com/file/d/1Idl3gocvc2jm6aw53GdbQvGt2Oet5P_P/view?usp=drive_link

[pancserzso]

thanks, I'll look into it.

This is the solution
ffmpeg -i $MKVFILE -c:v copy -bsf:v hevc_mp4toannexb -f hevc - | dovi_tool -m 2 convert --discard - -o P8.hevc

[Kuler087]

Yes, I tested color bars with the CMv4 pattern on Infuse 7.7.2b1, and they look great: https://youtu.be/D4WJow-iOA0


I should have mentioned that my pics are from LLDV and the issue is a lot worse. In tv-led it looks better but still not right and I can see the same in your video, unfortunately.

[speedy]

That is not true. All my results with plex are accurate otherwise all of my target brightness results would be the same

And I tested the RPU reaction before doing any test, see for yourself: https://drive.google.com/file/d/1Idl3gocvc2jm6aw53GdbQvGt2Oet5P_P/view?usp=drive_link
Were you using the "Old Video Player" (aka AVPlayer) and a Profile 5 MP4 to get those results?

Even Plex Staff states they only support the Profile 5 in MP4 with AVPlayer currently: https://forums.plex.tv/t/plex-fireside-in-the-forums/851849/37

[speedy]

I should have mentioned that my pics are from LLDV and the issue is a lot worse. In tv-led it looks better but still not right and I can see the same in your video, unfortunately.
Are you certain?

It looks significantly different (better as in gradient steps are more clear) to my eyes than it does to the camera? I have no idea what I'm doing when it comes to taking pictures of a screen.

[Kuler087]

Were you using the "Old Video Player" (aka AVPlayer) and a Profile 5 MP4 to get those results?

Even Plex Staff states they only support the Profile 5 in MP4 with AVPlayer currently: https://forums.plex.tv/t/plex-fireside-in-the-forums/851849/37

I don't remember if it was the old or new player but my file tests were ALL in profile 8. I linked it, just try you will see that the RPU is indeed used ( L1+L8+L3)

[Kuler087]

Are you certain?

It looks significantly different (better as in gradient steps are more clear) to my eyes than it does to the camera? I have no idea what I'm doing when it comes to taking pictures of a screen.
Yes and it looks just like in your video.
I'm not home right now, but I can have a look again tonight.

[CineManiac]

Quick question, if a video's Mastering Display primaries are in BT.2020, rather than the usual P3, do we export the DV XML in Resolve with Rec.2020 Color Encoding Primaries?

[speedy]

Yes and it looks just like in your video.
I'm not home right now, but I can have a look again tonight.
I think I see what you're seeing more now... 1000 & 4000 nits color bar patterns look perfect, but the gradient doesn't look right after 4000 nits. I think Apple has basically ignored properly rolling off content beyond 4000 nits (I assume this is what you're getting at).

This is definitely annoying in pursuit of a perfect device, but I think this has minimal impact on real world content compared to being able to support TV-led, CMv4, Chroma Weight, accuracy under 4000-nits, etc.

[Kuler087]

Quick question, if a video's Mastering Display primaries are in BT.2020, rather than the usual P3, do we export the DV XML in Resolve with Rec.2020 Color Encoding Primaries?

Yes, always match your base layer primaries.

[Kuler087]

I think I see what you're seeing more now... 1000 & 4000 nits color bar patterns look perfect, but the gradient doesn't look right after 4000 nits. I think Apple has basically ignored properly rolling off content beyond 4000 nits (I assume this is what you're getting at).

This is definitely annoying in pursuit of a perfect device, but I think this has minimal impact on real world content compared to being able to support TV-led, CMv4, Chroma Weight, accuracy under 4000-nits, etc.


yes that makes sense and I agree

[CineManiac]

Thank you, that's what I assumed but there's so much about primaries in MediaInfo hah

[guest]

I think my simple question got lost in the wave of posts, that happened last night.

Forgive me if I've asked this before (I have a very short term memory, sometimes).

I thought that 3-1 would encode any audio to EC3 at the bitrate set in the .bat.

[Kuler087]

yeah we went offtopic a bit... sorry

only the MP4 version will encode any lossless audio to EC3.
For the other version, you have to opt in and the best lossless audio will be selected to encode EC3.

If you meant for Lossy audio to EC3, only 8-1-1 can do that and I don't think I will not add lossy audio encoding to the other workflows.

[guest]

yeah we went offtopic a bit... sorry

only the MP4 version will encode any lossless audio to EC3.
For the other version, you have to opt in and the best lossless audio will be selected to encode EC3.

If you meant for Lossy audio to EC3, only 8-1-1 can do that and I don't think I will not add lossy audio encoding to the other workflows.

Thats fine, it's good to see more ppl posting here :)

I will ALWAYS be using the MP4 workflow.

Yeah, I just thought that 3-1 did, in earlier builds, but like I said, I have short term memory loss, sometimes.

Seems like a bit more "manual" manipulation is required, but lossy audio in 3-1 would be very handy for me, as that will be the workflow I use more than any others.

Cheers.

[Kuler087]

lossy audio in 3-1 would be very handy for me,

maybe, I'll think about it. I don't personally use the MP4 container and because it always encode any lossless audio, it has its own audio converter script unlike other versions which use all the same code from 8-1-1.

[guest]

maybe, I'll think about it. I don't personally use the MP4 container and because it always encode any lossless audio, it has its own audio converter script unlike other versions which use all the same code from 8-1-1.

Not just for me, but all the LG TV owners that would be able to use it.

I went thru the procedure yesterday to get better audio in a 3-1 conversion...its a lot of steps outside your workflows :(

Maybe I should be using the MKV workflows, then use the MP4 muxer as the final step.....

[benwaggoner]

yes that makes sense and I agree
Vanishing little real-world content actually has pixels much brighter than 1000 nits in any case. Content with MaxCLL of 4000 generally indicates it was graded on a Dolby Pulsar, which was capable of going that high. Rarely will a statistical analysis find any pixels close to that. Pretty much everything graded in the last five years was done on a X300 or X310, which only go up to 1000 nits.

[speedy]

Vanishing little real-world content actually has pixels much brighter than 1000 nits in any case. Content with MaxCLL of 4000 generally indicates it was graded on a Dolby Pulsar, which was capable of going that high. Rarely will a statistical analysis find any pixels close to that. Pretty much everything graded in the last five years was done on a X300 or X310, which only go up to 1000 nits.
@benwaggoner, Do you think Amazon is working or open to fixing the issues we've identified with the Fire TV?

[Kuler087]

Not just for me, but all the LG TV owners that would be able to use it.

I went thru the procedure yesterday to get better audio in a 3-1 conversion...its a lot of steps outside your workflows :(

Maybe I should be using the MKV workflows, then use the MP4 muxer as the final step.....

Well the mp4 and ts version already makes LG compatible files. TVs can play lossy AC3/AAC audio so there's no need to convert them to EC3. This is why I'm not sure I want to add lossy to lossy encoding in the workflows. 8-1-1 suffice IMO and converting them to EC3 doesn't make them better.

P-S, you can install Kodi on WEBos( (https://kodi.wiki/view/HOW-TO:Install_Kodi_for_webOS)your tv might be too old though), it supports DV MKV. I've been using this for a couple of months now.

Vanishing little real-world content actually has pixels much brighter than 1000 nits in any case. Content with MaxCLL of 4000 generally indicates it was graded on a Dolby Pulsar, which was capable of going that high. Rarely will a statistical analysis find any pixels close to that. Pretty much everything graded in the last five years was done on a X300 or X310, which only go up to 1000 nits.

Thank's for the info Ben :)
I always appreciate industry insider Info/opinion.

[quietvoid]

@benwaggoner, Do you think Amazon is working or open to fixing the issues we've identified with the Fire TV?

Considering even Dolby can't get answers, I wouldn't hold my breath.
See: https://github.com/jellyfin/jellyfin-androidtv/issues/2630#issuecomment-1865421633

[guest]

Well the mp4 and ts version already makes LG compatible files. TVs can play lossy AC3/AAC audio so there's no need to convert them to EC3. This is why I'm not sure I want to add lossy to lossy encoding in the workflows. 8-1-1 suffice IMO and converting them to EC3 doesn't make them better.

P-S, you can install Kodi on WEBos( (https://kodi.wiki/view/HOW-TO:Install_Kodi_for_webOS)your tv might be too old though), it supports DV MKV. I've been using this for a couple of months now

Thank's for the info Ben :)
I always appreciate industry insider Info/opinion.

That's great, I have been wanting to install Kodi on the TV....I have one of those Xiaomi "box's", and initially it was great, but then I started to notice that certain video types would be rather stuttery, and that was annoying, so I went back to the standard LG player.

Hopefully I can figure out how it get this side loaded :)

I think it was Ben that mentioned somewhere recently that he had the same model LG that I have...

As mentioned, I will try the MKV workflow & MP4 muxer, see if that works the way I need. (No it didn't)

Cheers.

PS:- Success (sort of), I was able to get Kodi installed on the LG, but I cannot figure out why I can't access or even find any USB sticks that are plugged into the TV.

It seems it's a little different to the Kodi setup on the Xiaomi.

Any suggestions will be VERY welcome.

[madey83]

Hi Kuler087,

is is safe to trim dolbyvision videos? i would like to cut off first few seconds of clip with dovi 5/8.1 using staxrip.

Could you please confirm that this can be done without any impact of RPU data?

[guest]

Hi Kuler087,

is is safe to trim dolbyvision videos? i would like to cut off first few seconds of clip with dovi 5/8.1 using staxrip.

Could you please confirm that this can be done without any impact of RPU data?

One thing that you could do, is just cut whatever you want out of the video, and then simply "remake" it with workflow 3-1.

Do you need to use StaxRip ??

But there's probably a more involved way of doing this.

Whatever works for you.

[Kuler087]

Hi Kuler087,

is is safe to trim dolbyvision videos? i would like to cut off first few seconds of clip with dovi 5/8.1 using staxrip.

Could you please confirm that this can be done without any impact of RPU data?

Yes, it should be fine. I would check if the trimmed RPU still starts with a refresh scene flag (2-3, quick).


if it doesn't, you can fix it with a json edit.
{
"mode": 0,
"scene_cuts": {
"0-0": true
}
}

[Kuler087]

PS:- Success (sort of), I was able to get Kodi installed on the LG, but I cannot figure out why I can't access or even find any USB sticks that are plugged into the TV.

It seems it's a little different to the Kodi setup on the Xiaomi.

Any suggestions will be VERY welcome.

I use the composite addon and my PLEX library shows up in Kodi.

[guest]

I use the composite addon and my PLEX library shows up in Kodi.

That's an addon for Plex...I don't use Plex.

There must be a simple explanation why Kodi can't recognise any USB drives attached to the TV.

But I can't find any info :(

Does yours ??

[Kuler087]

No idea, never tried... Configuring a plex server on your PC is easy and much more practical than using a USB drive.

[Gatorman3385]

I'd like to go from 4K HDR to 1080 SDR. Do you think I could modify 8-2 to resize and use x264? I'd like to avoid encoding twice.

[Kuler087]

I'd like to go from 4K HDR to 1080 SDR. Do you think I could modify 8-2 to resize and use x264? I'd like to avoid encoding twice.

line 115 set downscale=YES

the script doesn't support x264.exe though, x265.exe only.
I can add add the option to use x264.exe in the next beta (when I have time).

ps: you'll get better sdr tone mapping than libplacebo if you use Dolby Vision(tuning balanced) in resolve.

[guest]

I'd like to go from 4K HDR to 1080 SDR. Do you think I could modify 8-2 to resize and use x264? I'd like to avoid encoding twice.

I really think you should be using other apps to do what you want !!!

DS is mainly for DV type encoding, etc.

I would strongly suggest either RipBot264 (my go to), StaxRip, or even Handbrake.

Curious why you want to use x264. Each to their own, I guess.

[guest]

No idea, never tried... Configuring a plex server on your PC is easy and much more practical than using a USB drive.

I have no need or interest in setting up a Plex server, I don't want to have a PC running, just to play some movies or TV series...

Would it be too much to ask, when you have some time and you're sitting in front of your TV, that you check if your Kodi will recognise a USB stick that's plugged into the TV ??

I have left a message on the Kodi forum asking about it on WebOS, yet to get a reply.

[Gatorman3385]

I really think you should be using other apps to do what you want !!!

DS is mainly for DV type encoding, etc.

I would strongly suggest either RipBot264 (my go to), StaxRip, or even Handbrake.

Curious why you want to use x264. Each to their own, I guess.

I've used StaxRip for HDR to SDR conversions before. I agree with @Kuler087 that Resolve produces better color. As far as why I would use x264, it's about compatibility while using Plex. I try to limit transcoding for outgoing streams. I keep a 4K 265 version for those that have 4K displays, and 1080 264 for those without.

[Fuso]

I think I found a universal format for playing on a non-DV TVs, older LGs, newer LGs - the so called fake Profile 5

HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : hev1

Container is mp4.
This file plays in HDR on a Samsung JS8000 (2015), AU9072 (2021), in Dolby Vision on LG B8 and C2.

[Kuler087]

I think I found a universal format for playing on a non-DV TVs, older LGs, newer LGs - the so called fake Profile 5

HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : hev1

Container is mp4.
This file plays in HDR on a Samsung JS8000 (2015), AU9072 (2021), in Dolby Vision on LG B8 and C2.

You don't have to do that on LG TVs, just use my script MP4 version and it will play on any LG TV.

[Fuso]

Yes, but then it won't play on Samsung TVs because the Codec ID will be dvhe, correct?
The other way is to mux to TS/M2TS but I don't like the seeking with that container, also the size is increased compared to mp4/mkv. If you can give me a solution to hybrid HDR10/HDR10+/DoVi P8 which will play on Samsung in HDR10/HDR10+ and at the same time in Dolby Vision on both older and newer LGs

[guest]

Did you try this:-

Originally Posted by Fuso View Post
The other not-so-official way to change the Codec ID is to use HxD to edit the converted mp4.

Instead of going from hev1 to dvhe, do the opposite.

Just thinking out loud.

[Kuler087]

Yes, but then it won't play on Samsung TVs because the Codec ID will be dvhe, correct?
The other way is to mux to TS/M2TS but I don't like the seeking with that container, also the size is increased compared to mp4/mkv. If you can give me a solution to hybrid HDR10/HDR10+/DoVi P8 which will play on Samsung in HDR10/HDR10+ and at the same time in Dolby Vision on both older and newer LGs

I don't know about Samsung. I could try it on my monitor (LS49CG9)

[Kuler087]

Instead of going from hev1 to dvhe, do the opposite.


must be dvhe for 2018 LG OLEDs.

[guest]

must be dvhe for 2018 LG OLEDs.

Yes, but Fuso wants it to play on his Samsungs...

Could you change something so the Codec ID was hev1 ??

I'm sure Fuso would be happy to be your "tester".

It also sounds like he's using the built in Samsung player, 'cause if he was using "streaming box" it would just play it.

I would doubt that playing it on your Samsung monitor wouldn't prove anything.

[Kuler087]

Could you change something so the Codec ID was hev1 ??


the script already offers both options. The next version will default to NEW because it doesn't make sense to use the old way only for one model(2018) of TV.


:: choose the mp4muxer version (OLD or NEW default = OLD) OLD works on (2018) LG TVS but Itunes P8 hybrid wont work if you dont fix the bitstream framerate first. And when it has to mux lossless audio or subs, the old mp4box needed will not properly set the BL compatibility ID which doesnt seem to cause issues though.
set mp4_version=OLD

[guest]

the script already offers both options. The next version will default to NEW because it doesn't make sense to use the old way only for one model(2018) of TV.

I shouldn't have doubted it :)

But I guess us "newbies" have to ask about these things, and know where to change them.

I will have to try a couple of different settings to see if this pending change might affect me.

Or will it simply be set mp4_version=NEW ?

Cheers

[Kuler087]

IIRC, when set to NEW, 7.1 EC3 encoding in MP4 is disabled because for some reason mp4box can't mux them... It's been a while since I updated mp4box, I'll check if a more recent version fix it.

[guest]

IIRC, when set to NEW, 7.1 EC3 encoding in MP4 is disabled because for some reason mp4box can't mux them... It's been a while since I updated mp4box, I'll check if a more recent version fix it.

OK, well, I don't use 7.1 anyway as my system (home theatre) doesn't support it.

I went looking for newer versions of both mp4muxers the other day, not sure how different they are, haven't used them.

EXTRA:- I haven't used DS for a couple of days, and today I copied everything over to another PC, and did some tests to see if I'd installed everything, and I eventually got 3-1 to work.
But 8-2-1 just isn't interested, on either PC, and I can't figure out what I've done :(

This is the small error msg:-

Failed to initialize VSScript
x265 [error]: unable to open input file <->

[Fuso]

I've used your file RPU fake P5 L1.L2.L3.L8_cmv40 (ATV) which has Codec ID dvh1, converted it to MKV then mux it again to mp4 but now with Codec ID hev1. I know that this is not an official Dolby format, but still it was the only compatible format with both Samsung and LG. Even the "geniuine" Profille 5 which is default dvhe or dvh1 when converted to hev1 plays again on older LGs in Dolby Vision and also on Samsung TV but of course in green and pink tint.

So
Profile 8 with dvhe plays in Dolby Vision on older and newer LGs, doesn't play on Samsung TVs (I don't have other non-DoVi brand to test it);
Profile 8 with hev1 plays in Dolby Vision on newer LGs, in HDR10 on older LGs, in HDR10/HDR10+ on Samsung TVs;
Profile 5 (real) with hev1 plays in Dolby Vision on older and newer LGs, in green and pink tint on Samsung TVs;
Profile 5 (fake) with hev1 plays in Dolby Vision on older and newer LGs, in HDR10/HDR10+ on Samsung TVs.

Profile 5 (fake) is the only way to have universal DoVi support across old and new LG TVs, and also HDR support on Samsung TVs, in mp4 container.

[Guest]

I have an LG SK8500PTA 55", and up until I started using DS, the only way I could play DV was to run the video thru tsmuxer to either .ts or .m2ts, but the seeking was terrible.

I don't know how my model relates to the LG B8 or C2. (it's late 2018)

But it will play a DV 8.0 (with embedded subtitles), or 8.1 (without subtitles, use separate .srt) as an mp4 dvhe (haven't tried hev1).

[Kuler087]

This is the small error msg:-

did you install vapoursynth and python

[Kuler087]

I have an LG SK8500PTA 55"
But it will play a DV 8.0 (with embedded subtitles), or 8.1 (without subtitles, use separate .srt) as an mp4 dvhe (haven't tried hev1).

good to know. Yeah seeking is much better in mp4 as long as it's --no-open-gop encode. Open GOP encode mp4 just freeze on my C2 if I FF/RW.

[guest]

did you install vapoursynth and python

I know I did (maybe the wrong versions), but it definitely seems like a VS error, and that's probably what triggers the x265 error, as well.

Will re-install them tomorrow.

[guest]

good to know. Yeah seeking is much better in mp4 as long as it's --no-open-gop encode. Open GOP encode mp4 just freeze on my C2 if I FF/RW.

Don't know what this means --no-open-gop encode, whatever your MP4 muxer produces.

[benwaggoner]

Don't know what this means --no-open-gop encode, whatever your MP4 muxer produces.
It is an encoder setting that forces Closed GOP encoding. In an Open GOP, a GOP can have leading B-frames before the first IDR that reference the prior GOP. Slightly more efficient encoding, but more complex for random access in some implementations.

[guest]

It is an encoder setting that forces Closed GOP encoding. In an Open GOP, a GOP can have leading B-frames before the first IDR that reference the prior GOP. Slightly more efficient encoding, but more complex for random access in some implementations.

Thanks, Ben, still as clear as mud, to me....but I don't really need to know, I don't go into it as deeply as some :)

Cheers.

[guest]

did you install vapoursynth and python

I think I've fixed this problem, it might have been a version problem, I was using VS R66, & Python 3.12...went back to R65 & 3.11.8.

So that error seems to be gone, however, now I've got this (using MP4 muxer):-

Drag and drop folder with files or a single file and press enter..."G:\Dovi_Encodes_MP4\New folder"
processing..."Game of Thrones S01 hdr sw_encoded.hevc"
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
[1/2] Parsing track "G:\Dovi_Encodes_MP4\New folder\Game of Thrones S01 hdr sw_encoded.hevc"...
hevc: ******************** 100%
[2/2] Saving output file(s) "G:\Dovi_Encodes_MP4\Game of Thrones S01 hdr sw_encoded_DV.mp4"...
written: ******************** 100%
processing..."Game of Thrones S01 hdr sw_encoded.mkv"
reading input tracks format/id/language...
done.
Error: The ID '0' has already been used for another destination file.
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
ERROR! Can't open input file: E:\Dovi_Temp_MP4\temps\temp.folder66\HDR.hevc
Error parsing command line!

I did an 8-2-1, and then an 8-1-1, renamed then, put them in a folder, and...........

I deleted everything I could find associated with this, and still got the same error.

SO THEN I TRIED:-

I muxed the .mkv (video), and .hevc (audio) together with MKVToolNix, ran that thru MP4 muxer, got this:-

Drag and drop folder with files or a single file and press enter..."G:\Dovi_Encodes_MP4\New folder\Game of Thrones S01 hdr sw_encoded (1).mkv"
processing..."Game of Thrones S01 hdr sw_encoded (1).mkv"
reading input tracks format/id/language...
done.
Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'E:\Dovi_Temp_MP4\temps\temp.folder66\HDR.hevc'. Container format: HEVC/H.265 elementary stream
Extracting track 1 with the CodecID 'A_EAC3' to the file 'E:\Dovi_Temp_MP4\temps\temp.folder66\Game of Thrones S01 hdr sw_encoded (1).track_2_und.ec3'. Container format: Dolby Digital Plus (E-AC-3)
Progress: 100%
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
ERROR: For dolby vision deprecated profiles 0, 1, 2, 3 and 6, no longer supported.

ERROR: For dolby vision deprecated profiles 0, 1, 2, 3 and 6, no longer supported.
Never seen this before ??

[Kuler087]

I did an 8-2-1, and then an 8-1-1, renamed then, put them in a folder, and...........
I deleted everything I could find associated with this, and still got the same error.



you must not have renamed your external audio correctly. I just tried and no issue...

Drag and drop folder with files or a single file and press enter...D:\test.hevc
processing..."test.hevc"
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
[1/3] Parsing track "D:\test.hevc"...
hevc: ******************** 100%
[2/3] Parsing track "D:\test.ec3"...
ec3: ******************** 100%
[3/3] Saving output file(s) "D:\test_DV.mp4"...
written: ******************** 100%


SO THEN I TRIED:-
I muxed the .mkv (video), and .hevc (audio) together with MKVToolNix, ran that thru MP4 muxer, got this:-
Never seen this before ??
Looks like you muxed the wrong/original video stream that is just HDR10 and not the P8 encoded hevc file.

[guest]

you must not have renamed your external audio correctly. I just tried and no issue...

Looks like you muxed the wrong/original video stream that is just HDR10 and not the P8 encoded hevc file.

Thanks, still learning the basic's :(

[guest]

the script already offers both options. The next version will default to NEW because it doesn't make sense to use the old way only for one model(2018) of TV.

I just did a quick test with this setting, and indeed, OLD produces a dehv, which plays as DV, but NEW produces hev1, which plays as HDR.

[guest]

Got everything running sweet again.

I did stuff up on those couple of 8-2-1 & 8-1-1 tests, sorry.

As for Python & VS, this is what I've done, I have both Python 3.9.13 & 3.12.2 installed to Windows, with R66 VS, then copied the contents of R65 portable to the VS folder in the tools pack.

Copying R66 portable to the VS folder caused some of those errors, so clearly a change between the 2 builds.

[Balthazar2k4]

Hi R3S3T, I have been following your script work from the MakeMKV and Firecore forums. Nice to see you got something here too. So I am still struggling with very slow performance using 3-1 in the script to convert HDR10 to DV. Your suggestion was to consider the Resolve workflow. Watchmen for example is going to take 51 hours to complete with CM_analyze which is absurd given I did Halloween in only a couple hours. So before I drop $300 on Resolve (which I don't know how to use either) do you feel that is the best overall workflow quality wise vs the script? Thank you for the awesome tutorials on your YouTube channel. That is the only reason I am even considering this.

[guest]

Hi R3S3T, I have been following your script work from the MakeMKV and Firecore forums. Nice to see you got something here too. So I am still struggling with very slow performance using 3-1 in the script to convert HDR10 to DV. Your suggestion was to consider the Resolve workflow. Watchmen for example is going to take 51 hours to complete with CM_analyze which is absurd given I did Halloween in only a couple hours. So before I drop $300 on Resolve (which I don't know how to use either) do you feel that is the best overall workflow quality wise vs the script? Thank you for the awesome tutorials on your YouTube channel. That is the only reason I am even considering this.

I have to ask, what is your system, 'cause that IS very slow, I know Watchmen is a pretty long movie, but that IS ridiculous :(

Have you changed any of the settings in the .bat/workflow ??

Surely you can "acquire" Resolve cheaper than that (if you get my drift, without actually saying it)

[Kuler087]

Watchmen for example is going to take 51 hours to complete with CM_analyze which is absurd

woah 51h , that's crazy!!!

do you feel that is the best overall workflow quality wise vs the script?

The script uses the same Dolby algo as Resolve so there will be no difference.

[Balthazar2k4]

I have to ask, what is your system, 'cause that IS very slow, I know Watchmen is a pretty long movie, but that IS ridiculous :(

Have you changed any of the settings in the .bat/workflow ??

Surely you can "acquire" Resolve cheaper than that (if you get my drift, without actually saying it)

I am using a Ryzen 9 7950X and RTX 4090. R3S3T suggested there is a known defect in CM_analyze with certain AMD processors that may be affecting me. When the process starts I am seeing less than half second per frame, but by frame 200000 I am seeing 3.5 seconds/frame. It is insane indeed.

So Resolve was going to be my alternative. Yes, I could acquire it through other means and Blackmagic also offers a 14-day return period too. I could just jump in and see, but my time is generally pretty limited for this stuff so learning a new piece of software may not be in the cards within my 14 day window :) As for the other ways to get the software, I prefer to pay for a license. That is more a personal choice than anything :)

My last option is to build a 13900KS machine and call it a day. Just make it my video workhorse... I always love an excuse to build another machine :)

What's funny is that I am not entirely sure how much any of this conversion really benefits me. I am using a PlayerOne 8K and Infuse (on occasion) for playback. The PlayerOne can use the VS10 engine to convert HDR10 to DV on the fly. I did a little testing last night and I am not actually sure I can see the difference between the HDR10 VS10 conversion vs the DV file created through the script :D

[Kuler087]

What's funny is that I am not entirely sure how much any of this conversion really benefits me. I am using a PlayerOne 8K and Infuse (on occasion) for playback. The PlayerOne can use the VS10 engine to convert HDR10 to DV on the fly. I did a little testing last night and I am not actually sure I can see the difference between the HDR10 VS10 conversion vs the DV file created through the script :D

It all depends on the content brightness and your TV.
Generated DV is only useful when the content exceeds your TV capabilities.
So do the same comparison with bright content. EG. Spears and munsil montage: https://youtu.be/4DBRGDwzGW4

[Balthazar2k4]

It all depends on the content brightness and your TV.
Generated DV is only useful when the content exceeds your TV capabilities.
So do the same comparison with bright content. EG. Spears and munsil montage: https://youtu.be/4DBRGDwzGW4

All my of my displays in the house are WOLED or QD-OLED. My primary living room display is a Sony 83A90J so definitely not a torch. I am sure the generated DV is probably pretty useful.

[guest]

I am using a Ryzen 9 7950X and RTX 4090. R3S3T suggested there is a known defect in CM_analyze with certain AMD processors that may be affecting me. When the process starts I am seeing less than half second per frame, but by frame 200000 I am seeing 3.5 seconds/frame. It is insane indeed.

So Resolve was going to be my alternative. Yes, I could acquire it through other means and Blackmagic also offers a 14-day return period too. I could just jump in and see, but my time is generally pretty limited for this stuff so learning a new piece of software may not be in the cards within my 14 day window :) As for the other ways to get the software, I prefer to pay for a license. That is more a personal choice than anything :)

My last option is to build a 13900KS machine and call it a day. Just make it my video workhorse... I always love an excuse to build another machine :)

What's funny is that I am not entirely sure how much any of this conversion really benefits me. I am using a PlayerOne 8K and Infuse (on occasion) for playback. The PlayerOne can use the VS10 engine to convert HDR10 to DV on the fly. I did a little testing last night and I am not actually sure I can see the difference between the HDR10 VS10 conversion vs the DV file created through the script :D

That's interesting, I also have a 7950X, but only an RTX 3060, but the machine I have been using DS on, is a 13900KF, with an RTX 3050, so I will be interested to see if the 7950X has any issues.

Also, what version of CM do you have, I recently updated, and I got some WARNINGS (I actually posted here about them a few days ago)

And TBH, I really can't tell a huge difference between HDR10 & DV on my LG TV, I think it's more the novelty of seeing the Dolby Vision show on the screen, instead of HDR.

[Kuler087]

That's interesting, I also have a 7950X, but only an RTX 3060, but the machine I have been using DS on, is a 13900KF, with an RTX 3050, so I will be interested to see if the 7950X has any issues.

Also, what version of CM do you have, I recently updated, and I got some WARNINGS (I actually posted here about them a few days ago)



Yes its a known issue with non-MAC systems and on some AMD chips its way worse.


Dolby response about it:

Our Professional Tools make use of Apple’s ProRes decoding library and we have identified performance bugs, including lack of GPU accelerated decoding on Windows and Linux, and a severe performance hit when running on some AMD chips, including their high-performance scalable EPYC chips.

Unfortunately, we are dependent on Apple updating their ProRes libraries to get this fixed.
Until we get an update from Apple, the only recommendation we can offer is to use JPEG2000 which has full GPU decoding support.

I'm sorry I can't give you any better news.
Let me know if there's anything else we can support with.

Thanks,

Michael


And TBH, I really can't tell a huge difference between HDR10 & DV on my LG TV, I think it's more the novelty of seeing the Dolby Vision show on the screen, instead of HDR.

Dolby generated L1 metadata is not too complicated to understand.
As soon as the brightness exceed your TV tmax in tv-led or edid in lldv, the picture gets tone mapped to your TV target brightness.

I made huge research about it on different devices here:
edit, oops wrong link,, here's the right one: https://docs.google.com/spreadsheets/d/1jBIGF8XTVi9VmDBZ8a5hEyongYMCDlUiLHU9n1f_S74/edit#gid=1222148710
For the manual trim passes on the other hand, the colorist have more room to play with contrast (gamma/lift/gain) and colors( saturation gain and chroma weight)

[Balthazar2k4]

So Resolve is definitely the way to go from a speed perspective. More manual work for sure, but my 51 hour CM_analyze was shrunk to 22 minutes in Resolve.

[CineManiac]

I’ll second the Resolve recommendation. I have an RTX 3080 and cm_analyze would really slow down. Resolve’s workflow is easy to grasp with r3s3t’s informative YT walkthroughs :)

[thirdmoon]

Reset while trying to extract Resolve cuts using 2-9 for Blade Runner 1982, I'm getting this error.
https://i.imgur.com/6zQBLlH.png

[Kuler087]

I dont know, I did this rpu recently and had no issues...
Did you install python?
Did you add the latest version of EDL_maker.py to your tools folder?
Did you try with other metadata that doesn't have an illegal per-frame L5 ?

[guest]

I just checked if there was a new Beta (all I can go on is the size (kbs), seems there might be a new one)

Is there like a changelog ?? just to know what's different ??

And a tiny little update could be made here:-

https://github.com/R3S3t9999/DoVi_Sc...-main-settings

Adding:- IGNOREBITRATE

Cheers.

[Kuler087]

only minor changes so far, no changelog yet

[guest]

only minor changes so far, no changelog yet

I think I've just figured out what's going on with the Beta's, you're always changing or adding, and you save it as a Beta, there.

It's 1kb bigger than the other day :)

[Kuler087]

right, the beta file is automatically synced to Google Drive as soon as I make any changes.

[Scaramanga]

I've got a setup of Shield 2019 through to LG TV utilising a Plex server and it can happily play native DV rips (Dune) and standard UHD rips (Sicario) from MKV
no issue.
When I have ran Sicario through the script (3-1) the film does trigger DV on the TV but there are blocky aspects when it comes to dark colours on light background and a few frames that are obviously awry.

Just wondered if I am doing something wrong in prepping the scripts, or do I need to invest in a Nvidia GFX card or a SSD to carry out the conversion work?

Thanks

[guest]

I've got a setup of Shield 2019 through to LG TV utilising a Plex server and it can happily play native DV rips (Dune) and standard UHD rips (Sicario) from MKV
no issue.
When I have ran Sicario through the script (3-1) the film does trigger DV on the TV but there are blocky aspects when it comes to dark colours on light background and a few frames that are obviously awry.

Just wondered if I am doing something wrong in prepping the scripts, or do I need to invest in a Nvidia GFX card or a SSD to carry out the conversion work?

Thanks

Just thought I'd add my 10 cents worth. (I'm still learning)

What are the spec's of your PC ??

Which .bat are you using, .mp4 or .mkv version ??

Is the original video good, without these blocky aspects, etc ??

As you haven't got an nVidia GPU, you can't be using NVENC, so that's not an issue.

There are a lot of "behind the scenes" settings, but default should be fine.

An SSD or Nvme would only speed up certain parts of the process.

[Kuler087]

I've got a setup of Shield 2019 through to LG TV utilising a Plex server and it can happily play native DV rips (Dune) and standard UHD rips (Sicario) from MKV
no issue.
When I have ran Sicario through the script (3-1) the film does trigger DV on the TV but there are blocky aspects when it comes to dark colours on light background and a few frames that are obviously awry.

Just wondered if I am doing something wrong in prepping the scripts, or do I need to invest in a Nvidia GFX card or a SSD to carry out the conversion work?

Thanks

3-1 just generates metadata, it doesn't touch the video in any way. So it's in your source and DV maybe makes it more obvious?

Also, it might be a cmv4.0 vs cm2.9 thing, on my 2023 Hisense TV, cmv4.0 looks wrong/bad. So you could try to remove cmv4.0 with 2-1-5 and if it is the source of the problem, you can configure the script to always remove it at line 101

[Balthazar2k4]

Out of curiosity, what is the best method of dealing with L5 on something like Interstellar with changing aspect ratios when using 3-1?

[Kuler087]

Choose the largest AR but your min and avg pq metadata won't be 100% accurate.

[thirdmoon]

Reset can we get folder processing for 6-7 in future release? Like a folder containing multiple png or tiff and the script generates heatmap and gamut map for all of them?

[Kuler087]

png/tiff input is just for when you want to check a specific frame.
If you want more frames, input a video file and the script will output as many frames as you have configured at line 125 (set frame_number=50)

[thirdmoon]

But those frames are random. I usually take 10-15 screenshots manually and then analyze them. This isn't super important, maybe in some future release if possible.

[Gatorman3385]

I often crop my encodes. Sometimes the original video will have L5 values that are odd, e.g. 0,0,143,143. Can cropping the BL to 0,0,144,144 negatively affect the DV presentation?

If so, would it be better to crop to one row less than the original L5 values, 0,0,142,142 then edit the L5 to 0,0,1,1?

[Kuler087]

Can cropping the BL to 0,0,144,144 negatively affect the DV presentation?


no

If so, would it be better to crop to one row less than the original L5 values, 0,0,142,142 then edit the L5 to 0,0,1,1?
that should be fine but I'm no encoding expert. Maybe leaving a 1-pixel row is a problem, I don't know, others can respond.

[guest]

I've been wanting to ask you if certain workflows are, or could be multi threaded ?

Also, would some workflows benefit from having multiple nVidia GPU's ?

With all the video's you post on Youtube, you must be processing a lot of stuff, a lot of the time.

Which leads me to also ask, I'd be interested in what spec's your PC(s) (or Mac's) are. ?

I've currently got a 7950X & a 13900KF, pretty much the top of the line "normal" desktop CPU's

But I haven't got any hi end 4000 series nVidia GPU's, hence the question about multi cards.

You can never have enough processing power & "speed" :)

[Kuler087]

You can run more than 1 workflow at the same time. I do it all the time.
My PC is similar to yours. I have an i9 13900ks + RTX3070 + 32gb ram.

What allows me to do all the screenshot comparisons and dv plots so quickly is the very fast nvme pci-4 drives (https://www.amazon.com/WD_BLACK-SN850X-Internal-Gaming-Solid/dp/B0B7CQ2CHH/ref=sr_1_6?crid=1LTR4525CXAHQ&dib=eyJ2IjoiMSJ9._RMR3uLmhBd_QCrWsipAZnqEWFxprb3CwkUXYxfsziGvneFxpB2XyGutynJh2ai90RJoTrExy4R0yz001ubQ53fNr8faBUqg-bDTR_9LjrOaozKlbvi_MYrjEIjFBv2trdr5GXfIc1W6Q9xC4vzS0FmQgXXNsouWgOxnQK3jd8zy59k0W49eSZP2NS0EiQhscepu6F0joiStN1g5CCeIbfcz67FtlT_-1ySvXunv48Y.WK9Nf-txr2P0bYvek4z7lVAUR28zGyJN4Gh-l1VMCwk&dib_tag=se&keywords=pci-e%2B4%2Bnvme&qid=1710933233&sprefix=pci-e%2B4%2Bnvme%2Caps%2C70&sr=8-6&th=1) I have. I even have one dedicated to my temp folder so any remuxing/demuxing is crazy fast (1-2gb/s)

[guest]

You can run more than 1 workflow at the same time. I do it all the time.

Now that IS good to know :), but I have to ask, if you're "feeding" 2 or 3 jobs into the same temp folder, is there going to be any naming conflicts ?

My PC is similar to yours. I have an i9 13900ks + RTX3070 + 32gb ram.

So you've got the "Big" 13900, nice. I have a 3050 on the i9, and a 3060 on the 7950X, yet to detemine which system will do things the fastest, with my RipBot encoding the 7950X is noticeably faster.

What allows me to do all the screenshot comparisons and dv plots so quickly is the very fast nvme pci-4 drives (https://www.amazon.com/WD_BLACK-SN850X-Internal-Gaming-Solid/dp/B0B7CQ2CHH/ref=sr_1_6?crid=1LTR4525CXAHQ&dib=eyJ2IjoiMSJ9._RMR3uLmhBd_QCrWsipAZnqEWFxprb3CwkUXYxfsziGvneFxpB2XyGutynJh2ai90RJoTrExy4R0yz001ubQ53fNr8faBUqg-bDTR_9LjrOaozKlbvi_MYrjEIjFBv2trdr5GXfIc1W6Q9xC4vzS0FmQgXXNsouWgOxnQK3jd8zy59k0W49eSZP2NS0EiQhscepu6F0joiStN1g5CCeIbfcz67FtlT_-1ySvXunv48Y.WK9Nf-txr2P0bYvek4z7lVAUR28zGyJN4Gh-l1VMCwk&dib_tag=se&keywords=pci-e%2B4%2Bnvme&qid=1710933233&sprefix=pci-e%2B4%2Bnvme%2Caps%2C70&sr=8-6&th=1) I have. I even have one dedicated to my temp folder so any remuxing/demuxing is crazy fast (1-2gb/s)

I have also dedicated an nvme to both the temp & encodes folders.

So, you didn't mention if the workflows might benefit from multiple GPU's ?

Thanks.

[Kuler087]

Now that IS good to know :), but I have to ask, if you're "feeding" 2 or 3 jobs into the same temp folder, is there going to be any naming conflicts ?

each workflow uses a different temp folder. You cant run the same workflow at the same time though, use the batch mode instead.

So, you didn't mention if the workflows might benefit from multiple GPU's ?
I don't know

[guest]

each workflow uses a different temp folder. You cant run the same workflow at the same time though, use the batch mode instead.

Thanks for clarifying that...

I just thought of something, if you had multiple dovi_script folders that have all the tools in them, but you sent them to different temp folders, you might be able to do multiples of the same workflow then...

I don't know

Well, I might have to test that, then.

[CineManiac]

Thanks for clarifying that...

I just thought of something, if you had multiple dovi_script folders that have all the tools in them, but you sent them to different temp folders, you might be able to do multiples of the same workflow then...



Well, I might have to test that, then.

I believe you’d need to use different drives since some workflows write some temp files to the root of the drive, which could potentially lead to conflicts. Checking for positive lifts writes .trim.offset.txt, etc., to the root of the drive, par exemple.

[Kuler087]

Only the L2 L8 L5 L6 plotter does that so as long as you don't run two instances of 6-4 or 6-5, it will be fine.

This is something I want to revisit though. This is also the reason why these workflows are disabled when your output path is on a C:\ drive.

[speedy]

it might be a cmv4.0 vs cm2.9 thing, on my 2023 Hisense TV, cmv4.0 looks wrong/bad.
Does CMv4 always look bad on the U8K?
Any idea what is wrong with it?

[guest]

I thought I had to demux the audio from my videos before using 8-1-1.

I had a folder of 22 videos, and just for "kick's" I loaded that folder into 8-1-1, and lo & behold it demuxed & converted only the audio tracks :)

That's going to save me a LOT of time, going forward.

The only issue is, I then have to rename them from the .mkv container, to .eac3 so that RipBot264 recognizes them. (could that be changed?)

So I'm guessing that 8-2-x might do the same to the video tracks.

[Kuler087]

I thought I had to demux the audio from my videos before using 8-1-1.

I had a folder of 22 videos, and just for "kick's" I loaded that folder into 8-1-1, and lo & behold it demuxed & converted only the audio tracks :)

That's going to save me a LOT of time, going forward.

The only issue is, I then have to rename them from the .mkv container, to .eac3 so that RipBot264 recognizes them. (could that be changed?)

So I'm guessing that 8-2-x might do the same to the video tracks.

Yes the script batch modes are very useful. You can batch demux the files with
https://www.videohelp.com/software/Inviska-MKV-Extract

But remember that any delay present will be gone.


Does CMv4 always look bad on the U8K?
Any idea what is wrong with it?


I don't know, I did a couple of tests when I bought it a while ago and it looked strange(could be the internal player) but I haven't rechecked because I got this TV only for monitoring my SDR to HDR conversion in Resolve since it can do 850nits at 100% and 2000nits at 25%.

[guest]

Yes the script batch modes are very useful. You can batch demux the files with
https://www.videohelp.com/software/Inviska-MKV-Extract

But remember that any delay present will be gone.

Thanks, I will give that a try, never heard of it, TBH.

I've been using gMKVExtractGUI for years, it sort of has a batch function, by adding multiple files.

Extra:- Just installed Inviska, and it's almost exactly the same as gMKVExtractGUI.

[Scaramanga]

I've got a setup of Shield 2019 through to LG TV utilising a Plex server and it can happily play native DV rips (Dune) and standard UHD rips (Sicario) from MKV
no issue.
When I have ran Sicario through the script (3-1) the film does trigger DV on the TV but there are blocky aspects when it comes to dark colours on light background and a few frames that are obviously awry.

Just wondered if I am doing something wrong in prepping the scripts, or do I need to invest in a Nvidia GFX card or a SSD to carry out the conversion work?

Thanks
Just an update on this as I appreciate the time and effort people put into helping others on this thread.

I tried the original rip and that too has the slight distorted blocky look on at least two of the scenes in the film (Sicario) so nothing to do with the DoVi scripts.

After a lot of trial and error debloating the Shield, tweaking the WiFi 6 card on the Plex server it's almost unnoticeable now and the effect doesn't occur on any of the other movies I've processed so I assume it's an issue with the disc itself or MakeMKV handling the rip?

[Gatorman3385]

When would it be necessary to edit L6 values when injecting DV to HDR?

[Kuler087]

editing L6 from retail DV is not necessary.
When you generate it in Resolve and use 1-1 to inject the XML, the script uses the maxcll/fall of the generated metadata.

Btw, I tested different L6 values during DV playback and it has no effect.

[Gatorman3385]

With different versions of DV available for some releases, how do they rank amongst themselves? Is it worth generating DV from Resolve if the UHD release has DV MEL, or is converting from DV5 to DV8 the better path?

[guest]

With different versions of DV available for some releases, how do they rank amongst themselves? Is it worth generating DV from Resolve if the UHD release has DV MEL, or is converting from DV5 to DV8 the better path?

Metadata
Dolby Vision metadata include:[15]

L0 (static): Mastering and target display characteristics
L1 (dynamic): Automatically generated
L2 trims (dynamic): Manually generated per frame or per scene
L3 trims (dynamic): Manually generated per frame or per scene (since CMv4.0)
L8 trims (dynamic): Manually generated per frame or per scene (since CMv4.0) (equivalent of L2 trims)
L5: Timeline aspect ratio description
L6 (static and optional): MaxCLL and MaxFALL (required for HDR10)
L9 (dynamic): Mastering display color primaries (since CMv4.0)
Dolby Vision 4.0 introduces new secondary trims for hue and saturation adjustment.[18]

Profiles
Dolby Vision profiles[19][20]
Profile Codec BL:EL resolution Backward compatibility
4 10-bit HEVC 1:1/4 SDR
5 10-bit HEVC No enhancement layer None (It uses proprietary IPTPQc2)
7 10-bit HEVC 1:1/4 for UHD
1:1 for FHD

Ultra HD Blu-ray
8 10-bit HEVC No enhancement layer HDR10 or SDR or HLG
9 8-bit AVC High or High Progressive Profile SDR
10 10-bit AV1 None or HDR10 or SDR or HLG
20 10bit MV-HEVC for 3D or HEVC for 2D None (It uses proprietary IPTPQc2)
Profiles not supported for new applications[19][20]

Profile Codec BL:EL resolution Backward compatibility
0 AVC 1:1/4 SDR
1 AVC 1:1 None
2 8-bit HEVC 1:1/4 SDR
3 8-bit HEVC 1:1 None
6 10-bit HEVC 1:1/4 HDR10
8 10-bit HEVC No enhancement layer

[Kuler087]

With different versions of DV available for some releases, how do they rank amongst themselves? Is it worth generating DV from Resolve if the UHD release has DV MEL, or is converting from DV5 to DV8 the better path?

The only times I generate DV for a movie that has retail DV are:

1- static L1 and L2. (Static L1 + dynamic L2 is fine.)
2- P5 web-dl is a different grade and cant be injected into the bluray
3- The original DV was done in cmv2.9(2.5nits avg floor) without any manual trims
4- if the bluray is cmv2.9 MEL and web is 4.0, I injected the web metadata like in: Aquaman and the Lost Kingdom, Migration.2023, Wonka.2023, The.Hunger.Games.The.Ballad.of.Songbirds.and.Snakes.2023
Why? because cmv2.9 content has crushed/clipped black and cmv4.0 does not. It also has better tone mapping.


PS Ugoos AM6B+ has arrived and looks VERY promising: https://www.youtube.com/watch?v=4QUURfLy5ew

[Hellboy.]

I can use DoVi_Scripts to extract HDR10+ from a REMUX and then add the HDR10+ data to another REMUX? How?
Thanks.

[Kuler087]

Yes, 6-6 to export and then 1-1 to inject/resync.
Obviously, you have to make sure its the same HDR grade first.

[jayper]

The only times I generate DV for a movie that has retail DV are:

1- static L1 and L2. (Static L1 + dynamic L2 is fine.)
2- P5 web-dl is a different grade and cant be injected into the bluray
3- The original DV was done in cmv2.9(2.5nits avg floor) without any manual trims
4- if the bluray is cmv2.9 MEL and web is 4.0, I injected the web metadata like in: Aquaman and the Lost Kingdom, Migration.2023, Wonka.2023, The.Hunger.Games.The.Ballad.of.Songbirds.and.Snakes.2023
Why? because cmv2.9 content has crushed/clipped black and cmv4.0 does not. It also has better tone mapping.


PS Ugoos AM6B+ has arrived and looks VERY promising: https://www.youtube.com/watch?v=4QUURfLy5ew

Appreciate your sharing your findings on the Ugoos, I am very close to picking one up.

What container type are you using for playback? mp4? I've been using an Oppo for the last few years, so I invested heavily in ts. Do you see any sort of variance in playback or stability? I could always remux, but was just curious.

[Kuler087]

The test files used in this video are MP4, but I use the P7/P8/P5 MKV container for movies/tv shows.
I only watched one P7 ST-DL FEL MKV movie(primal fear) yet and it played flawlessly with DV+ TrueHD from start to end. FF/RW, seeking and resume work very well too.

I haven't tried TS yet but it should be fine. It doesn't support DT-DL DV rip but Mkvtoolnix can mux them to ST-DL just fine.

I'll do more comparisons this weekend...

[jayper]

Thanks very much. Always appreciate your time and insights. Sounds promising, it looks like I may need to place and order :)

[Hellboy.]

Yes, 6-6 to export and then 1-1 to inject/resync.
Obviously, you have to make sure its the same HDR grade first.

I use 6-6 and get the .json and .png. Then use the 1-1 to inject the .json file without problems.

But in 1-1 ask: "Do you want to re-sync the metadata? If yes, enter a frame number. E.G.: -24 or 24 and/or press enter..."

I just press enter. How i can check in what frame the HDR10+ start in the old video to use the same in the new video.

The 2 videos are remuxes from the same source, but in the HDR10+,
"Maximum Content Light Level and Maximum Frame-Average Light Level"
are modify.

[Kuler087]

Check the P8 Hybrid maker tutorial. I explain how to find the frame difference between two sources and how to verify if your final video is in sync with the metadata.

https://www.youtube.com/watch?v=hVWZpat34oc

[frandan]

Hi to everyone,
I tried a 6.2 workflow (Measure MadVR HDR) but i obtained a "test.mkv.measurements.incomplete" file and a related alert on cmd, where test.mkv is my BL.
From this point, the script stopped working corretcly not founding the expected " test.mkv.measurements" file.
Something wrong in my setup?
Thanks in advance for your replies

[Kuler087]

madvr will fail to measure some files. It usually happens with the TS/M2TS container and remuxing to MKV usually fixes the issue but your input is already MKV so unless you get the same result for all your files, there's nothing you can do about it unfortunately.
Is it an untouched bluray rip or some encode?

[frandan]

First of all thank you for the quick answer.
It's LOTR Fellowship of the Rings part 1 disc, demuxed with dgdemux and incapsulated in mkv with mkvtoolnix.
I'll try with a different disc, probably Back to the future that is in your black list :).
About it i understood that ,for this kind of movies, dovibaker is necessary for basic HDR10 rip too (without DoVi metadata).
Is it correct?
Thanks in advance

[MoonKnight]

Hey Kuler

Any reason why we must use balanced algorythm now ? I thought most highlight most details was the best ?

[Kuler087]

for this kind of movies, dovibaker is necessary for basic HDR10 rip too (without DoVi metadata).
Is it correct?
Thanks in advance

The movies that expand brightness requires a player that fully supports FEL P7. If not , you can use the dovi_baker to map the BL brightness to the EL which is what does a Profile 7 player.

For HDR10 playback, this is not required.

[Kuler087]

Hey Kuler

Any reason why we must use balanced algorythm now ? I thought most highlight most details was the best ?

You can use any tuning you prefer (line 107). I changed the default mode to match Davinci Resolve default. The tunings are user preference and none of them is wrong.

https://professionalsupport.dolby.com/s/article/Dolby-Vision-analysis-tuning-in-CMv-4-0-FAQs?language=en_US

[frandan]

The movies that expand brightness requires a player that fully supports FEL P7. If not , you can use the dovi_baker to map the BL brightness to the EL.

For HDR10 playback, this is not required.

Thank You Kuler.
Excuse me but i don't understand a point: If i compare BL only rip (HDR10) and BL+EL rip obtained using Dovibaker but without DoVi metadata injection (i suppose HDR10), do they looks the same on HDR device?

[Kuler087]

do they looks the same on HDR device?

No. if FEL expands the brightness, the baked HDR10 file will look much brighter and possibly clipped depending on your TV capabilities.

[frandan]

So it should be correct using dovibaker also for "simply" HDR rip , obviously when FEL modifies brightness, or no?

[Kuler087]

It depends on your TV capabilities.
If you have a 2000nits+ TV, yes but if you have a 1000nits or less TV, no you will just introduce more tone mapping/clipping.

[guest]

I read on another thread that the latest dovi_tool supports AV1, but looking thru the changelog of older builds, it looks like it might have supported it for some time...

Do you have any plans on using AV1 ??

I have no experience with it, not sure if it's a different way to process a .hevc, or if it's simply AV1 ??

[Boulder]

Regarding AV1 and DoVi, is it actually possible to use the original FEL and encoded AV1 to create a working DoVi mux? That would make things very interesting now that there are Android boxes that are very close to handling things properly with CoreELEC.

[Kuler087]

I'm not familiar with the av1 codec and I don't see any documentation on the dovi_tool page... What's the correct file extension? avif? ivf? av1? Does the RPU need to be edited? Does anyone have a sample?

dovi_tool.exe inject-rpu -i D:\1.ivf --rpu-in D:\1.bin -o D:\injected.ivf
Error: Invalid input file type.

the original FEL and encoded AV1 to create a working DoVi mux?

I doubt it since the EL would need to be av1 too I suppose and it's already not recommended to re-encode the FEL hevc stream.

[quietvoid]

AV1 isn't supported by dovi_tool. Only the internal library can handle AV1 RPUs for use in other software.

[Kuler087]

PS: I found an issue (https://slow.pics/c/z5XCkMkP) when converting Profile 5 to HDR10 or SDR with avisynthplus+libplacebo, I cannot get the color right and only when I use vapoursynth+libplacebo the output is right. So if someone is converting P5 video, he should update to the latest beta right now(update your tools pack too).

I've tried in staxrip and it's exactly the same issue when you use avisynth. Sorry for not noticing earlier, I rarely convert P5 videos.

Just a comeback on this issue. It turns out that the problem was the avs_libplacebo(2023-06-27) I was using.

https://slow.pics/c/88LnYnGa (ps The comparison has HDR metadata and can be viewed in HDR on browser that supports it like Chrome)

It doesn't matter for the encoding workflows because they now use vapoursynth but it does matter for the screenshots workflow (7-2) when you work with P5 files.

Just replace replace your libplacebo with this one: https://drive.google.com/file/d/1DgsKbK92So5KZVU15zC2-qN_tVeqZ_Bj/view?usp=drive_link

This means you can use the old script version if you prefer avisynth for frameserver for whatever reason.

[frandan]

Hi Kuler excuse me but i have another question: i ripped 1000 frames from a movie for testing. Would i inject the rpu referred to this 1000 frames? How can i extract these metadata only for 1000 frames? Can Dovi Scripts help me?

EDIT: I tried with mkvtoolnix with split-parts: Is it a possible way?

[Kuler087]

I'm not sure I understand what you're trying to do. When you just want to read the metadata from a specific frame, you just have to extract the whole rpu and then input it in 2-2 which will ask you if you want to check a specific frame.

[frandan]

Excuse me: What i wrote isn't really comprehensible.
I try to explain better: I ripped 1000 frames from BL (HDR10) trimming with avisynth.
Now i would inject the DoVi metadata in this 1000 frames and i suppose that i should extract dovi metadata for this 1000 frames.
Is it correct?

[Kuler087]

Inject the metadata in the original/whole file and then split it with mkvtoolnix if you want to keep the RPU in sync.

If you split the first 1000 frames of a video and then inject the original RPU, it will be fine and dovi_tool will remove the extra frames at the end.
But if you split some random 1000 video frames in the middle of a movie, you have to also trim the RPU exactly the same to match the splitted video.

[frandan]

Thank you again.
My idea was to trim the EL via mkvtoolnix and then i extract the rpu from trimmed EL.
In this way i hoped to do some test without full encoding
I'll do how you suggest or i'll take frames at the beginning of the movie
Bye

[TheHooligan95]

I think you're a fantastic person and I wish I could have even a tenth of your knowledge. Thanks for your work, OP. Truly.

For anyone noob like me (I learnt today everything I know about DV), I didn't really understand the installation instructions. Here's what I did that ended up making it work on Windows 11.

1) Created a folder in the root of a different hard drive from C: e.g. D:\doviscripts\
2) Download latest dovi scripts and then dovi scripts beta aswell from the github and put them into the dovitools folder.
3) created a tools folder within dovitools
4) downloaded https://forum.doom9.org/showthread.php?t=183479 and copied the contents of the tools folder inside the tools folder
5) downloaded and installed all things pointed out in the github.
6) copied and pasted all files from all things installed from the github also inside the tools folder, just to be sure
7) added both user and system paths to all things installed from the github, as specified here https://github.com/R3S3t9999/DoVi_Scripts/blob/main/TOOLS%20%26%20INSTALLATION (of course, not to the tools folder but to their og folders, and I skipped DEE because you can't download it if you're not in the business of making movies)
8) downloaded and installed justdan96/tsMuxer from his github and put it inside the tools folder


I hope this will come in handy to any other desperate users like me. :thanks:

[guest]

Hi Kuler,

I grabbed this movie earlier today, and was surprised that MediaInfo stated it was a DV encode, but as it's was .mkv, I knew it wouldn't play on my LG, so I quickly ran it thru Mp4 muxer, and it changed completely, and doesn't display either HDR or DV on the LG, the original .mkv didn't display HDR either....what a mess, so I thought I'd share the before & after MediaInfo, info:-

So this is the original .mkv

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, Profile 8, dvhe.08.06, BL+RPU, no metadata compression
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 18 min
Width : 3 840 pixels
Height : 1 604 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 : 10 bits
Writing library : x265 3.5+1-f0c1022b6:[Linux][GCC 7.5.0][64 bit] 10bit
Encoding settings : cpuid=1111039 (tl:dr)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

And then to this after MP4muxer:-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 2 h 18 min
Bit rate : 5 998 kb/s
Maximum bit rate : 32.6 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Original height : 1 604 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 : 10 bits
Bits/(Pixel*Frame) : 0.041
Stream size : 5.78 GiB (94%)
Writing library : x265 3.5+1-f0c1022b6:[Linux][GCC 7.5.0][64 bit] 10bit
Encoding settings : cpuid=1111039 (tl:dr)
Default : Yes
Alternate group : 1
Encoded date : 2024-04-10 05:41:53 UTC
Tagged date : 2024-04-10 05:42:11 UTC
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : hvcC

[Boulder]

The transfer characteristics is incorrect in both files so it's no wonder the HDR mode is not switched on.

[guest]

The transfer characteristics is incorrect in both files so it's no wonder the HDR mode is not switched on.

Yeah, I knew that had to be wrong... I just wanted to post this to show how some people just get it all wrong.

It'll be "fun" fixing it :)

[Kuler087]

I think you're a fantastic person and I wish I could have even a tenth of your knowledge. Thanks for your work, OP. Truly.


Thanks :)

FYI, I did an installation tutorial video last night:

https://www.youtube.com/watch?v=6SLtsVDse2w


Hi Kuler,

I grabbed this movie earlier today, and was surprised that MediaInfo stated it was a DV encode, but as it's was .mkv, I knew it wouldn't play on my LG, so I quickly ran it thru Mp4 muxer, and it changed completely, and doesn't display either HDR or DV on the LG, the original .mkv didn't display HDR either....what a mess, so I thought I'd share the before & after MediaInfo, info:-

So this is the original .mkv




Yeah, this is not common. Maybe someone attempted to make a profile 8.2 rip if that even possible ?

https://i.imgur.com/IpE40nt.png

[guest]

Yeah, this is not common. Maybe someone attempted to make a profile 8.2 rip if that even possible ?

I had a bit of a play with this mess, and I'm not going to waste anymore time on it, it's not worth it.

I did a quick conversion to BT2020, but it's looks crap, too dark, too red'ish.

I'll just get a better "proper" copy.

[guest]

Hi Reset,

I have a question about a couple of settings..

I have been editing GoT episodes, and I have them looking pretty nice as HDR, however, after I run them thru 3-1, the video is noticeably brighter, which basically negates the adjustments I made prior.

The original video is:-

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0020 cd/m2, max: 1000 cd/m2

and the DS DV encode is the same:-

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0020 cd/m2, max: 1000 cd/m2

So what option do I need to use here:-

BL Mastering Display Luminance and Colors:
min: 0.0020 cd/m2, max: 1000 cd/m2 BT.2020
------------------------------------------------

What is the Mastering Display? Choices are: 1000nits-P3= 20(default) / 1000nits-BT2020= 21 / 4000nits-P3= 7 / 4000nits-BT2020= 8 / 2000nits-P3= 30 / 2000nits-BT2020= 31

I've been using.. 1000nits-BT2020= 21

I'm still using 2.0.3, not that that should matter with this.

Maybe a simple solution might be to not do any colour/brightness changes beforehand (with these files, anyway)..I guess I'll figure out what needs to be done before the DS DV conversion.

Regards

[Kuler087]

Yes you should always match your source mastering luminance and primaries so 21 is correct. Generataed DV is just brightness metadata for tone mapping, it doesn't touch the colors like the L2-L8 trim pass can do.
Maybe your TV is like my old LG C8 where OOTB, DV looked so much brighter than HDR10 regardless of the content.

PS This show already has DV, why are you generating DV?

[guest]

Yes you should always match your source mastering luminance and primaries so 21 is correct. Generataed DV is just brightness metadata for tone mapping, it doesn't touch the colors like the L2-L8 trim pass can do.
Maybe your TV is like my old LG C8 where OOTB, DV looked so much brighter than HDR10 regardless of the content.

PS This show already has DV, why are you generating DV?

Thanks for the reply, so as a reference, moving forward, I will match the source with the options available.

I will have to compensate my color corrections, prior to running DS.

I generally like to reduce any redness, and maybe brightness, a little, more than anything.

Yes, I'm sure that GoT is available with DV, but the 4K copies I have are a little old, so I'll just convert them, thanks to DS :)

Cheers.

[Kuler087]

Instead of touching the BL , you could add some desaturation in the L2 trims like this:

change the duration("duration": 120000,) value to match your RPU framecount and run:
dovi_tool.exe generate -j X:\edits.json -o X:\P8_generated.bin

Then copy the generated L2 to your generated RPU from 3-1. You can do that with workflow 2-6


{
"cm_version": "V29",
"profile": "8.1",
"long_play_mode": false,
"source_min_pq": 7,
"source_max_pq": 3079,
"level5": {
"active_area_left_offset": 0,
"active_area_right_offset": 0,
"active_area_top_offset": 0,
"active_area_bottom_offset":0
},
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 20,
"max_content_light_level": 0,
"max_frame_average_light_level":0
},
"shots": [
{
"start": 0,
"duration": 120000,
"metadata_blocks": [
{
"Level1": {
"min_pq": 0,
"max_pq": 2081,
"avg_pq": 1229
}
},
{
"Level2": {
"target_max_pq": 2081,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1950,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2000,
"ms_weight": 2048
}
}
]
}
]
}

you can play the the trim_saturation_gain values. Values under 2048 desaturate.

[guest]

Instead of touching the BL , you could add some desaturation in the L2 trims like this:

change the duration("duration": 120000,) value to match your RPU framecount and run:
dovi_tool.exe generate -j X:\edits.json -o X:\P8_generated.bin

Then copy the generated L2 to your generated RPU from 3-1. You can do that with workflow 2-6


{
"cm_version": "V29",
"profile": "8.1",
"long_play_mode": false,
"source_min_pq": 7,
"source_max_pq": 3079,
"level5": {
"active_area_left_offset": 0,
"active_area_right_offset": 0,
"active_area_top_offset": 0,
"active_area_bottom_offset":0
},
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 20,
"max_content_light_level": 0,
"max_frame_average_light_level":0
},
"shots": [
{
"start": 0,
"duration": 120000,
"metadata_blocks": [
{
"Level1": {
"min_pq": 0,
"max_pq": 2081,
"avg_pq": 1229
}
},
{
"Level2": {
"target_max_pq": 2081,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1950,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2000,
"ms_weight": 2048
}
}
]
}
]
}

you can play the the trim_saturation_gain values. Values under 2048 desaturate.

:thanks:

Might take me a while to figure out how to do this ...

How do I check the RPU's framecount ?

[Kuler087]

input a rpu in 2-2

https://i.ibb.co/74VyCdj/Capture-d-cran-2024-04-24-085433.png

[guest]

input a rpu in 2-2

:thanks:

[guest]

OK, I have kind of figured out what to do with this, (I created the .json file) but you say to load the RPU from the original video, well, what if it isn't DV ?? where does the RPU come from ??

I run 3-1 to get the framecount (this test I'm doing had 7209 frames) it's a sample chunk generated with 8-5.


Which RPU level(s) do you want to copy and press enter... (Choices are 1 2 3 4 5 8 and you can select multiple values) ??

I used "8"..

Also, where do I change the trim_saturation_gain values ?, there's several to choose from (or all of them) ?

Can brightness/luminance be changed ?

Using 2-2 to check each .bin, (until there are any saturation changes, etc), they should be exactly the same ??

So once the "new" .bin is generated, how is it injected info the converted video ??

I'm thinking it might still be a better option to compensate for what DS does, with the previous adjustments..we'll see, I guess.

[Kuler087]

1- Generate DV with 3-1

2- create json with the framecount from the rpu generated in 3-1 step one
the json has three targets of metadata for Level 2 (not L8): 100(2081), 600(2851), and 1000nits(3079). You can use the json exactly as provided or edit it as much as you want.
Value under 2048 desaturates and usually, the 100nits trim has the stronger values followed by the 600 and 1000nits trims. The value at each target should be different for the interpolation to work properly.

3- run the cli to generate the RPU with L2 adjustments

4- Workflow 2-6, input 1 is rpu from step one and input 2 is the rpu from step 3. Select ''2''

5- inject the final rpu (the one with ''l2 copied'')


If you want to do the same for the CMv4.0 bloc (your tv is cmv2.9):

{
"cm_version": "V40",
"profile": "8.1",
"long_play_mode": false,
"source_min_pq": 7,
"source_max_pq": 3079,
"level5": {
"active_area_left_offset": 0,
"active_area_right_offset": 0,
"active_area_top_offset": 0,
"active_area_bottom_offset":0
},
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 20,
"max_content_light_level": 0,
"max_frame_average_light_level":0
},
"shots": [
{
"start": 0,
"duration": 120000,
"metadata_blocks": [
{
"Level1": {
"min_pq": 0,
"max_pq": 2081,
"avg_pq": 1229
}
},
{
"Level2": {
"target_max_pq": 2081,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1950,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2000,
"ms_weight": 2048
}
},
{
"Level8": {
"length": 19,
"target_display_index": 1,
"trim_slope": 1950,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048,
"target_mid_contrast": 2048,
"clip_trim": 2048,
"saturation_vector_field0": 128,
"saturation_vector_field1": 128,
"saturation_vector_field2": 128,
"saturation_vector_field3": 128,
"saturation_vector_field4": 128,
"saturation_vector_field5": 128
}
}
]
}
]
}

[guest]

1- Generate DV with 3-1

2- create json with the framecount from the rpu generated in 3-1 step one
the json has three targets of metadata for Level 2 (not L8): 100(2081), 600(2851), and 1000nits(3079). You can use the json exactly as provided or edit it as much as you want.
Value under 2048 desaturates and usually, the 100nits trim has the stronger values followed by the 600 and 1000nits trims. The value at each target should be different for the interpolation to work properly.

3- run the cli to generate the RPU with L2 adjustments

4- Workflow 2-6, input 1 is rpu from step one and input 2 is the rpu from step 3. Select ''2''

5- inject the final rpu (the one with ''l2 copied'')

Oh, RPU's are the .bin files.

Step #2 (have no idea what that's about)

OK, I'm good 'til step #5...what workflow do I use to inject ??

I haven't done these steps before, so I'm a little lost :(

Sorry.

[Kuler087]

you inject the final rpu with 1-1

[guest]

you inject the final rpu with 1-1

:thanks:

[guest]

If I have a DV movie that I want to filter, etc with RipBot264, and I extract the RPU.bin beforehand, then inject it after the filtering etc, would it be compatible ??

Not really wanting to do any Resolve fiddle.

Also, earlier today I started 3-1'ing an edited episode of GoT, and it was going to take, I'm guessing at least 3 - 4 hours to convert, I think I know why, but I had to stop it part way thru, just WAY TOO LONG :(

I was using CUDA on an RTX3060 (not fast enough), but would the 7950X or the 13900KF be faster than CUDA ??

Shame :(

[Kuler087]

If I have a DV movie that I want to filter, etc with RipBot264, and I extract the RPU.bin beforehand, then inject it after the filtering etc, would it be compatible ??
Depends on what filtering you do. If you change blacks or brightness, the metadata are no longer valid.

Not really wanting to do any Resolve fiddle.
Also, earlier today I started 3-1'ing an edited episode of GoT, and it was going to take, I'm guessing at least 3 - 4 hours to convert, I think I know why, but I had to stop it part way thru, just WAY TOO LONG
I was using CUDA on an RTX3060 (not fast enough), but would the 7950X or the 13900KF be faster than CUDA ??

CM_analyze is inconsistent and there's nothing we can do about it. Resolve (or MACos?) is the only other option.

[Gatorman3385]

CM_analyze is a great option if you don't own Resolve. However, using Resolve to generate DV was enough for me to make it a worthy investment.

Am I correct that CM_analyze is more consistent with Intel + CUDA than with AMD + CUDA?

[Kuler087]

supposedly

Am I correct that CM_analyze is more consistent with Intel + CUDA than with AMD + CUDA?

[jayper]

Reset, are these the steps you followed to get your Ugoos up and running? https://discourse.coreelec.org/t/guide-ugoos-am6b-coreelec-installation/51231

It looks like my device is set to be delivered today!

[Kuler087]

Yes, except that I'm still using an old 20.5 build because I have some movies that won't resume in v21.

[jayper]

Yes, except that I'm still using an old 20.5 build because I have some movies that won't resume in v21.
Thank you so much!

[Balthazar2k4]

Is it possible to batch process the 8-2-3 ProRes workflow? I would like to queue up some titles to convert to ProRes overnight so that I can run them through Resolve that next day.

[Kuler087]

You can use Staxrip for that. Here's my prores template: https://drive.google.com/file/d/1KUsOsSS-4NnXhDxqJMF4yOCwtprfZkxZ/view?usp=sharing
Put it in StaxRip\Settings\Templates

[Balthazar2k4]

Awesome! Much appreciated! I'll give it a try.

[jayper]

When you want to create a ST-DL MKV from a disc with FEL/MEL, what process do you recommend? Rip with MakeMKV, or with MKVToolNix? I am particularly curious about discs with seamless branching? I used to demux everything with TSMuxer first, now I am not so sure if there's a better/recommended route.

[Kuler087]

I've always used tsmuxer to demux the audio from seamless branching discs. Then mkvtoolnix to mux the video + demuxed audio + subs.
dgdemux or the latest eac3to might be even better, I don't know but I never had issues using tsmuxer on my x800m2. So far so good on the Ugoos but I'm not sure if I've watched a SB rip yet.

[jayper]

I've always used tsmuxer to demux the audio from seamless branching discs. Then mkvtoolnix to mux the video + demuxed audio + subs.
dgdemux or the latest eac3to might be even better, I don't know but I never had issues using tsmuxer on my x800m2. So far so good on the Ugoos but I'm not sure if I've watched a SB rip yet.
Thanks, appreciate the response and the perspective. I'll give that a try. I also had great luck with tsmuxer and my Oppo, so I was inclined to stick with it.

[jayper]

The only times I generate DV for a movie that has retail DV are:

1- static L1 and L2. (Static L1 + dynamic L2 is fine.)
2- P5 web-dl is a different grade and cant be injected into the bluray
3- The original DV was done in cmv2.9(2.5nits avg floor) without any manual trims
4- if the bluray is cmv2.9 MEL and web is 4.0, I injected the web metadata like in: Aquaman and the Lost Kingdom, Migration.2023, Wonka.2023, The.Hunger.Games.The.Ballad.of.Songbirds.and.Snakes.2023
Why? because cmv2.9 content has crushed/clipped black and cmv4.0 does not. It also has better tone mapping.


PS Ugoos AM6B+ has arrived and looks VERY promising: https://www.youtube.com/watch?v=4QUURfLy5ew

I'm guessing that all the Star Wars D+ shows fall into this camp. Spot-checked a few Andor episodes and it looks like static L2. Thinking about generating DV using cm4.0 and the newly released discs.

[Kuler087]

No, Andor is not static, at least not in this episode:

https://i.ibb.co/fCxJmwV/Star-Wars-Andor-S01-E02-That-Would-Be-Me-2160p-DSNP-WEB-Do-Vi-L2-PLOT-600nits-trim.png

[jayper]

OK, good to know. I was clearly looking in the wrong place. Thanks!

Also, curious to know if this warning is anything to be concerned with:

plugin_manager: ←[33;1mWARNING←[0m ←[Kplugin does not contain dlb_plugin_file_io_init_v1

[Kuler087]

You can ignore it.

[jayper]

Thank you so much!

[TheHooligan95]

sometimes ffmpeg gives me (running the script in 4-1 mode), during the first part of the process:

Application provided invalid, non monotonically increasing dts to muxer in stream 0: (number)>=(number)

It seems to depend on sync issues of the source (framerate?). The result will infact have audio and subtitles out of sync with the video, which will anticipate the audio and the subs. Asked on ffmpeg irc and almost got laughed at, they told me that it would be much easier to make dovitools better than to make ffmpeg fix this :(

[Kuler087]

You can disable ffmpeg piping when it causes issues.

line 171
set ffmpeg_pipe=YES

[guest]

Hi Reset,

I updated to 2.0.5, and downloaded the newer tools.7z, etc, yesterday, got everything sorted out (didn't want to overwrite anything in the 2.0.3 folders.

And it's performing well, but I just wanted to tell you of a strange thing that happened when attempting a 5 minute chunk with 8-5 (I think)...

I had 4 movies I wanted a chunk of, and this one movie "Kate & Leopold", threw up some really strange errors msg's, and would fail...

Part of the error msg was Leopold, so I changed the name, and it showed the same error, so I shortened the name even more, same msg, so I decided to run it thru MKVToolNix, stripped out everything I didn't want, the error msg was not displayed, and I got my chunk....so there must have been something DS didn't like.

BTW, is there a simple way to change the 5 minute chunk to something a little shorter, like 2 minutes ??

Cheers

[Kuler087]

The only change is the mkvtoolnix files are in a separate folder so you probably had the same MSG in the previous version. You can provide a sample and I'll have a look.
You can change the 8-5 sample timestamp at line: 125

:: choose the timestamp for the sample maker workflow (8-5) (default=5m)
set timestamp=00:00:00-00:05:00

[guest]

The only change is the mkvtoolnix files are in a separate folder so you probably had the same MSG in the previous version. You can provide a sample and I'll have a look.
You can change the 8-5 sample timestamp at line: 125

Yes, I'm sure I would have had the same error...this movie in question had many subtitles..it must have something to do with one of them...problem has been solved, I don't really think there's any need to provide a sample..unless you really want one !

I'd have to do it MKVToolNix.

:thanks: for the tip on the chunk size :)

[jayper]

Did you install avisynthplus?

https://github.com/AviSynth/AviSynthPlus/releases/download/v3.7.3/AviSynthPlus_3.7.3_20230715.exe

If it's for a profile 5 webdl, your GPU must support Vulkan.

Sorry, all is well. I mistakenly had a space in my new install folder location. I deleted my prior comment, hoping that you wouldn't have seen it.

[jayper]

Sorry to ask this here, but I haven't been able to find a clear answer on the CoreELEC forums. For the Ugoos AM6b+, I understand that the device hardware is fixed at outputting a rec709 flag.

But there are two options presented to change this via ssh:

echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry
echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_bt2020

I have an older TV, TCL 65R617 (2018 Model), is it best to send out no colorimetry flag? Or send bt2020? It sounds like newer TVs it doesn't matter, but I was curious if you had thoughts on this? Appreciate your time!

[Kuler087]

I think the correct way is no flag like the oppo/x800m2/ATV/Shield do but on my C2 it doesn't make a difference and the flag is always ignored.

[jayper]

I think the correct way is no flag like the oppo/x800m2/ATV/Shield do but on my C2 it doesn't make a difference and the flag is always ignored.

Always appreciate your time and expertise. Just sent a donation your way for all the efforts.

[Kuler087]

thank you :)

did i give you access to my generated RPU google drive link? if no and if you're interested, PM me.

[javieracdc]

Hi
Sorry for my noob question but how can I convert to STSL from a mkv files that has originally STDL?
I would like to convert it to Blu ray using tsmuxer.

this is the mediainfo of the file:

HDR format : Dolby Vision, Version 1.0, Profile 8.4, dvhe.08.05, BL+RPU, no metadata compression, HLG compatible

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : HLG
Matrix coefficients : BT.2020 non-constant

[Kuler087]

Your file has a HLG base layer(profile 8.4). I doubt it was STDL originally.
Anyway, you can't convert profile 8 ST-SL to profile 7 DT-DL without the original EL.

[javieracdc]

Your file has a HLG base layer(profile 8.4). I doubt it was STDL originally.
Anyway, you can't convert profile 8 ST-SL to profile 7 DT-DL without the original EL.

arent there any chance to convert to any profile a STSL?

[Kuler087]

your file is already single track single layer.

[javieracdc]

your file is already single track single layer.

When I convert this original file (MOV file) to mKV using handbrake (x265 bit 10 encoder) and later open the MKV file using tsmuxer and convert it to Blu Ray, this appears STDL warning

[Kuler087]

Well I don't know. According to your mediainfo, there is no 2nd layers.

HDR format : Dolby Vision, Version 1.0, Profile 8.4, dvhe.08.05, BL+RPU, no metadata compression, HLG compatible

[tormento]

I am a total noob about HDR video, so forgive me in advance.

If I have a DoVi UHD, how should apply the script if my final result has to be processed by DGCube or DGHDRtoSDR or DGHDRtoHLG?

I know that I can rip a DoVi compliant mkv with Matroska GUI but once I have a DoVI, what should I do?

I don't care to keep DoVi in the output file at all, just HLG or SDR but I want to use the 4k video to have 10/12 bit, better compression and wider range.

[Kuler087]

my final result has to be processed by DGCube or DGHDRtoSDR or DGHDRtoHLG?
The script doesn't use any of these and cannot convert HDR10 to HLG.

If you just want HDR to SDR tone mapping(workflow 8-2-2), the script relies on libplacebo and the SDR TM settings can be adjusted between lines 135-141.
When I convert HDR to SDR, I prefer delivering the original 100-nits trim pass from the Dolby Vision metadata since it respects the artistic intent of the colorist/director but this is a much longer/complicated process:
https://www.youtube.com/watch?v=lM56zLpKDQ8&t=2s

[tormento]

The script doesn't use any of these and cannot convert HDR10 to HLG.
I know and perhaps I wrote in a bad way what I wanted.

How to convert DoVi to a HDR format that can be processed by AVS+ without having to deal with dynamic metadata?

[Kuler087]

How to convert DoVi to a HDR format that can be processed by AVS+ without having to deal with dynamic metadata?

Sorry but now I'm confused...
From your initial question, I understand that you just want to convert a HDR format (DV-P7/P8/P5,HDR10 or HLG) to SDR which is exactly what dovi_scripts workflow 8-2-2 does but uses vapoursynth instead of AVS.
You don't have to deal with any metadata, everything is automated in that workflow and the outcome will be a hevc 10bit rec709 stream tone mapped from your HDR source with libplacebo.

[guest]

Never mind, things got screwed up. My bad, apologies. Please delete this post

You should be able to delete any of your posts, yourself, simply:-

Choose "Edit", then "Delete" (bottom right corner), then "Delete Message" (on the bottom left), then back over to the right bottom corner, and "Delete this Message"....done :)

[tormento]

Sorry but now I'm confused
Sorry, my english is not so good and unfortunately telepathy isn't a real thing. :o

I just want to have a stream that I can process as if it were a PQ one, without any DoVi metadata.

DoVi -> PQ -> my script to have SDR or HLG.

I want to have control on noise reduction etc.

[von Suppé]

Choose "Edit", then "Delete" (bottom right corner), then "Delete Message" (on the bottom left), then back over to the right bottom corner, and "Delete this Message"....done :)

Thank you TDS, deleting post went well :)


Sorry to ask this here, but I haven't been able to find a clear answer on the CoreELEC forums. For the Ugoos AM6b+, I understand that the device hardware is fixed at outputting a rec709 flag.

Sorry to get back on this rather late, but can you provide with a link to where this is discussed?

But there are two options presented to change this via ssh:

echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry
echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_bt2020

Dolby Vision looking good on my Ugoos now, I never touched SSH and am wondering what good both settings would do. The way I've learned it - please do correct me if I misunderstand something - is that with tv-led the video is decoded to YUV, composed (in case of extra FEL videodata) and together with RPU subsampled in a 8 bit RGB container for HDMI tunneling. Where the receiving part (display) will take RPU and do the dynamic tonemapping. Colorspace data already present in the decoded & composed video, wouldn't setting one of both SSH params add to confusion for the receiving part? And what to think about DoVi P5 where proprietary non-BT2020 colorspace is used? I can imagine setting BT2020 flag has a devastating effect.

[Kuler087]

Sorry, my english is not so good and unfortunately telepathy isn't a real thing. :o

I just want to have a stream that I can process as if it were a PQ one, without any DoVi metadata.

DoVi -> PQ -> my script to have SDR or HLG.

I want to have control on noise reduction etc.

Ok, you must meant DoVi profile 5, because the base layer of DV P8-P7 is already in PQ HDR10.

So let me describe what DoVi_Scripts can do:

8-2-1:
Can convert ANY HDR input (DVP5P8P7, HLG, HDR10) to PQ HDR10. This will re-encode to hevc rec2020 HDR10

8-2-2:
Can convert ANY HDR input (DVP5P8P7, HLG, HDR10) to SDR. This will re-encode to hevc rec709 SDR...

So the workflow in DoVi_Scripts to convert DV-P5(or any HDR source) to PQ-HDR10 is 8-2-1. The stream will still have DV metadata but it doesn't matter for what you want to do...

7-2(manual mode):
You can also create an AVS+ script with workflow 7-2 and add anything you wish(denoise etc). then you can encode that script to whatever format you want.

https://i.ibb.co/0tWsgGt/NVIDIA-Share-Fh-Eh-Qjijlo.gif

[Kuler087]

Dolby Vision looking good on my Ugoos now, I never touched SSH and am wondering what good both settings would do. The way I've learned it - please do correct me if I misunderstand something - is that with tv-led the video is decoded to YUV, composed (in case of extra FEL videodata) and together with RPU subsampled in a 8 bit RGB container for HDMI tunneling. Where the receiving part (display) will take RPU and do the dynamic tonemapping. Colorspace data already present in the decoded & composed video, wouldn't setting one of both SSH params add to confusion for the receiving part? And what to think about DoVi P5 where proprietary non-BT2020 colorspace is used? I can imagine setting BT2020 flag has a devastating effect.

It depends on your TV. The flag definitely had an effect on my old LG C8 but on my LG C2, the flag is always ignored and it doesn't make any difference.

The best approach is to use no flag IMO.

[Lucky38]

@Kuler087,

I have video in 4k DoVi profile 5 with black bars. i would like to resize it to 1080p and crop it. What i usually do in this case:

1) use your script to extract RPU and crop it;
2) open Staxrip and use same avisnth filters to do resize and crop.

I have noticed that your script shows information about black bars (top, bottom) 263px, but when i do cropping in Staxrip it crop only 262px due to output mod=2. This provide final resolution 1920x818 (it has additonal 1px on top and bottom) instead 1920x816 (without any additional black pixel).

https://imgur.com/a/dqY64it

According to Staxrip developer cropping (top, bottom) by 264px will break the metadata. Cropping by 264px gives in my opinion propper resolution 1920x816.

But my main question is: What will happen with RPU when i do cropping by 264px instead of 262px with metadata in RPU?

[Kuler087]

If 264/264 is the correct crop for the base layer video, you will not break the metadata because when you crop the RPU, the active area (L5) becomes 0/0 which is the correct value for any video without black bars.
If you crop the BL to 262/262 and there's a remaining 1/1 pixel row top/bottom, then set L5 to 1/1.

L5 is not too complicated to understand, it tells the Display how many pixels of black bar there are in the BL video and the Display will then ignore those offsets for the tone mapping.

[Lucky38]

ok. So what will happen when my RPU has 0/0 px but my encoded video has 1/1 pixel on top/bottom? Does it mean encode is broken?

[Gatorman3385]

No, the encode isn't broken. However, the RPU L5 values should be edited to 0,0,1,1 (left, right, top, bottom).

[Kuler087]

ok. So what will happen when my RPU has 0/0 px but my encoded video has 1/1 pixel on top/bottom? Does it mean encode is broken?

The DV tone mapping will be applied to the whole image including the 1px top/bottom row.

PS: This metadata (level 5) is ignored by 99% of the HDMI player. Only the TVs internal player uses it. On HDMI devices, the DV tone mapping is always applied to the whole image, letterbox included.

[smaiderman]

Hello. First of all, thank you very much for the tools.

I need some help.
Im trying to convert DOVI to SDR, and im using the 8-2-4 flow, but I get this error.

https://pastebin.com/iHXdeEVa


But I don understand, as after scanning the file with 2-2-q flow, it says it has that info.
https://pastebin.com/KnrWKBHQ

What am I doing wrong?

Im using the UHD bluray disc, created a mkv with mkvtoolnix from the index.bdmv in the bluray.

Thank you for the help!

[Kuler087]

It looks like there's something ffmpeg doesnt like about your input. There's an option to bypass ffmpeg piping but unfortunately, it's not implemented in this workflow (8-2-4).
Try the next beta (tonight or tomorrow)


[hevc @ 0000028e222fd0c0] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 19 >= 18
[hevc @ 0000028e222fd0c0] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 19 >= 19
Error: Invalid PPS index
Error: No RPU found



::choose if you dont want to use ffmpeg piping for 4-1 demuxing. Might need to be disable if you notice issues. only valid for the mkv version and when the script is set to mux all audio/subs (default = YES)
set ffmpeg_pipe=YES

[smaiderman]

It looks like there's something ffmpeg doesnt like about your input. There's an option to bypass ffmpeg piping but unfortunately, it's not implemented in this workflow (8-2-4).
Try the next beta (tonight or tomorrow)

Thank you Kuler. I'm not in a hurry. I'll be checking

[Kuler087]

Thank you Kuler. I'm not in a hurry. I'll be checking

In the latest beta (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link), ffmpeg piping can now be disabled for 8-2-4. (Line 173)

let me know if it fixes your issue.

[smaiderman]

In the latest beta (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link), ffmpeg piping can now be disabled for 8-2-4. (Line 173)

let me know if it fixes your issue.

Sorry to say that this didnt solve the problem.

https://pastebin.com/AzvWcHq9

[Kuler087]

You have to disable ffmpeg piping at line 173
This setting will never be disabled by default because it speeds up demuxing and causes issues only for a few rips.

[smaiderman]

You have to disable ffmpeg piping at line 173
After This setting will never be disabled by default because it speeds up demuxing and causes issues only for a few rips.

I edited the bat like this: (it said YES before, so I guess it is NO what I have to write)


::choose if you dont want to use ffmpeg piping for 4-1 / 8-2 / 7-1 demuxing. Might need to be disable if you notice issues. In 4-1: its only valid for the mkv version and when the script is set to mux all audio/subs (default = YES)
set ffmpeg_pipe=NO


This looked different this time. It showed a progress bar that wasnt there before, but still, errored.

Donate: https://www.paypal.com/donate/?hosted_button_id=6ML5KUZG9XGB6 Date: 28/05/2024 08:15
Contact: R3S3T_9999@proton.me Version: 2.0.7.beta_MKV


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



1) MODE.I= DoVi Inject/Convert/Edit/Re-sync TWO INPUTS (P8 Hybrid Maker/Injector)
2) MODE.F= DoVi Fix/Edit/Extract/Verify/Info ONE INPUT
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
7) MODE.S= Screenshots & Player
8) MODE.M= MIXED: Audio/Remover/Encoder/Playlist/Sample
9) Exit

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

*****************
* CHOOSE A MODE *
*****************

1) MODE.1= AUDIO Encoding (DDP, THDAC3, DEE)
2) MODE.2= VIDEO Encoding (x265/Prores/dovi_baker/libplacebo/cm_offline)
3) MODE.3= Find Main Movie Playlist (BD MPLS)
4) MODE.4= Dolby Vision / HDR10plus Remover
5) MODE.5= MKV Sample Maker
6) MODE.6= Find a video frame count
7) MODE.7= Subtitles_Tonemap (reduce SUP subtitles brightness)

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

*********************
* CHOOSE A WORKFLOW *
*********************

1) Workflow.1= X265: HDR to HDR (DVP7/DVP5/HDR10/HLG)
2) Workflow.2= X265: HDR to SDR (DVP7/DVP5/HDR10/HLG)
3) Workflow.3= PRORES: HDR to HDR (DVP7/DVP5/HDR10/HLG)
4) Workflow.4= PRORES: DV to SDR (Dolby CM_Offline 100nits L2 trim pass delivery)
5) Workflow.5= PRORES: SDR to HDR-100nits
6) Workflow.6= back to main menu

Choice? [1,2,3,4,5,6]?4
----------------------------------------------------------------------------------------------------------------
-- Can Encode any DV source that has a 100nits trim pass to SDR PRORES 422 HQ
-- Require Dolby CM_offline.exe
-- P7 fel baking requires and Nvidia GPU
-- Input MUST be PQ/HDR with a 100nits Level 2 trim.
-- Require a lot of HDD space and -qscale:v 3 is hardcoded since higher value reduce quality
-- Require Vapoursynth
------------------------------------------------------------------------------------------------------------------
Drag and drop a video and press enter...
C:\Users\Emilio\Desktop\GODMASTER.mkv
Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'H:\HDRtoSDR\HDRtoSDR\temp.folder49\BL.P7.hevc'. Container format: HEVC/H.265 elementary stream
Progress: 100%
Indexing the base layer...
Project
100
Indexing the enhancement layer...
Project
100
Error: Invalid PPS index
Error: No RPU found
[avisynth @ 000002088c1393c0] DoViBaker: parse_rpu_bin_file: Errored while parsing: No RPU found
(H:\HDRtoSDR\HDRtoSDR\temp.folder49\script.avs, line 7)
[in#0 @ 000002088c11aa80] Error opening input: Unknown error occurred
Error opening input file H:\HDRtoSDR\HDRtoSDR\temp.folder49\script.avs.
Error opening input files: Unknown error occurred
Error: El sistema no puede encontrar el archivo especificado. (os error 2)
Input doesnt have a 100nits trim pass.

[Fuso]

Is there a way to change the output bitrate for 7.1 encoding? I get 1024 kbps (which I want to keep for 5.1 DD+) but I want to set it higher e.g. 1536.

[Kuler087]

Is there a way to change the output bitrate for 7.1 encoding? I get 1024 kbps (which I want to keep for 5.1 DD+) but I want to set it higher e.g. 1536.

the maximum bitrate for 7.1 EC3 without a core in ffmpeg is 1024.
You can get 1536kbps in the DEE workflows 8-1-3 but DEE produces dynamic range metadata that can't be turned off, at least on my AVR. IIRC it's like a -10DB offset and it sucks.


Error: Invalid PPS index
Error: No RPU found


Then something is odd about your file. Which movie is that?
Also, did you try with other movies?

[Fuso]

the maximum bitrate for 7.1 EC3 without a core in ffmpeg is 1024.
You can get 1536kbps in the DEE workflows 8-1-3 but DEE produces dynamic range metadata that can't be turned off, at least on my AVR. IIRC it's like a -10DB offset and it sucks.

I see, so it's better to stick to default 1024.

1024 for 7.1 is still better than 640 for 5.1
1024 / 8 = 128kbps
640 / 6 = ~106kbps

[Kuler087]

You can set it to 1536 and it will work for 5.1 audio.

[smaiderman]

the maximum bitrate for 7.1 EC3 without a core in ffmpeg is 1024.
You can get 1536kbps in the DEE workflows 8-1-3 but DEE produces dynamic range metadata that can't be turned off, at least on my AVR. IIRC it's like a -10DB offset and it sucks.



Then something is odd about your file. Which movie is that?
Also, did you try with other movies?

It is Godzilla minus one. The UHD from the full collection.

Can it be a problem while exporting the mkv from the blu-ray disc?
Do you have any tip about a "proper" way to do it?

I didn't try with any other movie. This was my first attempt regrading

Thanks again

[Kuler087]

It is Godzilla minus one. The UHD from the full collection.

Can it be a problem while exporting the mkv from the blu-ray disc?
Do you have any tip about a "proper" way to do it?

I didn't try with any other movie. This was my first attempt regrading

Thanks again

Ah, that explains it. This movie is strangely authored and cant be processed in Dovi_scripts. You can try to demux the hevc stream from the original M2TS file and do everything manually in resolve (https://www.youtube.com/watch?v=lM56zLpKDQ8&t=5s)

I see, so it's better to stick to default 1024.

1024 for 7.1 is still better than 640 for 5.1
1024 / 8 = 128kbps
640 / 6 = ~106kbps

I've added a workaround (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link) in the DEE (8-1-3) workflow and it should now produce the same quality as 8-1-1 but at 7.1 channels + 1536kbps bitrate.

It turns out, my AVR (and many others) can't disable the Dialogue Normalization of DDP tracks. (https://www.avsforum.com/threads/defeating-dialnorm.3253654/)

[smaiderman]

[QUOTE=Kuler087;2002322]Ah, that explains it. This movie is strangely authored and cant be processed in Dovi_scripts. You can try to demux the hevc stream from the original M2TS file and do everything manually in resolve (https://www.youtube.com/watch?v=lM56zLpKDQ8&t=5s)

I'm going to watch the video, but the leading problem that made me discover your tool, was because daVinci studio can't import the hvec extracted from the bluray. (I use mkvtoolnix to extract the heck video file). But daVinci refuses to read that hevc

Thanks again

[Kuler087]

I'm going to watch the video, but the leading problem that made me discover your tool, was because daVinci studio can't import the hvec extracted from the bluray. (I use mkvtoolnix to extract the heck video file). But daVinci refuses to read that hevc

Thanks again

Your video must be in a mkv or mp4 container for Resolve to see it but don't do that, Resolve has poor hevc decoding. You must convert it to prores 422 like the tutorial if you want frame-accurate results.

Also I heard mkvtoolnix is not prrocessing this movie correctly, it will fail to play on the Ugoos and Shield. If you demux the original M2TS with tsmuxer, you should be able to extract the DV metadata for Resolve 100nits SDR delivery.

[Fuso]

I've added a workaround (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link) in the DEE (8-1-3) workflow and it should now produce the same quality as 8-1-1 but at 7.1 channels + 1536kbps bitrate.

It turns out, my AVR (and many others) can't disable the Dialogue Normalization of DDP tracks. (https://www.avsforum.com/threads/defeating-dialnorm.3253654/)

Thank you! I will try it...

[smaiderman]

Ah, that explains it. This movie is strangely authored and cant be processed in Dovi_scripts. You can try to demux the hevc stream from the original M2TS file and do everything manually in resolve (https://www.youtube.com/watch?v=lM56zLpKDQ8&t=5s)

Hi. Im trying to follow the tutorial, and I have some news.

Regarding your suggestion to use TsMuxer, your software instantly closes as I try to drag and drop the file obtained with TsMuxer, and I think that this happens because there is a step missing: converting the prores.mov to MKV.

Can you suggest a way to do this avoiding MKVtoolnix?

Davinci can importe the proress file, but I cant make the neccessary steps involving Dovi_tools

Thank you!

[Kuler087]

You have to input the demuxed .hevc DV layer track(1080p) in workflow 2-5 ? is that what you did?
Dont input the 2160p HEVC file, it doesn't have metadata.

[smaiderman]

You have to input the demuxed .hevc DV layer track(1080p) in workflow 2-5 ? is that what you did?
Dont input the 2160p HEVC file, it doesn't have metadata.

That is the problem. Sorry to be so ignorant, and thank you for your extensive help

[Kuler087]

BTW, I had a look at this movie and if you remux it with mkvtoolnix straight from the bluray disc, the output is incorrect.
If you remux the disc with MakeMKV, the output is correct.

[smaiderman]

BTW, I had a look at this movie and if you remux it with mkvtoolnix straight from the bluray disc, the output is incorrect.
If you remux the disc with MakeMKV, the output is correct.

Thnaks for the advice. My only experience was with toolnix, but I'm going to swap.

I have an oftopic question:

I managed to set Davinci with the xml and the correct color spaces, but my question now is how do I export from the color graded prores to the original hvec as loseless as possible? Is there a way to do this render loslessly? Or will there always be some kind of compression?

[Kuler087]

You have to deliver to a lossless codec from Resolve and then encode with high-quality settings in x265 or x264.
So depending on your x265/x264 final encode, there should not be any visible loss.

Example, this is my Aquaman 2 SDR 16mb/s x264 encode VS the 1080p bluray remux: https://slow.pics/c/hZDFm8Na

[smaiderman]

You have to deliver to a lossless codec from Resolve and then encode with high-quality settings in x265 or x264.
So depending on your x265/x264 final encode, there should not be any visible loss.

Example, this is my Aquaman 2 SDR 16mb/s x264 encode VS the 1080p bluray remux: https://slow.pics/c/hZDFm8Na

That would be, for example, export in proress again with resolve, and then encode that file with another software?
If exported with resolve to high quality h264 or h265, there is still a big loss?

[Kuler087]

That would be, for example, export in proress again with resolve, and then encode that file with another software?


yes. I use staxrip/x264 1080p 8bit 2-pass 16mb/s very slow with some custom cmd but this is for the small PLEX I share with friends and family. If you want transparent quality to the UHD bluray source, you should encode to x265 2160p 10bit CRF 14-15 slower preset.

If exported with resolve to high quality h264 or h265, there is still a big loss?

No, don't do that. Resolve h265/h264 encoding is bad. You always want to deliver a lossless codec from Resolve

[Fuso]

I've added a workaround (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link) in the DEE (8-1-3) workflow and it should now produce the same quality as 8-1-1 but at 7.1 channels + 1536kbps bitrate.

It turns out, my AVR (and many others) can't disable the Dialogue Normalization of DDP tracks. (https://www.avsforum.com/threads/defeating-dialnorm.3253654/)

Am I doing something wrong?
I've tried with MKV containing 7.1 TrueHD (no ac3 core) and this is the result:
1) Workflow.1= Lossless Audio to DD+ EC3 (can batch)
2) Workflow.2= Add an AC3 Core to TrueHD (thdmerge or eac3to)(can batch)
3) Workflow.3= DEE workflows(payware) (not recomended)

Choice? [1,2,3]?3
--------------------------------------------------------------------------------------
-- You must have edited the path to DEE for this workflow to work.
-- Can encode to DD+ 1536kbps 7.1(ac3 core) or TrueHD 7.1
-- Input must have 7.1 channels audio. For 5.1/2.0 audio, use workflow 8-1-1
--------------------------------------------------------------------------------------
Drag and drop a file and press enter...
"D:\Torrents\Movies\Gojira -1.0.2023.BDRemux.2160p.NNMClub\Gojira -1.0.2023.BDRemux.2160p.NNMClub (1)-001.mkv"
File 'D:\Torrents\Movies\Gojira -1.0.2023.BDRemux.2160p.NNMClub\Gojira -1.0.2023.BDRemux.2160p.NNMClub (1)-001.mkv': container: Matroska
Track ID 0: video (HEVC/H.265/MPEG-H)
Track ID 1: audio (TrueHD Atmos)
Attachment ID 1: type 'image/jpeg', size 39406 bytes, file name 'cover.jpg'
What is the audio track id (default=1) and press enter...
1
DD+ or TrueHD? choice are b or t (default=b)
b
ffmpeg version 2024-02-22-git-76b2bb96b4-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers
built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
configuration: --enable-gpl --enable-version3 --enable-static --pkg-config=pkgconf --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-dxva2 --enable-d3d11va --enable-libvpl --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
libavutil 58. 39.100 / 58. 39.100
libavcodec 60. 40.100 / 60. 40.100
libavformat 60. 21.101 / 60. 21.101
libavdevice 60. 4.100 / 60. 4.100
libavfilter 9. 17.100 / 9. 17.100
libswscale 7. 6.100 / 7. 6.100
libswresample 4. 13.100 / 4. 13.100
libpostproc 57. 4.100 / 57. 4.100
[matroska,webm @ 0000018070ba9f00] Invalid Block Addition value 0x0 for unknown Block Addition Mapping type 68766345, name "Dolby Vision enhancement-layer HEVC configuration"
Input #0, matroska,webm, from 'D:\Torrents\Movies\Gojira -1.0.2023.BDRemux.2160p.NNMClub\Gojira -1.0.2023.BDRemux.2160p.NNMClub (1)-001.mkv':
Metadata:
encoder : libebml v1.4.5 + libmatroska v1.7.1
creation_time : 2024-05-30T19:17:26.000000Z
Duration: 00:01:00.23, start: 0.000000, bitrate: 67367 kb/s
Stream #0:0(jpn): Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn (default)
Metadata:
BPS : 64217023
DURATION : 00:00:59.393000000
NUMBER_OF_FRAMES: 1424
NUMBER_OF_BYTES : 476755212
SOURCE_ID : 001011
_STATISTICS_WRITING_APP: mkvmerge v84.0 ('Sleeper') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-05-30 19:17:26
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE_ID
Side data:
DOVI configuration record: version: 1.0, profile: 7, level: 6, rpu flag: 1, el flag: 1, bl flag: 1, compatibility id: 6
Stream #0:1(jpn): Audio: truehd (Dolby TrueHD + Dolby Atmos), 48000 Hz, 7.1, s32 (24 bit)
Metadata:
title : Original
BPS : 3964436
DURATION : 00:01:00.227000000
NUMBER_OF_FRAMES: 72272
NUMBER_OF_BYTES : 29845768
_STATISTICS_WRITING_APP: mkvmerge v84.0 ('Sleeper') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-05-30 19:17:26
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream #0:2: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 640x360 [SAR 72:72 DAR 16:9], 90k tbr, 90k tbn (attached pic)
Metadata:
filename : cover.jpg
mimetype : image/jpeg
[in#0/matroska,webm @ 0000018070b8ac80] Codec AVOption drc_scale (percentage of dynamic range compression to apply) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some decoder which was not actually used for any stream.
Stream mapping:
Stream #0:1 -> #0:0 (truehd (native) -> pcm_s24le (native))
Press [q] to stop, [?] for help
[Parsed_pan_0 @ 0000018071138140] Pure channel mapping detected: 0 1 2 3 6 7 4 5
Output #0, wav, to 'D:\Torrents\Movies\MP4_DV_P5\DoVi_Scripts\temp_folder19\1.wav':
Metadata:
ISFT : Lavf60.21.101
Stream #0:0(jpn): Audio: pcm_s24le ([1][0][0][0] / 0x0001), 48000 Hz, 7.1, s32, 9216 kb/s
Metadata:
title : Original
BPS : 3964436
DURATION : 00:01:00.227000000
NUMBER_OF_FRAMES: 72272
NUMBER_OF_BYTES : 29845768
_STATISTICS_WRITING_APP: mkvmerge v84.0 ('Sleeper') 64-bit
_STATISTICS_WRITING_DATE_UTC: 2024-05-30 19:17:26
_STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
encoder : Lavc60.40.100 pcm_s24le
[out#0/wav @ 000001807113a200] video:0KiB audio:67755KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.000199%
size= 67755KiB time=00:01:00.22 bitrate=9216.0kbits/s speed=21.8x
The system cannot find the path specified.

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?

[Kuler087]

It looks like you didn't set your path to DEE.exe. This is a paidware and it's not included in the tools pack I share.

https://i.ibb.co/vv6nL6Y/Capture-d-cran-2024-05-31-095524.png

[Fuso]

It looks like you didn't set your path to DEE.exe. This is a paidware and it's not included in the tools pack I share.

https://i.ibb.co/vv6nL6Y/Capture-d-cran-2024-05-31-095524.png

Oh, I see. I've tried to see what's missing, but I missed that. Thank you!

[subnrg]

Hello @Kuler087.
I want to sincerely thank you for what must have been an immense amount of experience and work to put this together. Although I'm technically not a noob since I've been dabbling with encoding for over a decade, but I've never had the need to get too into the weeds on this stuff. I've been using staxrip forever, but never was able to figure out how to get their DV support to work. I think I've got most everything down now... thanks to you. I've read through this entire DS forum and watched a chunk of your very helpful videos, but I just have a few questions:

1. My goal is to take a remux file (normally P7.6) and make 2 files for each of these. One that is a 1080p 6M VBR DV8.1 EAC3 .mp4 file (that is roku compatible), and one that is 4k 18M VBR DV8.1 original lossless audio in .mkv (mainly used on Shield) for my Plex servers.
So far, I've been able to translate my staxrip encode settings into your .bat files, and created one for HD and one for 4K .mkv. The workflow that seems to work best and most consistently for me is:
- 8.2.1 & 8.1.1
- Mux .hevc .ec3 and subs from original file through mkvtoolnix
- Mux in staxrip to .mp4 (for some reason I haven't had luck w your batch muxer)
Do you think this is the best approach for this, and/or might there be a way to automate some of this?

2. For my HD encodes, I'm always downconverting to 5.1. Does the DDP encoding always convert from the original lossless, or does this default to the core for THD or DTS? Does it employ any dynamic compression or normalization?

3. For subs, one of the best features that I like in handbrake, is to burn in forced subs. Any advice how to make that work with this without tons of extra work?

[Kuler087]

- Mux in staxrip to .mp4 (for some reason I haven't had luck w your batch muxer)

with the mp4 version, if you rename your .hevc .ec3 .srt files the same(and same path), you can input just the .hevc file and the script workflow 5 will pick the audio and sub. Otherwise, you can just mux every track you want into an MKV and then run it in Workflow 5 which would get you proper track names and forced flags
For the mp4 version, you'll have to test which muxer version works for you (at the line 60 set mp4_version=NEW or OLD)

Do you think this is the best approach for this, and/or might there be a way to automate some of this?
Yes, one day, I should add muxing and audio encoding in the video encoder workflows eventually ... For now, they just output raw hevc files.


Does the DDP encoding always convert from the original lossless, or does this default to the core for THD or DTS?
it always encodes from the original lossless audio and you can set the script to downmix to 5.1 at line 76. The bitrate is controlled at line 78
7.1 ec3 requires the EAE folder (not included in the tools pack) and the MP4 ''NEW'' version has 7.1 encoding disabled.

Does it employ any dynamic compression or normalization?


No normalization/compression.

For subs, one of the best features that I like in handbrake, is to burn in forced subs. Any advice how to make that work with this without tons of extra work?

Nop can't help you with that, and DS will never do that. I hate burned-in subs.

[subnrg]

Thanks brotha! Appreciate the info. I totally agree with the burned-in subs. The only time I want those is if they are speaking Klingon or something like Handbrake does with "Foreign Audio Scan". Because I'm trying to create Roku/Firestick friendly DV .mp4 files, I can't use the PGS subs in that container and the IDX conversions are a bit wonky. Although I've found with some specific instructions, GPT4o does an okay job of fixing the srt files.

One other question/suggestion... you have an option of "choose if you want to also mux the lossless audio when you convert to DD+." If this option (or separate option) could apply to 8-1-1, it could save me from having to mux the original back into my 4k rips.

[wyup]

I'm getting significantly different plot results from different workflows: 6-2 (madVR) and 6-6 (json with ProRes conversion and Resolve detecting scene cuts and hdr10+):

MaxCLL 6-2: 1378 6-6: 915
MaxFALL 6-2: 607 6-6: 238
Scenes: 6-2: 2765 6-6: 2000

I guess their algorythms are different, but which is the most accurate?

[Kuler087]

Resolve scopes/waveforms are wrong if you dont downscale your timeline with ''custom cubic'' algo.
also, 6-2 madvr includes the black bars if you don't crop so this will directly affect your maxfall.

https://i.ibb.co/G7zR9HH/resolve-scaling.png

[wyup]

Okay thanks, and for the Timeline Output in Master Settings, what should I choose, the video native resolution or also 1920x1080 as the output scaling?
The video file I'm evaluating is already cropped at 3840x 2076 pixels.

[Kuler087]

master settings resolution is your input native resolution so 3840x2076

[wyup]

I re-generated the HDR10+ json in Resolve from Prores cropped video and obtained by 6-6 the new B plot. It is slightly different than the unscaled one:

6-6 unscaled: MaxCLL: 915 MaxFALL: 238
6-6 downscaled: MaxCLL: 901 MaxFALL: 228

Still far from 6-2: MaxCLL: 1378 MaxFALL: 607

What can I do with the 6-2 .measurement file? I played it alongside the original file with madvr filter and MPC-BE and I got random blanking during playback. Is the .measurement video automatically loaded? I can't find a option within madvr filter to import external .measurement file.

[Kuler087]

HDR10plus or DV will create metadata intended for playback(restrictions/rules in the way they are calculated) while madvr just measures the pixels as they are so differences are expected. So the 1378nits pixels spike could be ignored by the algo(should be visible in the scopes though) but overall, shot-by-shot maxcll is almost identical and the point is that for some reason, resolve does some resampling if you don't downscale. Anyway, static/single maxcll/maxfall values are pretty much meaningless metadata.

I can't find a option within madvr filter to import external .measurement file.
I don't use it and don't know if it works or is useful but the option for external files is there.

https://i.ibb.co/WktqZmv/Capture-d-cran-2024-06-04-081623.png

[subnrg]

Hey K.
I had everything working well, then all of a sudden I'm getting errors. I deleted and reinstalled everything and started with a fresh .bat file (only changing the output/temp directory and nvenc), but I'm still getting errors that seem like they may be PTS or nvenc issues? The .mkv i mux via mkvtoolnix seems to play fine, but when I try to mux back to MP4 in staxrip (whether lsmash or ffvideosource) i'm getting:

Script Error
FFVideoSource: The index does not match the source file
(P:\Muxes\Awaken (2018) UHD Disc Sample_temp\Awaken (2018) UHD Disc Sample_source.avs, line 5)

MODE.B shows the script was completed, but no file is rendered. I'm thinking something was updated or I messed with something I shouldn't have. Any ideas?

[guest]

Hey K.
I had everything working well, then all of a sudden I'm getting errors. I deleted and reinstalled everything and started with a fresh .bat file (only changing the output/temp directory and nvenc), but I'm still getting errors that seem like they may be PTS or nvenc issues? The .mkv i mux via mkvtoolnix seems to play fine, but when I try to mux back to MP4 in staxrip (whether lsmash or ffvideosource) i'm getting:

Script Error
FFVideoSource: The index does not match the source file
(P:\Muxes\Awaken (2018) UHD Disc Sample_temp\Awaken (2018) UHD Disc Sample_source.avs, line 5)

MODE.B shows the script was completed, but no file is rendered. I'm thinking something was updated or I messed with something I shouldn't have. Any ideas?

Why aren't you using the MP4 Muxer in DS ??

[subnrg]

Why aren't you using the MP4 Muxer in DS ??

It isn't working for me. It shows that it's completed, but no output. There has to be some driver or setting that's not compatible. Racking my brain trying to figure it out.

[Kuler087]

when I try to mux back to MP4 in staxrip (whether lsmash or ffvideosource) i'm getting:

Script Error
FFVideoSource: The index does not match the source file
(P:\Muxes\Awaken (2018) UHD Disc Sample_temp\Awaken (2018) UHD Disc Sample_source.avs, line 5)

This usually happens when you try to import a file with the same filename as another file you already imported in staxrip. Solution: Delete temp folder or rename input

MODE.B shows the script was completed, but no file is rendered. I'm thinking something was updated or I messed with something I shouldn't have. Any ideas?

not enough info to help you but it sounds like you're not using the MP4 version of the script. You have to show me your log (with 'echo on' line 2 preferably) like this:
https://justpaste.it/fbvgg

[subnrg]

This usually happens when you try to import a file with the same filename as another file you already imported in staxrip. Solution: Delete temp folder or rename input

not enough info to help you but it sounds like you're not using the MP4 version of the script. You have to show me your log (with 'echo on' line 2 preferably) like this:
https://justpaste.it/fbvgg

I do always delete the temp folder unless I'm doing 2 different encodes off the same source file to save time. There's something else going on. If I remux in XMedia Recode, it work just fine. Go figure.

And you were correct about using the mp4.bat being the reason I got no output. I was using the .mp4 version before I deleted everything and started over. But I'm still getting either remuxes with no audio or messed up audio like this one:
https://justpaste.it/3ecjd

[Kuler087]

I dont know, everything looks normal... Try the old mp4 muxer. line 60 set mp4_version=OLD

[guest]

Hi Kuler,

I'm using 2.0.7 beta, and I am randomly getting this annoying error:-

Workflow 3-1

Parsing XML metadata...ast frame: 0.045 seconds. ETA: 2:15:08.091
Error: The system cannot find the file specified. (os error 2)
File not found - S01E05 4K HDR vol 3.0 (1)_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Error: expected value at line 21 column 35
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)

I just noticed that 2.0.7 (proper) is out, so I will grab that and see what happens.

==========================================

I ran a Profile 5 DV mkv thru MP4 Muxer, and just at the end got this what I think is an irrelevant error :-

====== PROCESSING LOG ======================
Number of written frames = 168973
Number of Errors= 0
Processing finished successfully.
muxing into a DoVi MP4 file. Be patient, it can take a while. 40min+ on slow HDD
[1/2] Parsing track "E:\Dovi_Temp_MP4\tempstemp.folder66\HDR.hevc"...
hevc: ******************** 100%
[2/2] Saving output file(s) "E:\Dovi_Temp_MP4\tempstemp.folder66\temp.mp4"...
written: ******************** 100%
Broken argument specifier or file name missing - check usage with -h
'.Jerry.Zucker' is not recognized as an internal or external command,
operable program or batch file.

Was has Jerry Zucker got to do with anything ??

The movie is Top Secret.

[von Suppé]

Was has Jerry Zucker got to do with anything ??

The movie is Top Secret.

At its time a commemorably funny movie, created by Jim Abrahams and the Zucker brothers. Dunno how "Jerry.Zucker" is conjured up here though.

[guest]

At its time a commemorably funny movie, created by Jim Abrahams and the Zucker brothers. Dunno how "Jerry.Zucker" is conjured up here though.

I think it might be the dodgey way it was compiled, only being Profile 5 is not preferrable...hopefully I can re-encode it something better.

Cheers, thanks for the info :)

[Kuler087]

Nothing changed in 3-1 and the mp4muxer in a while but please remember to always post the complete log and not just parts of it.
A small sample would be nice too.


Was has Jerry Zucker got to do with anything ??

Maybe some of the track names have strange characters (EG Russian text for the tracknames cause this kind of error)

[guest]

Nothing changed in 3-1 and the mp4muxer in a while but please remember to always post the complete log and not just parts of it.
A small sample would be nice too.

Yeah, not sure why this is happening, I processed the same file again, and there was no error...just one of those things.


Maybe some of the track names have strange characters (EG Russian text for the tracknames cause this kind of error)

This movie hasn't got many tracks, tho.

And this so called DV, is some shitty thing that the colours all messed up, similar to a True Lies "DV" I got some time back, and I ended up downloading a "non DV" version, and this Top Secret has the same issue, not worth "playing" with, so I'm getting it again, "non DV".

[Kuler087]

the issue with that file is as i suspected, there are special characters in the track name of the commentary track
''Commentary by co-directors Jim Abrahams and David & Jerry Zucker, with co-producers Jon Davison and Hunt Lowry''

the DTSHD track has a delay btw and delays for lossless audio is not supported in the OLD mp4muxer workflow. so you might want to set keep_lossless=NO for this one

https://justpaste.it/g5pvd

[guest]

I generally run most videos thru MKVToolNix first to remove the stuff I don't want, but I just threw this in to see what happens to the Profile 5, but I acquired a much better conversion, it's actually Profile 8.1, so I will go with that one.

[guest]

I think I may have asked you this before...

I recall that you're running an Intel 13900KS, but I've forgotten what GPU you use, I'm guessing maybe a 4080, or even a 4090, just for all the CUDA cores !!! :)

You do use CUDA in preference to CPU, even the 13900 ?!?!

I've only got a 3050 & 3060, so even a 4070 Ti Super should process things a LOT faster, correct ??

Would save a lot of time.

[Kuler087]

3070

I always use my CPU for encoding. GPU encoding is not great.

[guest]

3070

I always use my CPU for encoding. GPU encoding is not great.

That IS interesting, thanks for that..

I'll have to change mine from CUDA to CPU, then!

It will be interesting to find out which CPU is faster, my 13900KF, or the 7950X.

You've just saved me a lot of money :) or not.

UPDATE:-

So I am doing another 3-1 with CUDA disabled, on the 7950X, and at the start of that CUDA process it shows approx ETA is 4:10:00, but with CUDA enabled (RTX 3060), it would be approx 3:10:00 ??? :(

Then I tried the same scenario on the 13900KF, and at the start of the CUDA process it shows approx ETA is 4:35:00, but with CUDA enabled (RTX 3050), it would be approx 3:30:00 ??? :(

Your RTX 3070 (with 5,888 CUDA cores) would be a little faster again, so my way of thinking is, an RTX 4080 Super (with 10,240 CUDA cores) would be close to 3 times faster than the RTX 3060, (with 3,584 CUDA cores).

In CPU "mode", it's only using 1-2% on both CPU's

So to me, that appears that the 7950X is faster than the 13900KF, maybe similar to your 13900KS

Doing a DS 3-1 on my 5950X with dual GTX 770's, (1532 CUDA cores) unfortunately it only uses 1 GPU, and its S-L-O-W, (ETA 6:00:00) so I kind of have to disagree that CPU is faster than CUDA...

[Yosho]

Can someone help with this MP4 playback problem on an LG C9 tv? I tried this mp4 script to make a p7 st-dl with GxK uhd but it comes out stuttering. P8 has issues too for some reason, but P7 DT-DL made with it works well though, no problems with playing back. I looked through script, saw OLD and NEW Muxer, tried both, but ST-DL stutters no matter what.. Am I doing something wrong? Modes 4 and 5 is what I used. No luck for st-dl. Made a mkv with makemkv, dropping in bdmv, dropping in mpls, and tried just the m2ts with no luck.
I tried dvvt tool as well but it also came out stuttering the same way unfortunately.

[Kuler087]

yeah, unfortunately, STDL MP4 does not work very well on 2017-2019 LG TVs. You should get the Ugoos AM6b+ (https://discourse.coreelec.org/t/dolby-vision-for-minix-u22x-j-max-and-ugoos-am6/24273) or you could try the mkv container with Kodi (https://forum.kodi.tv/showthread.php?tid=368381) but I don't know if the EL is used or ignored.

[Kuler087]

So I am doing another 3-1 with CUDA disabled, on the 7950X, and at the start of that CUDA process it shows approx ETA is 4:10:00, but with CUDA enabled (RTX 3060), it would be approx 3:10:00 ???

Then I tried the same scenario on the 13900KF, and at the start of the CUDA process it shows approx ETA is 4:35:00, but with CUDA enabled (RTX 3050), it would be approx 3:30:00 ???

Your RTX 3070 (with 5,888 CUDA cores) would be a little faster again, so my way of thinking is, an RTX 4080 Super (with 10,240 CUDA cores) would be close to 3 times faster than the RTX 3060, (with 3,584 CUDA cores).

In CPU "mode", it's only using 1-2% on both CPU's

So to me, that appears that the 7950X is faster than the 13900KF, maybe similar to your 13900KS

Doing a DS 3-1 on my 5950X with dual GTX 770's, (1532 CUDA cores) unfortunately it only uses 1 GPU, and its S-L-O-W, (ETA 6:00:00) so I kind of have to disagree that CPU is faster than CUDA...

I was talking about x265/x264 encoding and not about speed but quality.
For 3-1, there's no encoding, just decoding and the GPU is faster for that of course.

[guest]

I was talking about x265/x264 encoding and not about speed but quality.
For 3-1, there's no encoding, just decoding and the GPU is faster for that of course.

OK, well the majority of my use of DS is 3-1..so the faster I can get that done, the better :)

Each "job" I do takes well over an hour, and that's for a video thats less than a hour long..so long movies will take half the day :(

So I think I'll buy an RTX 4080 Super...

:thanks:

[Kuler087]

there's a lot of variation in 3-1 because of the prores decoding bug in CM with Windows. Sometimes I can do a 2h movie in just 1h-1h30 and some other times, it can take well over 4h. A 4080 will be a lot faster than a 3060 for sure but some movies will still take forever to process regardless of the GPU.
In Resolve it's always fast.

EDIT: workaround would be to use jpeg-2000 mxf but I'm not able to encode a cm_analyze compatible file with ffmpeg. It only works with the mxf file from Resolve.

[guest]

there's a lot of variation in 3-1 because of the prores decoding bug in CM with Windows. Sometimes I can do a 2h movie in just 1h-1h30 and some other times, it can take well over 4h. A 4080 will be a lot faster than a 3060 for sure but some movies will still take forever to process regardless of the GPU.
In Resolve it's always fast.

EDIT: workaround would be to use jpeg-2000 mxf but I'm not able to encode a cm_analyze compatible file with ffmpeg. It only works with the mxf file from Resolve.

Just read your edit...

Have you made a tutorial of this process, or is there one somewhere on how to do it ??

I ordered my Gigabyte RTX 4080 Super today :), 2nd most expensive single PC part I have ever bought :(

[Kuler087]

Just read your edit...

Have you made a tutorial of this process, or is there one somewhere on how to do it ??


Well I tried a bunch of different settings and CM_analyze just isn't able to decode the ffmpeg produced files.

E:\DoVi_Scripts\tools\ffmpeg.exe -i E:\input.mkv -c:v jpeg2000 -an -profile:v 3 -q 1 -compression_level 30 -pix_fmt yuv422p10le -y E:\output.mxf

E:\DoVi_Scripts\tools\cm_analyze.exe -m 20 --source-format "pq bt2020" --analysis-tuning 1 E:\output.mxf E:\DV.xml

EG, this a Resolve mxf file that works (https://drive.google.com/file/d/1wprNlmCbKX1GCGYfz-YNFfiLSZP-Q9OS/view?usp=sharing)


I ordered my Gigabyte RTX 4080 Super today :), 2nd most expensive single PC part I have ever bought
nice!!

[guest]

Well I tried a bunch of different settings and CM_analyze just isn't able to decode the ffmpeg produced files.

E:\DoVi_Scripts\tools\ffmpeg.exe -i E:\input.mkv -c:v jpeg2000 -an -profile:v 3 -q 1 -compression_level 30 -pix_fmt yuv422p10le -y E:\output.mxf

E:\DoVi_Scripts\tools\cm_analyze.exe -m 20 --source-format "pq bt2020" --analysis-tuning 1 E:\output.mxf E:\DV.xml

EG, this a Resolve mxf file that works (https://drive.google.com/file/d/1wprNlmCbKX1GCGYfz-YNFfiLSZP-Q9OS/view?usp=sharing)

nice!!

Not really my favourite thing, using command lines, so were these examples of what you've tried, do these work ??

And what do I do with that .mxf file ??

[Kuler087]

nop, anything I tried in ffmpeg failed to be decoded by cm.
Will try again this weekend...

[guest]

nop, anything I tried in ffmpeg failed to be decoded by cm.
Will try again this weekend...

But what about that .mxf file ??

Can I do anything with it ??

[Kuler087]

No, it's just a reference.

[Boulder]

I tried to have a quick peek to see if this workflow I'm thinking of is there, but not sure so I'll ask. Sorry for being a DoVi n00b, I'm just about to get a proper TV that supports TV Led DoVi so I'm going to create some samples to try it out.

I have a profile 7 STDL MKV file. I was thinking of extracting the BL, FEL and RPU, downscaling and re-encoding the BL video and recombining these three back to MKV. Is the extracting and recombining possible to do with the script? And is it possible to downscale the BL or does the frame size need to match the FEL?

[Kuler087]

It's possible but I wouldn't do that without DEE.exe. Re-encoding the BL and muxing back the original EL can be destructive and cause issues.
Instead, you should bake FEL into the BL and convert the RPU to Profile 8 which will be the same quality as the original FEL P7 playback.

[Boulder]

It's possible but I wouldn't do that without DEE.exe. Re-encoding the BL and muxing back the original EL can be destructive and cause issues.
Instead, you should bake FEL into the BL and convert the RPU to Profile 8 which will be the same quality as the original FEL P7 playback.

Bake and then re-encode like any normal 4K? (Of course, with proper DoVi related settings.)

I tried to find a way to extract the two layers with the script but didn't see the workflow there? Did I just miss it or is it not there?

[Kuler087]

Yes, you bake/encode with x265.exe at the same time, it's a one-step process. In dovi_scripts you can create the avs script in 8-2-1 or 7-1

Set echo to ''on'' (line 2) to expose the cmd lines I use and then run 8-2-1. Cancel the encode and go into the temp folder, you will have the demuxed layers + RPU and the AVS script needed to bake/encode.
you can downscale to 1080p at line 120.

::choose if you want 8-2 to downscale to 1080p (default = NO)
set downscale=NO

Then you have workflow 7-1 in manual mode. This will produce an AVS script ready to be encoded (remove the subtitles osd though)


In both ways, my scripts require an nvidia gpu.

[Boulder]

Thank you for the comprehensive answer, I'll take a deeper look at the process using those workflows :)

[Gatorman3385]

I'm getting this error when attempting to use the works.mxf. Am I doing something wrong?

I:\Working\Movies\2160>I:\Working\Dolby-Vision-Tools\tools\cm_analyze.exe -m 20 --source-format "pq bt2020" --analysis-tuning 1 I:\Working\Movies\2160\output.mxf I:\Working\Movies\2160\DV.xml
Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved
06/11/2024/15:06:53.060000000 CPU: AMD Ryzen 7 2700X Eight-Core Processor (AuthenticAMD) [ mmx mmxext sse sse2 sse3 ssse3 sse41 sse42 sse4a avx avx2 fma ]
06/11/2024/15:06:53.062000000 cm_analyze: ERROR Unable to open MXF 'I:\Working\Movies\2160\output.mxf' for read: File open failure.

[Kuler087]

well you have to change the command to:

I:\Working\Dolby-Vision-Tools\tools\cm_analyze.exe -m 20 --source-format "pq bt2020" --analysis-tuning 1 I:\Working\Movies\2160\works.mxf I:\Working\Movies\2160\DV.xml

[Gatorman3385]

Yup! That would help. :p

[Boulder]

Yes, you bake/encode with x265.exe at the same time, it's a one-step process. In dovi_scripts you can create the avs script in 8-2-1 or 7-1

Set echo to ''on'' (line 2) to expose the cmd lines I use and then run 8-2-1. Cancel the encode and go into the temp folder, you will have the demuxed layers + RPU and the AVS script needed to bake/encode.
you can downscale to 1080p at line 120.


Then you have workflow 7-1 in manual mode. This will produce an AVS script ready to be encoded (remove the subtitles osd though)


In both ways, my scripts require an nvidia gpu.

One question regarding the process came up. If DoViBaker already uses the RPU, won't the information be processed again during playback as it is input to x265 as well?
EDIT: or is it that if you go DoVi and not static HDR10, you just bake BL+FEL and then input the RPU while encoding to get a proper stream with dynamic metadata.

[Kuler087]

The original P7 RPU is required when you bake/decode EL+BL to a 16bit RGB PQ stream. Then, that 16bit PQ HDR stream is fed to the x265.exe with the P8 RPU.

[Boulder]

The original P7 RPU is required when you bake/decode EL+BL to a 16bit RGB PQ stream. Then, that 16bit PQ HDR stream is fed to the x265.exe with the P8 RPU.

Yeah, I was just a little confused when I consulted the DoViBaker examples in GitHub.. in the script there were all three items incorporated in the DoViBaker call, but in this case I would use only BL and EL there and RPU with x265.

[Kuler087]

yeah , ffms2 and lsmash read the P7 rpu directly from the stream. My script uses DGdecode.

[guest]

Is there a way to speed this part of the 3-1 process up ??

I'm using nVme's where I can, but maybe there not "fast" ones, if that is what is governing this speed.

Metadata:
encoder : Lavc61.5.104 prores_ks
frame= 8856 fps=105 q=-0.0 size= 6854912KiB time=00:06:09.36 bitrate=152030.7kbits/s speed=4.39x

[Kuler087]

You can try to raise qscale at line 164 but 4.39x(105fps) is already a decent speed for prores encoding.

:: choose the prores encoding quality/size for 3-1 and 8-2-3 (default = 4) higher values mean faster encoding(depending on your cpu) and smaller filesize.
set qscale=4

[guest]

You can try to raise qscale at line 164 but 4.39x(105fps) is already a decent speed for prores encoding.

I have fiddled with that setting, but if you say that the speed I'm getting is good, then that's good enough for me. :thanks:

[guest]

Hi Kuler,
I think I might be having to buy a new TV, my 2018 LG 4K TV shit itself last night, I was watching an episode of GoT, and the screen just went black, still had sound, tho.
Tried a few reset functions, but all I get is sound :(, not too impressed.
So I would like to ask what would you suggest for a suitable or better replacement ??
I really only want DV playback....
What do you have ??
Cheers.

[Kuler087]

You can't go wrong with LG C or G series.
I have an LG C2 77'' and I love it.

[guest]

You can't go wrong with LG C or G series.
I have an LG C2 77'' and I love it.

Yes, I would prefer to get another LG, but for some unknown reason I can't get one "online" 'til mid July :(

Not too interested in Sony's, or others....

I've just been trying to find the specs for some Samsungs, and there's no mention of Dolby Vision...will keep looking, I might have to do with the 50" 3D Samsung, or an old Samsung 42" Plasma, for a while :(

Thanks for your suggestion :)

UPDATE:-

So is the C2 & G2 a slightly older model ??

All I can find are B4, C4 & G4, the C being the cheaper, the B in the "middle", and the G is the top variant, some AU$1,000 dearer than a C.

[SamuriHL]

Samsung is not Dolby Vision friendly. They're HDR10+ only.

[guest]

Samsung is not Dolby Vision friendly. They're HDR10+ only.

Yes, I have found that...

Seems only LG & some Sony's are...

[Kuler087]

UPDATE:-

So is the C2 & G2 a slightly older model ??

All I can find are B4, C4 & G4, the C being the cheaper, the B in the "middle", and the G is the top variant, some AU$1,000 dearer than a C.

yes, the number represents the year. so C2=2022

[Fuso]

I also use 77C2. Don't bother with B series, the minimum is C series, but I can recommend you G3 or G4, but the later is still a new model and it is more expensive. G series has MLA (except 83"), which boosts the brightness.

[guest]

I also use 77C2. Don't bother with B series, the minimum is C series, but I can recommend you G3 or G4, but the later is still a new model and it is more expensive. G series has MLA (except 83"), which boosts the brightness.

Co-incidence...

I think C's would be plenty good enough, the G's are so much more $.

Either a 55, or maybe 65, no bigger.

[SamuriHL]

I love my g2 77.

Sent from my SM-S928U1 using Tapatalk

[guest]

I'm trying an 8-2-2, with 2.0.7, and I'm getting this error:-

vpy: Failed to load vsscript.dll.
failed to initialize file reader(s).
Failed to open input file.

But when using (same tools pack), 2.0.5 works :confused::confused:

Also, in 8-2-2, can this be changed, somewhere :-

Warning: Avisynth Compat: requested frame 181 not prefetched, using slow method

There's a pre-fetch setting, but it's only for 7-1.

[Kuler087]

But when using (same tools pack), 2.0.5 works

i don't know, works fine for me.

Warning: Avisynth Compat: requested frame 181 not prefetched, using slow method

it says that for the 200 first frame when I use avs_resize with vapoursynth. You can ignore it.


BTW, I added muxing in 8-2 in the latest beta

[guest]

i don't know, works fine for me.

it says that for the 200 first frame when I use avs_resize with vapoursynth. You can ignore it.

BTW, I added muxing in 8-2 in the latest beta

Well, there must be some tiny hiccup with my 2.0.7, so I might just grab the latest beta, and see what that does.

I don't usually use 8-2-* much, but I thought I'd try to convert HDR to SDR, as my LG 4K HDR TV "blew up", and I now only have an SDR Samsung, but strangely enough, it didn't make much difference :(

I have decided what TV, I'm going to get, but it won't be for a few weeks.

An LG C4 65 evo.

Cheers.

[Kuler087]

Well, nothing changed in 8-2 since 2.0.5...

I'm not sure if MP4 muxing will work for SDR though, I haven't tested. You might want to use the mkv version for SDR since mp4 is only useful for DV

[guest]

Well, nothing changed in 8-2 since 2.0.5...

I'm not sure if MP4 muxing will work for SDR though, I haven't tested. You might want to use the mkv version for SDR since mp4 is only useful for DV

I've now got 2.0.8 beta, so I will check that out tomorrow.

8-2-2 creates a .hevc file, which I then ran thru MKVToolNix to add audio and subs...

[Kuler087]

8-2-2 creates a .hevc file, which I then ran thru MKVToolNix to add audio and subs...
not in the latest beta, it will try to mux SDR to mp4 if you use the mp4 version
anyway even if it fails to mux, it will keep the encoded hevc file.

[guest]

not in the latest beta, it will try to mux SDR to mp4 if you use the mp4 version
anyway even if it fails to mux, it will keep the encoded hevc file.

Turned out that I had NOT installed VS properly, I have a reasonably fresh Windows setup, and hadn't installed everything, yet :(

Nevermind, I've now got the latest beta going :)

PS:- Is my new C4 going to need the new or old MP4 muxer...what do you use ??

[guest]

I took delivery of the LG 65" C4 today, and WOW...

Anyway, I "tested" a DS DV conversion that worked on the old LG, using the "old" Mp4Muxer option in the 3-1 workflow, and it worked, and displayed Dolby Vision.

Should I bother trying the "new" Mp4Muxer ??

Now all I need to do is install the RTX 4080 Super in the 7950X system, and see what difference that makes to the process.

[Kuler087]

NEW mp4muxer mode is faster and preserves the BL compatibility ID when muxing subtitles/lossless audio.

[CineManiac]

Hello, I just saw the release of 2.0.8 has the ability to remove dialnorm from ec3 and ac3 tracks. I’m not sure if you’re aware, Kuler, but the removal of dialnorm removes Atmos metadata if the track contains it. I would suggest a warning or something in case the track contains Atmos. After dialnorm removal the track will still show up as Atmos, but all sound will play through every speaker at the same time.

Sorry for the huge post.

[Kuler087]

Hello, I just saw the release of 2.0.8 has the ability to remove dialnorm from ec3 and ac3 tracks. I’m not sure if you’re aware, Kuler, but the removal of dialnorm removes Atmos metadata if the track contains it. I would suggest a warning or something in case the track contains Atmos. After dialnorm removal the track will still show up as Atmos, but all sound will play through every speaker at the same time.

Sorry for the huge post.

Atmos is not removed and I know that it does break object based metadata supports in some (most?)AVR and this is why this setting is set to OFF by default.

Personally, I prefer removing it because my AVR (and many others (https://www.avsforum.com/threads/defeating-dialnorm.3253654/)) can't disable DIALNORM for EC3/AC3 tracks and the volume sucks (check out Dune part two, it's -12DB). Sounds do not play in all the speakers at the same time, it plays like a regular 5.1 audio track but indeed the object-based metadata are not working.

and btw, there is a warning in the settings:

::choose if you want to remove the dialogue normalization of existing EC3/DDP/AC3/DD tracks (default= NO) DDP Atmos metadata may no longer works if you enable this. Works only if mux_all_audio=NO
set removeDialogueNorm=NO

[CineManiac]

Atmos is not removed and I know that it does break object based metadata supports in some (most?)AVR and this is why this setting is set to OFF by default.

Personally, I prefer removing it because my AVR (and many others (https://www.avsforum.com/threads/defeating-dialnorm.3253654/)) can't disable DIALNORM for EC3/AC3 tracks and the volume sucks (check out Dune part two, it's -12DB). Sounds do not play in all the speakers at the same time, it plays like a regular 5.1 audio track but indeed the object-based metadata are not working.

and btw, there is a warning in the settings:

Oh, I was unaware it depended upon the AVR. Thanks for the info.

[Hellboy.]

@Kuler087
The tsMuxer included with the Tools (don't know is already updated) contain some bugs that were fixed.

https://github.com/justdan96/tsMuxer/issues/874
https://github.com/justdan96/tsMuxer/issues/877

[Kuler087]

@Kuler087
The tsMuxer included with the Tools (don't know is already updated) contain some bugs that were fixed.

https://github.com/justdan96/tsMuxer/issues/874
https://github.com/justdan96/tsMuxer/issues/877

thanks for the info. I'll update the tools pack. I don't follow the tsmuxer github often since I got my Ugoos + MKV for everything.

[Black Ops]

Hi,

I am wondering if i can generate a hdr10+ layer for a Dovi/HDR10 video file and inject it in. I have a samsung TV and it seems the static metadata makes the video file appear quite dark

Is it possible using this tool? I cant seem to locate the correct workflow to do this . Below is the mediainfo excerpt indicating the current metadata inside of it

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

[Kuler087]

You have to generate the metadata (json) in Resolve and then you can inject with workflow 1-1

[Black Ops]

You have to generate the metadata (json) in Resolve and then you can inject with workflow 1-1

Thanks for getting back to me. Any particular settings and gotchas i need to keep in mind when using davinci to make sure the metadata generated is accurate. Havent really touched the software in awhile so just wanted to make sure im generating the data properly

[Kuler087]

see: https://www.youtube.com/watch?v=FVSh3oGqfXY

[Black Ops]

Thanks for the link. I've followed the guide sucessfully using a test HDR video and it seemed to have generated a working hdr10+ file. The batch files makes this process very simple

In regards to the blanking output, i did follow the video but im not sure if it applied my calculations to the entire video as im not familar with that part of davinci. Is there any way to check (maybe the JSON) check if the black bars were excluded in the hdr10+ analysis?

Also the pro-res render step is quite time consuming as it relies on the CPU, is there any other codec that are maybe GPU accelerated that would suffice? Im looking to speed up the generation of the new file and my current CPU (ryzen 5 5600x) isnt up to the task

[Kuler087]

In regards to the blanking output, i did follow the video but im not sure if it applied my calculations to the entire video as im not familar with that part of davinci

Yes, unless you manually change the blanking shot by shot as I did in the video, the timeline blanking you set is for the entire video/shots.

Is there any way to check (maybe the JSON) check if the black bars were excluded in the hdr10+ analysis?

No, but your maxfall metadata would be incorrect if your analysis included the letterbox. FYI, you can plot the metadata with workflow 6-6.


Also the pro-res render step is quite time consuming as it relies on the CPU, is there any other codec that are maybe GPU accelerated that would suffice? Im looking to speed up the generation of the new file and my current CPU (ryzen 5 5600x) isnt up to the task

I don't think so. You could downscale to 1080p and increase qscale to speed up the prores encoding.

[Black Ops]

Ah, might have been doing something wrong. Running through the davinci output blanking step, i can see the default value for the blanking values set at 1920x1080 despite the video being 3840x2160. What setting would i need to rectify in davinci so it defaults these values to the video i imported ? Would it be the output resolution setting in the image scaling tab (Within project settings)

Also during the import of the hdr10+ json, i get prompted if i want to resync the metadata which isnt shown in the video. Is the default option (no) ok?

EDIT ; I decided to set the custom resolution in the project seetings and it seemed to sort the resolution in the blanking tab. Applied the 2.4 blanking (Measured the offset 280 manually via the batch file) and generated the new HDR File

I then used the batch file to plot the metadata for the standard HDRD10 file leaving the left and right offsets blank and applied 280 to top and bottom when prompted. I also generated the plot for the HDR10Plus file using the built in workflow

HDR10 Original File Plot - https://imgur.com/a/zUhFUIa
HDR10+ New File - https://imgur.com/a/0Iv2Emd

Dont see anything out of the ordinary but its my first foray into the world of HDR since buying my first HDR TV (QN90C 50 inch) so want to make sure im not doing anything stupid. Aplogies for bothering the wise people of the forum

[Kuler087]

Also during the import of the hdr10+ json, i get prompted if i want to resync the metadata which isnt shown in the video. Is the default option (no) ok?

This is for when you want to inject hdr10plus from two different sources with different timing. Just press enter to skip.

Ah, might have been doing something wrong. Running through the davinci output blanking step, i can see the default value for the blanking values set at 1920x1080 despite the video being 3840x2160. What setting would i need to rectify in davinci so it defaults these values to the video i imported ? Would it be the output resolution setting in the image scaling tab (Within project settings)


Resolve usually detect the input resolution and set it accordingly so i dont know why you got 1920x1080

[Black Ops]

I guess my final question after going through this relatively straight forward process is why movie studio don’t bother including hdr10+ metadata alongside Dovi and HDR10. It seems simple to generate so why not

[rwill]

I guess my final question after going through this relatively straight forward process is why movie studio don’t bother including hdr10+ metadata alongside Dovi and HDR10. It seems simple to generate so why not

Most serious people don't let Resolve generate the HDR metadata. Serious people let a color grader do a HDR grade and then other serious people have to watch the result and they only sign it off if they are ok with it. The goal is to preserve the artistic intend of a production.

[Kuler087]

I could be wrong but I think they have fees to pay to use HDR10plus on bluray and streaming

[Black Ops]

Most serious people don't let Resolve generate the HDR metadata. Serious people let a color grader do a HDR grade and then other serious people have to watch the result and they only sign it off if they are ok with it. The goal is to preserve the artistic intend of a production.

No need for the passive aggressive remarks. Like I said, I’m a complete novice to the world of HDR so you can at least be polite

[maldon]

Hi, Kuler087. I just discovered this thread, I come from here:

https://forum.doom9.org/showthread.php?t=185308

I don't know if what I am about to say has already been asked but at this moment I have one doubt. Can I remove metadata without reencoding?

I am going to say what I want to do. I want to remove HDR10+ dynamic metadata i.e. I want to convert it to HDR10 (without +). That is:

Before (Mediainfo):

MPEG-H HEVC Video 49422 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 4:2:0 / 10 bits / HDR10+ / BT.2020 /

After (Mediainfo):

MPEG-H HEVC Video 49422 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 4:2:0 / 10 bits / HDR10 / BT.2020 /

If the UHD 4K Blu-ray has Dolby Vision I want to remove Dolby Vision. That is:

Before (Mediainfo):

MPEG-H HEVC Video 89803 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / HDR10 / BT.2020
* MPEG-H HEVC Video 80 kbps 1080p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / Dolby Vision / BT.2020

After (Mediainfo):

MPEG-H HEVC Video 89803 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / HDR10 / BT.2020


I think I have read that the latter can be done with TsMuxer but I am not sure. It seems to me that there is no 4K Ultra HD Disc with HDR10+ and Dolby Vision, so I only put those two examples.


Will it be possible to remove that without reencoding?

[Kuler087]

I don't know if what I am about to say has already been asked but at this moment I have one doubt. Can I remove metadata without reencoding?

I am going to say what I want to do. I want to remove HDR10+ dynamic metadata i.e. I want to convert it to HDR10 (without +). That is:

Before (Mediainfo):

MPEG-H HEVC Video 49422 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 4:2:0 / 10 bits / HDR10+ / BT.2020 /

After (Mediainfo):

MPEG-H HEVC Video 49422 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 4:2:0 / 10 bits / HDR10 / BT.2020 /

yes, workflow 8-2


If the UHD 4K Blu-ray has Dolby Vision I want to remove Dolby Vision. That is:

Before (Mediainfo):

MPEG-H HEVC Video 89803 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / HDR10 / BT.2020
* MPEG-H HEVC Video 80 kbps 1080p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / Dolby Vision / BT.2020

After (Mediainfo):

MPEG-H HEVC Video 89803 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / HDR10 / BT.2020


I think I have read that the latter can be done with TsMuxer but I am not sure. It seems to me that there is no 4K Ultra HD Disc with HDR10+ and Dolby Vision, so I only put those two examples.

Right, if you uncheck the 1080p DV layer in tsmuxer, the remuxed file will be HDR10 only.

[Guest]

Hi Kuler,

Seeing as TDS's profile hasn't been rectified yet, here's some info on his 1st 3-1 conversion with the 4080 Super..

Measuring the letterbox...


Done

---------------------------------
--> left border: 2104
--> right border: 1218
--> top border: 0
--> bottom border: 0
---------------------------------


Not sure why it detected these borders, as it should have 0's for all.

Parsing XML metadata...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 70406 frames
Done.
Parsing RPU file...
Processing input video for frame order info...
Rewriting file with interleaved RPU NALs..
Track Importing HEVC - Width 3840 Height 2160 FPS 24000/1001 SAR 1/1
OpenGOP detected - adjusting file brand
HEVC Import results: 70406 samples (214831 NALUs) - Slices: 624 I 16105 P 53677 B - 1806 SEI - 16 IDR - 586 CRA
HEVC Stream uses forward prediction - stream CTS offset: 4 frames
DV profile 8 must indicate a compatibility mode `hdr10`, `bt709` or `hlg2100`
Failure while setting DV profile: Bad Parameter
Error importing E:\Dovi_Encodes_MP4\Game of Thrones S05 E01 vol 3 0 gpu mb3_Generated.hevc:name=:hdr=none:dvp=8:fps=24000/1001p: Bad Parameter

Haven't seen this error before with any other GoT episodes, would it be the letterbox measurements ?

[Kuler087]

sometimes detectborder doesnt work. It's always better to do it manually.

[guest]

sometimes detectborder doesnt work. It's always better to do it manually.

I'm back :)

I guess I was more interested in seeing how the 4080 was going to go.

I'll have to compared it with the "old" 3060...

Is there a REALLY easy way to check the borders ??

[Kuler087]

Yeah, it's very easy( and 100% accurate) to do it manually in AVSpmod, workflow 6-1.

Zoom 400% and crop. You can watch the youtube P8 hybrid tutorial (https://www.youtube.com/watch?v=hVWZpat34oc), at some point in the video, I do the manual measurement of the letterbox.

[guest]

Yeah, it's very easy (and 100% accurate) to do it manually in AVSpmod, workflow 6-1.

I have tried that, but didn't have too much success :(

Zoom 400% and crop. You can watch the youtube P8 hybrid tutorial (https://www.youtube.com/watch?v=hVWZpat34oc), at some point in the video, I do the manual measurement of the letterbox.

I can also check the cropping with RipBot264, as it uses the same detect borders script...I VERY rarely crop anything.

Is there an option to "bypass" the cropping step ?? (in 3-1)

Now, back to the error that FTLOY posted for me, it seems there's something wrong with my DS setup on the 7950X, as it is now stalling at a different part of the workflow, but if I do the same file on the 13900KF with 2.0.7, there's NO issues...might need to start from scratch on the 7950X.

Are there any significant changes in the Tools Pack, recently ??

[Kuler087]

Is there an option to "bypass" the cropping step ?? (in 3-1)
nop

Now, back to the error that FTLOY posted for me, it seems there's something wrong with my DS setup on the 7950X, as it is now stalling at a different part of the workflow,
I don't know without the complete log with ''echo on''

Are there any significant changes in the Tools Pack, recently ??

nop

[guest]

I don't know without the complete log with ''echo on''

OK, I've been doing some tests with various builds, 2.0.7, 2.0.8 & 2.0.9 beta

And it seems that 2.0.7 doesn't have those errors, but 2.0.8. & 2.0.9 beta does.

I did an "echo on" run, and here's the log:- (too big to post here)

I hope it's something wrong at my end, but I tried it on 2 PC's.

See what you find.

Cheers

FIXED :)

[Kuler087]

try the latest beta

[guest]

try the latest beta

That log was created with the latest beta, I got it just before I ran that test...a couple of hours ago.

Surely you haven't posted a newer one ??

[Kuler087]

Yes, I posted a new one minutes ago. The file is synced with my PC Google Drive so it's updated automatically as soon as I make any change.

[guest]

Yes, I posted a new one minutes ago. The file is synced with my PC Google Drive so it's updated automatically as soon as I make any change.

SUCCESS :)

:thanks:

PS:- I like the extra touch of colour in the Workflows :)

[guest]

Something else...

Once that 2.0.9 beta had been fixed, I ran a 3-1 conversion, and once it was completed, played it with PotPlayer, and it was incredibly out of sync, the video wasn't full length, and it was jerky.

So I went back to 2.0.7, it actually processed a little quicker, and was perfect....

I just checked what mp4muxer was being used, and 2.0.7 was old, and 2.0.9 beta was new...could that be the issue/difference ? (I haven't got time today to try 2.0.9 with the old) :(

And not that it really matters, but is there a way to update the CUDA version ??

https://i.imgur.com/507QnKP.jpg

[Kuler087]

it actually processed a little quicker,
cm_analyze speed is inconsistent with prores+windows. Nothing we can do about it.

is there a way to update the CUDA version ??
no I have no control on cm_anlayze

played it with PotPlayer, and it was incredibly out of sync,
what about your TV?

[guest]

cm_analyze speed is inconsistent with prores+windows. Nothing we can do about it.


no I have no control on cm_anlayze


what about your TV?

TBH, when it played that badly with PotPlayer, I wasn't going to waste time trying it on the TV.. it can be "fussy" with video problems it doesn't like.

It was pretty messed up, believe me :(

I will try 2.0.9 with the "old" mp4muxer tomorrow, that is the only difference I know of.

[Kuler087]

I just tried it on my PC with MPC/MAVDR and no issue at all...

[guest]

I just tried it on my PC with MPC/MAVDR and no issue at all...

Did a couple more tests..

Did a chunk with 2.0.9 beta, 3-1, old muxer & new muxer.

Both played well with MPC, new did not like PotPlayer, old did.

Old played good on TV, new did not :(

======================================

I'm going to try and "learn" Resolve, just to know a different process.

Is there a tutorial for SDR to HDR, or is this the one:-

https://youtu.be/728R3ppSWuk?list=PLFGpkrmX_eOL2Dre1ZyIJP2uMtcQYH8ql

======================================

I'm sorry, I just seem to be going backwards with all this stuff :(

I get this with 8-2-3... (2.0.7 and 2.0.9.beta)

-------------------------------------------------------------------------------------
-- Can Encode any HDR source(DVP7/DVP5/HDR10/HLG) to HDR PRORES 422 HQ
-- This script use DoVi_Baker(require nvidia gpu) and libplacebo
-- Require Vapoursynth and P7 requires nvidia GPU. Does not support P5 to P5
-------------------------------------------------------------------------------------

Drag and drop a video and press enter...
"E:\Ripbot Encodes (4K)\The Fifth Element (1997) DV chunk tr6.mkv"

Reading input tracks format/id/language...
Done.
Done.
Indexing, please wait... 100%
Writing index... done.
Failed to initialize VSScript
[in#0 @ 000001588e89e140] Error opening input: Invalid data found when processing input
Error opening input file pipe:.
Error opening input files: Invalid data found when processing input
Deleting TEMP folder...

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?

[Kuler087]

I get this with 8-2-3... (2.0.7 and 2.0.9.beta)

Is your input P5 ? For some reason, some P5 iTunes web-dl won't work in vapoursynth libplacebo but works fine with avisynth. So you might want to use the old version of the script that still used avisynth for profile 5 for now until I change it back to avisynth as I said in my latest changelog.

if your input is HDR10/P8 or P7 or HLG, then the issue is on your end


Is there a tutorial for SDR to HDR, or is this the one:-

https://youtu.be/728R3ppSWuk?list=PLFGpkrmX_eOL2Dre1ZyIJP2uMtcQYH8ql

No tuto, but yes this is how I do it.

[guest]

Is your input P5 ? For some reason, some P5 iTunes web-dl won't work in vapoursynth libplacebo but works fine with avisynth. So you might want to use the old version of the script that still used avisynth for profile 5 for now until I change it back to avisynth as I said in my latest changelog.

if your input is HDR10/P8 or P7 or HLG, then the issue is on your end


I'm pretty sure they are "basic" HDR10 mkv's, I was wanting to convert to prores to use in Resolve..

I tried a couple of different clips, but same....just a little frustrating, as I thought I'd sorted things out with VS a week or so ago.

[guest]

I had a bit of a play with Resolve, and I think I have to very basic stuff figured out, but the blanking & color grading is a little over my head, even trying to follow some of your tuto's....when you're trying to follow the steps of someone that knows exactly what they're doing...it's a little intimidating.

Is the blanking important ???

I also noticed that there are some video files that Resolve will not import into its Media library...

I also grabbed the latest beta, and there's more changes, but I'm still getting those annoying VSscript, etc, errors, so I can't do some of the conversions necessary for Resolve, although I did manage to convert a "chunk" to .mov using 8-2-5 SDR to HDR workflow, (on another PC using 2.0.7) but after running that thru Resolve, I couldn't produce a HDR .mp4 or .mkv...just more errors :(

Even tho you haven't complied an SDR to HDR tutorial, it would be nice if you could find the time to do one.

But like I said the other day, I feel like I've taken one step forward, and many steps back...not sue what's going on :(

Might just have to settle to using only 3-1...

[Kuler087]

Is the blanking important ???

yes, without it, the letterbox is included in the DV analysis/metadata.

I also noticed that there are some video files that Resolve will not import into its Media library...
never happened to me with prores file. With mkv files, I think the ones with TrueHD audio will not show up but you should never use mkv/hevc file in resolve in the first place.

I also grabbed the latest beta, and there's more changes, but I'm still getting those annoying VSscript, etc, errors, so I can't do some of the conversions necessary for Resolve

Nothing changed in the encoder workflows in a while. The changes im doing right now are related to the menu selection. I simplified it a lot. (1-1) (1-2) (2-1-1) (2-1-2) (2-2) will soon be all merged together.

I did manage to convert a "chunk" to .mov using 8-2-5 SDR to HDR workflow, (on another PC using 2.0.7) but after running that thru Resolve, I couldn't produce a HDR .mp4 or .mkv...just more errors
you should not export to HEVC from resolve, it produces poor quality. It's always better to export to a lossless codec like jpeg2000 or cineform and then encode to hevc with x265.exe/staxrip/ffmpeg/whatever.


Even tho you haven't complied an SDR to HDR tutorial, it would be nice if you could find the time to do one.

Well what I'm doing depends on what I see on my mastering monitor, I never really do the same.

[guest]

yes, without it, the letterbox is included in the DV analysis/metadata.

Well, I'm going to have to watch your tutorials again, 'til I can figure out how you do it...

never happened to me with prores file. With mkv files, I think the ones with TrueHD audio will not show up but you should never use mkv/hevc file in resolve in the first place.

Noted..


you should not export to HEVC from resolve, it produces poor quality. It's always better to export to a lossless codec like jpeg2000 or cineform and then encode to hevc with x265.exe/staxrip/ffmpeg/whatever.

I don't think I explained this properly, I didn't export from Resolve, once I ran it thru Resolve and created the .json & .xml files, using 1-1 to inject, didn't work, they basically created empty files.


Well what I'm doing depends on what I see on my mastering monitor, I never really do the same.

Fair enough, you're obviously very well set up for what you're doing.

===================================

But before going forward, I need to figure out why I'm getting so many errors...I'll probably have to start from scratch with everything :(

[Kuler087]

I don't think I explained this properly, I didn't export from Resolve, once I ran it thru Resolve and created the .json & .xml files, using 1-1 to inject, didn't work, they basically created empty files.
I don't know, you said:

''8-2-5 SDR to HDR workflow, (on another PC using 2.0.7) but after running that thru Resolve, I couldn't produce a HDR .mp4 or .mkv...just more errors ''

You cant inject dv to prores with my script... the SDR to HDR process requires:
1- convert sdr to hdr bt2020 100nits prores
2- grade hdr in resolve
3- deliver to a lossless HDR codec (jpeg2000 or cineform for example)
4- encode to hevc HDR
5- export dv hdr10plus metadata
6- inject metadata

[guest]

I don't know, you said:

''8-2-5 SDR to HDR workflow, (on another PC using 2.0.7) but after running that thru Resolve, I couldn't produce a HDR .mp4 or .mkv...just more errors ''

You cant inject dv to prores with my script... the SDR to HDR process requires:
1- convert sdr to hdr bt2020 100nits prores
2- grade hdr in resolve
3- deliver to a lossless HDR codec (jpeg2000 or cineform for example)
4- encode to hevc HDR
5- export dv hdr10plus metadata
6- inject metadata

Aaah, that will make ALL the difference, to now actually know the workflow :)

I only missed 3 "important steps"...nice.

:thanks:

[guest]

I am testing a small clip to see what "delivery" options Resolve has, and using JPEG2000 just creates 1,000's of files, what do you do with them ??

Also, I can't find a cineform option, the one that "sounds" close in cineon, and that creates 1,000's of files too.

UPDATE:-I think you probably mean using Quicktime as the format, and under that, the codecs are either GoPro Cineform, or Kakadu JPEG 2000 (remember I am a complete novice, and don't know the "shortcuts")

On to try my luck with blanking (not too hopeful)

=================================================================

I downloaded the latest beta (changed again), and the newest tools pack, and I got this when using 8-2-5, which used AVS, and created a .mov file, but the .mp4 muxing failed (by the looks)

See this:-

https://www.mediafire.com/file/9ap412d09ak9jzc/DS+2.0.9.beta+8-2-5+warnings.txt/file

[Kuler087]

I downloaded the latest beta (changed again), and the newest tools pack, and I got this when using 8-2-5, which used AVS, and created a .mov file, but the .mp4 muxing failed (by the looks)
yea, this workflow is not supposed to mux, but you got the prores HDR file you needed.

[guest]

yea, this workflow is not supposed to mux, but you got the prores HDR file you needed.

I ran that .mov thru Resolve, did as much to it as I could understand, exported the .json & .xml, injected them, they don't play on the TV :(

[Kuler087]

again, you have to encode the Resolve delivery file to hevc

[guest]

again, you have to encode the Resolve delivery file to hevc

I had a 5 minute chunk file (.mkv), converted to prores .mov, (8-2-5) loaded it into Resolve, delivered it as a Quicktime, Kakadu JPEG 2000.

Loaded that into RipBot264 (took quite a while to process), so that produced an x265 .mkv.

Exported the .xml & .json files then tried to inject them, which seemed to work, played with PotPlayer, but the TV just wasn't interested, tried it in a little Android box, and they played, but very slow & jittery.

I again also tried blanking, but the clip I was using didn't seem to want to co-operate.

Is scaling the same as blanking ??? it's just that I watched a few other YT clips on blanking, and re-sizing clips.

[Kuler087]

Then you did not encode your HEVC file correctly. I don't know about ripbot and jpeg-2000 but here's a Staxrip template that will work with the cineform codec(the same delivery format I use in the video)
https://drive.google.com/file/d/12XPk5SJbR9bZtyjGJGfYMcW7tDfWLNgF/view?usp=drive_link

I again also tried blanking, but the clip I was using didn't seem to want to co-operate.
the clip? the blanking is done in resolve and recorded in the DV XML metadata.

[guest]

Then you did not encode your HEVC file correctly. I don't know about ripbot and jpeg-2000 but here's a Staxrip template that will work with the cineform codec(the same delivery format I use in the video)
https://drive.google.com/file/d/12XPk5SJbR9bZtyjGJGfYMcW7tDfWLNgF/view?usp=drive_link

I will have another attempt using the Cineform codec, but I did noticed that when encoding the JPEG2000 it wasn't running "smoothly" during the encode.

I'm not very familiar with Staxrip, but I will have a look at the script you sent.


the clip? the blanking is done in resolve and recorded in the DV XML metadata.

Sorry, by "clip" I was referring to the 5 minute chunk video that I was using in Resolve.

The "clip" had very small black bars top & bottom, but I couldn't remove them with blanking, but I could remove them with scaling.

PS:- should I be using the mkv.bat, instead of the mp4 one ??

[Kuler087]

I will have another attempt using the Cineform codec, but I did noticed that when encoding the JPEG2000 it wasn't running "smoothly" during the encode.
On my end, I could encode the jpeg2000 RGB 12bit master with staxrip/x265 but the RGB to YUV conversion with avsresize was slightly off so I'm using the Dolby Encoding Engine (DEE) (https://professional.dolby.com/product/media-processing-and-delivery/dee--dolby-encoding-engine/) and the encoded colors are perfect.

If you deliver to cineform and use the staxrip template I sent you, your hevc encode colors will be accurate, like my DEE workflow. I use an old staxrip version so that template might not work with the latest versions. Just copy it in your template folder and import a file, modify metadata/preset/crf if you want and encode. Staxrip is very easy to use.

The "clip" had very small black bars top & bottom, but I couldn't remove them with blanking, but I could remove them with scaling.
you're confusing blanking for DV/HDR10plus and cropping/removal of the letterbox. You will still see the black bars in Resolve when you set your blanking, it is normal. The blanking tells the DV and HDR10plus algorithm to ignore the black bars during the analysis (metadata creation).
The blanking will be recorded in the DV XML metadata which will be used by your TV during playback unless you crop your encode which will force the blanking to 0(because no more black bar to ignore)

PS:- should I be using the mkv.bat, instead of the mp4 one ??
All the script's versions are the same code. The only difference is the muxing when a workflow has been completed.
I'm almost done re-working the injector/editor menu selections. I really like how they work now, fewer user prompts and more straightforward. Direct drag and drop on the bat file is also much improved.

[guest]

On my end, I could encode the jpeg2000 RGB 12bit master with staxrip/x265 but the RGB to YUV conversion with avsresize was slightly off so I'm using the Dolby Encoding Engine (DEE) (https://professional.dolby.com/product/media-processing-and-delivery/dee--dolby-encoding-engine/) and the encoded colors are perfect.

If you deliver to cineform and use the staxrip template I sent you, your hevc encode colors will be accurate, like my DEE workflow. I use an old staxrip version so that template might not work with the latest versions. Just copy it in your template folder and import a file, modify metadata/preset/crf if you want and encode. Staxrip is very easy to use.

Like I said, I'm not familiar with Staxrip...what version do you use, (2.29) I might try and find it somewhere (videohelp, might have it)


you're confusing blanking for DV/HDR10plus and cropping/removal of the letterbox. You will still see the black bars in Resolve when you set your blanking, it is normal. The blanking tells the DV and HDR10plus algorithm to ignore the black bars during the analysis (metadata creation).
The blanking will be recorded in the DV XML metadata which will be used by your TV during playback unless you crop your encode which will force the blanking to 0(because no more black bar to ignore)

And also, I am not familiar with Resolve either, so it's VERY easy for me to get confused, trying to figure out something new.

I try to follow your tuto's, but because you know what you're doing, and I haven't got a clue, it's a little too fast for me to follow...it will take me some time :(


All the script's versions are the same code. The only difference is the muxing when a workflow has been completed.
I'm almost done re-working the injector/editor menu selections. I really like how they work now, fewer user prompts and more straightforward. Direct drag and drop on the bat file is also much improved.

More changes, sounds interesting....

Thanks

UPDATE:-

SUCCESS !!!!!!!!!!!!

It's an interesting process, lots of steps, but I have been successful in converting an SDR 1080p to HDR DV / HDR10+ :)

I managed to get your "script" into StaxRip 2.93.3 (which is still oldish), processed that, I tried chunk encoding, but for some weird reason it didn't mux them into a single file, so I combined them with MKVToolNix.

Imported into Resolve, did some basic "fiddle", and did the Detect Scene Cuts, etc, etc (probably only really need the Dolby Vision enabled), exported the json & xml, and played them on the LG, and it worked (didn't have an audio track), but the process has enhanced any defects in the original, which has a lot of small black spotty artifacts jumping around the screen, in certain scenes, might need to find a filter to get rid of those.

Just out of interest, how would I output a HLG version ?? would that be simply a Color Management Setting ??

[Kuler087]

Just out of interest, how would I output a HLG version ??
I don't know

[wyup]

Hi, what do you think about adding a tonemapping mode to the scripts for upscaling brightness of a low-nit movie with libplacebo library, with the goal of getting more brightness on a regular tv?

I.e: A 600-nit graded movie has limited brightness when displayed on a oled tv, even with max brightness setting on the menu. By upscaling peak brightness to 1k, 4k or 10k we get more available brightness for our tvs, even without DV or HDR10+, just using the internal tv tonemapping with relevant HDR10 MaxCLL and MaxMDL metadata.

Alternatively, it would be nice to have a down tonemapping option to downscale a 4k, 6k, 10k nit movie to user input value, let's say 1k nit, using libplacebo's algorithms such as ITU-R Report BT.2446, method A, for which you only need peak brightness for source and destination.

[Kuler087]

I guess I could add the option to deliver the 600 or 1000nits dolby vision trim pass in 8-2-5 (it does 100nits only right now).
As for boosting brightness, I don't believe in any form of automatic/one-click HDR conversion. HDR must be graded shot by shot so this won't happen in DoVi_scripts sorry.

[DMD]

......HDR must be graded shot by shot so this won't happen in DoVi_scripts sorry.
I think this is the most time-consuming work to do, and manual work is the one that gives the best results. But if there was an algorithm that could do this work automatically, it would be a dream.

[Kuler087]

I think this is the most time-consuming work to do, and manual work is the one that gives the best results. .

Yes, indeed. It takes me about 2-3H for the HDR grading and another 2-3H for the Dolby Vision trim pass.

But if there was an algorithm that could do this work automatically, it would be a dream

It already exists but I won't say the name because he's asking money for it and he's sharing my scripts(without my consent) in the pack he sells.

[DMD]

Yes, indeed. It takes me about 2-3H for the HDR grading and another 2-3H for the Dolby Vision trim pass.



It already exists but I won't say the name because he's asking money for it and he's sharing my scripts(without my consent) in the pack he sells.
I know who you are talking about, it has a disproportionate cost and a business policy that I don't like, with unfair behavior to you as well.
Software development with more reasonable cost in my opinion would have been more popular among enthusiasts.

[guest]

Yes, indeed. It takes me about 2-3H for the HDR grading and another 2-3H for the Dolby Vision trim pass.

It already exists but I won't say the name because he's asking money for it and he's sharing my scripts(without my consent) in the pack he sells.

Kuler,

Wow, I can't believe it takes so long to do all that, you must be VERY particular...

So the HDR grading is with Resolve, and the trim pass must be with your tools, correct ???

I haven't done any full length movies yet, only 1 hour +/- TV episodes, but I think the 4080 has made a nice difference to part of the process :)

Thing is, your grading could be a LOT different to someone else's "eye", for example, if you & DMD processed the same file, with basically the same processes, it could turn out a lot different.

With my communication with DMD (who actually introduced me to DS in the 1st place), he is a very particular encoder....

So is this something that you could work on, and figure out for yourself ??

Is there some way that you could arrange with some or your "friends" to buy this package, and then go from there ??

Or is there a principal in play here ?? I mean, he "stole" from you, you could "borrow" from him.

Just thinking out loud. (tell me if you don't want some of my comments to stay here, I will gladly edit it if you so desire)

[Kuler087]

So the HDR grading is with Resolve, and the trim pass must be with your tools, correct ???
No, everything is done in Resolve. The video you saw includes the DV trim pass creation too. The manual trim starts halfway through the video but remember that the video is sped up 50 (or 100%? I don't remember), I don't go that fast.

Once you're done with the shot-by-shot HDR grading(at 600-1000nits), I run the DV analysis which creates the DV L1 metadata and it also produces a preview of how the tone mapping will look at a 100, 600, 1000 and 2000nits target.
Then I go shot by shot again and do the 100nits SDR trim pass by referencing the original SDR grade(my source) side by side with my HDR grade tonemapped back to SDR and if it differs too much (too dark, too bright, crush, clip or saturation), I adjust the tone mapping with the Dolby Vision controls.
This trim metadata will then be used by the TV to tone map to its capabilities more accurately than if it had L1 only. It will reference what I did in the trims and extrapolate the adjustment to any TV brightness target.


FYI, DV trim pass is done at 100nits SDR only for about 80% of the Movies/TV because it's the maximum compression(lowest point) your HDR grade will get tone mapped. 600-1000nits trims are very rare, studios almost never require them.


Thing is, your grading could be a LOT different to someone else's "eye", for example, if you & DMD processed the same file, with basically the same processes, it could turn out a lot different.
of course

Is there some way that you could arrange with some or your "friends" to buy this package, and then go from there ??
Or is there a principal in play here ?? I mean, he "stole" from you, you could "borrow" from him.

Nah, I could easily do the same without having to buy their stuff. I'm just not interested in any form of one-click SDR to HDR conversion. You could just apply the same HDR settings to all the shots in Resolve and that would be the same.
They did not steal it, anyone can use my scripts. I'm just not a fan of their work and the fact that they sell stuff that should be free. I'm all about sharing...

[guest]

No, everything is done in Resolve. The video you saw includes the DV trim pass creation too. The manual trim starts halfway through the video but remember that the video is sped up 50 (or 100%? I don't remember), I don't go that fast.

Once you're done with the shot-by-shot HDR grading(at 600-1000nits), I run the DV analysis which creates the DV L1 metadata and it also produces a preview of how the tone mapping will look at a 100, 600, 1000 and 2000nits target.
Then I go shot by shot again and do the 100nits SDR trim pass by referencing the original SDR grade(my source) side by side with my HDR grade tonemapped back to SDR and if it differs too much (too dark, too bright, crush, clip or saturation), I adjust the tone mapping with the Dolby Vision controls.
This trim metadata will then be used by the TV to tone map to its capabilities more accurately than if it had L1 only. It will reference what I did in the trims and extrapolate the adjustment to any TV brightness target.

FYI, DV trim pass is done at 100nits SDR only for about 80% of the Movies/TV because it's the maximum compression(lowest point) your HDR grade will get tone mapped. 600-1000nits trims are very rare, studios almost never require them.

of course

Nah, I could easily do the same without having to buy their stuff. I'm just not interested in any form of one-click SDR to HDR conversion. You could just apply the same HDR settings to all the shots in Resolve and that would be the same.
They did not steal it, anyone can use my scripts. I'm just not a fan of their work and the fact that they sell stuff that should be free. I'm all about sharing...

I will have to watch that tuto again, slowed down :(

Like I said, I haven't done any full length movies yet, but I think my workflow would be something like this:-

If it was HDR (or SDR, but so much these days), I would run it thru RipBot264, and do any filtering, "grading", etc,

Then simply use 3-1 to create a DV, which looks so much nicer than HDR.

With SDR stuff (1080p or lesser),
I would still do my first run thru RipBot,
then convert to .mov with 8-2-5 (I think it is),
then run it thru Resolve, do the necessary steps, probably no "grading" or blanking, then deliver as CineForm, (can I get the HDR10 & DV metadata at this point ??)
then load that into StaxRip, using your script, (I'd really like to get a similar script set up for RipBot, (which would have to be for Avisynth) as it could be a LOT faster to process.)
then after that, back into Resolve to get the DV metadata, and inject that with 1-1.
And hopefully end up with "good enough for me" DV HDR .mp4, I can't justify spending so much time on one video :(

I will have to double check those steps, once I've finished GoT stuff.

[DMD]

Quickly summarizing the procedure to create REC709 SDR 100nits To REC2020 HDR10 Dolby Vision conversion:

1- Creating file with intermediate codec SDR 100 nit (ProRes 422 HQ) via DoVi script (8-2-5).
2- Via Resolve, scene-by-scene HDR detection and classification.
3- Via Resolve, Do.Vi analysis.
4- Via Resolve, Do.Vi xml metadata export.
5- Via Resolve, export file delivery format (Cineform).
6- Plotting HDR10 via DoVi Script (6-2).
7- x265 encoding via StaxRip.
8- Do.Vi. metadata injection via DoVi Script (1-1).

End.

Translated with DeepL.com (free version)

[guest]

Quickly summarizing the procedure to create REC709 SDR 100nits To REC2020 HDR10 Dolby Vision conversion:

1- Creating file with intermediate codec SDR 100 nit (ProRes 422 HQ) via DoVi script (8-2-5).
2- Via Resolve, scene-by-scene HDR detection and classification.
3- Via Resolve, Do.Vi analysis.
4- Via Resolve, Do.Vi xml metadata export.
5- Via Resolve, export file delivery format (Cineform).
6- Plotting HDR10 via DoVi Script (6-2).
7- x265 encoding via StaxRip.
8- Do.Vi. metadata injection via DoVi Script (1-1).

End.

Translated with DeepL.com (free version)

Hi DMD,

Thats a nice little summary of the process, thanks....

I'd like to ask 2 questions about StaxRip, I remember quite some time ago, on the RipBot264 thread, I told you about the chunk encoding feature in StaxRip, so I am wondering if you use that ??

I tried a chunk encode the other day, and I had it running 4 chunks, but at the end of the process, it didn't combine/mux them into a single file, I had to do it in MKVToolNix, but I'm sure it used to do it.

I still have the Post-It note I scribble on, from back then, but it works differently for some reason.

Also, do you use Vapoursynth or Avisynth script's in StaxRip to do this ??

[DMD]

Hi DMD,
Thats a nice little summary of the process, thanks....

I'd like to ask 2 questions about StaxRip, I remember quite some time ago, on the RipBot264 thread, I told you about the chunk encoding feature in StaxRip, so I am wondering if you use that ??
Yes. I always use block coding with StaxRip.
....I tried a chunk encode the other day, and I had it running 4 chunks, but at the end of the process, it didn't combine/mux them into a single file, I had to do it in MKVToolNix, but I'm sure it used to do it.
Try other combinations with your processor; perhaps you used too many blocks.
In my case I use:
Setting>General>Maximum number of parallel process 3
X265 Options>Input/Output> Chunks 3
....I still have the Post-It note I scribble on, from back then, but it works differently for some reason.
Also, do you use Vapoursynth or Avisynth script's in StaxRip to do this ??
This is the script I use for x265 encoding, selection asm avx512 depends on CPU instruction.
Values of CFR, Preset, MaxCLL Max FALL depend on custom processing:
--crf 14 --preset slow --output-depth 10 --profile main10 --level-idc 5.1 --vbv-bufsize 160000 --vbv-maxrate 160000 --no-cutree --hme-search umh,umh,star --hme --no-open-gop --pme --asm avx512 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --hdr10 --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-luma 1023 --max-cll "1000,400" --hdr10-opt --sar 1:1 --chromaloc 2 --no-info --repeat-headers --aud --hrd --deblock 2:2 --no-sao --no-strong-intra-smoothing

[guest]

Yes. I always use block coding with StaxRip.

Nice :)

Try other combinations with your processor; perhaps you used too many blocks.
In my case I use:
Setting>General>Maximum number of parallel process 3
X265 Options>Input/Output> Chunks 3

I have a 7950X, just like you, but what I don't understand is why it doesn't mux them into a single file, at the end of the process.

This is the script I use for x265 encoding, values of CFR, Preset and MaxCLL and Max FALL depend on custom processing:

Kuler posted the template he uses, see here:-

https://forum.doom9.org/showthread.php?p=2004006#post2004006

Do you have a "custom" .srip, template ??

This more to do with how x265 processes things, not a specific template for StaxRip

--crf 14 --preset slow --output-depth 10 --profile main10 --level-idc 5.1 --vbv-bufsize 160000 --vbv-maxrate 160000 --no-cutree --hme-search umh,umh,star --hme --no-open-gop --pme --asm avx512 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --hdr10 --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-luma 1023 --max-cll "1000,400" --hdr10-opt --sar 1:1 --chromaloc 2 --no-info --repeat-headers --aud --hrd --deblock 2:2 --no-sao --no-strong-intra-smoothing

[DMD]

Nice :)



I have a 7950X, just like you, but what I don't understand is why it doesn't mux them into a single file, at the end of the process.



Kuler posted the template he uses, see here:-

https://forum.doom9.org/showthread.php?p=2004006#post2004006

Do you have a "custom" .srip, template ??

This more to do with how x265 processes things, not a specific template for StaxRip
I don't use a template, I use the custom x265 preset.

[wyup]

I guess I could add the option to deliver the 600 or 1000nits dolby vision trim pass in 8-2-5 (it does 100nits only right now).
As for boosting brightness, I don't believe in any form of automatic/one-click HDR conversion. HDR must be graded shot by shot so this won't happen in DoVi_scripts sorry.
I believe you don't need to grade shot by shot to proportionally increase brightness. Any tv does this with picture settings, actually.
I think you are confusing this with grading SDR to HDR. There must be an avisynth or vapoursynth library plugin to proportionally increase overall brightness/gain of an image, or else with Resolve.

As for down-tonemapping from high luminance content, 600 or 1000 nits DV trim would do, especially 1000 since many tvs natively map to this capacity. This would be better than what non-DV tvs do internally.

[guest]

I don't use a template, I use the custom x265 preset.

But you must also need to use either an Avisynth or Vapoursynth script of some sort ???

Kuler's template uses Vapoursynth.

I wish I knew how to create an Avisynth script that does the same thing, unless Avisynth doesn't work with CineForm .mov's.

[guest]

I believe you don't need to grade shot by shot to proportionally increase brightness. Any tv does this with picture settings, actually.
I think you are confusing this with grading SDR to HDR. There must be an avisynth or vapoursynth library plugin to proportionally increase overall brightness/gain of an image, or else with Resolve.

As for down-tonemapping from high luminance content, 600 or 1000 nits DV trim would do, especially 1000 since many tvs natively map to this capacity. This would be better than what non-DV tvs do internally.

There are definitely many Avisynth filters/scripts that can do that, and so much more.

I have created many AVS scripts that I use with RipBot264, but I have no experience with Vapoursynth, as RipBot doesn't use it :(

[Kuler087]

But you must also need to use either an Avisynth or Vapoursynth script of some sort ???

Kuler's template uses Vapoursynth.

I wish I knew how to create an Avisynth script that does the same thing, unless Avisynth doesn't work with CineForm .mov's.

I don't know about ripbot, but I have a staxrip template in AVS too:

https://mega.nz/folder/EKNw2LZa#Id8kTHOTjRfbuN9GWb5tLQ

These are all set to my own path though. Change it for each template in:
Options / Paths

[guest]

I don't know

I found out how to do this, it's just a different option in the colour management selection.

When playing these back on the LG, it displays HLG HDR up in the top right corner :)

[guest]

I don't know about ripbot, but I have a staxrip template in AVS too:

https://mega.nz/folder/EKNw2LZa#Id8kTHOTjRfbuN9GWb5tLQ

These are all set to my own path though. Change it for each template in:
Options / Paths

:thanks: :)

[Kuler087]

I believe you don't need to grade shot by shot to proportionally increase brightness. Any tv does this with picture settings, actually.
I think you are confusing this with grading SDR to HDR.

Nop, it doesn't matter if you want to increase a 100nits or a 500nits grade to 1000nits. It must be done shot by shot for proper results.
There's no point in raising everything evenly but if that's what you want to do, just apply the same HDR settings in Resolve for all the shots. As I said, I'm not interested in doing a script that does that.

[DMD]

But you must also need to use either an Avisynth or Vapoursynth script of some sort ???

Kuler's template uses Vapoursynth.

I wish I knew how to create an Avisynth script that does the same thing, unless Avisynth doesn't work with CineForm .mov's.
This is my 3 chunks template:
https://mega.nz/file/QmUBCaAZ#1QDYp9PvO_1oQkMEaqLMr7gbta3qiirykD_K82TCGh8

[guest]

This is my 3 chunks template:
https://mega.nz/file/QmUBCaAZ#1QDYp9PvO_1oQkMEaqLMr7gbta3qiirykD_K82TCGh8

:thanks: :)

[guest]

I've had some success with some custom x265 profiles, and an AVS script to process these SDR-HDR .mov's from Resolve, with RipBot264 :)

A combination of the AVS script's that both DMD & Kuler provided (I had to dig thru the many you sent, to find one that I thought was the closest to the VS one you provided a couple of days ago), and a LOT of trial and error.

Thankfully I've had a little bit of experience with .mov's, a year or so back, with DMD.

The ONLY thing that is different, it doesn't like the GoPro CineForm codec, BUT JPEG2000 works just fine, whereas before, it was the other way around.

So at this point, that drops out the StaxRip step, and the advantage there is, RipBot is a LOT faster at encoding that StaxRip will EVER be.

Unless something catastrophic occurs, I'm pretty happy with that.

Thanks to all involved :)

[wyup]

Nop, it doesn't matter if you want to increase a 100nits or a 500nits grade to 1000nits. It must be done shot by shot for proper results.
There's no point in raising everything evenly but if that's what you want to do, just apply the same HDR settings in Resolve for all the shots. As I said, I'm not interested in doing a script that does that.
Why would I need to regrade a HDR movie if it's already HDR? A new grade would be a new interpretation and I'd like the same image, but brighter.
The point of raising everything evenly is to get more brightness from the tv. I've noticed that a 6,000-nit movie gets more available brightness from my tv than a 1,000-nit one does. Have you by chance noticed this?
I respect if you are not interested. Yes, it can be done with Resolve.

[Kuler087]

The ONLY thing that is different, it doesn't like the GoPro CineForm codec, BUT JPEG2000 works just fine, whereas before, it was the other way around.
I would compare the colors if I was you. I failed to color-accurate encode jpeg2000 RGB 12bit to YUV 10bits without DEE.

RipBot is a LOT faster at encoding that StaxRip will EVER be.
what? why would it be faster? Both are just GUI for x265.exe

Why would I need to regrade a HDR movie if it's already HDR? A new grade would be a new interpretation and I'd like the same image, but brighter.
That is not how it works. As soon as you change something in the video, that's re-grading regardless of how bright your source is(100, 200, 500nits).
There is no difference in the workflow and any change you make must be monitored shot by shot otherwise you're raising everything, even the non-highlight pixels (EG: white objects or source clipping that will look off).

I've noticed that a 6,000-nit movie gets more available brightness from my tv than a 1,000-nit one does
it does not. You're confusing clipping and maximum brightness/details your TV can display.

For example, this image is 3000nits &+ and appears brighter because everything is clipped by the TV but in reality, it does not respect the creator's intent and it is NOT brighter than the 800nits(my TV peak) mapped image.
Your TV cannot get brighter than its capabilities so both images peak at 800nits but the 3000nits one is clipped because my TV can't display the original brightness.

left= 3000nits right= tone mapped to 800nits
https://i.ibb.co/n3tTpvR/Capture-d-cran-2024-07-14-092621.png

[guest]

I would compare the colors if I was you. I failed to color-accurate encode jpeg2000 RGB 12bit to YUV 10bits without DEE.

So how can I use DEE ?? Is there a workflow for that ??

I will have a look at that, to see if I can see a difference...

But if I can't successfully use CineForm, then I'll have to do something else if the colours is "off".

Is there another suitable HD codec Resolve can deliver that suitably works ??

what? why would it be faster? Both are just GUI for x265.exe

Why, you ask...well unlike ANY other encoding app that is currently available, RipBot264 has this awesome feature called Distributed Encoding, it can "share" the encoding process with up to 16 PC's, and with each PC encoding a chunk of the encoding job, the process takes a fraction of the time...sure it might use more power, BUT it's done so much faster, you can get way more done.

You see, anybody that's new to RipBot, would not know of this feature, as it is turned off by default, admittedly there's a little bit of fiddle to get it setup, but it's so worth it.

So if you've got more than 1 PC, I'd give it a shot, but you can use it to some benefit on a single PC, but that would then be similar to StaxRip.

StaxRip has it's parallel / chunk encoding, but it only uses the PC that it's installed on, and up to a point, it maybe a little faster, but after that point, it slows the whole process down.

=====================================

As for "wyup", I can certainly see where he's coming from with his comments, obviously he can't justify the time it takes to "grade" every video he has, and just wants some basic "adjustments".

I doubt that I will ever go to the extent that you do, 'cos for me it's just not worth it...I just want a simple way to convert HDR to DV, and now the odd SDR to HDR/DV....and I have you to thank for me being able to do that, now.

I know you've said many times that you won't create a simple SDR - HDR workflow, but I can tell you, if you did, a lot of potential users would certainly appreciate it, and it certainly doesn't mean you've surrendered to a sub quality process.

It's just an option.

Respect.

[DMD]

.......
Is there another suitable HD codec Resolve can deliver that suitably works ??
....
You can try ProRes 422HQ or 4444 XQ using the free Voukoder plugin.
https://www.voukoder.org/forum/thread/783-downloads-instructions/#google_vignette
https://github.com/Vouk/voukoder

[Kuler087]

Why, you ask...well unlike ANY other encoding app that is currently available, RipBot264 has this awesome feature called Distributed Encoding, it can "share" the encoding process with up to 16 PC's, and with each PC encoding a chunk of the encoding job, the process takes a fraction of the time...sure it might use more power, BUT it's done so much faster, you can get way more done.

You see, anybody that's new to RipBot, would not know of this feature, as it is turned off by default, admittedly there's a little bit of fiddle to get it setup, but it's so worth it.

So if you've got more than 1 PC, I'd give it a shot, but you can use it to some benefit on a single PC, but that would then be similar to StaxRip.

StaxRip has it's parallel / chunk encoding, but it only uses the PC that it's installed on, and up to a point, it maybe a little faster, but after that point, it slows the whole process down.

I do dual PC x265 encoding all the time in CLI (or with staxrip GUI with the cutting/editing options). Those apps are just GUI and all use the same x265.exe

So how can I use DEE ?? Is there a workflow for that ??
DEE is a paidware. Workflow 8-2-5

[guest]

I do dual PC x265 encoding all the time in CLI

I'd be curious how you do that ?, or am I reading this wrong...

Do you mean dual encoding on the same PC, or over a LAN to another PC ??

================================

So here's a quick example of Distributed Encoding:-

I'm currently doing GoT episodes that are approx 50 - 60 minutes long, they are 4K, and I applied a light degraining filter.

If I encoded them in "single" mode, it would take between 4 - 5 hours, if I use DE over 4 different PC's of varying performance (not too different to each other), it's takes about 1 hour.

So you can roughly divide the original time it would take in "single" mode, by how many other PC's are "helping", up to a point.

But having said all that, RipBot is a little limited in what inputs & outputs, encoders & decoders, compared to StaxRip, but that's the stubbornness of the dev.

I use the builds in my sig..much better, but still a little limited.

=================================

DEE is a paidware. Workflow 8-2-5

That's Dolby Encoding Engine, isn't it ???

I'm sure I've got that....I'll check it out.

YEP, I've got it, and it worked on 8-1-3 :), but this changed it from 5.1 eac3 to 7.1 thd (actually without an association, I had to "add" the .thd)

[guest]

You can try ProRes 422HQ or 4444 XQ using the free Voukoder plugin.
https://www.voukoder.org/forum/thread/783-downloads-instructions/#google_vignette
https://github.com/Vouk/voukoder

Thanks again, DMD.

Got the latest build & then I had to get the connector, so I will see what that does for me. :)

[DMD]

Thanks again, DMD.

Got the latest build & then I had to get the connector, so I will see what that does for me. :)
Installation instructions:
To use the classic version of Voukoder, two components must be installed:

The Voukoder application and
The connector plug-in that connects Voukoder to your favorite NLE.

1. Install the main Voukoder application.

2. Extract the contents of the file "resolve-connector-x.xx.x.zip" to:
C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins

3. If the "IOPlugin" directory does not exist, create it.

4. Done


Settings:

https://i.postimg.cc/VNy1JqtM/01-R.png


Selection options ProRes 4222 HQ, 4444 HQ and 4444 XQ
https://i.postimg.cc/C5CJ4VrS/02r.png
https://i.postimg.cc/XY1LLLLG/02br.png
https://i.postimg.cc/25qwKW9H/02cr.png

https://i.postimg.cc/gcMWVFRG/03.png


In the audio section, select the Uncompressed PCM codec, as if different, StaxRip can block in the Demux audio section.

https://i.postimg.cc/jSfYYD1j/04.png


Selection container mov.

https://i.postimg.cc/NGC3y8qM/05.png

[guest]

Installation instructions:
To use the classic version of Voukoder, two components must be installed:

The Voukoder application and
The connector plug-in that connects Voukoder to your favorite NLE.

1. Install the main Voukoder application.

2. Extract the contents of the file "resolve-connector-x.xx.x.zip" to:
C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins

3. If the "IOPlugin" directory does not exist, create it.

4. Done


Settings:

https://i.postimg.cc/VNy1JqtM/01-R.png

Yes, I done most of that, a few times :)

I'm curious that a YUV (10bit 4:2:0) isn't displayed, there's only YUV (High Bit Depth)
I've delivered one at both settings and the 8 bit is a larger file size that the high bit..:confused:

A lot more trial & error, and thanks again for your help :)

[wyup]

That is not how it works. As soon as you change something in the video, that's re-grading regardless of how bright your source is(100, 200, 500nits).
There is no difference in the workflow and any change you make must be monitored shot by shot otherwise you're raising everything, even the non-highlight pixels (EG: white objects or source clipping that will look off).

it does not. You're confusing clipping and maximum brightness/details your TV can display.

For example, this image is 3000nits &+ and appears brighter because everything is clipped by the TV but in reality, it does not respect the creator's intent and it is NOT brighter than the 800nits(my TV peak) mapped image.
Your TV cannot get brighter than its capabilities so both images peak at 800nits but the 3000nits one is clipped because my TV can't display the original brightness.

I'm not confusing with clipping because that 10,000 demo didn't clip at all on my Samsung tv. My tv reads MaxDML HDR10 metadata and tonemaps it to its capacity. It has two curves: one for 1,000 to 4,000 nits, and another for 4,000 to 10,000 nits. 0 to 1,000 is mapped directly as is.

Can I obtain a 400, 600 or 1,000 nit tonemap from the 10k nit original with your scripts or from your drive? This way I can compare between them and check. I'm not sure, but I have the impression that low nit videos, such as 400 to 600 nits watch darker than a 4k or 6k nit. Yes, i know they should watch similarly, but I'd like to check up.

However, a 400 to 1,000 up tonemapping would make sense because it would benefit from the full capacity of my tv. Otherwise, 600 nits would be wasted IMHO.

Fair enough, bringing up brightness with Resolve might change the grade already, but there must be a way of doing it 'transparently', or 'non destructively'. I.e: when I use brightness or peak brightness control on my tv, the image doesn't change much per se, it remains largely the same. It is a similar process to watching SDR: it is mapped to the tv capacity and blacks remain anchored. I think tonemapping algorithms are for down-tonemapping mostly, because you must make concessions and priorities. For up-tonemapping, it is a matter of scaling up brightness, nothing is lost.

By the way, I wonder how they grade movies at 10,000 nits: they must use sunglasses because for one, mastering monitors of that capacity must be extremely expensive, and who can watch luminance that high? I presume these are up-tonemapped for mastering.

For example: have a look at this 3-minute 200 Mb (no Dolby Vision, just HDR10) clip extracted from a download of a 2023 30th Anniv. HDR10 remaster of The Fugitive (1993) film. It has a maxCLL of 5,800 nits and average of 1,500 nits. Since it comes from celulloid, it is impossible the negative had luminance this high: it must have been up-tonemapped. The whole movie has a maxCLL of 6,800 nits, so a mastering monitor of at least that much must have been used, if not much less and then up-mapped.

plot (https://mega.nz/file/L1xEUSRR#XrgJ2yaATk0HqPxt5ibl7F4uVQB3xjkY-JHLXtrzWTI)
clip (https://mega.nz/file/mlZClIhA#qREGGDMbOXEKPlckjapf9tUiA98mpxhIY6rgKQR7cts)

[Kuler087]

Can I obtain a 400, 600 or 1,000 nit tonemap from the 10k nit original with your scripts or from your drive?

yes, I've added it in the beta version the day after you asked but I haven't tested it yet. The SM disc already have a 1000/600 nits version of the montage btw.

line 169:
::Choose the trim target to deliver in 8-2-5. Choicies are: 100nits=1 / 600nits=28 / 1000nits=49 (default = 1 )
set CMOFFLINE.TARGET=1


Dolby CM_offline has the same prores slow performance bug as CM_analyze so it is much faster to do it in resolve and you have more target options.

https://i.ibb.co/hmbK90H/Capture-d-cran-2024-07-17-101223.png

[guest]

Sorry for my forgetfulness, but when using 8-1-3 either DD+ or THD, I am getting a 7.1 from the original 5.1 ac3.

Is there a setting to NOT convert to 7.1 ??? I was looking around the other day, and couldn't find any relevant settings, or is it a DEE thing ??

[Kuler087]

the dee workflow is just for 7.1 audio. No point using it for 5.1, use 8-1-1

[Guest]

the dee workflow is just for 7.1 audio. No point using it for 5.1, use 8-1-1

Good to know, tho :)

:thanks:

[halls]

Hi!

@Kuler087
Could you make a video on how to resync the HDR10+ metadatas and inject to normal HDR10 base layer?

As in "web streaming to to HDR10 BD rip P8 Hybrid" video.

[Kuler087]

You do that the same way as when you inject/resync DV from WEB with workflow (1-1).
https://www.youtube.com/watch?v=hVWZpat34oc

[halls]

:thanks:You do that the same way as when you inject/resync DV from WEB with workflow (1-1).
https://www.youtube.com/watch?v=hVWZpat34oc

[jayper]

If I have:
- an HDR10-only disc
- a retail P5-RPU (cmv2.9)
- a CM_Analyze generated RPU (cmv4.0)

Is there any value in running workflow 1-1 with the HDR10 base layer, and the retail P5-RPU (cmv2.9).

Then running the resulting file (HDR10 base with retail P5-RPU) through 1-1 again, this time with the CM_Analyze generated RPU (cmv4.0) to get the colorists trims from the retail P5 plus the cmv4.0 metadata from the CM_Analyze?

[Kuler087]

Then running the resulting file (HDR10 base with retail P5-RPU) through 1-1 again, this time with the CM_Analyze generated RPU (cmv4.0) to get the colorists trims from the retail P5 plus the cmv4.0 metadata from the CM_Analyze?
That would remove the retail cmv2.9 rpu and would replace it by the new cmv4.0 rpu. In other words, 1-1 always overwrite any existing RPU from the BL(input one).

The workflow to transfer metadata levels from one rpu to another is 2-6 (and now 2-3 in upcoming 2.0.9 (https://justpaste.it/g1u2l)) but you cannot transfer levels from RPUs that were created from difference analysis. The Dolby 2.9 and 4.0 calculate the metadata quite differently. See this comparison (https://slow.pics/c/WlGwchoE)
You can only transfer levels when both RPU comes 100% from the same DV analysis.

[jayper]

That would remove the retail cmv2.9 rpu and would replace it by the new cmv4.0 rpu. In other words, 1-1 always overwrite any existing RPU from the BL(input one).
Ah, I see. I wasn't sure if that process replaced or transferred the levels. Good to know. Thanks.


The workflow to transfer metadata levels from one rpu to another is 2-6 (and now 2-3 in upcoming 2.0.9 (https://justpaste.it/g1u2l)) but you cannot transfer levels from RPUs that were created from difference analysis. The Dolby 2.9 and 4.0 calculate the metadata quite differently. See this comparison (https://slow.pics/c/WlGwchoE)
You can only transfer levels when both RPU comes 100% from the same DV analysis.
I see, once again, I had no idea. I am glad I asked. Thanks very much.

I realize that the answer to this question probably depends on the type of TV you have, but is there a general rule as to what is better? cmv2.9 with custom trims, or generated cmv4.0 with no trims?

[Kuler087]

The only times you could replace a retail RPU by a cmv4.0 generated rpu are:

1- cmv2.9 rpu without any trims
2- a rpu with static L1/L2. (static L1 + dynamic L2 is fine)
3- if the hybrid sources are not the same grade
4- On some rare occasions, when I think the retail rpu doesn't make sense like in ''Risky Business 1983'' (https://slow.pics/c/Ekjrb0Ot)
5- If you don't have a FEL capable device and fel expand the brightness, I guess its fine to generate DV for the HDR10 BL brightness.

[guest]

Hi Kuler,

I have been using the latest 2.0.9 beta, and using Workflow 3 to create a "Dovi" of PotC clip.

I used 3-1 7 (4000/P3), and 3-1 20 (1000/P3) & 3-2 (no other options), and using both the new & old mp4 muxers.

And I cannot tell any difference between any of them, and both the muxers work with my new LG C4.

Not sure if there will be any difference in encoding time for the full length movie (processing atm), between 3-1 & 3-2, but I had one doing 3-1 a couple of days ago, it was going to take a L-O-N-G, the CUDA encoding countdown started at about 18 hours :(

Would there be any difference in encoding time, if it was just the video track (add the audio later)

Might have to start using Resolve.

Anyway, still learning, and you keep improving your workflows...

Cheers

[Kuler087]

3-2 use madVR for generating the metadata and it's not as good as the DV algo.
You could possibly get some brightness fluctuation between shots and the average_PQ metadata is much higher with madvr which will result in a darker tone-mapped image.

Here's the actual difference between metadata generated with Dolby algo, HDR10plus and Madvr: https://drive.google.com/file/d/1PiiK4WVgXr2LTorJ6Ci2BWgJadNFZTVA/view?usp=drive_link

[guest]

3-2 use madVR for generating the metadata and it's not as good as the DV algo.
You could possibly get some brightness fluctuation between shots and the average_PQ metadata is much higher with madvr which will result in a darker tone-mapped image.

Here's the actual difference between metadata generated with Dolby algo, HDR10plus and Madvr: https://drive.google.com/file/d/1PiiK4WVgXr2LTorJ6Ci2BWgJadNFZTVA/view?usp=drive_link

So does that explain why 3-2 is a faster process that 3-1 ??

Can this be done with Resolve ??

[Kuler087]

Of course, 3-2 will always be faster than 3-1 and faster than Resolve as well because it can create the metadata straight from the HEVC stream with madMeasureHDR.exe or HDR10plus.

In 3-2:
if present, will convert HDR10plus to DV
if no hdr10plus, it will use madvr to measure the video and convert the madvr measurement file to DV.
in both cases, no prores transcoding and no slow performance (cm_analyze.exe) so that's why it is so fast but less accurate than using the official Dolby Algo (the same algo the studios use).

[guest]

Of course, 3-2 will always be faster than 3-1 and faster than Resolve as well because it can create the metadata straight from the HEVC stream with madMeasureHDR.exe or HDR10plus.

In 3-2:
if present, will convert HDR10plus to DV
if no hdr10plus, it will use madvr to measure the video and convert the madvr measurement file to DV.
in both cases, no prores transcoding and no slow performance (cm_analyze.exe) so that's why it is so fast but less accurate than using the official Dolby Algo (the same algo the studios use).

OK, thanks for that, I'll have to do a couple of my own comparisons, to determine the time taken, and the "quality".

My old eye's probably won't be able to tell too much difference.

So just for my information, I am currently watching Pirates Of The Caribbean Curse of the Black Pearl, and there is a LOT of different "colour grading" through out, some scenes are quite "natural" looking, and other's are dark and "reddish", is this the grading process that you speak of that takes hours in Resolve ???

[Kuler087]

So just for my information, I am currently watching Pirates Of The Caribbean Curse of the Black Pearl, and there is a LOT of different "colour grading" through out, some scenes are quite "natural" looking, and other's are dark and "reddish", is this the grading process that you speak of that takes hours in Resolve ???

yes, movies are graded shot by shot.

[guest]

yes, movies are graded shot by shot.

So is "shot by shot" the same as "frame by frame" ?

That IS a hell of a lot of frames or shots to be manually graded,
surely Resolve has some way of copying the graded shot/frame, from one adjusted frame to another or group of others ??

I watched a few YT clips on Colour Grading, and most of them are using nodes, to keep track of their changes.

Seems like way too much work for a one off.

[Kuler087]

So is "shot by shot" the same as "frame by frame" ?
no

That IS a hell of a lot of frames or shots to be manually graded,
yes, the colorist can spend weeks/months grading big-budget movies.

surely Resolve has some way of copying the graded shot/frame, from one adjusted frame to another or group of others ??
of course and this is exactly what I do in the SDR to HDR video when I select multiple shots. You can copy the grade of one shot to another by pressing your mouse's wheel over a shot.
Same story for the Dolby Vision trim pass(es). It doesn't work with the mouse wheel but you can map a key to copy trim or level 1 metadata to any shot.

[CineManiac]

Quick question. I see the FEL RPUs you are now uploading with cmv 4.0 added. Is it okay to bake FEL and then copy the L8 levels to the P8 RPU?

[Kuler087]

yes it's ok


PS:
The latest beta now supports FEL baking/encoding(8-2) without a Nvidia GPU.

[CineManiac]

Nice! Thanks

[CineManiac]

Loving the ability to create heatmaps/gamuts with folders of PNGs with 3.0.0! Would it be possible to create a folder within the output folder like with video screenshots?

[Kuler087]

yes sure

[guest]

Just a quick question...have you ever considered buying an AMD Threadripper ??

[Kuler087]

never. I'm an intel/nvidia guy.

[guest]

So I thought I'd run a DV conversion with the new 3.0.0.

I chose WF 3-1, and after it doing all it's process, just over an hour later, I get some error msg's, and that was it :(

Here's some info:-

https://www.mediafire.com/file/9xtl63f1x52g6st/first_run_with_3.0.0_WF_3-1_errors.txt/file

https://www.mediafire.com/file/576l1g53jyyoywf/MediaInfo.txt/file

I'm running 3-2 on the same movie, as we speak, will comment when completed (or not)

3-2 completed, but the audio is way out of sync...

I must be missing something needed for 3-1 to complete properly.

[guest]

never. I'm an intel/nvidia guy.

So Blue & Green team.

I have a majority of AMD's CPU's, but nearly always go for nVidia GPU's.

[Kuler087]

So I thought I'd run a DV conversion with the new 3.0.0.

I chose WF 3-1, and after it doing all it's process, just over an hour later, I get some error msg's, and that was it :(

Here's some info:-

https://www.mediafire.com/file/9xtl63f1x52g6st/first_run_with_3.0.0_WF_3-1_errors.txt/file

https://www.mediafire.com/file/576l1g53jyyoywf/MediaInfo.txt/file

I'm running 3-2 on the same movie, as we speak, will comment when completed (or not)

3-2 completed, but the audio is way out of sync...

I must be missing something needed for 3-1 to complete properly.

nothing changed in 3-1 / 3-2...

looks like you added space or special characters in your script path

[guest]

nothing changed in 3-1 / 3-2...

looks like you added space or special characters in your script path

Damn it...I keep forgetting about :(

Thanks, I'll try again tomorrow.

[DMD]

Finished now procedure 3-1 with Script 3.0.0
All OK, I did not detect any audio sync problems.

[Kuler087]

I did a stupid redirection bug/typo in workflow 1 when the input doesn't have lossless audio (DTS or THD). Get the latest beta or turn off EAC3 encoding in the settings: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
I did not notice because my own script EAC3 conversion settings is set to OFF. sorry

[hgny]

Hi
I'm new to the script, amazing job!
I'm trying to do workflow 8-2-4 for converting DV file to SDR. I'm getting some errors and warnings.

I took some pictures, will upload it. Does this is a regular behavior?

Thanks.

https://imgur.com/a/mQbL7X2

[Kuler087]

Hi,
this looks like a Dolby cm_offline.exe error on an AMD GPU and I dont think there's anything I can do about it since it's working fine with an Nvidia gpu.
You might have to contact Dolby or do it in Resolve (https://youtu.be/lM56zLpKDQ8), it will be faster anyway.

https://i.ibb.co/q0pgSs1/Windows-Terminal-a-P46q-KQRKS.gif

[hgny]

Yes i tried with resolve. Problem is, my computer doesn't support dolby vision so profile 5 has some pink color and it seems resolve is tone mapping it wrongly.

[Kuler087]

Just tonemap P5 to PQ HDR10 with workflow 8-2-3 which is exactly what the script does in 8-2-4

[guest]

So just for dummies like me, it might be helpful if you mentioned where those 3 new .py files need to be put...

"new files needed"

[Kuler087]

in the tools folder

[guest]

in the tools folder

Thanks, updating everything now...

With this extra :-

::choose osd text color in 7-1 / 7-2 / 7-3 (default = dark grey: $808080)
set osdcolor=$808080

What are the "number codes" for other colours ??

https://html-color.codes/

[Kuler087]

What are the "number codes" for other colours ??

https://html-color.codes/

yes, any color code from that website should work... but instead of # you use $
EG: $3cb300

[guest]

Hi Kuler,

I just want to run this by you, and get your thoughts, and possible suggestions -

I processed "The Fifth Element" yesterday, and ran it thru DS 8-1-1.

The movie is just over 2hrs:06minutes (181171 frames)

It started it's cm_analyze "countdown" @ approx 6hrs:30minutes, after several minutes, it was counting up, then it settled, then started counting down, (after a couple of hours) and it seemed that it was taking a little bit more time to process each frame.

So it ended up taking well over 4.5 hours to complete, and I was SO relieved that it did finish, and I had a workable file name, and plenty of free space :)

So a couple of questions, is this time frame is something I need to expect as the norm, with movie length encodes ??

I'd hate to think how long ultra long movies like the extended LoTR & The Hobbit, etc are going to take.

I'm glad I got a 4080, as I'm sure the poor little 3060 would take a LOT longer.

Is there anyway that this process can be sped up, or is it just the way it has to be ??

[Kuler087]

I have no control over the speed with cm_analyze unfortunately. I really wish Dolby fixed that slow performance issue on windows but they haven't updated the tools since February 26, 2024.

[guest]

I did a really quick & dirty Resolve HDR10 & DV metadata edit today, and using the MP4 script (as I always do), after injecting the .xml, I got an .mp4, then I injected the .json into that file, and I got an .mkv :confused:

If I imported the folder containing both the .xml & .json it would state that the video file was only HDR10, and would quit.

Seems I have to inject the .json first, then inject the .xml into the .json video.

[Kuler087]

Yes, I think that if you inject HDR10plus, the script will force the MKV container since the only reason to use the MP4 container is for DV and the reason is that there's no code in my script to mux non-DV input to MP4

try this:
Rename hdr10plus json file the same as the HDR10 BL and input-1 the BL HDR10 video and input-2 the XML. This should inject both metadata in one job but you still might end up with a MKV, I'm not sure.

[ReciprocalUniverse]

Great Work Kuler!!

[Kuler087]

@ReciprocalUniverse thank's :)

[ReciprocalUniverse]

It is wonderful you are active and involved here and with Resolve. I hope you can help me with some answers. I can't afford the Dolby license for Resolve Studio but I can run the HDR10+ analysis and encode with x265 to get a compatible HDR10+ file. Running some of the DDVT scripts I made it into a playable DV Profile 8.1 (BL + RPU).

1.) With DV, there is a collection of available target RPU's. With HDR10+, you don't get that. So when a script converts HDR10+ json metadata to DV RPU, what exactly is the tone mapping target you end up with? 100 nit? 200 nit? Something else?
2.) If I upload an HDR10 to YouTube, they render a version in SDR. If the file is not streamed, it needs an HDR and SDR copy. A dual layer DV (BL + EL + RPU) would not be of help for a player not supporting DV. However, if it was supporting of DV what would be the point of an SDR layer if the player/display can already do the HDR layer? Part of my question then relates to, what is the special relevance of tone mapping to the 100 nit SDR level for a DV device?

As an aside, I don't think it's visually essential to encode a jpeg2000 sequence or open exr for the source to HEVC. DNxHR or Prores is fine.

**************************************************

Unrelated to the above questions, it came up in the conversation about doing trims on individual frames, and the amount of work involved. I would add that outside of the DV realm, grading a scene clip doesn't have to always involve every single frame or grading just one frame. Example, the bride is wearing a white dress in the bright sun, and when she is followed by the camera into a dark hallway, the scene darkens, the scene ends up with very different exposure than it started with. Another example is an unmanned camera on a tripod filming an outdoor wedding ceremony. Suddenly the sky darkens as clouds move overhead. The scene again ends up with very different exposure than it started with. In my opinion, these are not the intended situations for frame by frame dynamic metadata. The approach I take is to use Resolve keyframes to 'transition' between the changing conditions, averaging across a sequence of frames. Frame by frame would take too long. Carry on and thanks again!

[Kuler087]

I can't afford the Dolby license for Resolve Studio
DV is free for any user to use. Only the manual level 8 or 2 artistic trims require a license.

With HDR10+, you don't get that. So when a script converts HDR10+ json metadata to DV RPU, what exactly is the tone mapping target you end up with? 100 nit? 200 nit? Something else?
I don't know much about HDR10plus but in DV only the trim passes have targets which are used to tonemap the image more accurately according to the colorist's shot-by-shot adjustments.
HDR10plus doesn't have trim passes, so it most likely works like DV without trims and uses the TV internal target brightness to apply tone mapping according to the metadata.

A dual layer DV (BL + EL + RPU) would not be of help for a player not supporting DV.
The metadata in DV can be used on any display, HDR10 and SDR. This is done by forcing the player to decode the image + metadata (LLDV) and mapping the tone according to the EDID target brightness.

what would be the point of an SDR layer if the player/display can already do the HDR layer?
The 100nits SDR DV trim pass is extrapolated and can tone map to any target between 100-10 000nits. The point of doing the SDR trim pass(maximum compression an HDR grade can get) is that the colorist can control the tone mapping regardless of the display capabilities.

After grading the HDR master shot by shot, they do the automated DV metadata generation and then they monitor shot by shot(again) the mapping to different targets (100-600-1000-2000). They make adjustments to the trims target if they are not satisfied by Dolby default mapping.
They almost never do more than a 100nits trim since it's the lowest point of tone mapping possible but I've seen a couple of bluray that cancel the 100-600-1000nits interpolation(They do the 100nits trim and reset to 0 the 600nits-1000nits values which create a blank 600 trim). This is useful when they want to be more aggressive with the 100nits trim that will be used for the SDR bluray delivery without affecting the 600-1000 target interpolation mapping.




Unrelated to the above questions, it came up in the conversation about doing trims on individual frames, and the amount of work involved.
I've checked pretty much all the DV releases on this planet and only one time I've seen frame by frame metadata and it was for the Amazon show Jack Ryan. But they did not do any trim pass. I cant imagine how long it would take to grade a movie frame by frame.

[ReciprocalUniverse]

DV is free for any user to use. Only the manual level 8 or 2 artistic trims require a license.

Yes, the DV trim panels are enabled with a license only. Without a license Resolve can still export an RPU.XML from an automated analysis of clips but not a DV compliant HEVC file. Perhaps not even with the license can you export compliant HEVC? Are you saying Resolve's licensed involvement stops with enabling the trim panel and generating an RPU.XML, but not generating a RPU.BIN or HEVC? I had assumed previously that with the license you could export compliant, playable DV HEVC files, but that may have been wrong.


I don't know much about HDR10plus but in DV only the trim passes have targets which are used to tonemap the image more accurately according to the colorist's shot-by-shot adjustments.
HDR10plus doesn't have trim passes, so it most likely works like DV without trims and uses the TV internal target brightness to apply tone mapping according to the metadata.

The Resolve DV display targets can be selected without the DV license but not the trim panel. For HDR10+ there are no selectable display targets, so my question to you was what then does it use which you didn't have the answer for, which is okay. I assume it really does not matter because the HDR10+ processing inside the display will use it appropriately.

The HDR10+ trim panel was enabled in Resolve until V.17 when it was disabled at the request of Samsung. Otherwise, the process workflow of running an automated analysis is identical. A json sidecar file is generated with dynamic metadata that can be interleaved in x265 with the HDR10 BL to produce a playable HDR10+ HEVC file. The x265 process for DV is similar except the RPU has to be in binary form, requiring the extra step from CMD tools (or yours) to convert the RPU.XML to binary.

Okay so the one, 100 nit target level is potentially sufficient to accommodate any DV display.

I've checked pretty much all the DV releases on this planet and only one time I've seen frame by frame metadata and it was for the Amazon show Jack Ryan. But they did not do any trim pass. I cant imagine how long it would take to grade a movie frame by frame.

Ignore my prior remarks about frame by frame, dynamic metadata as with Profile 8.4, it was a misunderstanding by me.

In summary, what this all boils down to for me is that HDR10+ only has intended application for Samsung tv's, and if you want to make playable HEVC files for DV tv's with Resolve, you will still need the DoVi tools whether you have a licensed Resolve copy or not. Have I got that right?

[ReciprocalUniverse]

Here's my final question, thanks for your patience!

Using the DoVi scripts and x265 is it possible to make a profile 8.4 playable HEVC from Resolve with no DV license?

I hope I'm clear about that. I'm not talking about manually doing a sequence of trim passes. I'm talking about automatic, frame by frame bitstream insertion of metadata for every single frame, like an i-Phone can do, with no trim passes.

[Kuler087]

Without a license Resolve can still export an RPU.XML from an automated analysis of clips but not a DV compliant HEVC file. Perhaps not even with the license can you export compliant HEVC?
Resolve hevc encoding sucks anyway so just export the XML and inject it with dovi_scripts workflow 1 but yes, a DV license will enable the P5/P8 hevc encoding in resolve delivery page. The best option is to deliver to a lossless codec and do the encoding with x265.exe and inject the xml/rpu.
FYI If you know how to change your edid, you can use this custom one (https://mega.nz/file/8DNC2D6J#aB8reR8iUSMGLXW7dqLUbEPsV3z3OSuj7n5wJkNOs84) that will allow P5/P8 encoding without a DV license.

Resolve P5/P8 encoding though, will ignore your existing shot by shot analysis and create new frame by frame metadata.

or HDR10+ there are no selectable display targets, so my question to you was what then does it use which you didn't have the answer for, which is okay. I assume it really does not matter because the HDR10+ processing inside the display will use it appropriately.

The HDR10+ trim panel was enabled in Resolve until V.17 when it was disabled at the request of Samsung. Otherwise, the process workflow of running an automated analysis is identical.

I'm no expert with HDR10plus but I think the process is 100% automated and is never monitored unlike DV trims creation. So there's no target AFAIK, it just creates shot by shot brightness metadata but I could be wrong.

Using the DoVi scripts and x265 is it possible to make a profile 8.4 playable HEVC from Resolve with no DV license?

My script cannot encode the HLG base layer but if you input any XML with an HLG video in workflow 1, the XML file will be converted to an 8.4 RPU and injected into your HLG BL. I've done it many times with BBC TV shows.

EG. You convert the HLG file to HDR10 prores with workflow 8-2-3, generate an XML as usual, and inject it with Workflow 1.

[ReciprocalUniverse]

Resolve hevc encoding sucks anyway so just export the XML and inject it with dovi_scripts workflow 1 but yes, a DV license will enable the P5/P8 hevc encoding in resolve delivery page. The best option is to deliver to a lossless codec and do the encoding with x265.exe and inject the xml/rpu.
FYI If you know how to change your edid, you can use this custom one (https://mega.nz/file/8DNC2D6J#aB8reR8iUSMGLXW7dqLUbEPsV3z3OSuj7n5wJkNOs84) that will allow P5/P8 encoding without a DV license.

Resolve P5/P8 encoding though, will ignore your existing shot by shot analysis and create new frame by frame metadata.



I've tried lossless to x265 for P5.0 but without RPU got no DV. Would injecting shot by shot rpu.xml with DoVi tools give me compliant P5.0 DV?

[Kuler087]

P5 encoding from scratch requires the proprietary Dolby engine.

You can do that with Workflow 8-2-6 but you first have to configure your path to DEE.exe. Input can be prores mov, jpeg-2000 mxf, hevc DVP8/7, HDR10, HLG.
For mov, mxf, HDR10 and HLG inputs, you must provide an XML and Dolby default encoding scripts produce garbage 2-pass hevc encoding so you should modify it as I say in workflow 8-2-6 to allow custom settings and CRF encoding.

Also there's a bug in the latest version of dovi_scripts with mov and prores if you don't crop, so get the latest beta. (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link)

[guest]

P5 encoding from scratch requires the proprietary Dolby engine.

You can do that with Workflow 8-2-6 but you first have to configure your path to DEE.exe. Input can be prores mov, jpeg-2000 mxf, hevc DVP8/7, HDR10, HLG.
For mov, mxf, HDR10 and HLG inputs, you must provide an XML and Dolby default encoding scripts produce garbage 2-pass hevc encoding so you should modify it as I say in workflow 8-2-6 to allow custom settings and CRF encoding.

Also there's a bug in the latest version of dovi_scripts with mov and prores if you don't crop, so get the latest beta. (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link)

There are quite a few things you "need" DEE for with DS, BUT, where to get it, is the question.

Shame there's a bug in the latest release, I only just got it the other day, so I guess 3.0.2 might be out soon'ish...

[Kuler087]

There are quite a few things you "need" DEE for with DS
not really... only workflow 8-2-6 8-2-5 and 8-1-3

Shame there's a bug in the latest release, I only just got it the other day, so I guess 3.0.2 might be out soon'ish...
No, not soon. Nothing new and its a minor bug only in 8-2-6 and only when you don't crop and only with prores jpeg-2000 input.

[guest]

not really... only workflow 8-2-6 8-2-5 and 8-1-3

Maybe "need" wasn't the right word, it's a "nice to have", and adds extra functionality to the app :)


No, not soon. Nothing new and its a minor bug only in 8-2-6 and only when you don't crop and only with prores jpeg-2000 input.

OK, well that IS a fairly particular "bug".

All good, :thanks:

Your 300th post :)

[ReciprocalUniverse]

Question:
Can dovi scripts directly make a RPU.BIN from a RPU.XML?

[Kuler087]

Yes, just plot the xml in 6-3 and it should output a rpu.bin

[ReciprocalUniverse]

Yes, just plot the xml in 6-3 and it should output a rpu.bin

That's perfect, (I think). Couldn't I then with x265

--dolby-vision-profile 8.1 --dolby-vision-rpu filename.bin

...have x265 interleave rpu.bin at runtime instead of injecting it with DoVi tool later to save a step?

[Kuler087]

yes, you can do that but if you crop or downscale, you have to edit your RPU Level 5.

6-3 assume your video is 2160p.

[guest]

That's perfect, (I think). Couldn't I then with x265

--dolby-vision-profile 8.1 --dolby-vision-rpu filename.bin

...have x265 interleave rpu.bin at runtime instead of injecting it with DoVi tool later to save a step?

I used to do that with RipBot, but because I need an mp4, and RipBot can't output x265 mp4's, it was of no use to me :(

[ReciprocalUniverse]

yes, you can do that but if you crop or downscale, you have to edit your RPU Level 5.

6-3 assume your video is 2160p.

Video is from a camera, 7680 x 4320 59.94 fps

[Kuler087]

Video is from a camera, 7680 x 4320 59.94 fps

Then you will have to edit L5 to 8K or use dovi_tool to generate the rpu from XML

"%dovi_tool_path%" generate --xml %XML% --canvas-width %Width% --canvas-height %Height% --rpu-out "%TEMP%P8.RPU.bin"

[ReciprocalUniverse]

Sorry, not trying to be evasive, just substantively clear, in which case I may not be giving you as much information as you need to help me, so let me know.

[ReciprocalUniverse]

Then you will have to edit L5 to 8K or use dovi_tool to generate the rpu from XML

"%dovi_tool_path%" generate --xml %XML% --canvas-width %Width% --canvas-height %Height% --rpu-out "%TEMP%P8.RPU.bin"

Thanks, L5 meaning profile 5.0, or Dolby level 5? Is L5 something else? Is L5 a call from the script?

I'm sorting in my mind your syntax, so that says dovi tool > XML > 7680 > 4320 > Profile_8 = RPU.bin? I would enter your string on the command line?

Really appreciate your patience with me, already a big help.

[Kuler087]

L5 = Level 5 = the active area of the image without black bars. Dolby Vision is designed to apply tone mapping only to the active area of the image. Incorrect L5 can result in over-cropping or tone mapping applied to the letterbox which could cause raised black.
You can edit L5 with DS workflow 1 or you can use dovi_tool.exe in cli and L5 will be set automatically and correctly according to your input resolution.

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4320 --rpu-out D:\rpu.output.bin


All of this doesn't matter if your video is 1.78 (no black bars) though.

[ReciprocalUniverse]

Is it less complicated, better or faster to inject? I don't have to do it a particular way. Here's what I did up to this point which worked for 4K but not 8K, I used Resolve to export uncompressed and a timeline.json from an HDR10 analysis, which I interleaved with x265. I muxed in my audio to mkv and got a playable HDR10+ file, then used DDVT_DEMUXER to make it a DV8.1 [BL+RPU] and with DDVT_MKVTOMP4 it became DV playable (in 4k). The same process didn't work for 8k.

I think I'd rather have the DV analysis than HDR10+ but didn't know how to do that with the DDVT scripts I started with. The object is to make a playable 7680x4320 59.94 fps DV compliant file.

[ReciprocalUniverse]

L5 = Level 5 = the active area of the image without black bars. Dolby Vision is designed to apply tone mapping only to the active area of the image. Incorrect L5 can result in over-cropping or tone mapping applied to the letterbox which could cause raised black.
You can edit L5 with DS workflow 1 or you can use dovi_tool.exe in cli and L5 will be set automatically and correctly according to your input resolution.

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4320 --rpu-out D:\rpu.output.bin


All of this doesn't matter if your video is 1.78 (no black bars) though.

I am liking this idea!

[ReciprocalUniverse]

If I am understanding correctly, if my uncompressed 7680 x 4320 contained 160 pixel blackbars on top and bottom then:

D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4000 --rpu-out D:\rpu.output.bin

No, ignore that, you already explained, two steps.

[Kuler087]

I muxed in my audio to mkv and got a playable HDR10+ file, then used DDVT_DEMUXER to make it a DV8.1 [BL+RPU] and with DDVT_MKVTOMP4 it became DV playable (in 4k). The same process didn't work for 8k.

I think I'd rather have the DV analysis than HDR10+ but didn't know how to do that with the DDVT scripts I started with. The object is to make a playable 7680x4320 59.94 fps DV compliant file.

Converting HDR10plus to DV is a bad idea. There's a reason my script workflow 3-2 says ''not recommended''. I don't know about DDVT scripts , never used it, and never will.

My scripts though, should work with 8K input. I just tried with the mp4 version in workflow 1 and it works. I don't have a 8K TV to test though

General
Complete name : D:\8K_DV.mp4
Format : mp43
Codec ID : mp43 (isom/mp43/dby1)
File size : 58.0 MiB
Duration : 12 s 555 ms
Overall bit rate : 38.8 Mb/s
Frame rate : 23.976 FPS
Encoded date : 2024-08-15 21:24:53 UTC
Tagged date : 2024-08-15 21:24:53 UTC

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.1@High
HDR format : Dolby Vision, Version 1.0, Profile 8.0, dvhe.08.11, BL+RPU, no metadata compression / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 12 s 555 ms
Bit rate : 38.8 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.049
Stream size : 58.0 MiB (100%)
Default : Yes
Alternate group : 1
Encoded date : 2024-08-15 21:24:53 UTC
Tagged date : 2024-08-15 21:24:53 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 192 cd/m2
Maximum Frame-Average Light Level : 82 cd/m2
Codec configuration box : hvcC+dvcC


D:\DoVi_Scripts\tools\dovi_tool.exe generate --xml D:\DV.metadata.xml --canvas-width 7680 --canvas-height 4000 --rpu-out D:\rpu.output.bin

No, ignore that, you already explained, two steps.

yeah don't do that. canvas must be the input resolution and dovi_tool will set L5 automatically

[ReciprocalUniverse]

I got the *.bin from dovi-tool. Gosh that was simple! Now to test to see if it works.

Thanks for all your help so far. I'll be back very soon.

[Kuler087]

DS MP4 version + workflow 1 would be even simpler. Input 1: video source, Input 2: XML source and the script will read the input resolution, generate the rpu, inject and mux to MP4

[ReciprocalUniverse]

DS MP4 version + workflow 1 would be even simpler. Input 1: video source, Input 2: XML source and the script will read the input resolution, generate the rpu, inject and mux to MP4

The issue is the learning curve for getting the scripts set up. I'd rather work from the command line. That created a problem too. Although dovi-tools converted the xml to bin, and x265 says it was successful in muxing it, the mediainfo isn't reporting dolby metadata, just HDR10 2086.

[Kuler087]

The issue is the learning curve for getting the scripts set up
For workflow 1, theres nothing to install. It should work out of the box and there's an installation tutorial on the first page.

Although dovi-tools converted the xml to bin, and x265 says it was successful in muxing it, the mediainfo isn't reporting dolby metadata, just HDR10 2086.
raw hevc stream will not show DV metadata, you have to mux it.

[ReciprocalUniverse]

For workflow 1, theres nothing to install. It should work out of the box and there's an installation tutorial on the first page.


raw hevc stream will not show DV metadata, you have to mux it.

I had muxed the x265 raw hevc into mkv with mkvtoolnix, but no DV metadata was indicated in the mkv.

I am willing to try workflow 1, but I don't know what it is or where to find it. I had already downloaded the toolpack and found Dovi_tool.exe, but all the other stuff, of which half of it at least I already have, and the other half I loathe downloading and installing. I downloaded the Dolby Professional set. Your instructions say I MUST download python, avisynth + 64b, visual C++, lav filters, vapoursynth, madVR.

I played the YT tutorial, I love the Canadians, I worked for them for 11 years, but I don't know French.

[guest]

I had muxed the x265 raw hevc into mkv with mkvtoolnix, but no DV metadata was indicated in the mkv.

I am willing to try workflow 1, but I don't know what it is or where to find it. I had already downloaded the toolpack and found Dovi_tool.exe, but all the other stuff, of which half of it at least I already have, and the other half I loathe downloading and installing. I downloaded the Dolby Professional set. Your instructions say I MUST download python, avisynth + 64b, visual C++, lav filters, vapoursynth, madVR.

I played the YT tutorial, I love the Canadians, I worked for them for 11 years, but I don't know French.

Admittedly there are several dependencies to be installed, etc, etc, but once that's done, you have FULL use of any workflow.

[ReciprocalUniverse]

Admittedly there are several dependencies to be installed, etc, etc, but once that's done, you have FULL use of any workflow.

I appreciate that, but I am one functional bin file away from finishing this.

[Kuler087]

all the things to install are for the very technical stuff. If you just want to inject and mux to mp4, workflow 1 doesn't need any of these softwares.

Sure my Windows is in French, but the instructions are in English and pretty easy to follow if you dont install the extra software and just use workflow 1:

Create a folder
put the tools folder in it
put the bat file(mkv mp4 or ts) you want to use in it
click on the bat file
select a workflow
drag and drop input 1, 2 and press enter. You can skip all the user prompts by pressing enter.

or

just drag and drop a file on the bat file, then the metadata and press enter.

[ReciprocalUniverse]

I love ALL Canadians, our neighbors and friends to the north, anything that's mine is yours except Lord Stanley's Cup.

I can handle that workflow I think. I will try.
:-)

[ReciprocalUniverse]

My 8K Samsung as everyone knows doesn't do Dolby Vision, but the 8K-hevc.mkv before injection plays perfectly in HDR10 on everything,
but after the RPU.XML is input to workflow 1,the output MP4 file plays in HDR10 in the Windows Media Player, but only haltingly in MPC-HC,
and not at all from the tv's own media player. Isn't DV P8.1 backward HDR10 compatible? The metadata seems okay.

General
Complete name : C:\Users\Monstro\Videos\Captures\8K_Sunset_DV.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/dby1/isom)
File size : 119 MiB
Duration : 11 s 542 ms
Overall bit rate mode : Variable
Overall bit rate : 86.3 Mb/s
Frame rate : 59.940 FPS
Encoded date : 2024-08-16 03:35:16 UTC
Tagged date : 2024-08-16 03:35:16 UTC

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.1@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.12, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 11 s 528 ms
Bit rate : 86.2 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.043
Stream size : 118 MiB (100%)
Writing library : x265 3.6+35-dd594f59d:[Windows][MSVC 1940][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=7680x4320 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / temporal-layers=0 / open-gop / min-keyint=25 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=8 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / no-deblock / no-sao / no-sao-non-deblock / rd=3 / selective-sao=0 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=-3 / crqpoffs=-3 / rc=cbr / bitrate=85000 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=85000 / vbv-bufsize=70000 / vbv-init=0.9 / min-vbv-fullness=50.0 / max-vbv-fullness=80.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=0 / display-window=0 / master-display=G(13574,32227)B(7617,2686)R(33496,15723)WP(14063,14209)L(10000000,300) / cll=985,27 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf / no-sbrc
Default : Yes
Alternate group : 1
Encoded date : 2024-08-16 03:35:16 UTC
Tagged date : 2024-08-16 03:35:16 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=0.669920 y=0.314460, G: x=0.271480 y=0.644540, B: x=0.152340 y=0.053720, White point: x=0.281260 y=0.284180
Mastering display luminance : min: 0.0300 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 985 cd/m2
Maximum Frame-Average Light Level : 27 cd/m2
Codec configuration box : hvcC+dvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 11 s 542 ms
Bit rate mode : Variable
Bit rate : 192 kb/s
Maximum bit rate : 198 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 275 KiB (0%)
Default : Yes
Alternate group : 2
Encoded date : 2024-08-16 03:35:16 UTC
Tagged date : 2024-08-16 03:35:16 UTC

[guest]

My 8K Samsung as everyone knows doesn't do Dolby Vision, but the 8K-hevc.mkv before injection plays perfectly in HDR10 on everything,
but after the RPU.XML is input to workflow 1,the output MP4 file plays in HDR10 in the Windows Media Player, but only haltingly in MPC-HC,
and not at all from the tv's own media player. Isn't DV P8.1 backward HDR10 compatible? The metadata seems okay.

I'm sure someone will correct me if I'm wrong, but from what I understand the RPU.bin is only for Dolby Vision.

So why are you injecting it into a file that plays properly on your Samsung ?? when you clearly know that your Samsung does not support DV anyway.

And, if the 8K .mkv plays, why convert it to .mp4, when you probably don't need to ??

And where did this come from:- dvhe.08.12

[ReciprocalUniverse]

I'm sure someone will correct me if I'm wrong, but from what I understand the RPU.bin is only for Dolby Vision.

So why are you injecting it into a file that plays properly on your Samsung ?? when you clearly know that your Samsung does not support DV anyway.

And, if the 8K .mkv plays, why convert it to .mp4, when you probably don't need to ??

And where did this come from:- dvhe.08.12

Your point about RPU.bin specific to Dolby Vision is true but profile 8 is backward compliant to the HDR10 base layer, so anything should play it, without RPU metadata of course.

You're right, I can play 8K HDR10 without DV but I have a pal, we are both shooting Nikon Z8, 8K 60fps, he has an LG 8K model with DV and we want to see if it's possible to make 8K Dolby Vision. I'm also doing 8k HDR10+. My Samsung can play that, his LG cannot, we want to compare these, so enough, we have our reasons, no one is harmed.

I have been making HDR10 videos since 2014, and one of them you've probably seen because it played around the globe in 2015 in every Magnolia HiFi showroom on Sony Z9D demo loops. I have one of the very first HDR videos of any kind on YouTube, within the first week or 10 days of the HDR service being offered. I have graded videos in HDR internationally with credits. So back off, friend! Let's be positive.

As for where dvhe.08.12 came from, that probably means profile 8, level 12, level 12 is for 7680 x 4320 up to 60 fps. It is not a parameter set by the user but is reported by x265. I also saw it reported at 08.0C, which is the hex representation for P08 L12.

[guest]

Your point about RPU.bin specific to Dolby Vision is true but profile 8 is backward compliant to the HDR10 base layer, so anything should play it, without RPU metadata of course.

You're right, I can play 8K HDR10 without DV but I have a pal, we are both shooting Nikon Z8, 8K 60fps, he has an LG 8K model with DV and we want to see if it's possible to make 8K Dolby Vision. I'm also doing 8k HDR10+. My Samsung can play that, his LG cannot, we want to compare these, so enough, we have our reasons, no one is harmed.

Interesting, OK, AFAIK, LG TV's will ONLY play DV from .mp4, .m2ts or .ts.

Up until recently (a couple of months) I had a 2018 LG 4K 55" TV, that would only play DV (using this great app), when using the "old" version of the mp4 muxer, but then that TV died, and I now have an LG C4 65", and it seems to work OK with both the "old" & "new" mp4 muxer's

Sux for you, that you have a Samsung.

I have been making HDR10 videos since 2014, and one of them you've probably seen because it played around the globe in 2015 in every Magnolia HiFi showroom on Sony Z9D demo loops. I have one of the very first HDR videos of any kind on YouTube, within the first week or 10 days of the HDR service being offered. I have graded videos in HDR internationally with credits. So back off, friend! Let's be positive.

A little bit aggressive at the end, not sure where that came from, but kudos to your self promotion, and no I wouldn't have seen that, and where's Magnolia HiFi ???, I'm in Australia !!

As for where dvhe.08.12 came from, that probably means profile 8, level 12, level 12 is for 7680 x 4320 up to 60 fps. It is not a parameter set by the user but is reported by x265. I also saw it reported at 08.0C, which is the hex representation for P08 L12.

That explains that too, only doing 4K here.

[ReciprocalUniverse]

A little bit aggressive at the end, not sure where that came from, but kudos to your self promotion, and no I wouldn't have seen that, and where's Magnolia HiFi ???, I'm in Australia !!



I'm a fan of your country and a customer of Australia's Blackmagic Design and Grant Petty, and own a few cameras including the Ursa Mini Pro 12K, other stuff too. Magnolia HiFi's were a department of the higher end Best Buy retail stores.

I think I have a working 8k DV file. My pal is going to test it tomorrow. Fingers crossed. I'll report the findings as soon as I know, and thanks to everyone for the help.

[ReciprocalUniverse]

Results are in for the LG Z3, 8K Dolby Vision OLED television, and they are a no-go for 8K-60 fps DV playability. I don't think there is anything wrong with these 8K-60 files, which you can download from my Google Drive account to do as you wish, inspect them for metadata, play them, share them, I don't care. They were shot with the Nikon Z8 in 8K60 NRaw/NLog, graded in DaVinci Resolve Studio 19.0B, Dolby Vision DV dvhe.08.12, HEVC based, CMv4.0, XML version 5.1.0 profile 8.1 Level 12 for 7680x4320 at 60 fps.

I tried (3) methods to get them to play.

1.) Workflow 1 in DoVi_Scripts method as described by Kuler087: https://drive.google.com/file/d/1IZUaMXnINCEHWOnoxsfhVXlntOU2DUnK/view?usp=sharing
2.) XML.BIN from Dovi_tool interleaved in x265: https://drive.google.com/file/d/1wz2Bg3sTAYRF5K9g46kakLkwwji1xMAH/view?usp=sharing
3.) Method 2 file RPU injected with DDVT_DEMUXER: https://drive.google.com/file/d/142IR3r96pERxclXxFTdIRTiv8Hpn-64a/view?usp=sharing

All 3 methods result in playable HDR10 files on both Samsung 8K and LG Z3, but were not playable in DV on Z3. The same clip encoded in 4K does play in DV on Z3 and my Hisense U8. Again, I don't think anything is wrong with the files, my judgement is the Z3 does not support dvhe.08.12. I am only aware of one other possible DV compliant 8K-60-fps television, The Sony Z9K. Maybe we'll get around to that one.

[ReciprocalUniverse]

I'm having a hard time with this notion of the LG Z3 not being DV compliant at 8K/60. I'm going to make one more shot at DV by dropping the bitrate to 60 Mbps, down from 85 Mbps, before pronouncing the Samsung 8K king since it is able to support 8K/60 HDR10+ streamed and USB flash drive.

[Kuler087]

Please, try these: https://drive.google.com/drive/folders/1JFepTfCgk3jGK8N-3Qq-ch4N5H3ZWBGM?usp=sharing

[guest]

Please, try these: https://drive.google.com/drive/folders/1JFepTfCgk3jGK8N-3Qq-ch4N5H3ZWBGM?usp=sharing

I thought I'd try a couple of these, but of course, they wouldn't play, as they are 8K after all.

But one thing I did notice, these are dvhe.08.11, not dvhe.08.12...

And also the Codec ID was either, hev1, hvc1 or dvhe depending on the mp4 muxer being used.

Anyway, I guess we'll have to wait for a reply, after they've tested them.

[Kuler087]

dvhe.08.11, not dvhe.08.12...

different framerate

they wouldn't play, as they are 8K after all.
They are all working(LLDV) correctly on Windows Energy player (https://apps.microsoft.com/detail/9p9zh5fl1bfk?hl=en-US&gl=US) + DV extension (https://apps.microsoft.com/detail/9pltg1lwphlf?activetab=pivot%3Aregionofsystemrequirementstab&hl=en-us&gl=US).

hev1, hvc1 or dvhe
hev1 = latest mp4muxer which strangely doesn't work on my Win11 PC but works fine on my Win10 PC.
dvhe= old mp4muxer
hvc1= Resolve and mp4box

[guest]

They are all working(LLDV) correctly on Windows Energy player (https://apps.microsoft.com/detail/9p9zh5fl1bfk?hl=en-US&gl=US) + DV extension (https://apps.microsoft.com/detail/9pltg1lwphlf?activetab=pivot%3Aregionofsystemrequirementstab&hl=en-us&gl=US).

I should have mentioned that I tried them on my LG C4....they do play with PotPlayer on my little laptop.

[Kuler087]

they do play with PotPlayer on my little laptop.
yes of course, but without decoding the DV metadata. The player I'm talking about processes the metadata(P5-P8-P7).

[ReciprocalUniverse]

Kuler087, your 8K hybrid "p8.1.HDR10plus.8K DS_NEW_mp4box.mp4" played perfectly in HDR10+ on my Samsung 8K, in 7680x4320 - 23.98 fps.

The 4000 nit grade of the Yellowstone Park clipped in HDR10 but tone mapped beautifully in HDR10+. I'll try the others soon.

[ReciprocalUniverse]

Update:

"p8.1.HDR10plus.8K DS_NEW_mp4box.mp4" does not play on LG 8K Z3, "file not supported".

[Kuler087]

You should try all the variants. They all have something ''different'' that could make them work or not.

[ReciprocalUniverse]

You should try all the variants. They all have something ''different'' that could make them work or not.

But you said this, "P5 encoding from scratch requires the proprietary Dolby engine,"

...so not interested in P5 file list unless we can make them without license.

P8.1 works on the Z3, just in 4k not 8k.

The (3) other remaining files have HDR10+ naming inclusions, are they DV compliant?

[ReciprocalUniverse]

Never mind, I see that they have DV. We'll try them.

[Vymrr]

Hello. How do I find out if my TV supports CM4.0?

[guest]

Hello. How do I find out if my TV supports CM4.0?

Unless it mentions it in your user manual...

Maybe you might have to do a sample of both, and see what your TV does with it.

If it's reasonably new, I'd say it will support CM4.0.

What brand & model is your TV ??

[Vymrr]

Unless it mentions it in your user manual...

Maybe you might have to do a sample of both, and see what your TV does with it.

If it's reasonably new, I'd say it will support CM4.0.

What brand & model is your TV ??

Hisense U8H (non US version)

[guest]

Hisense U8H (non US version)

I was able to get the specs on this....is it a 75" ??

It doesn't mention anything about that, but I would think that it will be OK with CM4.0, but like I said, try a sample of each, and test for yourself, it won't take long, and you'll know for sure :)

You can easily create a 5 minute chunk of a movie, and process it both ways.

Good luck.

[Vymrr]

I was able to get the specs on this....is it a 75" ??

It doesn't mention anything about that, but I would think that it will be OK with CM4.0, but like I said, try a sample of each, and test for yourself, it won't take long, and you'll know for sure :)

You can easily create a 5 minute chunk of a movie, and process it both ways.

Good luck.

it's a 65inch. Alright thanks :thanks:

[Kuler087]

But you said this, "P5 encoding from scratch requires the proprietary Dolby engine,"

You can with Resolve and the custom edid I gave you.

Hello. How do I find out if my TV supports CM4.0?

All the TVs made after 2019 should support it. You can try the cmv4.0 test files here: https://drive.google.com/drive/u/1/folders/1nMz95KqgkO95EDGrYhrk-Ifx6vRYDEfs

[ReciprocalUniverse]

You can with Resolve and the custom edid I gave you.

My only serious reason for wanting to try P5 was to see if there was *any* profile that would get 8K DV working in the LG Z3.

Of the files you offered, unfortunately, none worked on the LG and only one would play on his Mac (p8.1.HDR10plus.8K DS_NEW_mp4box).

He did say that a file I created in P8.1 played on the Z3 in HDR10. My assumption prior to that was that standalone HDR10 would be playable anyway, but perhaps not. Does the LG need HDR10 to be the base layer in a DV profile to play?

Edit: It's an LG Z2, not 3,

[Kuler087]

unfortunately, none worked on the LG

I'm surprised that even the files encoded/muxed in Davinci Resolve didn't work.

[ReciprocalUniverse]

I'm surprised that even the files encoded/muxed in Davinci Resolve didn't work.

Just not 8K files. Seems to be a failing of the tv, not your files. Played nicely in 8K HDR10+ on mine.

[ReciprocalUniverse]

P5 files obviously don't play on Samsung.

[guest]

I've been doing a bit of "research", and there must be a fairly simple explanation why nobody can get 8K DV to work (yet) on LG Z2 (3), I wonder if it needs different settings ???

Chipset-based 8K TV
• dvhe.05.12
• dvhe.08.12
• dvhe.09.05

Dolby Vision 8.4 Profile

Level Maximum pixel rate resolution at frame rate Maximum bit rates
ID

11 995,328,000 7680 7680 × 4320 @ 30 60 240
12 1,990,656,000 7680 7680 × 4320 @ 60 120 480
13 3,981,312,000 7680 7680 × 4320 @ 120 240 800

[ReciprocalUniverse]

We know that dvhe.08.12 works in 4K, and that 8K did not, even after lowering 8K bitrate to 30 Mbps, except HDR10 it did. If you have a 8.4 profile to try in 8K, we will. My theory has been tv is not supporting 8K DV in any flavor.

[guest]

We know that dvhe.08.12 works in 4K, and that 8K did not, even after lowering 8K bitrate to 30 Mbps, except HDR10 it did. If you have a 8.4 profile to try in 8K, we will. My theory has been tv is not supporting 8K DV in any flavor.

I looked up the spec's on the Z2, and it states that Dolby Vision IS supported, but that's ALL it says :(

Not sure how to create an 8.4, that's something that Kuler would have to comment on.

You might be able to do something with Resolve, and inject the DV metadata into "something"

I downloaded an 8K clip off YouTube earlier today, but it was encoded with AV1, as an mp4, but of course I don't have an 8K LG TV.

[ReciprocalUniverse]

I looked up the spec's on the Z2, and it states that Dolby Vision IS supported, but that's ALL it says :(

Not sure how to create an 8.4, that's something that Kuler would have to comment on.

You might be able to do something with Resolve, and inject the DV metadata into "something"

I downloaded an 8K clip off YouTube earlier today, but it was encoded with AV1, as an mp4, but of course I don't have an 8K LG TV.

YouTube DV AV1 (nor VP9) is not playing in DV on his Z2 nor my Hisense U8. That's in 4K of course. You found one that does? Would like to have the link to try.

[guest]

YouTube DV AV1 (nor VP9) is not playing in DV on his Z2 nor my Hisense U8. That's in 4K of course. You found one that does? Would like to have the link to try.

Have you searched for 8K DV clips on YouTube from your (your friends) TV's to see how they play ??

Here's a link to something that may help:-

https://www.youtube.com/watch?v=QqI9eKQnFL4

[ReciprocalUniverse]

We haven't found any clips streamed in DV by YouTube. They play fine in regular HDR10 and even 8K. By DV I mean it's got to turn on the Dolby Vision icon on the tv set, not just whatever badge the YouTuber sticks on his video saying Dolby Vision. I think there is confusion with people seeing a DV badge added by the uploader versus actually turning on the tv's own icon or indicator light, whatever. My understanding remains that YouTube does not stream DV. I will try your link though.

[guest]

We haven't found any clips streamed in DV by YouTube. They play fine in regular HDR10 and even 8K. By DV I mean it's got to turn on the Dolby Vision icon on the tv set, not just whatever badge the YouTuber sticks on his video saying Dolby Vision. I think there is confusion with people seeing a DV badge added by the uploader versus actually turning on the tv's own icon or indicator light, whatever. My understanding remains that YouTube does not stream DV. I will try your link though.

I agree, you've gotta see that Dolby Vision icon on the tv set, that's for sure.

[ReciprocalUniverse]

Have you searched for 8K DV clips on YouTube from your (your friends) TV's to see how they play ??

Here's a link to something that may help:-

https://www.youtube.com/watch?v=QqI9eKQnFL4

That link played in 8K but not even HDR10, never mind DV.

I found one here that plays in 8K HDR10 on my Samsung.
https://youtu.be/7PIji8OubXU?si=G3jZr5wBhg_pc6Pa

I have to go in the other room where my U8 is to see if it plays in actual DV (in 4K). Will report back.

[guest]

That link played in 8K but not even HDR10, never mind DV.

I found one here that plays in 8K HDR10 on my Samsung.
https://youtu.be/7PIji8OubXU?si=G3jZr5wBhg_pc6Pa

I have to go in the other room where my U8 is to see if it plays in actual DV (in 4K). Will report back.

That clip was only available (to download & play) in 2160p/4K @ 60fps, you need at least 4320p/8K @ whatever fps !!!

Did it actually display @ 8K ??

here's another:- choose to play it in 4320p !!!

https://www.youtube.com/watch?v=vIN9Q1Slk0w

[ReciprocalUniverse]

[QUOTE=TDS;2005861]That clip was only available (to download & play) in 2160p/4K @ 60fps, you need at least 4320p/8K @ whatever fps !!!

Did it actually display @ 8K ??

Yes, it streamed in 7680 x 4320 @ 60fps AV1 smpte2084/bt2020
...but not Dolby Vision.

120 fps is just the camera frame rate it was shot at, slowed to 60 in post. YouTube doesn't stream higher than 60, at least not at 8K. And there's no tv that supports native 8K 120 playback either.

I don't know about downloading from YouTube, never tried, just streaming.

[ReciprocalUniverse]

here's another:- choose to play it in 4320p !!!

https://www.youtube.com/watch?v=vIN9Q1Slk0w

This one streamed in 8K SDR, no HDR.

[guest]

That clip was only available (to download & play) in 2160p/4K @ 60fps, you need at least 4320p/8K @ whatever fps !!!

Did it actually display @ 8K ??

Yes, it streamed in 7680 x 4320 @ 60fps AV1 smpte2084/bt2020
...but not Dolby Vision.

120 fps is just the camera frame rate it was shot at, slowed to 60 in post. YouTube doesn't stream higher than 60, at least not at 8K. And there's no tv that supports native 8K 120 playback either.

I don't know about downloading from YouTube, never tried, just streaming.

It would be nice if someone posted some "proper" demo's (not YouTube), the first time I ever saw the Dolby Vision icon was when I downloaded a DV demo that was a .ts.....seeing that icon for the first time put a huge smile on my face.

I use Internet Download Manager to download off YouTube.

[ReciprocalUniverse]

It would be nice if someone posted some "proper" demo's (not YouTube), the first time I ever saw the Dolby Vision icon was when I downloaded a DV demo that was a .ts.....seeing that icon for the first time put a huge smile on my face.

I use Internet Download Manager to download off YouTube.

So if IDM is giving you the native file uploaded to YouTube, it may very well contain compliant DV metadata, but what YouTube streams does not.

That was a conversation I had with my pal, he objects to all these YT videos claimed to be DV, but if they really are DV and it's YT that's not streaming DV, shouldn't YT have an obligation to disclose since they are re-encoding them? Afterall, the uploader would not be the one misrepresenting the file.

[guest]

So if IDM is giving you the native file uploaded to YouTube, it may very well contain compliant DV metadata, but what YouTube streams does not.

That was a conversation I had with my pal, he objects to all these YT videos claimed to be DV, but if they really are DV and it's YT that's not streaming DV, shouldn't YT have an obligation to disclose since they are re-encoding them? Afterall, the uploader would not be the one misrepresenting the file.

I'm not sure if it gives you that access...

Not being someone that uploads ANYTHING to YT, from what I've heard, YT WILL change anything that doesn't follow the "rules".

So I agree with your buddy, just because it says it is, doesn't mean a thing :(

I mean you might be able to download something that's close to what you want, and re-process it...

For example, I download quite a few train videos from Norway, etc, and re-process them to play a LOT faster, and with no ads :)

I know that you can play YT @ 2x, but you still get the ad's and occasionally buffering in high res.

[Vymrr]

I tried running your test files but somehow my ugoos am6b+ (running coreelec) is playing them as SDR and HDR content only? I have no issues playing normal DV movies as DV, only your files.

You can with Resolve and the custom edid I gave you.



All the TVs made after 2019 should support it. You can try the cmv4.0 test files here: https://drive.google.com/drive/u/1/folders/1nMz95KqgkO95EDGrYhrk-Ifx6vRYDEfs

[Kuler087]

I tried running your test files but somehow my ugoos am6b+ (running coreelec) is playing them as SDR and HDR content only? I have no issues playing normal DV movies as DV, only your files.

works fine on mine

[wyup]

In 8-2-2 (Encode DV to SDR), it would be nice to preview/compare different analyse tunings: balanced, more/most highlights, less/least-highlights and legacy, to choose the best looking SDR for the user.

In 3-1 (DoVi MAKER from HDR10, Dolby Algorythm), something similar would be desired aswell to estimate how DV is going to behave when doing the interpolation for the tv capability. I.e: If my DV-enabled tv has 400 nits of brightness for HDR and the content is graded at 1,000 nits, depending on the chosen analyse tuning, the final image interpolated from the 100-nit mandatory trim would be different.

Also, is it possible to choose how many DV trims to generate? Ie: 100, 400, 600, 1000.
And finally, it would be nice to choose desired trim encoding for HDR10. Ie: convert a native HDR10 4,000 movie to a 1,000, 600 or 400 one, to get better tonemapping than a non-enabled DV tv does.

Thanks for the good work.

[Kuler087]

In 8-2-2 (Encode DV to SDR), it would be nice to preview/compare different analyse tunings: balanced, more/most highlights, less/least-highlights and legacy, to choose the best looking SDR for the user.
In 3-1 (DoVi MAKER from HDR10, Dolby Algorythm), something similar would be desired aswell to estimate how DV is going to behave when doing the interpolation for the tv capability. I.e: If my DV-enabled tv has 400 nits of brightness for HDR and the content is graded at 1,000 nits, depending on the chosen analyse tuning, the final image interpolated from the 100-nit mandatory trim would be different.

I guess you meant 8-2-4 because 8-2-2 use libplacebo for the SDR tonemapping.

The analysis tunings are filtering that Dolby applies during the metadata creation so you cannot edit it when the metadata has been exported/delivered. The only way to edit/preview the tuning is within Resolve (or whatever grading software you use) during the grading process.
You can use different tunings in the same timeline and if you hover the metadata, it will tell you the tuning used for this particular shot.

https://i.ibb.co/c1xqZNz/Capture-d-cran-2024-08-21-114351.png




Also, is it possible to choose how many DV trims to generate? Ie: 100, 400, 600, 1000

No, you need a DV license for that.
In a cmv4.0 workflow, even if you don't do any manual trim, the dolby system will auto generate L2 at three targets: 100-600-1000nits
In a cmv2.9 workflow, if you don't do trims, the system will not generate any.

You can remove trims with the metafier though. workflow 2-6

And finally, it would be nice to choose desired trim encoding to HDR10. Ie: convert a native HDR10 4,000 movie to a 1,000, 600 or 400 one, to get better tonemapping than a non-enabled DV tv does.


you can already do that with 8-2-4. You can deliver the 48-100-300-600-1000-2000nits trim even if not present in the metadata. When not present, the desired target is created by extrapolating the existing trims.

[Vymrr]

works fine on mine

I got it working, turned out DV option in settings was turned off when I played your files.. What are the most obvious clips that would show my TV supports CM4? Maybe it's my eyes, but I kind of found it hard to differentiate for the real content clips. For the test files, are all of them CM4.0 ? I can see differences in brightness for the L8 clips at various nits.

[Kuler087]

When cmv4.0 works, you will see brightness changes when the metadata changes.


Example:

https://i.ibb.co/zG1xQTX/Application-Frame-Host-COL6uocd4-G.gif

[ReciprocalUniverse]

Kuler, few questions here:

1.) When or why would P5.0 be preferred over P8.1? I understand it's proprietary, differs because of PQ with shaping and IPT-PQ-C2 matrix. Is it better generally or else when or why would it be recommended?

2.) With Resolve Studio, are you monitoring HDR with one of the Decklink cards or are you monitoring with the Windows GPU? The reason I ask is because of the quantity of variations of encoded files in your Drive library. With each change of DV metadata are you having to encode a file to see the result of the change? And yes, they all do play for me on my Hisense U8.

3.) Before you encode HEVC or export an intermediate from Resolve with IPT-PQ-C2, are you able to live monitor this color matrix?

[Kuler087]

1- 10bit DV P5 is more efficient than HDR10/P8 when it comes from a 12bit master.

https://i.ibb.co/ckt87KJ/p5-itp-colorspace.png


2- Yes, I monitor HDR with my decklink card. I don't think the HDR preview in Resolve is accurate (too dark). Most of the rpu test file in my GD are generated with dovi_tool. You can generate any p8.1 rpu with a json config, and then I use my script DEE (8-2-6) to encode the profile 5 version.
For example, this is the json config I used for my latest FEL vs BL test file. (https://www.youtube.com/watch?v=iKUf2GpqoeU) BTW, if this test file doesn't convince one to get a proper FEL P7 player, nothing will.
https://justpaste.it/3p8rw
D:\DoVi_Scripts\tools\dovi_tool.exe generate -j D:\config.json -o D:\P8_generated.bin



3- No, DV tunneling requires the very expensive decklink card but DV tunneling is pretty much useless. You can see the DV mapping for any target on your HDR mastering monitor and make all the adjustments to the trims. DV is graded in HDR and tunneling is mostly for previewing the final product on a consumer TV. You should never make any change to your trim or grade based on what you see on a consumer TV, always make change according to what you see on your mastering monitor.
trims / master preview example: https://slow.pics/c/cTDiL8Mn

[Vymrr]

When cmv4.0 works, you will see brightness changes when the metadata changes.


Example:

https://i.ibb.co/zG1xQTX/Application-Frame-Host-COL6uocd4-G.gif

Yes I got that when the L8 slope number changes. Thanks!

[Hellboy.]

Kuler087 I using workflow (4-3) with (TS version), (set MUX=NO) and (set encode_DDP=NO).
The problem is the audio get extracted and converted and i don't need that. How can i stop the audio from extracting and converting.
I try with a movie with "TrueHD Atmos 7.1" and the audio was converted to .wav and .ec3.
Thanks.

Edit: I check the audio and the audio extracted and converted was not the first, was the last one. A FLAC 2.0 commentary track.

[Kuler087]

Because FLAC is not supported in tsmuxer, the script encodes it to pcm.
I added an exception when MUX=NO, try this: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link

[Hellboy.]

Thanks, that worked.

[Vymrr]

I saw on the excel sheet some movies that have a L5 edits text file. Is that supposed to be injected into the movie file? If so what workflow is it?

[Kuler087]

The L5 text files are active area config .json for when you do a dynamic aspect ratio P8 hybrid with metadata from WEB.
you can use them in workflow 1 if you rename the inputs the same and skip the 2nd input.

EG:
D:\movie.mkv
D:\movie.json (L5 config)

[Gatorman3385]

Is it a bad idea to import the CM4.0 levels from a resolve-generated XML into a MEL CM2.9 RPU from the original disc? Should CM4.0 levels only be imported from videos mastered with it?

[Kuler087]

cmv4.0 and 2.9 metadata must come from the same dv analysis, so yes it's a bad idea.

[Gatorman3385]

That makes sense. Thank you.

[Kuler087]

3.0.2 released (minor changes)
https://github.com/R3S3t9999/DoVi_Scripts/releases


- (8-2) tools pack: x265.exe must be updated (https://drive.google.com/file/d/1-7MO9DWEQUOmmfTCNkBRPc2umrLC8h_o/view) and old versions will no longer work.
- Plotter: added Level 9 info in L1 plot(6-3 / 6-4) and quick info (1)
- Screenshots: added an option to disable screenshot OSD in 7-1 / 7-2 / 7-3 (line 145)
- Editor: added an option to edit source_PQ (for testing only: never change it in real movies/shows)
- Default settings change: DDP EC3 encoding default is now: NO. (Line 75: set encode_DDP=NO)

[Hellboy.]

Thanks Kuler087

[Atari1971]

Good morning. I've had problems with Dolby Vision encoding for several months. I thought the update would fix it, but I still get this error with the official Dolby script or the MadVr script... :(

Generating DoVi from a MadVR measurement file...
Reading generate config file...
Parsing madVR measurement file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: BaseThreadInitThunk
11: RtlUserThreadStart
Done.

Editing L5 (active area) to left=0, right= 0, top= 278, bottom= 278
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Appuyez sur une touche pour continuer...

[Kuler087]

This looks like workflow 3-2?
Did you install madVR and lavfilter? it looks like madvr failed to measure the video

https://i.ibb.co/Fmbz95Z/Windows-Terminal-Njvk3q-Frqi.gif

[Atari1971]

how to install madvr?

[Kuler087]

go in tools/madvr folder and click (with admin rights) on the install bat.

[Atari1971]

Installation succeeded.
Please do not delete the madVR folder.
The installer has not copied the files anywhere

[Atari1971]

Apparently everything is installed well. What can cause this error?

[Kuler087]

if everything were installed correctly, it would work :)

post the complete log of the workflow, not just part of it otherwise there's not much I can do to help you.

[Atari1971]

Hello, here is the full capture of the final message...:scared:

Donate: https://www.paypal.com/donate/?hosted_button_id=6ML5KUZG9XGB6 Date: 13/09/2024 10:33
Contact: R3S3T_9999@proton.me Version: 3.0.2_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]?3

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

1) Workflow.1= CM_analyzer HDR10 to DoVi maker (can batch) (Professional CM v4.0 Dolby Algo)
2) Workflow.2= Convert HDR10plus videos to DoVi (can batch) (Not Recommended)
3) Workflow.3= Back to main menu

Choice? [1,2,3]?2

--------------------------------------------------------------------------------------------------
-- NOT RECOMMENDED: you'll get better DV if you use 3-1.
-- See: https://drive.google.com/file/d/1IXR60nWe2Ylb7CTRjZ3_tpI5RsAajU5G/view?usp=drive_link
-- This script will batch convert HDR10plus or HDR10 video to DoVi with dynamic metadata or madVR
-- Can use external L5 json if filepath/name is the same as the BL input
-- 10/100nits floor can be removed at line 169
--------------------------------------------------------------------------------------------------

Drag and drop folder with files or a single file and press enter...
D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv

Auto or Manual Active Area L5 edit... a or m ? and press enter...
a
processing..."revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
Measuring letterbox of "D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
left border: 0
right border: 0
top border: 278
bottom border: 278

Reading input tracks format/id/language...
Done.


====================
- DEMUXING -
====================

Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'F:\DoVi_Scripts\temp.folder34\hdr.hevc'. Container format: HEVC/H.265 elementary stream
Extracting track 1 with the CodecID 'A_DTS' to the file 'F:\DoVi_Scripts\temp.folder34\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.track_2_fre.dts'. Container format: Digital Theater System (DTS)
Progress: 100%
LAV Splitter Source not found.

Generating DoVi from a MadVR measurement file...
Reading generate config file...
Parsing madVR measurement file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: BaseThreadInitThunk
11: RtlUserThreadStart
Done.

Editing L5 (active area) to left=0, right= 0, top= 278, bottom= 278
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Appuyez sur une touche pour continuer...
Done.

Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Editing L6 to MDL=1000/1, MaxCLL/FALL=0/0
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Appuyez sur une touche pour continuer...

[Kuler087]

LAV Splitter Source not found.
Lab filter is not installed or misconfigured

[Atari1971]

Lav Splitter is installed

[Atari1971]

What is the configuration of Lav Splitter? Lav Audio, video and splitter are installed.

[Kuler087]

all shown in the tutorial installation video but it depends on your hardware.

here's mine:

https://i.ibb.co/8KNCgzT/Capture-d-cran-2024-09-14-094045.png

[Atari1971]

I try it

[Atari1971]

same error...

[Atari1971]

My configuration:

[Kuler087]

Well, I dont know but the issue is on your end. Try the nightly lav filters

[Atari1971]

I also have the teckno3D app. Can this play a role?

[Kuler087]

I dont know what it is but probably not.
Your best option is to try lavfilters nightly and different decoding options (especially if you don't have a GPU).

[Atari1971]

New error, but with the same purpose (Nightly lav filters):

Donate: https://www.paypal.com/donate/?hosted_button_id=6ML5KUZG9XGB6 Date: 14/09/2024 11:42
Contact: R3S3T_9999@proton.me Version: 3.0.3.beta_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]?3

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

1) Workflow.1= CM_analyzer HDR10 to DoVi maker (can batch) (Professional CM v4.0 Dolby Algo)
2) Workflow.2= Convert HDR10plus videos to DoVi (can batch) (Not Recommended)
3) Workflow.3= Back to main menu

Choice? [1,2,3]?2

--------------------------------------------------------------------------------------------------
-- NOT RECOMMENDED: you'll get better DV if you use 3-1.
-- See: https://drive.google.com/file/d/1IXR60nWe2Ylb7CTRjZ3_tpI5RsAajU5G/view?usp=drive_link
-- This script will batch convert HDR10plus or HDR10 video to DoVi with dynamic metadata or madVR
-- Can use external L5 json if filepath/name is the same as the BL input
-- 10/100nits floor can be removed at line 169
--------------------------------------------------------------------------------------------------

Drag and drop folder with files or a single file and press enter...
D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv

Auto or Manual Active Area L5 edit... a or m ? and press enter...
a
processing..."revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
Measuring letterbox of "D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
left border: 0
right border: 0
top border: 278
bottom border: 278

Reading input tracks format/id/language...
Done.


====================
- DEMUXING -
====================

Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'F:\DoVi_Scripts\temp.folder34\hdr.hevc'. Container format: HEVC/H.265 elementary stream
Extracting track 1 with the CodecID 'A_DTS' to the file 'F:\DoVi_Scripts\temp.folder34\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.track_2_fre.dts'. Container format: Digital Theater System (DTS)
Progress: 100%
Measuring video file "D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv" using D3D11 (copy-back)...
Metadata:
Mastering display luminance: 0.0001/1000, gamut: 0.708 0.292, 0.131 0.046, 0.17 0.797, 0.3127 0.329
MaxCLL: 1000, MaxFALL: 400 nits

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

Generating DoVi from a MadVR measurement file...
Reading generate config file...
Parsing madVR measurement file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: BaseThreadInitThunk
11: RtlUserThreadStart
Done.

Editing L5 (active area) to left=0, right= 0, top= 278, bottom= 278
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart

[guest]

New error, but with the same purpose (Nightly lav filters)

Maybe you should provide a sample of the video that is causing this problem...see if Kuler can replicate it !!

[DMD]

I performed procedure 3-2 on a sample file (one minute) in HDR10+ and a everything worked smoothly.

[Kuler087]

New error, but with the same purpose (Nightly lav filters):



Now you got madvr+lavfilters working. Unfortunately, the problem is your input file and there's nothing I can do about it. Sometimes madVR fails to measure videos but it rarely happens with MKV files. I usually get this issue when the container is TS/M2TS and simply remuxing it in mkvtoolnix fix the issue.

If you try with other ''proper'' HDR10 mkv files , it should work.

[Kuler087]

I performed procedure 3-2 on a sample file (one minute) in HDR10+ and a everything worked smoothly.

FYI, when the input has HDR10plus, workflow 3-2 doesn't use madvr to generate DV. It just convert the original HDR10plus metadata to Level 1 DV. @Atari1971 file is HDR10 only so madvr has to measure the video.

About the HDR10plus to DV conversion, there's a potential improvement thanks to @doppingkoala on the CoreELEC forum (https://discourse.coreelec.org/t/dynamic-conversion-of-hdr10-sei-to-dv-p8-nal/51770/166)


10 movies example: https://slow.pics/c/NnIvEwN7
dynamic metadata files: https://drive.google.com/drive/u/0/folders/1BgYitM6lM-MlDSstIK4E8_fCVnWjHFE8
latest DS beta with this update: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
put this file in tool folder: https://mega.nz/file/hbkQWDDI#7ml6Pr1SKXsTLNnhFOS6iVCzJi68n9w8sqk7yWPFo4s

The latest DS beta also has a new workflow(2-7) that can quickly parse your DV library and export the information to a text file like this (https://justpaste.it/3uryc). It will also calculate how many FEL/MEL/P7/P8/P5/cmv4.0/cmv2.9 movie you have.

my library:

Profile 7 FEL total: 274
Profile 8 total: 1013
Profile 5 total: 78
CMv4.0 total: 674
CMv2.9 total: 692

[DMD]

FYI, when the input has HDR10plus, workflow 3-2 doesn't use madvr to generate DV. It just convert the original HDR10plus metadata to Level 1 DV. @Atari1971 file is HDR10 only so madvr has to measure the video.........
Thank you very much.
I was not aware of this information and thank you for the new feature that allows me to analyze movies.

[Atari1971]

I thought it was good, but in the end I got this message... :(

Custom DoVi_Scripts by the TEKNO3D Labs team.
Date: 14/09/2024 13:00
Contact Author: R3S3T_9999@proton.me Version: [Custom]_MKV

Dolby Vision Generation
====================================================================================
Generate Scene by Scene Dolby Vision metadata [Official cm_analyze by Dolby Labs].
Output will be placed in the DoVi_Scripts_Output folder [Software Installation Folder/HDR10Plus]
====================================================================================


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


--------------------------------------------------------------------------------------------------------------------
-- Input must be HDR MKV/TS/M2TS/MP4/MOV(prores) for the video and the external files: MDL5-bat/xml/rpu/json/txt
-- Input can be a folder or a single file
-- Input with ")" in the filename will NOT work and [] in the filename is not allowed by dolby tools
-- This workflow will convert an HDR10 video to DoVi using official Dolby Vision tools
-- Require Dolby metafier.exe , cm_analyze.exe, lavfilter, madvr and avisynth+
-- https://customer.dolby.com/content-creation-and-delivery/dolby-vision-professional-tools
-------------------------------------------------------------------------------------------------------------------
Scene by Scene metadata generation will be performed using GPU.
Drag and drop folder with HEVC video files or a single file and press enter...
F:\Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter.mkv

------------------------------------------------
BL Mastering Display Luminance and Colors:
min: 0.0001 cd/m2, max: 1000 cd/m2 BT.2020
------------------------------------------------

What is the Mastering Display? Choices are: 1000nits-P3= 20(default) / 1000nits-BT2020= 21 [Converter's Default] / 4000nits-P3= 7 / 4000nits-BT2020= 8 / 2000nits-P3= 30 / 2000nits-BT2020= 31
2121
Manual or Auto L5... a or m ? and/or press enter... (default=m)
a
Processing: "Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
reading input tracks format/id/language...
done.

Making a small sample from the input...

Done

Measuring the letterbox...


Done

---------------------------------
--> left border: 0
--> right border: 0
--> top border: 277
--> bottom border: 277
---------------------------------

Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'F:\SDR_TO_HDR_VIDEO_CONVERTER\HDR10Plus\DoVi_Scripts_Output\temp.folder77\BL.hevc'. Container format: HEVC/H.265 elementary stream
Progress: 100%
Measuring video file "F:\Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter.mkv" using D3D11 (copy-back)...
Metadata:
Mastering display luminance: 0.0001/1000, gamut: 0.708 0.292, 0.131 0.046, 0.17 0.797, 0.3127 0.329
MaxCLL: 1000, MaxFALL: 400 nits
Measurements:
Frames: 164613, MaxCLL 100%: 626, 99.9%: 585, MaxFALL: 496, AvgFALL: 15, AvgFMLL: 310 nits
Reading generate config file...
Parsing madVR measurement file...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 164613 frames
Done.
1 fichier(s) déplacé(s).
Parsing RPU file...
Exporting scenes list...
Done.
Indexing, please wait... 100%
Writing index... done.
Input #0, avisynth, from 'F:\SDR_TO_HDR_VIDEO_CONVERTER\HDR10Plus\DoVi_Scripts_Output\temp.folder77\script.avs':
Duration: 01:54:25.73, start: 0.000000, bitrate: N/A
Stream #0:0: Video: rawvideo (Y3[11][10] / 0xA0B3359), yuv420p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x2160, 23.98 fps, 23.98 tbr, 23.98 tbn
Stream mapping:
Stream #0:0 -> #0:0 (rawvideo (native) -> prores (prores_ks))
Press [q] to stop, [?] for help
Output #0, mov, to 'F:\SDR_TO_HDR_VIDEO_CONVERTER\HDR10Plus\DoVi_Scripts_Output\temp.folder77\Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter_prores.422.mov':
Metadata:
encoder : Lavf60.21.101
Stream #0:0: Video: prores (HQ) (apch / 0x68637061), yuv422p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x2160, q=2-31, 200 kb/s, 23.98 fps, 24k tbn
Metadata:
encoder : Lavc60.40.100 prores_ks
[out#0/mov @ 0000016daec12a40] video:135937513KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.001388%
frame=164613 fps= 48 q=-0.0 Lsize=135939400KiB time=01:54:25.73 bitrate=162199.1kbits/s speed=2.02x
Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved
09/14/2024/19:44:05.616000000 CPU: INFO 13th Gen Intel(R) Core(TM) i9-13900KF (GenuineIntel) [ mmx sse sse2 sse3 ssse3 sse41 sse42 avx avx2 fma ]
09/14/2024/19:44:05.683000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:05.740000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:05.816000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:05.859000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:05.909000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:05.999000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:06.050000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:06.161000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:44:06.345000000 cm_analyze: INFO Shot cut detection is disabled when shot list is used
09/14/2024/19:44:06.346000000 cm_analyze: INFO Source: 'file:///F:/SDR_TO_HDR_VIDEO_CONVERTER/HDR10Plus/DoVi_Scripts_Output/temp.folder77/Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter_prores.422.mov'
09/14/2024/19:44:06.346000000 cm_analyze: INFO Master Display: 1000-nit, BT.2020, D65, ST.2084, Full
09/14/2024/19:44:06.346000000 cm_analyze: INFO Src Info: '3840x2160x3 u16 interleaved 422 le tight 0-164612 23.976fps top_left pq ycbcr_bt2020 video bt2020'
09/14/2024/19:44:06.347000000 cm_analyze: INFO Frames: 0 - 164612
09/14/2024/19:44:06.347000000 cm_analyze: INFO Frame rate: 24000/1001
09/14/2024/19:44:06.347000000 cm_analyze: INFO Algorithm Version: 4
09/14/2024/19:44:06.347000000 cm_analyze: INFO XML Version: 4.0.2
09/14/2024/19:44:06.376000000 analysis: INFO analyzing from 0 - 228 - dissolve=0

[...]

09/14/2024/19:44:06.818000000 cm_analyze: INFO Metadata aspect ratios: canvas 1.777778e+00, image 2.391034e+00
09/14/2024/19:44:06.838000000 cuda: INFO initializing CUDA
09/14/2024/19:44:07.000000000 cuda: INFO using CUDA version 9.2.0
09/14/2024/19:44:07.000000000 cuda: INFO NVIDIA GeForce RTX 4070 Ti: compute 8.9, cores 7680*2610MHz, memory 12281MB
Removing L2 trims.te. Last frame: 0.254 seconds. ETA: 6:44:49.606
Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved
09/14/2024/19:57:28.299000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.303000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.305000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.307000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.308000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.308000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.310000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.312000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
09/14/2024/19:57:28.367000000 metafier: ERROR unable to open file file:///F:/SDR_TO_HDR_VIDEO_CONVERTER/HDR10Plus/DoVi_Scripts_Output/temp.folder77/Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter_DV.xml (file does not exist)
Generate RPU from XML
Parsing XML metadata...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Fichier introuvable - Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter_DV.xml
Le fichier spécifié est introuvable.
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: expected value at line 21 column 35

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
convert: unable to open image 'F:\Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter_DoVi_L1_PLOT1.png': No such file or directory @ error/blob.c/OpenBlob/3569.
convert: no images defined `F:\Poltergeist_HDR-1000nits-HEVC_TEKNO3DConverter_DoVi_L1_PLOT.png' @ error/convert.c/ConvertImageCommand/3342.
========= Dolby Vision PLOT stored in the DoVi_Scripts_Output Folder =========
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Appuyez sur une touche pour continuer...
mkvmerge v76.0 ('Celebration') 64-bit

[Kuler087]

This is an old custom version of my script not made by me. You have to use the official DoVi_Scripts version (https://github.com/R3S3t9999/DoVi_Scripts) if you want me to help you.

[Atari1971]

Ok. How do we do a scene-by-scene analysis with official DoVi_Scripts version instead of frame-by-frame analysis? thanks

[Atari1971]

Donate: https://www.paypal.com/donate/?hosted_button_id=6ML5KUZG9XGB6 Date: 14/09/2024 11:42
Contact: R3S3T_9999@proton.me Version: 3.0.3.beta_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]?3

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

1) Workflow.1= CM_analyzer HDR10 to DoVi maker (can batch) (Professional CM v4.0 Dolby Algo)
2) Workflow.2= Convert HDR10plus videos to DoVi (can batch) (Not Recommended)
3) Workflow.3= Back to main menu

Choice? [1,2,3]?2

--------------------------------------------------------------------------------------------------
-- NOT RECOMMENDED: you'll get better DV if you use 3-1.
-- See: https://drive.google.com/file/d/1IXR60nWe2Ylb7CTRjZ3_tpI5RsAajU5G/view?usp=drive_link
-- This script will batch convert HDR10plus or HDR10 video to DoVi with dynamic metadata or madVR
-- Can use external L5 json if filepath/name is the same as the BL input
-- 10/100nits floor can be removed at line 169
--------------------------------------------------------------------------------------------------

Drag and drop folder with files or a single file and press enter...
D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv

Auto or Manual Active Area L5 edit... a or m ? and press enter...
a
processing..."revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
Measuring letterbox of "D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv"
left border: 0
right border: 0
top border: 278
bottom border: 278

Reading input tracks format/id/language...
Done.


====================
- DEMUXING -
====================

Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'F:\DoVi_Scripts\temp.folder34\hdr.hevc'. Container format: HEVC/H.265 elementary stream
Extracting track 1 with the CodecID 'A_DTS' to the file 'F:\DoVi_Scripts\temp.folder34\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.track_2_fre.dts'. Container format: Digital Theater System (DTS)
Progress: 100%
Measuring video file "D:\revenant_HDR-1000nits-HEVC_TEKNO3DConverter.mkv" using DXVA2 (copy-back)...
Metadata:
Mastering display luminance: 0.0001/1000, gamut: 0.708 0.292, 0.131 0.046, 0.17 0.797, 0.3127 0.329
MaxCLL: 1000, MaxFALL: 400 nits

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

Generating DoVi from a MadVR measurement file...
Reading generate config file...
Parsing madVR measurement file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: BaseThreadInitThunk
11: RtlUserThreadStart
Done.

Editing L5 (active area) to left=0, right= 0, top= 278, bottom= 278
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart

[Kuler087]

Ok. How do we do a scene-by-scene analysis with official DoVi_Scripts version instead of frame-by-frame analysis? thanks

there are two workflows( 3-1 and 3-2) to generate DV, and all default to shot-by-shot metadata. To enable frame-by-frame metadata, you would have to set line 115 to YES

:: choose if you want to force frame by frame analysis in 3-1 (default = NO)
set force.FBF=NO

[CODE]

Metadata:
Mastering display luminance: 0.0001/1000, gamut: 0.708 0.292, 0.131 0.046, 0.17 0.797, 0.3127 0.329
MaxCLL: 1000, MaxFALL: 400 nits

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


I already answered that.

[Atari1971]

Ok thank you very much :)

[AbuQutaita]

When using 8-2-1, is comparing the encode MaxFALL to the source useful? Source had 632 cd/m2 and encode has 341 cd/m2. Also, are there any situations where one should be careful about doing FEL baking when converting from DVP7 to DVP8, or will it always result in a better copy?

Thanks

[Kuler087]

When using 8-2-1, is comparing the encode MaxFALL to the source useful? Source had 632 cd/m2 and encode has 341 cd/m2.
When your input is FEL, the script takes the static metadata from the RPU and ignores the original ones. Maxfall is useless in HDR10 anyway so that doesn't matter.

Also, are there any situations where one should be careful about doing FEL baking when converting from DVP7 to DVP8, or will it always result in a better copy?

Well, FEL + BL merged restore the original 12bit Master so it should always be better but I've once seen a movie that I didn't like because FEL was raising the black levels. Watchmen Ultimate Cut IIRC.

[Kuler087]

Work in progress, a GUI for DoVi_Scripts:


https://s11.gifyu.com/images/SAnow.gif

[Gatorman3385]

Work in progress, a GUI for DoVi_Scripts:


This looks great! Willing to test if needed.

[Kuler087]

thanks, I still have some code to write before releasing but it should be available for testing soon(ish) when I release DS 3.0.3



- (2-7) Added a new workflow that can batch export the DV RPU summary info to a text file (very fast, about 5-10sec per file)
- (9-8) Added a new workflow that simply convert 12-bit PQ values to Nits or Nits values to 12-bit PQ
- (8-6) Audio waveform plot can now downmix 7.1 to 5.1 (line 187, default = NO)
- (6-2) When you opt to CROP, added an option to convert to prores instead of reading a VERY slow avisynth script. Depending on your CPU, it may be faster but require more HDD space. ( line 165 default = NO)
- (3-2) Improved HDR10plus and madVR to Dolby Vision metadata conversion. New tool needed: Thank's to doppingkoala !
- Added a timer to all the workflows.

[DMD]

Work in progress, a GUI for DoVi_Scripts:
.....
Great!!!
Can't wait to try it out
Congratulations on the time and sacrifices you are putting into this project.

[dbezerra]

@kuler087 what are the encoding options you use when baking the FEL layer? have you experienced any loss in quality due to the encoding choices? Do you always use the same one or does it vary depending on the source (digital vs lots of grain, dark movie vs lots of light, etc).

[Kuler087]

I dont encode movies and I'm no expert with the x265.exe settings. The best approach is always to use different settings based on the source type as you said.
I think the script default settings(line 199) are decent and in the comparisons I did, it looks transparent to the source but you might have to use higher CRF values for grainy content because the encode could end up larger than the source.

[Vymrr]

How do I use the scripts to check if a REMUX DV P7 mkv has FEL encoding?

Edit: Nvm, I found the answer - Workflow 1 RPU file summary

[CineManiac]

Hey Kuler, is it possible for you to confirm this HDR10+ plot is accurate?

https://i.imgur.com/mg4OTMK.png

https://i.imgur.com/KSwWnY6.png

I can send the json as well.

[Kuler087]

Interesting, first time I've seen a static HDR10plus plot. It looks correct because it only has 1 shot/scene.
It doesn't matter since the whole movie is under 100nits.

[CineManiac]

Interesting, first time I've seen a static HDR10plus plot. It looks correct because it only has 1 shot/scene.
It doesn't matter since the whole movie is under 100nits.

Okay, thanks, man. And thank you for all the hard work you do. I just made another donation :)

[Kuler087]

Thank you :)
Did i already give you have access to my RPU collection (over 1000rpus) ? I give a link to any donors.

[lemaireus]

Hi Kuler, thank you so very much for these wonderful scripts. Thanks to you, I have been able to do my first EAC3 7.1 encode from a TrueHD Atmos 7.1 track. I have three questions or, in fact, one question asked in three different ways:

1. Is there any way in which I can get DoVi_scripts to encode to 7.1 EAC3-JOC format?
2. Is there any way in which DoVi_scripts can extract Atmos metadata from a TrueHD Atmos track and inject that back into an EAC3 7.1 encode?
3. Is it possible that DoVi_scripts's EAC3 7.1 encode already includes JOC but cannot use the name of that format because of licensing issues?

Basically, I am searching for a way to encode to EAC3 7.1 with Atmos intact. Any help would be much appreciated. Thank you.

[Kuler087]

No, DS cannot encode EAC3 + the atmos metadata. But there's a way because I've seen other people doing it. The quality was much worse than DS 7.1 EAC3 .

[lemaireus]

The quality was much worse than DS 7.1 EAC3 .

Thank you for letting me know that, Kuler. There's little point in using an encoder that will produce substandard results, so I shall let go of the EAC3-JOC project for now.

Wish you all the very best with the work that you are doing on a GUI for DoVi_Scripts.

[lemaireus]

I have run into two issues:

1. Each time I encode audio with EAE in DoVi_Scripts, a second CMD window which initially flashes a sign about Dolby being a proprietary format, begins flashing this when the track is being encoded:

https://i.postimg.cc/m2BgqfQb/EAC3-Failure-Message.jpg

However, the encoded audio track I get comes out just fine. Any ideas on what I might be doing wrong?

2. Another alert that I haven't been able to figure out is this, highlighted in the blue rectangle:

https://i.postimg.cc/ydCHZcjV/EAE-Alert.jpg

[Kuler087]

it's normal, you can ignore it.

[lemaireus]

it's normal, you can ignore it.

That is reassuring. Thank you!

[CineManiac]

Thank you :)
Did i already give you have access to my RPU collection (over 1000rpus) ? I give a link to any donors.

Oh yeah I've got it, thanks :)

[sk2316]

1.sdr file with sharp picture
2.hdr10 file with worse picture
can i extract hdr10 meta and inject to sdr file?

[Kuler087]

1.sdr file with sharp picture
2.hdr10 file with worse picture
can i extract hdr10 meta and inject to sdr file?

no, you can't and even if you could, your SDR video would still be 100nits.

[Hellboy.]

1.sdr file with sharp picture
2.hdr10 file with worse picture
can i extract hdr10 meta and inject to sdr file?

Why are you asking the same question that already someone give you the answer in another thread???

https://forum.doom9.org/showthread.php?p=2007433#post2007433

[sk2316]

no, you can't and even if you could, your SDR video would still be 100nits.

your program can do that?


Why are you asking the same question that already someone give you the answer in another thread???

https://forum.doom9.org/showthread.php?p=2007433#post2007433

that is "DDVT Tool" but this is "DoVi_Scripts" management of HDR/Dolby Vision files

[Kuler087]

your program can do that?


no, not to HEVC.

[sk2316]

no, not to HEVC.

last question , your program can extract and inject hdr(not hdr10+) metadata to hevc file?

[Kuler087]

no, it cant

[sk2316]

no, it cant

thank you

[smaiderman]

Hello.
You updated dovitools since the last time I used it, and I cant find "Convert RPU to XML" option.
Im trying to convert alien HDR to SDR
Summary:
Frames: 624
Profile: 8
DM version: 2 (CM v4.0)
Scene/shot count: 3
RPU mastering display: 0.0001/1000 nits
RPU content light level (L1): MaxCLL: 149.86 nits, MaxFALL: 10.05 nits
L6 metadata: Mastering display: 0.0001/1000 nits. MaxCLL: 335 nits, MaxFALL: 122 nits
L2 trims: 100 nits, 600 nits, 1000 nits
L8 trims: 100 nits
L9 MDP: BT2020
L5 offset: TOP=N.A., BOTTOM=N.A., LEFT=N.A., RIGHT=N.A.
1st Frame is a Scene Cut: YES (good)
Consecutive Scene Cuts: NO (good)
Base Layer (HDR10+P8): "min: 0.0050 cd/m2, max: 1000 cd/m2"(BT.2020), MaxCLL: 714 nits, MaxFALL: 123 nits
Resolution/FPS: 3840 x 1606 @ 24.000

Thnaks in advance :)

[wyup]

I guess you meant 8-2-4 because 8-2-2 use libplacebo for the SDR tonemapping.

What algorithm does libplacebo library use for SDR tonemapping?
You can check some here:
https://libplacebo.org/options/
Interesting ones are bt2446a and st2094-40. These seem to accept actual and target display luminances for the OOTF adjustement. Ie: actual=MaxCLL or MaxMDL, target=100. I'm not sure if it stays in PQ or translates to BT.1886 (2.4) for either one.

It looks like st2094-10 takes HDR10+ metadata if available.

I think these algorithms, if tuned correctly might be interesting to compare to Dolby's own.

[Kuler087]

You updated dovitools since the last time I used it, and I cant find "Convert RPU to XML" option.
Workflow 1, then enter ''m''

[Kuler087]

What algorithm does libplacebo library use for SDR tonemapping?
You can check some here:
https://libplacebo.org/options/
Interesting ones are bt2446a and st2094-40. These seem to accept actual and target display luminances for the OOTF adjustement. Ie: actual=MaxCLL or MaxMDL, target=100. I'm not sure if it stays in PQ or translates to BT.1886 (2.4) for either one.

It looks like st2094-10 takes HDR10+ metadata if available.

I think these algorithms, if tuned correctly might be interesting to compare to Dolby's own.

Right now it uses the default libplacebo settings but the current dovi_scripts version is using an older version because they changed things a bit in the latest libplacebo.

If you download the latest DS beta + tools (https://drive.google.com/file/d/1S4dqemaD8snI7QW29InG_XjI6VP0PNhk/view?usp=drive_link), I've updated libplacebo and added more controls on the tone mapping. I've compared the other mode and i much prefer bt2390 + target 125nits honestly but the Resolve Dolby cmv4.0 with balanced tuning is still the best HDR to SDR tone mapping IMO.

:: choose if you want to use dynamic peak detection in 7-2 / 7-1 / 8-2-2 true or false (default= true) true or false : 'true' can be misleading if you compare two HDR sources in SDR. see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set peak_detect=true
:: choose the SDR tone mapping function for 7-2 / 7-1 / 8-2-2 (default = bt2390) choices are: "clip", "st2094-40", "st2094-10", "bt2390", "bt2446a", "spline", "reinhard", "mobius", "hable", "gamma", "linear", "linearlight" see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set tone_mapping_function=bt2390
:: choose the SDR tone mapping mode in 7-2 / 7-1 / 8-2-2 choices are: (default = perceptual") "perceptual", "softclip", "relative", "saturation", "absolute", "desaturate", "darken", "highlight", "linear" see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set gamut_mapping_mode=perceptual
:: This helps block out annoying "sparkling" or "flickering" due to small variations in frame-to-frame brightness for the SDR tone mapping mode in 7-2 / 7-1 / 8-2-2 (default=20.0) see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set smoothing_period=20.0
::Which percentile of the input image brightness histogram to consider as the true peak of the scene for the SDR tone mapping mode in 7-2 / 7-1 / 8-2-2 (default=99.995) see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set percentile=99.995
:: choose if you want to use dolby vision metadata in 7-2 / 7-1 / 8-2-2 (default = false) true or false. Profile 5 input default to true see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set use_dovi=false


@all I'm almost done debugging the new GUI and a new scripts version should be released soon :D

- (2-7) Added a new workflow that can batch export the DV RPU summary info to a text file (very fast, about 5-10sec per file)
- (9-8) Added a new workflow that simply convert 12-bit PQ values to Nits or Nits values to 12-bit PQ
- (8-6) Audio waveform plot can now downmix 7.1 to 5.1 (line 187, default = NO)
- (6-2) When you opt to CROP, added an option to convert to prores instead of reading a VERY slow avisynth script. Depending on your CPU, it may be faster but require more HDD space. ( line 165 default = NO)
- (6-2) Can now measure HDR PNG images.
- (7-1) (7-2) Can now display the frame maxcll/fall values but it makes the process two times slower and require python and opencv library: ''pip install opencv-python'' (line 143 , default =NO)
- (7-1) (7-2) (8-2-2) added more controls to the SDR tone mapping and changed the default 200nits target to 125nits. avs_libplacebo must be updated.
- (7-1) (7-2) Added an option to use custom filename(s) different than the input(s) (lines 98-99)
- (3-2) Improved HDR10plus and madVR to Dolby Vision metadata conversion. New tool needed: Thank's to doppingkoala !
- Added a timer to all the workflows.
- Added HDD output path free space check
- Introducing a GUI for DoVi_Scripts (not every workflow is supported and require python)
- Bugfix: (7-2) FEL vs FEL screenshots did not work
- Bugfix: (3-1) M2TS/TS/MP4 container input did not work

https://i.ibb.co/1McSP76/Capture-d-cran-2024-10-19-131258.png

[smaiderman]

Workflow 1, then enter ''m''

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]?1


==================================
- INJECTOR / EDITOR / EXTRACTOR -
==================================

-------------------------------------------------------------------------------------
-- This workflow inject / extract and can edit two or one input (press enter to skip the 2nd input)
-- Can batch process files: input(s) can be folder(s) with files
-- Input can be MKV/TS/M2TS/MP4/HEVC/RPU/XML/HDR10plus.json/P5/P8/P7/folder(s)
-- Can auto-Crop, Edit L5/L6/L9 and Resync DV or HDR10plus, validate metadata with metafier(XML)
-- Can use external json config for more rpu edition. json must be same filename/path. do not input as metadata
-- json input for the metadata input must be hdr10plus.
-- You can inject both DV and HDR10plus if the metadata inputs have the same path/filename as the BL.
-- For the batch injector, both folders must contain only the files to process and they must be in the same order
-------------------------------------------------------------------------------------

Drag and drop a file or a folder with files (MKV/TS/M2TS/HEVC/H265/RPU/XML/FOLDER) and press enter...
m

(OPTIONAL) Drag and drop a folder with Dynamic Metadata (RPU/XML/JSON/MKV/MP4/TS/M2TS/HEVC) and/or press enter...

[Kuler087]

https://i.ibb.co/VYdvMk1/Windows-Terminal-s-TQLly-UGqe.gif

[Gatorman3385]

@all I'm almost done debugging the new GUI and a new scripts version should be released soon :D

https://i.ibb.co/1McSP76/Capture-d-cran-2024-10-19-131258.png

:p Woohoo!

[smaiderman]

https://i.ibb.co/VYdvMk1/Windows-Terminal-s-TQLly-UGqe.gif

Thank you.

I'm trying to follow this tutorial, but I'm lost.

https://www.youtube.com/watch?v=lM56zLpKDQ8&t=5s

In the minute 2:29, when you need to import the DV xml, I get this message
The edit rate of Dolby Vision metadata
is not matched to timeline.

To get this XML, I used DoviTools "1-M"

This is the XML first lines, it says 24000 101 in the edit rate section, and my project and the file are in 24fps
<?xml version="1.0" encoding="UTF-8"?>
<DolbyLabsMDF>
<xmlns>http://www.dolby.com/schemas/dvmd/4_0_2</xmlns>
<Version>4.0.2</Version>
<RevisionHistory>
<Revision>
<DateTime>2024-10-20T00:44:34Z</DateTime>
<Author>Rainbaby</Author>
<Software>dovi_meta</Software>
<SoftwareVersion>1d32ca0</SoftwareVersion>
</Revision>
</RevisionHistory>
<Outputs>
<Output>
<CompositionName>Timeline</CompositionName>
<UniqueID>ac5018b5-c906-4937-8026-e25b9f7201a3</UniqueID>
<NumberVideoTracks>1</NumberVideoTracks>
<CanvasAspectRatio>1.7777778</CanvasAspectRatio>
<ImageAspectRatio>1.7777778</ImageAspectRatio>
<Video>
<Track>
<TrackName>V1</TrackName>
<UniqueID>db77339f-2e48-41b7-bc6d-063c492bc1e3</UniqueID>
<EditRate>24000 1001</EditRate>
<ColorEncoding>
<Primaries>
<Red>0.708 0.292</Red>
<Green>0.17 0.797</Green>
<Blue>0.131 0.046</Blue>
</Primaries>
<WhitePoint>0.3127 0.329</WhitePoint>
<PeakBrightness>10000</PeakBrightness>
<MinimumBrightness>0</MinimumBrightness>
<Encoding>pq</Encoding>
<ColorSpace>rgb</ColorSpace>
<SignalRange>computer</SignalRange>
</ColorEncoding>
<Level6 level="6">
<MaxCLL>0</MaxCLL>
<MaxFALL>0</MaxFALL>
</Level6>
<PluginNode>
<DVGlobalData level="0">
<MasteringDisplay>
<ID>21</ID>
<Name>1000-nits, BT.2020, ST.2084, Full</Name>
<Primaries>
<Red>0.708 0.292</Red>
<Green>0.17 0.797</Green>
<Blue>0.131 0.046</Blue>
</Primaries>
<WhitePoint>0.3127 0.329</WhitePoint>
<PeakBrightness>1000</PeakBrightness>
<MinimumBrightness>0.0001</MinimumBrightness>
<EOTF>pq</EOTF>
<DiagonalSize>42</DiagonalSize>
</MasteringDisplay>
<TargetDisplay>
<ID>1</ID>
<Name>100-nits, BT.709, BT.1886, Full</Name>
<Primaries>
<Red>0.64 0.33</Red>
<Green>0.3 0.6</Green>
<Blue>0.15 0.06</Blue>
</Primaries>
<WhitePoint>0.3127 0.329</WhitePoint>
<PeakBrightness>100</PeakBrightness>
<MinimumBrightness>0.005</MinimumBrightness>
<EOTF>gamma_bt1886</EOTF>
<DiagonalSize>42</DiagonalSize>
</TargetDisplay>
<TargetDisplay>
<ID>28</ID>
<Name>600-nits, BT.2020, ST.2084, Full</Name>
<Primaries>
<Red>0.708 0.292</Red>
<Green>0.17 0.797</Green>
<Blue>0.131 0.046</Blue>
</Primaries>
<WhitePoint>0.3127 0.329</WhitePoint>
<PeakBrightness>600</PeakBrightness>
<MinimumBrightness>0</MinimumBrightness>
<EOTF>pq</EOTF>
<DiagonalSize>42</DiagonalSize>
</TargetDisplay>
<TargetDisplay>
<ID>49</ID>
<Name>1000-nits, BT.2020, ST.2084, Full</Name>
<Primaries>
<Red>0.708 0.292</Red>
<Green>0.17 0.797</Green>
<Blue>0.131 0.046</Blue>
</Primaries>
<WhitePoint>0.3127 0.329</WhitePoint>
<PeakBrightness>1000</PeakBrightness>
<MinimumBrightness>0</MinimumBrightness>
<EOTF>pq</EOTF>
<DiagonalSize>42</DiagonalSize>
</TargetDisplay>
</DVGlobalData>
<Level254 level="254">
<DMMode>0</DMMode>
<DMVersion>2</DMVersion>
<CMVersion>4 1</CMVersion>
</Level254>
</PluginNode>
<Shot>
<UniqueID>04566c40-df2b-4758-acef-3715f66ecb83</UniqueID>
<Record>
<In>0</In>
<Duration>24</Duration>
</Record>
<PluginNode>
<DVDynamicData>
<Level1 level="1">
<ImageCharacter>0 0.3001221 0.5492064</ImageCharacter>
</Level1>
<Level2 level="2">
<TID>1</TID>
<Trim>0 0 0 -0.00784724 -0.13330078 0.21885157 0 0.0048828125 0</Trim>
</Level2>
<Level2 level="2">
<TID>28</TID>
<Trim>0 0 0 0 0.0068359375 0.04646516 0 0.00048828125 0</Trim>
</Level2>

[Kuler087]

yes because an rpu doesnt have a framerate and dovi_meta always assumes 23.976 so you have to edit the XML manually. Replace ''24000 1001'' with ''24 1'' or just ''24'' (I don't remember).
I'll script something to automate this in the next version.

[smaiderman]

yes because an rpu doesnt have a framerate and dovi_meta always assumes 23.976 so you have to edit the XML manually. Replace ''24000 1001'' with ''24 1'' or just ''24'' (I don't remember).
I'll script something to automate this in the next version.

Yes, I was experimenting, and when creating a timeline in Davinci, if you force it to 23.976 it works.

Thanks again

I confirm it is "24"

[wyup]

Right now it uses the default libplacebo settings but the current dovi_scripts version is using an older version because they changed things a bit in the latest libplacebo.

If you download the latest DS beta + tools (https://drive.google.com/file/d/1S4dqemaD8snI7QW29InG_XjI6VP0PNhk/view?usp=drive_link), I've updated libplacebo and added more controls on the tone mapping. I've compared the other mode and i much prefer bt2390 + target 125nits honestly but the Resolve Dolby cmv4.0 with balanced tuning is still the best HDR to SDR tone mapping IMO.
[/IMG]

I've tried 8-2-2 in latest 3.0.3 beta & tools file but it doesn't offer algorithm and target nits. Wouldn't the more modern bt2446a and 100 nits as I think mpv player uses by default? Can't find where to edit in script. 125 nits produces darker image. Do you think it preserves highlights better? Bt2446a uses input target in nits which is very appropiate to shrink dynamic range effectively. I.e: input target=1,000 nits, output target=100 nits. I see it is 1,000 nits by default.

My GPU is Intel Graphics UHD 770, which is vulkan compatible 1.3.295.
Script outputs this error constantly:
vpy [WARN]: Avisynth Compat: requested frame 0 not prefetched, using slow method
Validation failed: !params->renderable || fmt_caps & PL_FMT_CAP_RENDERABLE (../../../../../src_packages/libplacebo/src/gpu.c:234)
for texture: ../../../../../src_packages/vs-placebo/src/tonemap.c:114

Output file produces a green tint image.

Dolby Balanced may produce better results, but libplacebo bt.2446 with input and output nits would be a contender, since it's a ITU standard.

POST_EDIT: I found by chance SETTINGS rename me to use external settings.bat file which has options for bt.2446 and input/output target nits. I see it has dynamic peak detection on by default, which uses dynamic tonamapping and brightness shifts in mpv player. Best result would be reading MaxCLL or MaxDML from metadata as input and disable peak detection. Even better, it could be manually offered as options on live script run.

[Kuler087]

You sure bt2390 and 125 nits is better than more modern bt2446a and 100 nits
well, tone mapping is subjective but yes, in the test I did, I preferred bt2390 in terms of overall brightness, contrast, shadow and HL details.

input target=1,000 nits, output target=100 nits. Otherwise, which input target does it take: default PQ max 10,000 nits?
No, libplacebo default is 1000 and I did not change that.

src_max, src_min, dst_max, dst_min
Source max/min and output max/min in nits (cd/m^2).
The source values can be derived from props if available.
Default: max = 1000 (HDR)/203 (SDR); min = 0.005 (HDR)/0.2023 (SDR)

Output file produces a green tint image.
no such issue on my end

Script outputs this error constantly:
yes its because I use an avisynth plugin in vapoursynth. It,s just a warning and you can ignore. The msg disappear after about 200 frame I think.


it doesn't let me choose algorithm and target nits
you have to edit the bat file with notepad++, the tone mapping section is around line 102
But I think in 8-2,I didn't do the change yet and the tone mapping mode is hardcoded to bt2390 in the latest beta but the target nits value is working for sure. In the final stable version, you will have the same control as in 7-2.
For testing, you should use 7-2 and avspmod. It's easier to switch from one setting to another.


https://i.ibb.co/RYW6dFL/Capture-d-cran-2024-10-22-081300.png

[halls]

yes because an rpu doesnt have a framerate and dovi_meta always assumes 23.976 so you have to edit the XML manually. Replace ''24000 1001'' with ''24 1'' or just ''24'' (I don't remember).
I'll script something to automate this in the next version.

Hi!

And how can i edit/modify the fps of the hdr10+ in the metadata file?

[Kuler087]

Hi!

And how can i edit/modify the fps of the hdr10+ in the metadata file?

You don't have to, AFAIK. HDR10plus and DV metadata don't have a framerate; just a frame order, and the video stream dictates the framerate.

So as long as you sync the metadata frames correctly with the video frames, you can inject the metadata from a 24fps source to a 23.976fps video for example.

[halls]

Thank You!

[wyup]

Thanks Kuler, you are the man :-). Great professional job with your scripts.

Tweaking HDR to SDR tonemapping algos is interesting to compare with previous SDR blu-ray editions in SDR environment such as average computer monitors. I believe the better brightness gradation of HDR should come across in SDR aswell as show your libplacebo stills (in some cases better than DV clorist trims as you say).

What do you think of the regular 100-nit trims extrapolation job to tv brightness? I think colorists should do a 400-nit or 600-nit grade by default since DV tvs are already HDR400, capable at least of 400 nits. No DV tv is 100 nits, which I think already is too much tonemapping to begin with, even with extrapolation.

Aside from custom-nit DV trim outs with your script, which is awesome, it would be nice to do custom HDR to HDR tonemapping aswell, i.e: bt2446a reading metadata. Resolve has CST with PQ to PQ tonemapping I/O nit settings, but plot measurements from Resolve HDR deliver metadata and your script plot don't seem to correlate after rendering. I think for example a 400-nit to 1,000-nit tonemapping would be useful to scale up tv brightness. Usually low HDR nit content does not scale to tv capacity. Although tonemapping always change the picture to some extent as it modifies the original.

On the other hand, I don't know how HDR10+ tools in Resolve can help to deliver a tonemapping output render instead of only the .json metadata.

[Kuler087]

Great professional job with your scripts.


thank's man

What do you think of the regular 100-nit trims extrapolation job to tv brightness? I

I never tested that but assuming all the trim metadata works on the player, I think it should be the same as delivering the 100nits trim from the master. The problem is that almost all the players handle the metadata differently and some trims metadata are ignored depending on the player:
EG:
- Chroma Weight is ignored by all the cmv2.9 devices.
- Some devices ignore any positive lift (offset metadata)
- All the devices I tried ignore ms_weight
- All the devices I tried ignore the vector fields (hue and saturation secondary trims metadata)

So in the end, it is much more accurate to deliver the 100nits from the HDR source since all the metadata works this way and the tone mapping is identical to the official bluray SDR release in 95% of the case.

One other strange behavior I noticed recently with the Dolby trims is in resolve when you adjust 100nits trim of the Chroma Weight and/or the trim saturation controls, the values (not even extreme values) are not extrapolated to the 600-1000nits trims. For all the other controls, any adjustment in 100nits get extrapolated to the 600-1000trim and you can see the difference on your mastering monitor.
What is strange is when you deliver that 100nits trim with CW and Saturation metadata, (https://drive.google.com/file/d/1chqSnXo7ijixQlPmrXagpK7ohAF5YmeH/view?usp=drive_link) it has an obvious effect on my 800nits LG C2 TV. So this doesn't make much sense to me.

It's a similar story for the ms_weight control, if I make an adjustment, I see the difference on the mastering display but I don't see it in DV playback.

I think colorists should do a 400-nit or 600-nit grade by default since DV tvs are already HDR400, capable at least of 400 nits.
There's no 400 control in DV but there is a 300nits trim but I have never seen any colorist using it. I do use it sometimes in my personal projects.


No DV tv is 100 nits, which I think already is too much tonemapping to begin with, even with extrapolation.

They see the extrapolation to 600-1000 nits when they make the 100nits trim , so as long as they don't go stupid like in the movie ''the conversation'' which brighten the 600nits trim more than the master (https://slow.pics/c/cTDiL8Mn), the 100nits trim extrapolation can be very good. They can also blank the 600 and 1000nits trim which will make the 100 nits to
be ignored on any display with a target lower than 600 or 1000. (https://drive.google.com/drive/u/1/folders/1J-jBAHSgHlixq9Lkjc_p98JnvY8naE0X) This way the colorist can be very aggressive with the 100nits trim without affecting the other target.

it would be nice to do custom HDR to HDR tonemapping aswell,
the scripts or resolve can already deliver the 300-600-1000 or 2000nits trims but it is not for increasing the brightness. It always reduces the brightness from the master so if your master is 1000 nits and you deliver the 2000nits , there wont be any tone mapping and the output will be the same.
Increasing the master brightness requires grading and Dolby can only map down the brightness, not the other way around.

On the other hand, I don't know how HDR10+ tools in Resolve can help to deliver a tonemapping output render instead of only the .json metadata.
I never tried the HDR10+ tone mapping option, and there's no target so I have no idea what it does.

[Kuler087]

3.0.3 Released: https://github.com/R3S3t9999/DoVi_Scripts/releases/tag/3.0.3

[wyup]

No standalone more MKV MP4 TS .bat downloads? It's more "transparent" to see their source code, even when you need additional and updated libraries.
While downloading "tools pack" or the whole DoVi.Scripts.7z is convenient, does it override user installed python scripts and plugins, as well as MadVR, LavFilters, Avisynth, Vapoursynth? I installed all these requirements but I don't know if those in DoVi.Scripts.7z do override my system user installed ones. In such case, is it still required to manually install these tools?

[Kuler087]

There's only the full package in this release because updating the tools folder is mandatory. You already got the new tools because I shared it here before the stable release.
unless you want to use the GUI, the files you downloaded the other day should be fine and you can just download the beta version (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link)which is the same as the latest stable at the moment.

And no, you don't have to touch your python, avisynthplus, lav, madvr installation. Vapoursynth should no longer be needed, I reverted back the encoders workflow to avisynthplus.

[Lucky38]

hi Kuler,

is it something to worry about when do 7.1 eac encode?

https://imgur.com/a/e8CDXX5

[Kuler087]

no all normal

[lemaireus]

Each time I do a 7.1 encode using EAE, the resulting track has .mkv as its file extension. Is there any way I can get DoVi scripts to produce a file with the correct .eac3 file extension? It'll be convenient to not have to change the file extension manually each time.

I should add that the 7.1 encodes work wonderfully well and it's great to finally have an application that can do 7.1 encodes. Many thanks!

[Kuler087]

The ec3 file is muxed to mkv to preserve any delay in the source. You can't just change it manually to ec3, this would make a file with an invalid extension so you have to demux it(mkvextract) if you want it to have ec3 extension.
But why do you need a raw ec3 file? you can mux it with your source in mkvtoolnix directly and if there's a delay, it will be transferred to the new file.

[wyup]

Hi Kuler,
This reddit thread (https://www.reddit.com/r/jellyfin/comments/v2nudu/dolby_vision_to_sdr_hwa_tonemapping_is_coming/) has someone say:
Profile 5 DoVi content usually comes from the "WEB-DL" version of films, which doesn't contain the HDR10 base layer(BL) as a fallback.
Is it possible that a WEBDL video file doesn't have a HDR10 layer (no HEVC stream), only a self contained Dolby Vision Profile 5 RPU file with a ICtCp stream?
Or by HDR10 layer they just mean HDR10 static metadata?

Do you need to reshape this data with libplacebo to get a HDR10 or SDR conversion from a Profile 5?

[Kuler087]

right profile 5 doesnt have HDR10 support but libplacebo can tone map it to SDR (or HDR10). This libplacebo conversion is automated in DS workflow 8-2 or 7-2. EG: https://slow.pics/c/n8tkRieq

[lemaireus]

But why do you need a raw ec3 file?

I use Ripbot for x265 encoding and its audio options do not allow me to choose a track with an .mkv extension as the audio track. Of course, I can mux the 7.1 audio track with .mkv file extension with mkvtoolnix and I have been doing exactly that without any problem. Just that doing so adds one additional step to my encoding routine.

If there was an option to get the 7.1 output with .eac3 file extension, then I could get Ripbot to take that as the audio track right away, when I set up the encoding parameters.

Not a big issue, but it would help to have the option to choose an .eac3 output.

Thank you for all your splendid work.

[lemaireus]

You can't just change it manually to ec3, this would make a file with an invalid extension . . .

That is exactly what I have been doing. I change the EAE encoded 7.1 audio track's file extension from .mkv to .eac3 [not ec3]. Thereafter I show that .eac3 track as the one to mux to the .mkv/.hevc video stream to Ripbot and everything works perfectly well.

[Kuler087]

ok, when i have time I'll write something to use delayfix.exe instead of mkv to deal with potential source delay

[Black Ops]

I've got davinci resolve 19. Is h265 decoding still a problem in terms of the workflow involving generating hdr10+ metadata? I was hoping the newer version would negate the need to create a prores file before importing into davinci saving time.

[Kuler087]

I think they improved in the latest versions according to the release notes but I did not test because encoding to prores doesn't take much time on my PC and I don't want to risk dropped frames.

[Black Ops]

I think they improved in the latest versions according to the release notes but I did not test because encoding to prores doesn't take much time on my PC and I don't want to risk dropped frames.

if its not too much trouble, can you tell me how i can confirm if its improved and fully functional to the point where its not required to convert to prores anymore?

[Kuler087]

when Resolve drop frames, there will be 10 000nits spikes in your metadata plot. In my test, it dropped frames every two movies with the mkv container and about every 5 movies with the mp4 container.

[lemaireus]

ok, when i have time I'll write something to use delayfix.exe instead of mkv to deal with potential source delay

Much appreciated, thank you!

[Black Ops]

Looks like davinci doesnt like certain x265 videos and refuses to show them as importable in media manager so cant test

Im trying to find ways to speed up this pro res conversion. Looking at setting qscale to 8 or higher but not sure if its gonna affect hdr10+ metadata generated values when using davinci. Currently im just generating hdr10+ metadata and injecting it into the original so i dont need anything else.

Any problems with setting qscale to 8 and higher? What is the highest value you would go?
Any other ways to speed up this conversion besides getting a better CPU or trying a diffrent intermedite format for conversion

[Kuler087]

I think if the input has lossless audio, Resolve wont accept the mkv file.

Any problems with setting qscale to 8 and higher?
8 should be fine but I wouldn't go higher. On my end, the prores encode is running at about 4-5X depending on the source bitrate.

[Black Ops]

Yes it seems if i strip out the Audio, the file can be imported. Gonna test the h265 hdr10+ metadata and see if i get any indicators of dropped frames

Would it be a problem if i use NVENC h265 4.2.0 10 bit as my intermediate codec to import into davinci and generate hdr10+ json metadata to import back into the original? Seems to encode 4x faster than prores since its using my GPU.

[Kuler087]

<Would it be a problem if i use NVENC h265 4.2.0 10 bit as my intermediate codec to import into davinci
Well you would be converting HEVC to HEVC, no point doing that. And the GPU encode will lose grain/details which will affect resolve metadata generation.

[Black Ops]

What do you think about these plots? I've ran 4 movies and generated Hdr10+ 3 times. These movies were imported as HEVC 10bit around 6-10gb into Davinci Resolve 19.0.00069. I needed to remove the audio to import (via mkvtoolnix). Not seeing any 10,000 nit spikes at all in this version.

Bad Boys Plots
https://slow.pics/c/GUDr6Nrf

InfinityWar Plots
https://slow.pics/c/bXosUDgL

Raid Plots
https://slow.pics/c/byv4f0Rg

Riddick Plots
https://slow.pics/c/CgTUl4S0

[Kuler087]

Yes, they look fine but maybe you were just lucky.

If you have the Spears And Munsil demo clip, try it because it still drops frame with the MKV container, I just tried.
With the MP4 container, it's fine so as far as I can tell, HEVC decoding in resolve is still not reliable.

https://i.ibb.co/P4jHQcg/Capture.jpg

[Black Ops]

is it free to download? or paid?

All 4 movies were mkv's. I wonder if its system specific? I would need an exact video that is confirmed to be dodgy to really confirm. I would have thought 4 movies doing 3x runs would show any defects in HEVC decoding

[Kuler087]

I wonder if its system specific?
why would it work fine with the mp4 container then?

I would have thought 4 movies doing 3x runs would show any defects in HEVC decoding
I did a lot of movies without problems too. It's just not reliable enough for me and while MP4 is 10 times more stable, I just cannot trust it and prores is safer.

is it free to download? or paid?
check your pm

[Black Ops]

Fair point. you would expect it on both containers.

You are correct in saying that prores is safer but the extra hour added in creating the intermediate video becomes quite time consuming when doing multiple files hence why im trying to bypass it.

[wyup]

Hi. Your Trap 2024 HDR analysis shows a MaxCLL of 127 nits. This will watch dark on tvs. Have you thought of a workflow to tonemap these low nit movies to say 1,000 nits and take advantage of the display brightness? We could choose libplacebo Bt.2446.a, input MaxCLL, target 1,000 nits.

[Kuler087]

No, I won't do that because, as I said some time ago, I don't believe in automatically boosting the brightness evenly throughout the movie.
For ''proper'' result, it must be monitored and adjusted manually in grading software which is what I did with this movie:

https://i.ibb.co/1rnG6kf/Trap-2024-FDV-Do-Vi-L1-PLOT.png

[Black Ops]

Not sure if ive stumbled upon a bug in workflow 6-1 (Measuring LetterBox Manual).

If the file association isnt set for the .AVS file to AVSPmod then an error message pops up saying "this file does not have an app associated with it" mainly occurs when Windows can't find a compatible app for opening a specific file type" . Currently the AVS file association is set to avisynth+ since i installed it as part of the pre-req required for the tools

Looking at the batch file i see AvsPmod is invoked via the command like below

start "%AvsPmod_path%" "%output_path%%filename%.avs"

if i modify the line like below, it works properly

start "" "%AvsPmod_path%" "%output_path%%filename%.avs"


https://ss64.com/nt/start.html

[Kuler087]

thanks, will modify

[wyup]

No, I won't do that because, as I said some time ago, I don't believe in automatically boosting the brightness evenly throughout the movie.
For ''proper'' result, it must be monitored and adjusted manually in grading software which is what I did with this movie:

A manual regrade is always fine, but as much as I respect your opinion, if this script provides automatic workflows for HDR10 to SDR using libplacebo tonemapping, why not the inverse? In theory, evenly boosting brightness isn't as critical as compressing to SDR, as you don't have to trade up or lose anything. (similar to linear audio normalization vs loudness compression :-)

For example, rigaya hardware encoder provides (https://github.com/rigaya/QSVEnc/blob/master/QSVEncC_Options.en.md#--vpp-libplacebo-tonemapping-param1value1param2value2) libplacebo tonemapping options for any purpose.

[Kuler087]

Well, it's not the same thing. When you convert HDR to SDR, you just compress data present in the source. When you go from SDR to HDR, you create/simulate data not in the source. Maybe I'm not explaining it correctly, sorry English is my second tongue.
You might want to look into staxrip (https://forum.doom9.org/showthread.php?t=172068). There are many filters/plugins that should be able to do what you want.

If you have access to my RPU collection link, I share all my HDR re-grade project files (https://drive.google.com/file/d/1fe09lZEvDG7HudTIp-r6z67IjJQ2mpnC/view?usp=sharing) (Resolve) so you just have to load the DRP file, rip your disc and import the movie in Resolve. Once in Resolve, you can edit or preview my work and then you can deliver it.

[wyup]

Please allow me to disagree. I mean HDR to HDR, although it doesn't change much.
When you convert HDR to SDR, you just compress data present in the source.
When you convert HDR to SDR, you can't fit all HDR range in a narrower SDR range, you have to discard something, so you lose data in the source. You choose your balance from different tonemapping algorithms.
When you go from SDR to HDR, you create/simulate data not in the source.
When upping nits, you just tonemap up the same content, like turning up brightness + contrast, or peak brightness on a tv. In that sense, you create/simulate as much as in HDR to SDR conversion, but you don't lose information. None of these conversions will be the same, but it might be interesting to try turning up the brightness while keeping the original grade as intact as possible. What I think you do with low nit grades like Romulus is tweaking up highlights, which is fine, but I'd just want the same image, only proportionally brighter, because tvs don't let you increase more brightness.

I am not familiar with Staxrip, but fast reading its wiki there are HDR to SDR functions although not HDR to HDR. I can choose from all libplacebo tonemapping options with Rigaya QSVEncC.

[tormento]

Much better to go for HLG than SDR.

[ac777103]

Having run 6-2 and 3-1 on quite a few titles now, I've come across just a couple where the graph produced by 6-2 reports BT2020 in the mastering display info: The Empire Strikes Back and Inside Out 2 UK discs. So I've used the 21 option for 3-1 on these titles, just curious though what the visual significance is of BT2020 vs P3, and if I made the mistake of specifying P3 for these titles how things would change.

[Kuler087]

I've never tested if there was any visual difference but I don't think it matters that much.

[Black Ops]

Might be another bug using Windows 11 24h2. Looks like WMIC is deprecated and only available as a Feature on demand so the disk space check fails since WMIC is not present. Ive got the powershell command below which should calculate the freespace. Seems to run in command prompt (Assuming you set the letterPath variable first). Hopefully the command below should help you incoperate the free space check in the newer version of your scripts.


powershell -command "[math]::Floor((Get-WmiObject Win32_LogicalDisk -Filter "DeviceID='%letterpath%'").FreeSpace / 1GB)"

[Kuler087]

my win11 pc didnt get that update yet. I'll check it out

[Black Ops]

Is there any way to completely automate the workflow to generate hdr10+ metadata and inject it into the original. The davanci side of stuff (Scene Detect, Output blanking and generating hdr10+ metadata and export). Are there any 3rd party CLI tools that can automate this side of the workflow?

It gets quite tiresome to do this for multiple episodes of a TV show. In my case, i do this because my samsung qn90c 50 inch TV doesn't have dolby vision so HDR content is dimmed abit too much since it tonemaps the input based on MAXDML.

[Kuler087]

No, I don't think so.

[Black Ops]

I guess if I can’t automate it. Is there any way to stop the TV from tone mapping hdr10 unceccesarily and display a more 1:1 image?

[Kuler087]

With Dolby Vision content (generated or original), you can do that with LLDV and a high edid but if you have a bright TV (1000+), you need to find a cmv4.0 player because all the 2.9 players have a bug with lldv (https://docs.google.com/spreadsheets/d/1jBIGF8XTVi9VmDBZ8a5hEyongYMCDlUiLHU9n1f_S74/edit?gid=1222148710#gid=1222148710) and edid higher than 1000nits. If your TV is less than 1000nits, then the Ugoos AM6B+ is the perfect solution for any HDR10/HDR10plus display since it has a built-in edid injector and supports 12-bit FEL decoding as a bonus... Unfortunately, cmv4.0 is not supported in lldv on the ugoos but it supports everything else.

ATV and Shield support cmv4.0 LLDV but they require expensive HDfury products to force LLDV and don't support 12-bit FEL.

[lemaireus]

I made the move from 3.0.2 to 3.0.3 last week and have run into a couple of issues.

Each time I try to launch the GUI, I get an error "Windows cannot find 'pythonw' ". I rolled back my Python installation from 3.13 to 3.12.6 but that hasn't helped. I probably need to show the Python installation directory to DoVi_Scripts. How do I do that?

Also, how do I show DoVi_Scripts the path to my Dolby Encoding Engine and Dolby Vision Professional Tools installation directories?

I've copied the Python, DEE, and Dolby Vision tools folders into the 'tools' folder of DoVi_scripts, but that has not resolved the issue.

[Kuler087]

Each time I try to launch the GUI, I get an error "Windows cannot find 'pythonw' "

open a cli window and type: pip install pythonw

how do I show DoVi_Scripts the path to my Dolby Encoding Engine
path to dee is around lines 330 for the cli version
for the GUI version, its in tools\SETTINGS_GUI.bat

Dolby Vision Professional Tools installation directories

just put the exe in the tools folder without renaming it. You can also edit the path around lines: 338
for the GUI version, its in tools\SETTINGS_GUI.bat

[lemaireus]

open a cli window and type: pip install pythonw

Thank you, Kuler. The DEE issue is resolved now, and I've also added the Dolby Vision .exe files in the tools folder without renaming them.

Alas, the 'pythonw' issue remains. I and not familiar with CLI. Tried using the command prompt window to install Pythonw but failed. :(

The strange thing is that I wasn't getting the pythonw error while I was using DoVi_scripts 3.0.2.

Anyway, I'll let it rest at that for the moment. I'll stick to using DoVi_Scripts for 7.1 audio transcoding and that is working fine.

Thank you for helping out.

[Kuler087]

Strange. You could also try installing Python from the Windows Store.
The GUI should work with the default Python libraries but some workflows do require installing the libraries listed in the DS github page

[lemaireus]

Strange. You could also try installing Python from the Windows Store.

Strange indeed. I had initially installed Python from the link that you shared on the github page and I continued to get the missing 'pythonw'
message each time I tried launching the GUI.

I followed your suggestion and installed Python 3.13 from the Windows store, without uninstalling 3.12, and now everything works. DoVi_Scripts no longer flashes the missing 'pythonw' message and the GUI launches as it should. I should probably go ahead and uninstall Python 3.12 but since everything is working as it should, I am a little hesitant at the moment. :)

Anyhow, I finally have everything going. Thank you, once again!

[Kuler087]

Glad it worked. I'll add the info on the github page.
PS keep both python installations.

[lemaireus]

Uninstalled Python 3.12 and the GUI continues to launch flawlessly.

[lemaireus]

Glad it worked. I'll add the info on the github page.
PS keep both python installations.

Had uninstalled by the time a page refresh brought your message to my notice. No problem thus far, though. The GUI works with Python 3.13 installed from the Windows store.

[Kuler087]

all good then. If you notice that other workflows are not working, just re-install it. I think the heatmap and gamut workflow(7-3) requires it.

[lemaireus]

all good then. If you notice that other workflows are not working, just re-install it. I think the heatmap and gamut workflow(7-3) requires it.

Sure, will do. Thank you!

[ac777103]

I've been using auto L5 without issue for many titles processed via 3-1. My rip of Bladerunner Final Cut gives crazy values though. Is there a recommended way around this?

[Kuler087]

yeah ''auto-L5 '' is never ideal and can sometimes output crazy values. It's always better / more accurate to measure the letterbox manually.

FYI, the correct L5 values for this movie is: 0,0,280,280

https://i.ibb.co/F8XHYsZ/Capture-d-cran-2024-11-14-144658.png

[ac777103]

many thanks.

[ac777103]

forgot to ask, which program do you use for measuring the letterbox manually?

[Kuler087]

avspmod, workflow 6-1

[ac777103]

I've used 6-2 without problem on around 60 UHD disc rips now, but have encountered a problem with Pacific Rim (UK release). It gets very close to the end and then there is an error about an incomplete file having been produced, and it crashes out. I thought there might be an issue with the rip so re-ripped with latest makemkv 1.17.8, and got the same error. Any ideas? There is nothing changing in the set up or file location, this one title persistently fails. I suppose a third party RPU could be injected, but puzzled as to what is happening here.

[Kuler087]

Yes, some rips might fail to be measured with madvr. It usually happens with TS/M2TS input but I've seen it too with some MKV rip on rare occasions and I don't think there's anything we can do about it. As a workaround, you can crop and enable prores around line 182: set crop.prores62=YES
My US mkv rip works fine for this movie though.

https://i.ibb.co/s23qsT1/Pacific-Rim-2013-BD-HDR-plot.png

[ac777103]

thanks, so could it be worth me ripping to a full disc backup, and then trying 6-2 using the TS bat file?

[Kuler087]

Yes, you could try the original M2TS.

The TS/MP4 or MKV bat files are all the same scripts. The .bat filename just determines the preferred container for muxing. It's not a script issue anyway.

[Atari1971]

processing..."Pirates of the Caribbean.mkv"

Reading input tracks format/id/language...
Done.


====================
- DEMUXING -
====================

Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'E:\temp.folder92\hdr.hevc'. Container format: HEVC/H.265 elementary stream
Extracting track 1 with the CodecID 'A_TRUEHD' to the file 'E:\temp.folder92\Pirates of the Caribbean.track_2_eng.thd'. Container format: TrueHD
Extracting track 2 with the CodecID 'A_EAC3' to the file 'E:\temp.folder92\Pirates of the Caribbean.track_3_fre.ac3'. Container format: Dolby Digital Plus (E-AC-3)
Extracting track 3 with the CodecID 'S_HDMV/PGS' to the file 'E:\temp.folder92\Pirates of the Caribbean.track_4_fre.sup'. Container format: SUP
Extracting track 4 with the CodecID 'S_HDMV/PGS' to the file 'E:\temp.folder92\Pirates of the Caribbean.track_5_fre.sup'. Container format: SUP
Progress: 0%
Progress: 1%
Progress: 2%
Progress: 3%
Progress: 4%
Progress: 5%
Progress: 6%
Progress: 7%
Progress: 8%
Progress: 9%
Progress: 10%
Progress: 11%
Progress: 12%
Progress: 13%
Progress: 14%
Progress: 15%
Progress: 16%
Progress: 17%
Progress: 18%
Progress: 19%
Progress: 20%
Progress: 21%
Progress: 22%
Progress: 23%
Progress: 24%
Progress: 25%
Progress: 26%
Progress: 27%
Progress: 28%
Progress: 29%
Progress: 30%
Progress: 31%
Progress: 32%
Progress: 33%
Progress: 34%
Progress: 35%
Progress: 36%
Progress: 37%
Progress: 38%
Progress: 39%
Progress: 40%
Progress: 41%
Progress: 42%
Progress: 43%
Progress: 44%
Progress: 45%
Progress: 46%
Progress: 47%
Progress: 48%
Progress: 49%
Progress: 50%
Progress: 51%
Progress: 52%
Progress: 53%
Progress: 54%
Progress: 55%
Progress: 56%
Progress: 57%
Progress: 58%
Progress: 59%
Progress: 60%
Progress: 61%
Progress: 62%
Progress: 63%
Progress: 64%
Progress: 65%
Progress: 66%
Progress: 67%
Progress: 68%
Progress: 69%
Progress: 70%
Progress: 71%
Progress: 72%
Progress: 73%
Progress: 74%
Progress: 75%
Progress: 76%
Progress: 77%
Progress: 78%
Progress: 79%
Progress: 80%
Progress: 81%
Progress: 82%
Progress: 83%
Progress: 84%
Progress: 85%
Progress: 86%
Progress: 87%
Progress: 88%
Progress: 89%
Progress: 90%
Progress: 91%
Progress: 92%
Progress: 93%
Progress: 94%
Progress: 95%
Progress: 96%
Progress: 97%
Progress: 98%
Progress: 99%
Progress: 100%
Could not retrieve IMeasureHDR interface.

Generating DoVi from a MadVR measurement file...
Reading generate config file...
Parsing madVR measurement file...
Error: Le fichier spécifié est introuvable. (os error 2)
Done.

Stack backtrace:
0: std::backtrace::Backtrace::create
1: std::backtrace::Backtrace::capture
2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from

3: madvr_parse::MadVRMeasurements::parse_file
4: dovi_tool::dovi::generator::Generator::generate
5: dovi_tool::main
6: std::sys_common::backtrace::__rust_begin_short_backtrace
7: std::rt::lang_start::{{closure}}
8: std::rt::lang_start_internal
9: main
10: __tmainCRTStartup
11: mainCRTStartup
12: <unknown>
13: <unknown>
Editing L5 (active area) to left=0, right= 0, top= 262, bottom= 262
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
Appuyez sur une touche pour continuer...
0: std::backtrace::Backtrace::create
Done.
1: std::backtrace::Backtrace::capture

2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
3: dolby_vision::rpu::utils::parse_rpu_file
4: dovi_tool::dovi::editor::Editor::edit
5: dovi_tool::main
6: std::sys_common::backtrace::__rust_begin_short_backtrace
7: std::rt::lang_start::{{closure}}
8: std::rt::lang_start_internal
9: main
10: __tmainCRTStartup
11: mainCRTStartup
12: <unknown>
13: <unknown>
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Editing L6 to MDL= 50/50, MaxCLL/FALL= 0/0
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
Appuyez sur une touche pour continuer...
0: std::backtrace::Backtrace::create
Done.
1: std::backtrace::Backtrace::capture

2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from

3: dolby_vision::rpu::utils::parse_rpu_file
4: dovi_tool::dovi::editor::Editor::edit
5: dovi_tool::main
6: std::sys_common::backtrace::__rust_begin_short_backtrace
7: std::rt::lang_start::{{closure}}
8: std::rt::lang_start_internal
9: main
10: __tmainCRTStartup
11: mainCRTStartup
12: <unknown>
================
13: <unknown>
- INJECTING DV -
================

Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
Appuyez sur une touche pour continuer...
0: std::backtrace::Backtrace::create
1: std::backtrace::Backtrace::capture
2: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
3: dolby_vision::rpu::utils::parse_rpu_file
4: dovi_tool::dovi::rpu_injector::RpuInjector::inject_rpu
5: dovi_tool::main
6: std::sys_common::backtrace::__rust_begin_short_backtrace
7: std::rt::lang_start::{{closure}}
8: std::rt::lang_start_internal
9: main
10: __tmainCRTStartup
11: mainCRTStartup
12: <unknown>
13: <unknown>

=================
- MUXING TO MKV -
=================

mkvmerge v88.0 ('All I Know') 64-bit
Error: The type of file 'E:\Pirates of the Caribbean_DV.hevc' could not be recognized.
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
Parsing RPU file...
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
Parsing RPU file...
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder92\full.json
Le fichier sp‚cifi‚ est introuvable.
Le fichier sp‚cifi‚ est introuvable.
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

L5 Left offset: 0
Stack backtrace:
L5 Right offset: 0
0: <unknown>
L5 Top offset: 262
1: <unknown>
L5 Bottom offset: 262
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
1st Frame is a Scene Cut: NO
12: RtlUserThreadStart
Consecutive Scene Cuts: NO (good)
Deleting TEMP folder...

Start time: 21:34:47,31
End time: 21:47:48,72
Time taken: 0:13:01

"The script has been completed..."

Process finished.

Good evening. I always have these errors, whether in madvr DV encoding or original DV encoding. This code is from Dovi_Script GUI V1.0.0 BETA, but same code with DoVi_Scripts_MKV...:angry:

[Kuler087]

Looks like you did not install madvr or you're using an old non-beta version.
I believe madmeasureHDR.exe works only with the beta builds so go to the tools/madvr folder and click with admin rights on the install bat.

Also, make sure that you have installed lavfilters.

[Atari1971]

THANKS. It works with madvr, but original dolby encoding does not work. I installed all the apps, as well as "Dolby_Vision_Professional_Tools_v5.5.0"...

[Kuler087]

you have to put the .exe in the tools folder without renaming them.

[Atari1971]

I put all the .exe from the dolby folder into the tools folder. It doesn't work

[Kuler087]

show me the logs, it sure works.

https://i.ibb.co/fFqbYdC/Windows-Terminal-6o-Tm0-Kcmej.gif

https://i.ibb.co/H2cDHR0/pythonw-OVInlts-HNS.gif

[Atari1971]

Processing: "Pirates of the Caribbean - Dead Man's Chest.mkv"

Reading input tracks format/id/language...
Done.
Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'E:\temp.folder77\BL.hevc'. Container format: HEVC/H.265 elementary stream
Progress: 0%
Progress: 1%
Progress: 2%
Progress: 3%
Progress: 4%
Progress: 5%
Progress: 6%
Progress: 7%
Progress: 8%
Progress: 9%
Progress: 10%
Progress: 11%
Progress: 12%
Progress: 13%
Progress: 14%
Progress: 15%
Progress: 16%
Progress: 17%
Progress: 18%
Progress: 19%
Progress: 20%
Progress: 21%
Progress: 22%
Progress: 23%
Progress: 24%
Progress: 25%
Progress: 26%
Progress: 27%
Progress: 28%
Progress: 29%
Progress: 30%
Progress: 31%
Progress: 32%
Progress: 33%
Progress: 34%
Progress: 35%
Progress: 36%
Progress: 37%
Progress: 38%
Progress: 39%
Progress: 40%
Progress: 41%
Progress: 42%
Progress: 43%
Progress: 44%
Progress: 45%
Progress: 46%
Progress: 47%
Progress: 48%
Progress: 49%
Progress: 50%
Progress: 51%
Progress: 52%
Progress: 53%
Progress: 54%
Progress: 55%
Progress: 56%
Progress: 57%
Progress: 58%
Progress: 59%
Progress: 60%
Progress: 61%
Progress: 62%
Progress: 63%
Progress: 64%
Progress: 65%
Progress: 66%
Progress: 67%
Progress: 68%
Progress: 69%
Progress: 70%
Progress: 71%
Progress: 72%
Progress: 73%
Progress: 74%
Progress: 75%
Progress: 76%
Progress: 77%
Progress: 78%
Progress: 79%
Progress: 80%
Progress: 81%
Progress: 82%
Progress: 83%
Progress: 84%
Progress: 85%
Progress: 86%
Progress: 87%
Progress: 88%
Progress: 89%
Progress: 90%
Progress: 91%
Progress: 92%
Progress: 93%
Progress: 94%
Progress: 95%
Progress: 96%
Progress: 97%
Progress: 98%
Progress: 99%
Progress: 100%
Measuring video file "E:\Pirates of the Caribbean - Dead Man's Chest.mkv" using D3D11 (native)...
0%1%2%3%4%5%6%7%8%9%10%11%12%13%14%15%16%17%18%19%20%21%22%23%24%25%26%27%28%29%30%31%32%33%34%35%36%37%38%39%40%41%42%43%44%45%46%47%48%49%50%51%52%53%54%55%56%57%58%59%60%61%62%63%64%65%66%67%68%69%70%71%72%73%74%75%76%77%78%79%80%81%82%83%84%85%86%87%88%89%90%91%92%93%94%95%96%97%98%99%100%Metadata:
Mastering display luminance: 0.005/4000, gamut: 0.68 0.32, 0.15 0.06, 0.265 0.69, 0.3127 0.329
MaxCLL: 0, MaxFALL: 0 nits
Measurements:
Frames: 216724, MaxCLL 100%: 451, 99.9%: 369, MaxFALL: 175, AvgFALL: 12, AvgFMLL: 106 nits
Reading generate config file...
Parsing madVR measurement file...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 216724 frames
Done.
1 fichier(s) d‚plac‚(s).
Parsing RPU file...
Exporting scenes list...
Done.
Indexing, please wait... 0%
Indexing, please wait... 1%
Indexing, please wait... 2%
Indexing, please wait... 3%
Indexing, please wait... 4%
Indexing, please wait... 5%
Indexing, please wait... 6%
Indexing, please wait... 7%
Indexing, please wait... 8%
Indexing, please wait... 9%
Indexing, please wait... 10%
Indexing, please wait... 11%
Indexing, please wait... 12%
Indexing, please wait... 13%
Indexing, please wait... 14%
Indexing, please wait... 15%
Indexing, please wait... 16%
Indexing, please wait... 17%
Indexing, please wait... 18%
Indexing, please wait... 19%
Indexing, please wait... 20%
Indexing, please wait... 21%
Indexing, please wait... 22%
Indexing, please wait... 23%
Indexing, please wait... 24%
Indexing, please wait... 25%
Indexing, please wait... 26%
Indexing, please wait... 27%
Indexing, please wait... 28%
Indexing, please wait... 29%
Indexing, please wait... 30%
Indexing, please wait... 31%
Indexing, please wait... 32%
Indexing, please wait... 33%
Indexing, please wait... 34%
Indexing, please wait... 35%
Indexing, please wait... 36%
Indexing, please wait... 37%
Indexing, please wait... 38%
Indexing, please wait... 39%
Indexing, please wait... 40%
Indexing, please wait... 41%
Indexing, please wait... 42%
Indexing, please wait... 43%
Indexing, please wait... 44%
Indexing, please wait... 45%
Indexing, please wait... 46%
Indexing, please wait... 47%
Indexing, please wait... 48%
Indexing, please wait... 49%
Indexing, please wait... 50%
Indexing, please wait... 51%
Indexing, please wait... 52%
Indexing, please wait... 53%
Indexing, please wait... 54%
Indexing, please wait... 55%
Indexing, please wait... 56%
Indexing, please wait... 57%
Indexing, please wait... 58%
Indexing, please wait... 59%
Indexing, please wait... 60%
Indexing, please wait... 61%
Indexing, please wait... 62%
Indexing, please wait... 63%
Indexing, please wait... 64%
Indexing, please wait... 65%
Indexing, please wait... 66%
Indexing, please wait... 67%
Indexing, please wait... 68%
Indexing, please wait... 69%
Indexing, please wait... 70%
Indexing, please wait... 71%
Indexing, please wait... 72%
Indexing, please wait... 73%
Indexing, please wait... 74%
Indexing, please wait... 75%
Indexing, please wait... 76%
Indexing, please wait... 77%
Indexing, please wait... 78%
Indexing, please wait... 79%
Indexing, please wait... 80%
Indexing, please wait... 81%
Indexing, please wait... 82%
Indexing, please wait... 83%
Indexing, please wait... 84%
Indexing, please wait... 85%
Indexing, please wait... 86%
Indexing, please wait... 87%
Indexing, please wait... 88%
Indexing, please wait... 89%
Indexing, please wait... 90%
Indexing, please wait... 91%
Indexing, please wait... 92%
Indexing, please wait... 93%
Indexing, please wait... 94%
Indexing, please wait... 95%
Indexing, please wait... 96%
Indexing, please wait... 97%
Indexing, please wait... 98%
Indexing, please wait... 99%
Indexing, please wait... 100%

Writing index... done.
Encoding to prores, you need at least 300gb of free HDD space...
[in#0 @ 0000028ae7f3c680] Error opening input: Unknown error occurred
Error opening input file E:\temp.folder77\script.avs.
Error opening input files: Unknown error occurred
Generating Dolby Vision with CM_Analyze...
Copyright (c) 2013-2024 Dolby Laboratories, Inc. All Rights Reserved
11/19/2024/13:50:39.521000000 CPU: 13th Gen Intel(R) Core(TM) i9-13900KF (GenuineIntel) [ mmx sse sse2 sse3 ssse3 sse41 sse42 avx avx2 fma ]
11/19/2024/13:50:39.546000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.597000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.652000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.666000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.689000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.724000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.743000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.798000000 plugin_manager: WARNING plugin does not contain dlb_plugin_file_io_init_v1
11/19/2024/13:50:39.799000000 cm_analyze: ERROR Unable Open Sequence 'file:///E:/temp.folder77/Pirates of the Caribbean - Dead Man's Chest_prores.422.mov'. Check file permissions are/or existence
Parsing XML metadata...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Fichier introuvable - Pirates of the Caribbean - Dead Man's Chest_DV.xml
Le fichier sp‚cifi‚ est introuvable.
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Reading generate config file...
Error: invalid type: null, expected usize at line 3 column 18

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: BaseThreadInitThunk
11: RtlUserThreadStart
Error: expected value at line 21 column 36

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
Parsing RPU file...
6: <unknown>
7: <unknown>
Appuyez sur une touche pour continuer...
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)


Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
=================
- MUXING TO MKV -
=================

mkvmerge v88.0 ('All I Know') 64-bit
Error: The type of file 'E:\Pirates of the Caribbean - Dead Man's Chest_Generated.hevc' could not be recognized.
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
Parsing RPU file...
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
Le fichier sp‚cifi‚ est introuvable.
Le fichier sp‚cifi‚ est introuvable.
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
L5 Left offset: 0
0: <unknown>
L5 Right offset: 0
1: <unknown>
L5 Top offset: 280
2: <unknown>
L5 Bottom offset: 280
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
1st Frame is a Scene Cut: NO
Consecutive Scene Cuts: NO (good)
Deleting TEMP folder...

Start time: 13:15:06,25
End time: 13:50:40,95
Time taken: 0:35:34

"The script has been completed..."

Process finished.

[Kuler087]

it looks like you did not install avisynth plus.. please read the installation instructions or watch the installation video tutorial.

[Atari1971]

I watched the tutorial and installed all the requested apps

[Kuler087]

well the error your getting is because of your avisynthplus installation. It's on your end so I cant help you more.

[Atari1971]

THANKS. I actually reinstalled avisynth+. It seems to work. To encode with the Dolby encoder, you have to click the Generate CM button?

[Kuler087]

Yes CM = Dolby CM_Analyze.exe

[Atari1971]

thanks :)

[Atari1971]

Frame 0 complete
Frame 1 complete. Last frame: 0.054 seconds. ETA: 3:16:43.113
Frame 2 complete. Last frame: 0.232 seconds. ETA: 8:37:30.592
Frame 3 complete. Last frame: 0.136 seconds. ETA: 8:29:20.554
Frame 4 complete. Last frame: 0.188 seconds. ETA: 9:12:17.147
Frame 5 complete. Last frame: 0.174 seconds. ETA: 9:27:52.533
Frame 6 complete. Last frame: 0.187 seconds. ETA: 9:45:52.725
Frame 7 complete. Last frame: 0.182 seconds. ETA: 9:56:07.458
Frame 8 complete. Last frame: 0.202 seconds. ETA: 10:13:10.378
Frame 9 complete. Last frame: 0.191 seconds. ETA: 10:21:46.953
Frame 10 complete. Last frame: 0.202 seconds. ETA: 10:32:54.900
Frame 11 complete. Last frame: 0.132 seconds. ETA: 10:18:58.743
Frame 12 complete. Last frame: 0.227 seconds. ETA: 10:36:00.838
Frame 13 complete. Last frame: 0.127 seconds. ETA: 10:22:30.135
Frame 14 complete. Last frame: 0.220 seconds. ETA: 10:34:56.544
Frame 15 complete. Last frame: 0.181 seconds. ETA: 10:36:21.652
Frame 16 complete. Last frame: 0.166 seconds. ETA: 10:34:07.925
Frame 17 complete. Last frame: 0.133 seconds. ETA: 10:25:14.715
Frame 18 complete. Last frame: 0.224 seconds. ETA: 10:35:36.961
Frame 19 complete. Last frame: 0.251 seconds. ETA: 10:50:02.089
Frame 20 complete. Last frame: 0.054 seconds. ETA: 10:27:21.126
Frame 21 complete. Last frame: 0.185 seconds. ETA: 10:29:22.253
Frame 22 complete. Last frame: 0.186 seconds. ETA: 10:31:24.476
Frame 23 complete. Last frame: 0.163 seconds. ETA: 10:29:37.631
Frame 24 complete. Last frame: 0.279 seconds. ETA: 10:45:28.364
Frame 25 complete. Last frame: 0.063 seconds. ETA: 10:28:52.183
Frame 26 complete. Last frame: 0.174 seconds. ETA: 10:28:53.281
Frame 27 complete. Last frame: 0.192 seconds. ETA: 10:31:17.690
Frame 28 complete. Last frame: 0.176 seconds. ETA: 10:31:28.664
Frame 29 complete. Last frame: 0.172 seconds. ETA: 10:31:10.564
Frame 30 complete. Last frame: 0.205 seconds. ETA: 10:34:49.443
Frame 31 complete. Last frame: 0.141 seconds. ETA: 10:30:52.869
Frame 32 complete. Last frame: 0.221 seconds. ETA: 10:36:10.079
Frame 33 complete. Last frame: 0.137 seconds. ETA: 10:31:56.028
Frame 34 complete. Last frame: 0.232 seconds. ETA: 10:38:03.707
Frame 35 complete. Last frame: 0.130 seconds. ETA: 10:33:15.788
Frame 36 complete. Last frame: 0.221 seconds. ETA: 10:37:50.565
Frame 37 complete. Last frame: 0.177 seconds. ETA: 10:37:58.196
Parsing XML metadata...
Frame 38 complete. Last frame: 0.129 seconds. ETA: 10:33:31.914
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Fichier introuvable - Pirates of the Caribbean - Dead Man's Chest_DV.xml
Le fichier sp‚cifi‚ est introuvable.
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Reading generate config file...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 216724 frames
Done.
Error: expected value at line 21 column 36

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
Appuyez sur une touche pour continuer...
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart

=================
- MUXING TO MKV -
=================

mkvmerge v88.0 ('All I Know') 64-bit
Error: The type of file 'E:\Pirates of the Caribbean - Dead Man's Chest_Generated.hevc' could not be recognized.
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
Parsing RPU file...
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
Parsing RPU file...
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
Error: Le fichier spécifié est introuvable. (os error 2)

Stack backtrace:
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
FINDSTR*: Impossible d’ouvrir E:\temp.folder77\full.json
Le fichier sp‚cifi‚ est introuvable.
Le fichier sp‚cifi‚ est introuvable.
Parsing RPU file...
Error: Le fichier spécifié est introuvable. (os error 2)
L5 Left offset: 0

L5 Right offset: 0
Stack backtrace:
L5 Top offset: 280
0: <unknown>
L5 Bottom offset: 280
1: <unknown>
2: <unknown>
3: <unknown>
1st Frame is a Scene Cut: NO
4: <unknown>
5: <unknown>
Consecutive Scene Cuts: NO (good)
6: <unknown>
Deleting TEMP folder...
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: BaseThreadInitThunk
12: RtlUserThreadStart

Start time: 14:17:20,82
End time: 16:04:10,77
Time taken: 1:46:50

"The script has been completed..."

Process finished.



I'm sorry, but I have a new error...

[Kuler087]

no idea but it's on your end. Your input is only 38 frames?

[Atari1971]

No, 216686 frames

[Kuler087]

then it sounds like cm_analyze crashed. I have this issue too but only on my Windows 11 PC, so there's nothing we can do about it since it seems CM just doesn't like win11.
It crashes after about 15 000frames on my end. You could open a ticket on the Dolby forum.

[Atari1971]

Ah OK :). What is the difference between MadVR and Dolby encoding?

[Kuler087]

Dolby is the official way to generate the metadata. Madvr generates the metadata the same way but it calculates the average brightness quite differently and can introduce brightness instability between shots.

As a workaround to CM, you can use Resolve (https://www.youtube.com/watch?v=FVSh3oGqfXY).

[Atari1971]

All right. Is there a tutorial for using an HDR10 file in Resolve and exporting the Dolby XML file?

[Kuler087]

yes click on the link i just gave you

[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)

[en6ads]

Shield has color issues with P8 P7 DV. you should encode to P5 with 8-2-6 (support FEL baking too)

I don't own a shield, I was being facetious ;). I do own the latest gen apple tv, a zidoo Z9X PRO (not my favorite), and Ugoos AMB6+.

Based on your testing, youtube videos, I see the ATV has some color issues with DV. Shame, I would have used that with baked FEL as it's the one I use for streaming content. Watching color accurate baked FEL on apple TV would be awesome - and would allow me to manage one less box to maintain.

[Kuler087]

Yeah but the ATV is much better than the Shield and also 10 times more stable. The Shield drop or dup at least 1 or 2 frames per hour(tested many times with a capture card).
But there is definitely something going on with the ATV DV colors too, if you look at the Spears and Munsil colorspace pattern, only the X800m2/X700/Oppo and the Ugoos are perfect. I don't know about the zidoo but it's not an option since this device can't do True TV-LED.
colorspace pattern comparison: https://slow.pics/c/NBQVuXQw (my C2 internal player also looks wrong)

Ugoos + CE is simply the best device if you want it all and the latest update seems to have fixed the OOS audio when you seek or FF.

[en6ads]

Yeah but the ATV is much better than the Shield and also 10 times more stable. The Shield drop or dup at least 1 or 2 frames per hour(tested many times with a capture card).
But there is definitely something going on with the ATV DV colors too, if you look at the Spears and Munsil colorspace pattern, only the X800m2/X700/Oppo and the Ugoos are perfect. I don't know about the zidoo but it's not an option since this device can't do True TV-LED.
colorspace pattern comparison: https://slow.pics/c/NBQVuXQw (my C2 internal player also looks wrong)

Ugoos + CE is simply the best device if you want it all and the latest update seems to have fixed the OOS audio when you seek or FF.

Maybe a Amlogic S928X-J device such as Ugoos AM8 PRO might be worth testing as truely a 1 box solution [for streaming and local color correct baked FEL DV playback; if 3D is not needed].

Would love a simple docker, or PC script that auto rips disk with chosen language and options, auto bakes FEL into an 8.1 file. That is probably the end goal.

[Kuler087]

newer DV SOCs do not allow profile 7 decoding.
only these devices can work with FEL: https://discourse.coreelec.org/t/ce-ng-dolby-vision-fel-for-dv-licensed-socs-s905x2-s922x-z-s905x4/50953

[en6ads]

newer DV SOCs do not allow profile 7 decoding.
only these devices can work with FEL: https://discourse.coreelec.org/t/ce-ng-dolby-vision-fel-for-dv-licensed-socs-s905x2-s922x-z-s905x4/50953

Yes, that's why I use an Ugoos AMB6+ for local file playback, and an Apple TV for streaming playback.

However, If I bake FEL using workflow 8-2-1 or 8-2-6, then FEL playback requirement using the Ugoos is no longer necessary.

So is there a one TX box that: 1) can play all the streaming services at highest 4k quality, is Netflix/Disney/Prime etc 4k certified; 2) can play baked-FEL local files with correct color (which ATV and Shield can't do)?

Baking FEL takes many hours, but run on a home server overnight is not a problem.

If I can get my setup down to just 1 box would be ideal.

[Kuler087]

Yes, the firecube 2nd gen. IIRC you can install in dual-boot the coreelec build.

There's a user on avsforum that uses it, ask him: https://www.avsforum.com/posts/63702599/

[benwaggoner]

newer DV SOCs do not allow profile 7 decoding.
only these devices can work with FEL: https://discourse.coreelec.org/t/ce-ng-dolby-vision-fel-for-dv-licensed-socs-s905x2-s922x-z-s905x4/50953
Are there any scenarios that use Profile 7? I don't think I have ever seen one in the wild.

[Kuler087]

Yeah, on paper, profile 7 should be only for bluray players and bluray discs so it makes sense for Dolby to offer only Profile 5 & 8 compatible SOC for the streaming boxes.
The older 2018-2019 SOCs support P7 (LG C8/C9 internal player + all the devices listed in the discourse/coreelec link) but I guess they didn't expect that people would be able to reverse-engineer the format and allow lossless MKV single-track dual-layer Profile 7 rip compatible with these media players.

[Korbus]

Hello everyone! First, let me just say thanks to @R3S3t9999 for this great tool!
I also have a quick question, since even after searching the thread I could not find the answer. For my own quirky reasons and lack of HDD space, I prefer to rip my UHD's to 1080p files, with a fixed bitrate, using the 2-pass process, in order to better alocate the bitrate depending on the needs. I do not like the CRF encoding, since neither the avg. bitrate, nor file size are predictable. Hence, my question:
How do I modify the Encoders section of the .bat file to do the 2-pass encoding (full 1st-pass) with a fixed value for avg. bitrate (meaning what command line argument should I use - I am a perfect newbie in command line, so far I have used RipBot to do my encodes)? I prefer X265 encodes, not nVidia ones (which are, by default, 2-pass, I guess).
Thanks in advance for any help!

[Kuler087]

I would have to add 2-pass support, right now it only supports CRF or 1-pass bitrate. I can have a look later

[Korbus]

Thank you for the answer, that clears it. I thought I was doing something wrong.

[Black Ops]

Ordered the firecube 2nd gen and looking forward towards running corelec on it.

Ive just realised that windows seems to not report the proper max luminance of the panel via the edid and thus defaults to a peak brightness of 1499. Whats the best way to determine peak luminance for appropriately setting LLDV edid.

[Kuler087]

which TV/monitor? you could look at the measurements on rtings

https://www.rtings.com/

[Black Ops]

Yes its the qn90c 50 inch. The measurements were taken with a 55 inch model. Samsung states that 55 inch and above utilise "Neo quantum HDR+" panel which is "double the peak brightness". They reported 2000 ish nits

I have set the qn90c to HGIG mode previously and ran thru the XBOX HDR calibration and it seems the image clips at 1100 nits. Weather this brightness translates whilst the TV is not in game mode is a mystery to me.

[Kuler087]

You can try this app. On my Samsung monitor it reports 400nits which is the same as the edid extracted with hdfury vertex
https://apps.microsoft.com/detail/9pgn3nwpbwl9?hl=en-US&gl=US

otherwise, the cheaper way would be to export the edid with a Raspberry Pi and Pi Generator.


You can also try these patterns via USB and see when it clips but it might not be a proper way since the TV does static tone mapping so I don't know.
https://drive.google.com/drive/u/1/folders/1EJm_GAiNEXsaleXGmQenxzRiSeEAg72W
https://drive.google.com/drive/u/1/folders/1jE0WBNaF9JlgxeQsa7-_axh0zRiGA8pC

[Black Ops]

The app also has 1499 but when running the HDR calibration Store app, it updates accordingly so i dont think its pulling direct from EDID. The patterns cut off at 1500.

Looks like custom resolution utility can export the EDID. No mention of peak luminance tho for HDR

https://pastebin.com/49yx9Rvr

I suspect 1000 nits is indeed the peak. HGIG effectively disables any tonemapping and tells the TV to effectively hard clip at peak brightness of the display. Looking at Rtings, the values for game mode didnt really change

[Kuler087]

With the cpm's coreelec build you can select different edid anyway so you'll be able to tell if the patterns are clipped or not with a 1500nits edid.

[Black Ops]

Is this the luminance? I had a skim through the edid again and spotted this. So 800 nits?

Maximum luminance: 128 (800.000 cd/m^2)
Minimum luminance: 1 (0.000 cd/m^2)
Maximum luminance (without local dimming): 107 (507.620 cd/m^2)
Minimum luminance (without local dimming): 15 (0.018 cd/m^2)
Checksum: 0xff

[Kuler087]

yep, looks like it.

[Black Ops]

Looks like i have rtings to thanks since they stated that the 50 inch panel only differs in terms of higher refresh rate and it being a VA panel failing to mention that the peak brightness is effectively half of the 55 inch+

[Korbus]

I would have to add 2-pass support, right now it only supports CRF or 1-pass bitrate. I can have a look later

Thank you so much for adding two-pass bitrate encoding! Now time to rip those pesky P7 FEL UHD's :)!

[lemaireus]

If a blu-ray has six lossless audio tracks, and I wish to use DoVi_Scripts (workflow 8-1-1) to encode, for example, the fourth audio track. How do I get DoVi_Scripts to encode track 4 while excluding the others?

[Kuler087]

If a blu-ray has six lossless audio tracks, and I wish to use DoVi_Scripts (workflow 8-1-1) to encode, for example, the fourth audio track. How do I get DoVi_Scripts to encode track 4 while excluding the others?

There's an option to select only one language.

line 60
::choose if you want to mux all the audio from the input or just the main audio track. This is valid only if "set MUX=YES" (YES or NO default = YES )
set mux_all_audio=YES

line 221
:: set desired audio language (YES or NO default = english) If all set to no, it will get you the first best audio regardless of the language. (otherwise the audio selected is preferred by default).


otherwise, you'll have to mux your file with only the audio/subs you want first and then run the script.

[Kuler087]

Thank you so much for adding two-pass bitrate encoding! Now time to rip those pesky P7 FEL UHD's :)!

you're welcome.

[lemaireus]

There's an option to select only one language.

line 60
::choose if you want to mux all the audio from the input or just the main audio track. This is valid only if "set MUX=YES" (YES or NO default = YES )
set mux_all_audio=YES

line 221
:: set desired audio language (YES or NO default = english) If all set to no, it will get you the first best audio regardless of the language. (otherwise the audio selected is preferred by default).


otherwise, you'll have to mux your file with only the audio/subs you want first and then run the script.

Thank you very much, Kuler, for the helpful guidance. Unfortunately, in my case the movie is of the silent era and its Criterion blu-ray now comes with four different orchestral scores (and two commentary tracks that do not need re-encoding). I ended up extracting each of the four audio tracks as a separate file and then encoded each of those separately with 8-1-1 workflow in DoVi_Scripts.

Your tip will come in handy with blu-rays with audio tracks of multiple languages. Thank you. For other scenarios, such as the one I outlined above, perhaps an option to select one particular audio track on the basis of track ID or audio track number--track 2, or 3, or 4, or audio 1, 2, or 3 . . .--could be added as a feature in one of the future versions of DoVi_Scripts.

[lemaireus]

Each time I do a 7.1 encode using EAE, the resulting track has .mkv as its file extension. Is there any way I can get DoVi scripts to produce a file with the correct .eac3 file extension?

The ec3 file is muxed to mkv to preserve any delay in the source. You can't just change it manually to ec3, this would make a file with an invalid extension so you have to demux it(mkvextract) if you want it to have ec3 extension.

This is with reference to a conversation thread--cited above--on p. 37:

As a matter of fact, 'eac3' would be the correct file extension of the encoded EAC3 audio. The extension '.mkv' is incorrect because it makes the operating system believe that the file is a video file, when it is in fact an audio file.

Is there any way in which I can tinker with the settings of 'DoVi_Scripts_MKV.bat' in order to get it to output encoded EAC3 audio with the .eac3 file extension rather than .mkv?

[Korbus]

Is there a workflow that would allow me to use an already made 1080p HDR10 rip, to which to add the DV metadata extracted from a P7 FEL UHD/remux and get an P8 mkv with the FEL metadata baked in, similar to the result i would get with the 8-2-1 workflow? I'm asking this because getting a BL HDR10 rip is much faster with RipBot, due to Distributed Encoding (twice as fast, actually). If I could then use DoviScripts to bake in that rip the P7 metadata, it would speed up the whole process, I guess.

[Kuler087]

I ended up extracting each of the four audio tracks as a separate file and then encoded each of those separately with 8-1-1 workflow in DoVi_Scripts.

if you want to encode each track, you can set all the language options to ''NO''. I think this should enable the encoding of every track present.

As a matter of fact, 'eac3' would be the correct file extension of the encoded EAC3 audio. The extension '.mkv' is incorrect because it makes the operating system believe that the file is a video file, when it is in fact an audio file.
yes, I remember but I never did it because it's just simpler to deal with the mkv container when the input has a delay. And it really takes 2-sec to demux with mkvextract (https://www.videohelp.com/software/Inviska-MKV-Extract) anyway.

Is there any way in which I can tinker with the settings of 'DoVi_Scripts_MKV.bat' in order to get it to output encoded EAC3 audio with the .eac3 file extension rather than .mkv?

I think the TS version doesn't have this mkv container muxing for ec3 encoding for a reason I forgot. So I guess you could use it for audio encoding.

[Kuler087]

Is there a workflow that would allow me to use an already made 1080p HDR10 rip, to which to add the DV metadata extracted from a P7 FEL UHD/remux and get an P8 mkv with the FEL metadata baked in, similar to the result i would get with the 8-2-1 workflow? I'm asking this because getting a BL HDR10 rip is much faster with RipBot, due to Distributed Encoding (twice as fast, actually). If I could then use DoviScripts to bake in that rip the P7 metadata, it would speed up the whole process, I guess.

No, to merge the FEL into the BL, it requires re-encoding.

But ripbot can probably accept avisynth script for input? I know staxrip does so you can use workflow 8-2-1 to create the script, cancel the encode right away and use the avisynth script from the TEMP folder.

[Korbus]

Well, apparently it does (it loads it), but when executing it it does not use distributed encoding (which was the only reason to use RB), uses my predefined encoding preset, not the whatever it is defined in the script and the result is a bare HDR10 file. So I'll continue to use Dovi Scripts, exercise patience and accept it'll be some months until I'll convert all the relevant movies in my library.

[Kuler087]

not the whatever it is defined in the script and the result is a bare HDR10 file
Yes, that's normal, the dovibaker output is fel+BL merged into an RGB HDR16 stream. You have to specify the P8 rpu path and the profile in ripbot(if there's an option)

it does not use distributed encoding
Are you talking about dual PC encoding?
If so, just run the script on both PC with two movies, and in the end, it will be the same speed as ripbot dual PC encoding.

[Korbus]

Are you talking about dual PC encoding?


No, distributed encoding, as implemented in RB, can also be used with a single PC, if you have two network interfaces (such as ethernet and wifi, which most PC's do nowadays). With the same encoding settings and video file, the speed basically doubles, but the PC resources are heavily taxed (meaning you can't do much while there's an encode running, but... it's half the time). Also, you can pause the conversion at any time and resume it whenever you like, which is very convenient.
But... no DoVi metadata of any kind are preserved when encoding, nevermind P7 FEL baking...

[Kuler087]

yes, but it's the same speed as using two pc to encode two movies at the same time. (unless one of the two PC is very old/slow)
The PC cannot go faster than 100% CPU usage, distributed or not.

so two movies being encoded by two PC at the same time is the same speed as encoding 2 movies in a row in Ripbot with distributed encoding.

[Korbus]

I don't have two PC's, so for me that gimmick was very convenient. I would rip a DV movie to HDR10 and then use DDVT Tool or your script to inject the RPU and get a P8 mkv, but now that there's a way to preserve the FEL information, of course I prefer that. So I'll just take the slower path :)

[Gatorman3385]

Encoding FEL to SDR I'm getting very little CPU usage, ≈15%. Is this expected?

[Kuler087]

I don't know. On my end, I get 90-100% cpu usage when I encode anything:

https://i.ibb.co/pvRx6hK/Windows-Terminal-haq-Omx-Hz8-S.png

[Kuler087]

oh never mind... I misread that you were talking about x264...
Indeed it's not very fast, I get about 40% usage only... not sure why

https://i.ibb.co/5rR3R0q/SLx-Z6-Q6pdh.png

[lemaireus]

I think the TS version doesn't have this mkv container muxing for ec3 encoding for a reason I forgot. So I guess you could use it for audio encoding.

I just tried it and even the TS version outputs an .eac3 file as .mkv. Anyway, this is not really a big deal; all I need to do is to change the file extension and that does the job.

Thank you for the link to mkvextract. It works well in extracting each track. Mkvtoolnix also pretty much does the same job in about the same time.

Thank you once again for making available what, to the best of my knowledge, is the only 7.1 audio encoder that there is at the moment.

[Gatorman3385]

oh never mind... I misread that you were talking about x264...
Indeed it's not very fast, I get about 40% usage only... not sure why

Adding "Prefetch(8)" after the DoViBaker(bl, el, rpu="I:\Working\Dolby-Vision-Tools\temp.folder31\RPU_FEL.bin") call, significantly increased my CPU usage (60%). Adding "Prefetch(2)" at the end of the script increased CPU usage again (90%-100%). Encoding FPS went from 2fps to 12fps. Is this a reasonable fix or could this affect the encode negatively?

DoViBaker(bl, el, rpu="I:\Working\Dolby-Vision-Tools\temp.folder31\RPU_FEL.bin")
Prefetch(8)
z_ConvertFormat(pixel_type="YUV420P10",colorspace_op="rgb:st2084:2020:full=>2020ncl:st2084:2020:limited",dither_type="error_diffusion",resample_filter="spline36",resample_filter_uv="spline36",chromaloc_op="left=>top_left")
ConvertBits(16)
libplacebo_Tonemap(src_csp=1, dst_csp=0, dst_max=125, dynamic_peak_detection=false, smoothing_period=20.0, percentile=99.995, tone_mapping_function="bt2390", gamut_mapping_mode="perceptual")
ConvertToYUV420(matrix="709")
ConvertBits(10)
Crop(0, 264, -0, -264)
Spline36Resize(Width / 2, Height / 2)
Prefetch(2)

[Kuler087]

I dont know, it should be fine. thanks

added in latest beta: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link

[Kuler087]

I just tried it and even the TS version outputs an .eac3 file as .mkv. Anyway, this is not really a big deal; all I need to do is to change the file extension and that does the job.

Thank you for the link to mkvextract. It works well in extracting each track. Mkvtoolnix also pretty much does the same job in about the same time.

Thank you once again for making available what, to the best of my knowledge, is the only 7.1 audio encoder that there is at the moment.

For 7.1, the TS version should not use the mkv container but If you want to use the mkv version, you can edit line 17191. Replace ''TEMP'' by ''output_path'' and delete lines 17195 and 17196

"%PLEX%" -eae_root "%output_path%\EAE" -c:a pcm_s24le -i "%TEMP%1.wav" -eae_root "%output_path%\EAE" -b:a %DDP_bitrate%k "%output_path%%temp.name%_EAE%DELAYB%.eac3"


For 5.1, change the output extension to .ec3 at line 17185
"%ffmpeg_path%" -i "%temp.path%%temp.name%%temp.ext%" -map 0:%FID% -c:a eac3 -b:a %DDP_bitrate%k %ffmpeg_channels% -ar 48000 -c:s copy -map_chapters -1 -metadata:s:a:0 title="DDP @ %DDP_bitrate%kbps" -y "%output_path%%temp.name%_EC3.ec3"

[lemaireus]

For 7.1, the TS version should not use the mkv container but If you want to use the mkv version, you can edit line 17191. Replace ''TEMP'' by ''output_path'' and delete lines 17195 and 17196

"%PLEX%" -eae_root "%output_path%\EAE" -c:a pcm_s24le -i "%TEMP%1.wav" -eae_root "%output_path%\EAE" -b:a %DDP_bitrate%k "%output_path%%temp.name%_EAE%DELAYB%.eac3"


For 5.1, change the output extension to .ec3 at line 17185
"%ffmpeg_path%" -i "%temp.path%%temp.name%%temp.ext%" -map 0:%FID% -c:a eac3 -b:a %DDP_bitrate%k %ffmpeg_channels% -ar 48000 -c:s copy -map_chapters -1 -metadata:s:a:0 title="DDP @ %DDP_bitrate%kbps" -y "%output_path%%temp.name%_EC3.ec3"

Thank should fix it, I'm sure. Will give that a shot and let you know whether it worked or not. Thanks a lot!

[lemaireus]

For 7.1, the TS version should not use the mkv container

Yes, this worked! On the previous occasion I had tried encoding a 2.0 DTS-HD MA track to EAC3 with the TS version and the output was in .mkv format. The moment I encoded a 7.1 track with TS.bat, the encoded file came out as .eac3, exactly as it should have. Thank you!

If you want to use the mkv version, you can edit line 17191. Replace ''TEMP'' by ''output_path'' and delete lines 17195 and 17196

"%PLEX%" -eae_root "%output_path%\EAE" -c:a pcm_s24le -i "%TEMP%1.wav" -eae_root "%output_path%\EAE" -b:a %DDP_bitrate%k "%output_path%%temp.name%_EAE%DELAYB%.eac3"

I was almost certain that this would work--since the file extension at the end of line 17191 is .eac3 (and I had deleted lines 17195 and 17196)--but it didn't. I wonder why.

In any case, the TS version is happily encoding 7.1 tracks with .eac3 extension so the job is done. Thank you!

[Gatorman3385]

Am I correct that 8.2.1 FEL to Baked HDR, encodes the RPU with the video or does x265 inject the RPU at the end? I wonder if this uses up bitrate that could be used by the video encode if the P8 RPU were injected after the process finishes.

I should say that I've modified my x265_HDR settings to limit bitrate (--vbv-bufsize 24000 --vbv-maxrate 12000). This is for remote playback not local viewing.

[guest]

Hi Kuler,

Just a quick question, does the AV1 codec support Dolby Vision ??

Can AV1 be used in an .mp4 container ??

And then can DV, AV1 & .mp4 "live" together ??

If so, do you have any plans for AV1 support ??

Cheers

[Kuler087]

Am I correct that 8.2.1 FEL to Baked HDR, encodes the RPU with the video or does x265 inject the RPU at the end?



It injects the RPU on the fly while encoding the new HEVC stream.

I wonder if this uses up bitrate that could be used by the video encode if the P8 RPU were injected after the process finishes.
I don't understand what you mean. Bitrate is not related to the RPU.

I should say that I've modified my x265_HDR settings to limit bitrate (--vbv-bufsize 24000 --vbv-maxrate 12000). This is for remote playback not local viewing.
You probably should use a low two-pass bitrate for these values.

[Kuler087]

Hi Kuler,

Just a quick question, does the AV1 codec support Dolby Vision ??

Can AV1 be used in an .mp4 container ??

And then can DV, AV1 & .mp4 "live" together ??

If so, do you have any plans for AV1 support ??

Cheers

Sorry, I have no experience with this codec but yes it supports DV.

[thirdmoon]

Sorry, I have no experience with this codec but yes it supports DV.

I have done some testing with AV1. It's not good for high quality encoding especially when film grain is present.

Its better at high CRF values with low/no grain.

[Korbus]

While using workflow 3-1, I have encountered the error from the attached screenshot - basically LAV Splitter Source not found and madvr failing to make the scene cuts. I have used the same workflow successfully two times before, with no problems whatsoever, with two different video files.
Nothing has changed since. I have reinstalled both LAV filters and madvr and rebooted, to no avail. I have tried with three different video files, same error. I don't understand what could have happened...

[Kuler087]

Looks like you broke your madMeasureHDR.exe, download the tools pack again.
It happened to me one time when I was using the beta time-limited madvr builds.

[Korbus]

Just did that. Now I was able to get past the LAV error, but still not past the madvr error... I have redownloaded the tools and installed madvr through install.bat as administrator.

[Kuler087]

https://forum.doom9.org/showthread.php?p=2010369#post2010369

[Korbus]

I have tried with changing prores setting to yes, still no luck, same error as above. Guess I'm giving up on this workflow, although I'm very frustrated that it worked the first two times. Something has changed and I can't pinpoint it. In the 2 successful cases, measurements were done by prores, I guess, which created a temp .mov file several hundred GB in size. Now it's dxva (copy-back) doing the measurement, which reaches 100% and then the madvr error follows...
Thanks for your help anyway! Sent a donation and got the link for the rpu's, thank you for this and your amazing work!

[Kuler087]

The problem is your input. I've seen this happen only once or twice with my own mkv rip and I processed thousands of files.
You can convert it first to prores with workflow 8-2-3 and then input the prores file in 3-1, it should bypass your problematic MKV rip

[Korbus]

Tried that too. Still no luck... Before that, I have tried 3-1 (mkv, not prores) with 2 different files (Pacific Rim and Blade Runner Final Cut). The same error as in my previous post.

[Kuler087]

oh, I forgot to tell you... You have to put ''transfer=hdr.matrix=2020'' in the prores filename...

Anyway, I added a workaround for those badly hevc muxed MKVs in the latest beta (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=sharing). If madvr fails to measure, it will now convert to prores and then generate the scene cuts with madvr.
If you already know a specific input will fail, you can force the workaround at line: 211 set madvr_workaround=YES

[Korbus]

Thank you, it worked by renaming the file. After that it finally initiated the cm-analyze.exe.
L.E. Meanwhile, I have completely uninstalled and removed madvr entries from registry, redownloaded and installed it again and now a file that was previously failing 3-1 (Blade Runner Final Cut) successfully completed the workflow with madvr. So I guess something has corrupted its settings or Windows registry entries, but now everything seems to be working ok again.

[ac777103]

thanks for the updated script with the prores workaround for 3-1. I have been using 6-2 to generate an HDR plot and decide on which setting to use for the mastering display luminance/primaries when starting 3-1, as I've seen cases where MediaInfo stats on MDL aren't that sensible for the content. Is there a workaround that will generate the HDR plot before starting 3-1 ?

[Kuler087]

Is there a workaround that will generate the HDR plot before starting 3-1 ?

the workaround for files that won't work in madvr is only for 3-1.

In 6-2, if you have a file that doesn't work, you can enable prores encoding and crop (even you if use 0,0,0,0)

:: choose if you want 6-2 to convert to prores when you opt to crop. This may be faster depending on your CPU (default = NO)
set crop.prores62=YES

[ac777103]

thanks, I updated the bat file to force prores for 6-2 but got the following error:
18797

[Kuler087]

Oops, this was intended for when you crop the letterbox. I forgot to test it when you don't crop.
This should fix it. (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link)

[ac777103]

Many thanks, making progress but not quite there. I ran 6-2 with the new script, having modified the line to force prores for cropping, and set the crop to 0,0,0,0. I obtained an HDR plot but as you can see the stats on %MaxCLL and %MaxFALL haven't been derived. Nevertheless, the plot appears useful.

18798

18799

[Kuler087]

it looks like your tool folder is not up to date. These files specifically: https://drive.google.com/drive/folders/18403rSHIaVFkHIFVkO1ZYoIZmZrRKwag?usp=sharing

[ac777103]

thanks, did those get updated at some point? I've never had this stage of 6-2 fail before.

[Kuler087]

In 3.0.4 (https://github.com/R3S3t9999/DoVi_Scripts/releases/tag/3.0.4) yes. I added a lot of new stats and these py scripts were updated.
I always put a link to the updated files in the release note so if you update only once in a while, you probably should update the tools too.

[ac777103]

thanks, yes I was on a version pre 3.0.4. Will check the notes from now on per your suggestion. I was able to get a stats complete plot by just plotting the RPU once I'd downloaded the new .py files. Although Pacific Rim is by no means a favourite of mine (you could say it's so dumb it's good), it's niggled me that it's the only film in my collection that failed on 3-1, so glad to have it in DV now (as dumb as the film is, it certainly looks spectacular).

[Kuler087]

so glad to have it in DV now (as dumb as the film is, it certainly looks spectacular).
yes and DV helps a lot in this one. (unless you have a 2000nits TV)

[Korbus]

Sorry to pester, but now I'm getting this error while running workflow 8-2-1, which until now I have used successfully dozens of times...

[Kuler087]

I dont know. Works fine for me, and nothing changed in this workflow since I added 2-pass support...

https://justpaste.it/ahew2

[Korbus]

The first pass is not done at all, after demuxing/indexing/metadata ordering it jumps almost instantly to pass 2, which throws the error. I have recopied mkvtoolnix afresh from the tool pack, reinstalled avisynth+, rebooted and still get the error. It does it on each 4k remux i try.

[Kuler087]

I dont know and can't reproduce...

Set echo to ''on''(line2) and post the complete log on https://justpaste.it/

[Korbus]

Done https://justpaste.it/gt9gi

[Kuler087]

I dont see anything wrong but if you say that it worked before, it must be your input...
You can try to Set the script to keep the temp folder and run the avs script in avspmod.
"D:\Downloads\DoVi.Scripts\temp.folder31\script.avs"

:: choose if you want the temp folder to be deleted after each workflow YES or NO (default=YES)
set DEL_temp=YES

you can also try this sample: https://drive.google.com/file/d/1AflJT_C8Emocm4uyNDw67ZVnl-AC1Gqz/view?usp=drive_link

[Korbus]

... run the avs script in avspmod.
"D:\Downloads\DoVi.Scripts\temp.folder31\script.avs" ...


How do I do that? I got that in order to keep the TEMP folder I need to input NO to set DEL_temp=, but what do I have to do to run the avs script in avspmod?

[Kuler087]

open "D:\Downloads\DoVi.Scripts\temp.folder31\script.avs" in avspmod and try to play it

[Korbus]

With your sample, 8-2-1 worked. I will now try again with my remux (which will surely fail) and then recover the avs script and play it in avspmod.
L.E. This is what happens when I play the script:

[Kuler087]

it means the RPU has more or fewer frame than the video layers.

You can try to extract and inject the rpu back into the P7 ST-DL rip. This should fix the framecount mismatch.

[Korbus]

As usual, you're right. Did what you recommended and now it's running pass one as it should. Thank you!

[Gatorman3385]

Is there a reason to change the default (125) Target Nits when tone mapping to SDR? Is this personal preference or based on the device being used to view the media?

[Kuler087]

You can raise it for a brighter HDR grade if you notice clipping.
125 should be fine for most content.

[Kuler087]

it looks like the latest LG C2 firmware update broke profile 8 DV MP4 support for files with codec ID DVHE which is needed for older TV/hardware (EG C8).
Now all my dvhe P8 samples no longer work on my TV SMH... :(

profile 5 still work...

[SamuriHL]

Oh man. That's not good news!

Sent from my SM-S928U1 using Tapatalk

[-QfG-]

it looks like the latest LG C2 firmware update broke profile 8 DV MP4 support for files with codec ID DVHE which is needed for older TV/hardware (EG C8).
Now all my dvhe P8 samples no longer work on my TV SMH... :(

profile 5 still work...

You can mux "Fake P5" profiles in MP4, that will work.


Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : Dolby Vision, Version 1.0, Profile 5.0, dvhe.05.07, BL+RPU, no metadata compression / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 58 s 975 ms
Bit rate : 26.6 Mb/s
Maximum bit rate : 33.3 Mb/s
Width : 3 840 pixels
Height : 1 920 pixels
Display aspect ratio : 2.000
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.151
Stream size : 187 MiB (95%)
Tagged date : 2025-01-11 20:52:41 UTC
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 366 cd/m2
Maximum Frame-Average Light Level : 105 cd/m2
Codec configuration box : hvcC+dvcC

This is a P8 Hybrid file with P5 header.

[Fuso]

it looks like the latest LG C2 firmware update broke profile 8 DV MP4 support for files with codec ID DVHE which is needed for older TV/hardware (EG C8).
Now all my dvhe P8 samples no longer work on my TV SMH... :(

profile 5 still work...

I have LG C2 but I don't have P8 with dvhe ID. What exactly is broken - can't be played, fallback to HDR10?

[-QfG-]

all mp4 muxer write dvhe instead hev1 in the header. (Codec ID). mp4muxer has a switch to set CODEC ID:

--dvh1flag = Set the elementray stream index to set HEVC track's sample entry name to 'dvh1',
default sample entry box name is 'dvhe' for non-cross compatible stream.
--hvc1flag = Set the elementray stream index to set HEVC track's sample entry name to 'hvc1',
default sample entry box name is 'hev1' for cross compatible stream.

But during my tests the switch doesn't work, don't know why. Only FFMPEG mux the files with Codec ID hvc1. And with Codec ID dvhe mp4 files will not work on older SAMSUNG/LG TVs.

[Kuler087]

You can mux "Fake P5" profiles in MP4,

Oh I know but that's not standard and I don't have to do that since the "hev1" codec id(new mp4muxer) "hvc1" codec id (new mp4box) work just fine on all the TVs made after 2019.
For the TV from before that, you don't even need the ''fake p5'' headers, they just need the "dvhe" codec id which was used in the very first mp4muxer version and also used in the old mp4box version I use in DoVi_Scripts.

So now since the latest update, my C2 plex app fallback to HDR10 with the codec id ''dvhe'' profile 8 (profile 5 still works). I always used the dvhe ID because it worked on older and newer TVs so the patterns and test files (https://drive.google.com/drive/u/1/folders/1yAq-jgsb8pYa92PnGZkxyEV0E3VVkhiC) I did were supported on more devices. Now I have hundreds of files shared everywhere that no longer work on my C2 and possibly all the newer TV.

Kodi probably still works though but since I got my Ugoos, I no longer use my tv internal player and my C2 dev mode expired so I lost my kodi installation and I did not try the native lg app, only the PLEX app.
The TS container still works fine on older and newer TVs so I guess I'll have to remux all my files and upload them again.


My script has two modes for the mp4 muxing

OLD: (supported on older TVs)
use a custom mp4muxer version with dvhe id
use an old mp4box version that keep the id to dvhe

NEW: (supported only on 2019+ TVs)
use the latest mp4muxer with codec id hev1
use the latest mp4box with codec id hvc1

https://i.ibb.co/VmBq3qz/Media-Info-6f-LJtd-NKET.png

[Kuler087]

all mp4 muxer write dvhe instead hev1 in the header. (Codec ID). mp4muxer has a switch to set CODEC ID:

--dvh1flag = Set the elementray stream index to set HEVC track's sample entry name to 'dvh1',
default sample entry box name is 'dvhe' for non-cross compatible stream.
--hvc1flag = Set the elementray stream index to set HEVC track's sample entry name to 'hvc1',
default sample entry box name is 'hev1' for cross compatible stream.

But during my tests the switch doesn't work, don't know why. Only FFMPEG mux the files with Codec ID hvc1. And with Codec ID dvhe mp4 files will not work on older SAMSUNG/LG TVs.

only the first version of mp4muxer(the ones in my tool pack) use the dvhe id and that's the only version that worked on the LG C8 in profile 8

[-QfG-]

Oh no, do you think LG has capped the P8 support for the TVs? Files with P8 and hev1 still working?

[Kuler087]

I'll try the native app later and i hope it's just a PLEX issue but since HEV1 and HVC1 still work, it doesn't look good for ''dvhe'' support on my TV and possibly the newer ones.

My script is using a modded version of the first mp4muxer though, I probably should try the original mp4muxer.
FYI, the modded version (https://drive.google.com/file/d/14fAbUrg8BWRCtb9aRcmznWfMV_PJyh2M/view?usp=sharing)speed up the muxing and adds the compatibility ID parameter which was not present in the very first mp4muxer. (https://drive.google.com/file/d/1FUqXlGoXA7vIFOLnnun_3fsjsCRZEeot/view?usp=sharing)

[Fuso]

Oh I know but that's not standard and I don't have to do that since the "hev1" codec id(new mp4muxer) "hvc1" codec id (new mp4box) work just fine on all the TVs made after 2019.
For the TV from before that, you don't even need the ''fake p5'' headers, they just need the "dvhe" codec id which was used in the very first mp4muxer version and also used in the old mp4box version I use in DoVi_Scripts.

And with Codec ID dvhe mp4 files will not work on older SAMSUNG/LG TVs.

They will play on older LGs. The reason for the fake P5 was to work also on non-DoVi TV (in my case Samsung).

- P8 dvhe plays on both old and new LGs (until the last update apparently);
- P8 hev1 plays DoVi on on new LGs and HDR10[+] on Samsung, on older LGs fallbacks to HDR10, but as a matter of playback it works on all tvs;
- P5 hev1 plays DoVi on both new and old LGs, and HDR10[+] on Samsung.

[Kuler087]

They will play on older LGs. The reason for the fake P5 was to work also on non-DoVi TV (in my case Samsung).

- P8 dvhe plays on both old and new LGs (until the last update apparently);
- P8 hev1 plays DoVi on on new LGs and HDR10[+] on Samsung, on older LGs fallbacks to HDR10, but as a matter of playback it works on all tvs;
- P5 hev1 plays DoVi on both new and old LGs, and HDR10[+] on Samsung.

that's correct.

[Fuso]

I just tested some of your P8 dvhe test videos and yes they fallback to HDR when played from PLEX. But from the internal played they don't play at all.
P8 hev1 and Fake P5 hev1 from PLEX are working fine.

[Kuler087]

Also, the plex app and the tv menu navigation are noticeably slower and sometimes lag. I hate this update!!!

[-QfG-]

I have a Dune Homatics 4k R Plus Box, with a CoreELEC CPM build and full FEL support. I can only recommend it to everyone.

Also, the plex app and the tv menu navigation are noticeably slower and sometimes lag. I hate this update!!!

God damned, i have a C8 and no OTA update still yet.

[dapope]

Thank you again Kuler087 for the awesome tools and research. Do you or anyone else know if Snake Eyes 1998 or Andor S01 UHD are safe to convert to 8.1 without baking fel etc. ? I don't see them on the spreadsheet. Thanks!

[Kuler087]

I dont remember. Run the files in workflow 7-1 and find out.

[Kuler087]

If anyone is interested in testing a new function? I did a new workflow(7-4) that can create DV metadata comparison videos with 10 frames in loop.
it takes 10 different frames (auto or manual) and makes a loop of 69 frames alternating No metadata/no tone mapping vs L1(L3) only vs L1+ artistic trims

The whole process is very fast, about 5 minutes on my PC and supports batch processing.
So comparing the DV tone mapping is now very easy and effortless.

latest beta: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
new files to put in the tools folder: https://drive.google.com/drive/folders/18403rSHIaVFkHIFVkO1ZYoIZmZrRKwag?usp=drive_link
I did a couple of samples: https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf

(7-5) I'll also add another similar workflow that compares DV metadata with FEL baked and without FEL. This workflow is not completed yet.

[DMD]

If anyone is interested in testing a new function? I did a new workflow(7-4) that can create DV metadata comparison videos with 10 frames in loop.
it takes 10 different frames (auto or manual) and makes a loop of 69 frames alternating No metadata/no tone mapping vs L1(L3) only vs L1+ artistic trims

The whole process is very fast, about 5 minutes on my PC and supports batch processing.
So comparing the DV tone mapping is now very easy and effortless.

latest beta: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
new files to put in the tools folder: https://drive.google.com/drive/folders/18403rSHIaVFkHIFVkO1ZYoIZmZrRKwag?usp=drive_link
I did a couple of samples: https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf

(7-5) I'll also add another similar workflow that compares DV metadata with FEL baked and without FEL. This workflow is not completed yet.
Thank you it's great like your other tools.

[Korbus]

@R3S3T

If I bake FEL using workflow 8-2-1 to get a 1080p rip, then from that rip I extract the 8.1 RPU with workflow 1, can I inject the said RPU to a fresh 1080p BL/HDR10 rip of the same movie and preserve the FEL information as the original rip did?

[Kuler087]

only if the other 1080p encode has FEL baked in.

[Korbus]

You mean the first rip, right? Thanks, good to know I can store those RPUs from FEL baked rips.

[Kuler087]

The P7 RPU can only be played properly with a BL that has fel baked in so if the second video was not processed with the dovi baker, you can't inject the rpu.

[Korbus]

Oh, ok, I misunderstood. Pity... Thank you!

[ac777103]

Is anyone aware of a list of P7 disc-sourced titles that are CMv4 ? I just looked at the UK release of The Usual Suspects and doviscripts reports it as MEL CM 4. I can't imagine that my Panny UB820 can take advantage of that, but my Ugoos and ATV can. For curiosity I guess there is a plotting workflow that can show what the additional v4 levels are doing?

[Kuler087]

Is anyone aware of a list of P7 disc-sourced titles that are CMv4 ?

no, but there are a few cmv4.0 BD and all recent movies have cmv4.0 on streaming which can easily be transferred to the P7 rip. (https://www.youtube.com/watch?v=RI_e-MPIPlw)

For curiosity I guess there is a plotting workflow that can show what the additional v4 levels are doing?
You can use the new workflow I posted a few days ago (https://forum.doom9.org/showpost.php?p=2013053&postcount=947). Make a CMV4.0 and CMV2.9 versions and compare them.

[ac777103]

thanks. Among my modest collection of 81 P7 DV titles, The Usual Suspects is the only one that is CMv4, I'll look out for this in future.

[Gatorman3385]

I've noticed a similar CPU usage scenario when encoding from HDR to SDR ( x264) as with FEL to SDR (x264). Adding Prefetch(2) to ::tonemap, enabled ≈ 100% CPU usage from ≈ 70%.

::tonemap
if "%SDR%"=="y" echo ConvertBits(16) >> "%TEMP%script.avs"
if "%SDR%"=="y" echo libplacebo_Tonemap(src_csp=%inCS%, dst_csp=0, dst_max=%SDR_target_nits%, dynamic_peak_detection=%peak_detect%, smoothing_period=%smoothing_period%, percentile=%percentile%, tone_mapping_function="%tone_mapping_function%", gamut_mapping_mode="%gamut_mapping_mode%") >> "%TEMP%script.avs"
if "%SDR%"=="y" echo ConvertToYUV420(matrix="709") >> "%TEMP%script.avs"
if "%SDR%"=="y" echo ConvertBits(10) >> "%TEMP%script.avs"
if "%SDR%"=="y" echo Prefetch(2) >> "%TEMP%script.avs"

[Kuler087]

If anyone is interested in testing a new function? I did a new workflow(7-4) that can create DV metadata comparison videos with 10 frames in loop.
it takes 10 different frames (auto or manual) and makes a loop of 69 frames alternating No metadata/no tone mapping vs L1(L3) only vs L1+ artistic trims

The whole process is very fast, about 5 minutes on my PC and supports batch processing.
So comparing the DV tone mapping is now very easy and effortless.

latest beta: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
new files to put in the tools folder: https://drive.google.com/drive/folders/18403rSHIaVFkHIFVkO1ZYoIZmZrRKwag?usp=drive_link
I did a couple of samples: https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf

(7-5) I'll also add another similar workflow that compares DV metadata with FEL baked and without FEL. This workflow is not completed yet.


Ok, (7-5) is now completed. You can now create BL vs FEL videos comparison that will show you exactly how FEL looks on device that can't decode it and on device that can.

latest beta: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
You must update these files again: https://drive.google.com/drive/folders/18403rSHIaVFkHIFVkO1ZYoIZmZrRKwag?usp=drive_link
I did a couple of samples: https://drive.google.com/drive/u/0/folders/1FS42T95TOSpoy4xtwUBIQmziCe_R_IKe

These updated files also fix a bug in 7-4 with input that had a 100 and 1000nits trim (rare).

these are SDR GIFs of HDR output, so ignore the clipping...
https://i.ibb.co/d6JMZQp/Application-Frame-Host-Pw-Xu-RJ91-LB.gif
https://i.ibb.co/6B7JKG2/Application-Frame-Host-PUQo-Dkjc2-Q.gif

[Kuler087]

I've noticed a similar CPU usage scenario when encoding from HDR to SDR ( x264) as with FEL to SDR (x264).

thanks

[spasv]

Some help please.
Running DoVi_Scripts_MKV.bat’s workflow(6-2) process Calculating per shot MaxFALL threshold...issues:
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings.
Both python.exe and pythonw.exe are in a same folder. Python.exe opens its Dolby_Scripts_GUI V1.0.0_BETA Window.
And, how to understand run without arguments?
I’ve tried running DoVi_Scripts_MKV.bat without processing file but no result.
Thanks

[Kuler087]

install python:

https://apps.microsoft.com/detail/9pjpw5ldxlz5?hl=en-US&gl=US

[spasv]

Thanks.
Probably, the strange behavior I see is caused by dynamic RAM errors.

[coopzr]

Hello,
My AVR is unable to play DTS or Dolby TrueHD. It supports up to E-AC3-JOC and Multichannel PCM connected via eARC. It has 5 channels.

If I wish to watch a video with DTS-HD MA or Dolby TrueHD, what is the best way to enjoy as much audio quality as possible?

I understand that Atmos will be lost no matter what I do.

As I see it, my options are:

1. Let Kodi transcode the audio.

2. Using Workflow 8-1-1 (Lossless audio --> E-AC3)
2.1. 7.1 channels @ 1024kbps
2.2. 5.1 channels @ 1536kbps

3. Do something else, perhaps convert to LCPM or FLAC?

Since DTS is open source, is there anything I can do with DTS-HD MA that I cannot do with Dolby TrueHD? Again, the goal is to retain as much quality as possible.

Thanks for your help!

[Kuler087]

Kodi should be able to send the audio as lossless PCM so that would be the best option for your setup.

[coopzr]

Forgive me if this is off-topic. I don't know any other forum or community discussing HDR / Dolby Vision for home cinema. If there are communities out there, please link me to them so I can stop bothering you :p

I have come across two versions of the same movie.
The original source movie is in HDR10. It is my understanding that this HDR metadata is static and applies throughout the entire movie.
The modified version is DV/HDR10+ - "Generated in DaVinci Resolve Studio using the official Dolby Algorithm L5 - 280/280". It appears that an enthusiast has applied dynamic metadata across 2338 scenes.

On paper, the DV/HDR10+ version should be better, right? In the real world, does that mean all DV-generated releases are better than the original?

My questions are: For all movies, and all dynamic DV/HDR10+ versions that enthusiasts have generated, can these versions be worse than the original? Does this defeat the colorist's intent and style choices? Is this process completely automatic, and essentially flawless?

What should I look out for? What should I know about this process?

Thank you very much for any replies. I am very new to this field, as I just got a LG OLED for the first time a week ago.

[Kuler087]

The ultimate HDR intended look is the 12-bit or 10-bit Master. When the master is brighter than your TV and the bluray or stream encode doesn't have dynamic metadata, it relies on your TV's internal static tone mapping curve, which can defeat the director/colorist intent and style choices a lot more than dynamic HDR.
Unless you do manual trims which require a license, the process is non-destructive when you generate DV metadata. It just tells your TV about each shot's brightness, so the TV can tone map it more accurately and stay closer to the master.

[coopzr]

I would like to learn more about this stuff, to really understand all the intricacies. Can you please point me to where I can learn about this stuff?

Thank you for taking the time to reply ��

[Kuler087]

See the DV tone mapping in action with thes (https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf)e and i did some videos on my YT channel (https://www.youtube.com/@RESET_-bg7kw)

[Aldebaran_hun]

Do you have a list which 4k films have the best picture? I've heard that the Dolby Vision CMv4.0 L8 is the best, like Dune part2 iTunes webdl version.

[Kuler087]

Many movies look great.
I don't have a list but find movies that are brighter than your TV capabilities in these HDR/DV plot. (https://drive.google.com/drive/u/1/folders/154fBNllwOHL4Lckc7wDV8QKFJwFxnDt-). This is when DV is really useful.

[prudentavocado]

Thanks Reset 9999, 3 questions for the Dolby_Vision_stuff:

On the "List of DV movies that can't be converted to profile 8 Dolby Vision" does this mean that as long as the DV injected is the one listed, it doesn't matter what HDR source is used?

So 8mile from itunes on that list shows as can't be converted - is that true whether I used the 4k HDR stream from itunes or elsewhere like the 4k HDR stream from UHD disk?

Second question - "PROFILE 7 DOLBY VISION SINGLE-TRACK DUAL-LAYER FEL SUPPORT" - do you recall how you got a file to play on the chromecast with GTV? Everytime I try it falls back to HDR regardless of audio/sub selections.

Third, the comment "Can only be played on a FEL device and can't be converted to P8 without baking FEL into BL" can the proper groups you listed actually bake the FEL into the BL and then it can be played on a p8 device?

p.s., any way to donate to you besides paypal?

Appreciate the assistance.

[Kuler087]

So 8mile from itunes on that list shows as can't be converted - is that true whether I used the 4k HDR stream from itunes or elsewhere like the 4k HDR stream from UHD disk?

Maybe other streaming services have a different encode but it is unlikely. This movie was mastered at 4000nits and they tone mapped a 1000nits version for the bluray release.

do you recall how you got a file to play on the chromecast with GTV? Everytime I try it falls back to HDR regardless of audio/sub selections.
With plex. The newer GTV chromecast probably dropped P7 support so you need to use the older device.
Anyway, don't use this device, the BL and EL are out of sync and it's doing ''fake'' TV-LED.
Get a Ugoos, you wont regret it, especially with the latest development that allows unaltered RPU processing and Level 5 + positive lift support.


"Can only be played on a FEL device and can't be converted to P8 without baking FEL into BL" can the proper groups you listed actually bake the FEL into the BL and then it can be played on a p8 device?
Yes, these groups bake FEL properly and can be played on any device. Their older encodes might not be though.

p.s., any way to donate to you besides paypal?
no

[Vymrr]

Get a Ugoos, you wont regret it, especially with the latest development that allows unaltered RPU processing and Level 5 + positive lift support.



I seem to have problem viewing this setting on the demo files. Which build allows this? CoreElec latest nightly or which CPM build?

[Korbus]

This (https://github.com/cpm-code/xbmc/releases/tag/CoreELEC-Amlogic-ng.arm-21.2-Omega_20250128030125.A13) build alone.

[ac777103]

I installed the CPM A13 build on my Ugoos yesterday and at first didn't pay attention to the new parameters to force use of source DV levels but today have experimented with the level_5 option and just want to check I understand what's going on.

The first option, set to Y, is for use_source_meta_levels, which by its name sounds global but I guess isn't, and relates to peak brightness to avoid clippling?

the keep_source_meta_level_5 option when set to Y causes OSD masking on my Panny HZ980 when in tv-led mode, but this display does a pretty poor job on tv-led DV anyway as it has a tendency to drop frames (perhaps the processor isn't really up to the job). However, in player-led mode all is good and I've no complaints at all about the picture. Even though it's in player-led mode, am I benefitting from the L5? If so, are there any other devices that also do this, e.g. does Infuse on the ATV account correctly for L5 ?

Is the new option for keep_source_meta_level_6 going to improve HDR10?

[Kuler087]

The first option, set to Y, is for use_source_meta_levels, which by its name sounds global but I guess isn't, and relates to peak brightness to avoid clippling?
This option is enabled by default so you don't have to send that cmd.
This setting enables true dv metadata passthrough. It was altering the RPU before that update. I explained everything in this video: https://www.youtube.com/watch?v=HyrA3KmcJBU

the keep_source_meta_level_5 option when set to Y causes OSD masking on my Panny HZ980 when in tv-led mode, but this display does a pretty poor job on tv-led DV anyway as it has a tendency to drop frames (perhaps the processor isn't really up to the job). However, in player-led mode all is good and I've no complaints at all about the picture. Even though it's in player-led mode, am I benefitting from the L5? If so, are there any other devices that also do this, e.g. does Infuse on the ATV account correctly for L5 ?

Yes, L5 is designed to mask the black bars. In the next version, there is an option to keep L5 to 0. This way it doesn't hide anything and it still allow the positive lift trim metadata to work... Without L5, the positive lift is ignored.
player-led ignores L5 but positive lift still works so it seems to be a tv-led bug. Player led mode on this player is only cmv2.9 though.

All the other HDMI devices ignore L5 and positive lift in TV-LED which is why this update is a very big deal.

L6 is useless, you can ignore it.

[Vymrr]

This (https://github.com/cpm-code/xbmc/releases/tag/CoreELEC-Amlogic-ng.arm-21.2-Omega_20250128030125.A13) build alone.

Thanks, I installed A13 and also estuary A13 skin. I tried running the demo files listed in the 10 reasons video (https://www.youtube.com/watch?v=HyrA3KmcJBU&t=555s&ab_channel=RESET_9999) but I don't see any difference between L1/L2 and L1/L2 no offset. Only when L1 is on do I see a change, no changes too when running the real content. Also, when running the L5 aspect ratio demo file, nothing changes?? The red screen fills up my entire TV screen during the whole clip and no aspect cut off happens, same as the real content folder. Is there a setting somewhere I'm missing?

Just for reference, my TV is a Hisense U8H and I can run DV CM4.0 movies with no issue.

[Kuler087]

Did you enable L5? In A13, it's disabled by default.

https://www.avsforum.com/posts/63803659/

[ac777103]

Yes, L5 is designed to mask the black bars. In the next version, there is an option to keep L5 to 0. This way it doesn't hide anything and it still allow the positive lift trim metadata to work... Without L5, the positive lift is ignored.
player-led ignores L5 but positive lift still works so it seems to be a tv-led bug. Player led mode on this player is only cmv2.9 though.

All the other HDMI devices ignore L5 and positive lift in TV-LED which is why this update is a very big deal.

L6 is useless, you can ignore it.

thanks for the explanation. Perhaps my general impression of an improvement since installing A13 is that the RPU is being processed correctly for the first time on the Ugoos.

Will any of my HDR10 titles that have been processed via the 3-1 workflow have any L5 positive lift data, or is that a manual intervention?

[Kuler087]

It depends... Does your TV support CMv4.0?

If yes, then there won't be any positive lift in the L8 trim because it's a manual intervention.
if no, then yes, the Dolby vision algorithm will create a small positive lift in the generated L2 600nits trim.

in player-led, the ugoos doesn't support cmv4.0, so yes, there will be a positive lift in the generated L2 600nits trim.

[ac777103]

thanks, while my TV supports cm v4 I tend to avoid tv-led playback as it can be glitchy (regardless of DV playback device). So I tend to switch between the ATV and the Ugoos for player-led. Either way, looks like I should stick with the CPM build.

[Vymrr]

Did you enable L5? In A13, it's disabled by default.

https://www.avsforum.com/posts/63803659/

Thanks! Got it enabled but it looks like my TV blacks out my OSD and subtitles on the black bars.. got it reverted and waiting for newer cpm version

I got another question not really related to this, but concerning DV movies in general with dark scenes, the dark is really dark and it's really hard to see sometimes, is this considered normal? For instance, for web streaming services (netflix, etc), this problem doesn't seem to exist, and the picture seems to be perfectly balanced in dark scenes where I can still see details.

[Kuler087]

There's a black crush issue with cmv2.9 content especially if the RPU MDL is 4000nits. For 1000nits RPU, it's not really noticeable in real content but it is crushed in patterns.
I did some test files about this a while ago: https://drive.google.com/drive/u/1/folders/1OH-DT9jfodpGKX9LwN5FsewWGPBII1Ib

On my C2, HDR10 and DV dark scenes look pretty much identical as long as the RPU is not cmv2.9 4000nits.

[ac777103]

thinking some more about player-led playback of HDR10 source files processed via 3-1. The ATV supports CM v4 in player-led, per the explanation in a previous post re positive lift, does this explain my impression that the devices have different brightness profiles in player-led mode? I find them to be more similar for MEL 2.9 content, and more different for my 3-1 conversions.

[Vymrr]

There's a black crush issue with cmv2.9 content especially if the RPU MDL is 4000nits. For 1000nits RPU, it's not really noticeable in real content but it is crushed in patterns.
I did some test files about this a while ago: https://drive.google.com/drive/u/1/folders/1OH-DT9jfodpGKX9LwN5FsewWGPBII1Ib

On my C2, HDR10 and DV dark scenes look pretty much identical as long as the RPU is not cmv2.9 4000nits.

How about CM4.0? The dark scenes also appear in movies converted to CM4.0 (using your tutorials).

[Kuler087]

Since they are two different algorithm, there will be a difference between cmv2.9 or cmv4.0 playback but not much. In a cmv4.0 workflow, the v2.9 L1+generated_L2 should roughly equal v4.0 L1+L3

The ATV seems broken with cmv4.0 in the tests I did a while ago. with the pattern specifically: https://drive.google.com/file/d/1s-3GHjwqvuAy7lxehBoBukvz18NqKYia/view?usp=drive_link

[Kuler087]

How about CM4.0? The dark scenes also appear in movies converted to CM4.0 (using your tutorials).

As I said, as long as the RPU is not cmv2.9 and 4000nits MDL, DV dark scenes look identical to HDR10 on my C2.

[ac777103]

Since they are two different algorithm, there will be a difference between cmv2.9 or cmv4.0 playback but not much. In a cmv4.0 workflow, the v2.9 L1+generated_L2 should roughly equal v4.0 L1+L3

The ATV seems broken with cmv4.0 in the tests I did a while ago. with the pattern specifically: https://drive.google.com/file/d/1s-3GHjwqvuAy7lxehBoBukvz18NqKYia/view?usp=drive_link

I've seen your screenshot of the ATV playing the Spears and Munsil color test. I have that disc and in my system the ATV does much better on that test. What we see is a combination of the player and the display and settings on both. I find my Panny OLED does a better job of rendering a 422 input from the ATV than I get from a 444 input from any Amlogic device. And 444 output from my Panny disc player beats the Ugoos on the SM test. So I avoid 444 playback from the Ugoos as I don't think it upsamples as well compared to my TV rendering 422 HDR10 (ATV) or 422 DV (ATV or Ugoos).

[Kuler087]

I have that disc and in my system the ATV does much better on that test. What we see is a combination of the player and the display and settings on both.

what?? the screenshot is an hdmi capture... No TV is involved...
Unless they fixed something recently, the ATV is broken in cmv4.0 at least with 4000-10000 content ( the blue channel specifically )

https://i.ibb.co/MX9kVz3/firefox-9yg-FEAm9-GF.png

[ac777103]

Since they are two different algorithm, there will be a difference between cmv2.9 or cmv4.0 playback but not much. In a cmv4.0 workflow, the v2.9 L1+generated_L2 should roughly equal v4.0 L1+L3

The ATV seems broken with cmv4.0 in the tests I did a while ago. with the pattern specifically: https://drive.google.com/file/d/1s-3GHjwqvuAy7lxehBoBukvz18NqKYia/view?usp=drive_link

I tried this test file and I think it's probably demonstrating how bad my Panny HZ980 is at TV-led DV.

With TV-led DV, from the Ugoos the first 3 or 4 red and green steps are a single block, no grading at all, but the blue channel has all the steps. On the ATV/Infuse all the steps are present in the red channel but there is terrible noise in the 10000 red block. Like the Ugoos, the green channel is one block until it drops to 2500 nits or so. The blue is cleaner on the Ugoos than from the ATV.

In player-led, the ATV loses the step grading in the red as well as the green at the brightest levels, it's not very good. The Ugoos renders a clean pattern with all the steps but of course it's not CMv4.

This test might confirm my impression that picture quality on my TV is degraded in TV-led mode, since neither the ATV nor the Ugoos were able to produce that good a result in TV-led mode. But it might also be showing that player-led CM v4 from the ATV isn't that great either, suggesting that I may as well stick with player-led from the Ugoos until I change my display?

[ac777103]

apologies for the confusion, my earlier reply related to a different screenshot you'd posted.

[prudentavocado]

Maybe other streaming services have a different encode but it is unlikely. This movie was mastered at 4000nits and they tone mapped a 1000nits version for the bluray release.


With plex. The newer GTV chromecast probably dropped P7 support so you need to use the older device.
Anyway, don't use this device, the BL and EL are out of sync and it's doing ''fake'' TV-LED.
Get a Ugoos, you wont regret it, especially with the latest development that allows unaltered RPU processing and Level 5 + positive lift support.



Yes, these groups bake FEL properly and can be played on any device. Their older encodes might not be though.


no

Thanks

Oh I see.....So, "List of DV movies that can't be converted to profile 8 Dolby Vision" doesn't necessarily mean there is a technical hurdle to where nobody can convert it. If it's one of the proper groups then they could actually do it. (as long as it's not an older encode)


That's a big difference I was missing; I was avoiding all those releases in that red section because I thought it was an impossibility. Why include the BD-FEL ones in the red section then? Seems like you could move those to the green list if we just stick to the proper encoder groups.

[Kuler087]

The list is for REMUX rip and I say:

Can only be played on a FEL device and can't be converted to P8 without baking FEL into BL

The list about the proper encoder groups is just a bonus. I really don't care about encodes, I only watch/keep REMUX.

[Kuler087]

3.0.6 Released: https://github.com/R3S3t9999/DoVi_Scripts/releases

** LATEST Tools pack + bat files + GUI (bat files only link below)**
[GoogleDrive](https://drive.google.com/file/d/1S4dqemaD8snI7QW29InG_XjI6VP0PNhk/view?usp=drive_link)
[MEGA](https://mega.nz/file/BO0TFK5Y#m3jW75vgavjO1kAbSNoQuWsZrIPLqmvntq_OFpUJWZM)
(case sensitive) PASSWORD FOR THE TOOLS PACK IS THE ZIP FILENAME= DoVi.Scripts

**CHANGES:**

- (7-4) NEW workflow that can quickly and automatically create 2min (10 frames) DV L1 vs L2 metadata comparison [videos like these](https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf)
- (7-5) NEW workflow that can quickly and automatically create 2min (10 frames) FEL vs MEL comparison[ videos like these.](https://drive.google.com/drive/u/0/folders/1FS42T95TOSpoy4xtwUBIQmziCe_R_IKe)
- (8-2) NEW: Can now create DV/HDR10 samples of a single frame in loop (line 180, default = NO)
you must [add these new files](https://drive.google.com/drive/folders/18403rSHIaVFkHIFVkO1ZYoIZmZrRKwag?usp=drive_link) to your tools folder. (or re-download the tools pack)
- (6-2) Sped up the P5 input measurement 2.2X (if your cpu can handle it)
- (6-2) Sped up when you opt to crop and use prores
- (3-1) Added a workaround for mkv/ts/m2ts files that fail with madmeasureHDR.exe
- (6-3)(6-4) Added more stats to the L1 plot
- (1) RPU input + ''e'' selection can now loop the RPU frame(s) to check/info.
- (7-1) OSD will now display the frame(s) Level 1 rpu values in nits
- (7-2) OSD can now display the frame(s) Level 1 rpu values in nits if DV is present (line 123 , default = NO)
- (7-2) Can now accept up to 20 inputs
- (7-2) Manual mode will now ask for the frame to export before indexing.

[ac777103]

I've been looking at the custom skin for the Ugoos that provides in-play DV data, and noticed a few titles that seem to be static: e.g. Aliens and The Abyss (disc sourced MEL). I just ran a plot of Aliens and indeed it's flat. For such titles, would I get a better result via 3-1 and discard the original RPU?

[Kuler087]

Well, those movies are just 200nits grade. It won't make much difference unless you have a very low nits display...

[ac777103]

thanks, so for a release like Aliens, the provision of DV on the disc is just a marketing gimmick - the peak nits level per shot is really low, and the RPU is static.

to confirm presence of a static RPU, do I just look at all the plots from 6-4, and check that they are all flat? (at least for MEL discs). It's not sufficient that L1 on its own is flat? I guess it's harder to check for FEL titles?

[Korbus]

thanks, so for a release like Aliens, the provision of DV on the disc is just a marketing gimmick - the peak nits level per shot is really low, and the RPU is static.

The same is true for the Abyss and Titanic and, I suspect, for most of Cameron's latest batch of UHD releases (Avatars). Seems to be another of his oddities after DNR'ring Terminator 2 UHD to death ...

[Kuler087]

to confirm presence of a static RPU, do I just look at all the plots from 6-4, and check that they are all flat? (at least for MEL discs). It's not sufficient that L1 on its own is flat? I guess it's harder to check for FEL titles?
yes 6-4. Sometimes L1 is static but the trims are not.

I guess it's harder to check for FEL titles?
FEL can be checked with 7-1 or 7-5

[ac777103]

The same is true for the Abyss and Titanic and, I suspect, for most of Cameron's latest batch of UHD releases (Avatars). Seems to be another of his oddities after DNR'ring Terminator 2 UHD to death ...

Yes, I just ran through my Cameron mkv's. Aliens and The Abyss (MEL) are completely static. The Terminator (MEL) is static apart from some negligible dynamic data early on. Titanic and True Lies (FEL) have completely static RPUs, the FEL is between 5-6gb for each title. I don't have an nVidia GPU so the FEL workflows are a challenge for me to run. I'll look at new P7 titles more carefully from now on.