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

guest

7th July 2024, 03:35

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

7th July 2024, 13:21

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

7th July 2024, 13:46

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

8th July 2024, 08:04

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

8th July 2024, 12:05

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

8th July 2024, 12:28

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

8th July 2024, 13:06

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

8th July 2024, 13:39

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

9th July 2024, 02:49

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

9th July 2024, 05:12

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

9th July 2024, 05:23

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

9th July 2024, 11:51

again, you have to encode the Resolve delivery file to hevc

guest

9th July 2024, 12:06

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

9th July 2024, 12:11

guest

10th July 2024, 01:28

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

10th July 2024, 01:56

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

10th July 2024, 02:13

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

10th July 2024, 12:26

Just out of interest, how would I output a HLG version ??
I don't know

wyup

10th July 2024, 15:29

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

10th July 2024, 17:45

DMD

11th July 2024, 19:16

......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

11th July 2024, 20:16

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

11th July 2024, 21:27

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

12th July 2024, 03:54

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

12th July 2024, 04:44

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

12th July 2024, 05:05

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

13th July 2024, 09:34

guest

13th July 2024, 10:22

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

13th July 2024, 11:41

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

13th July 2024, 12:09

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

13th July 2024, 12:17

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

13th July 2024, 12:26

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

13th July 2024, 14:02

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

13th July 2024, 14:05

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

13th July 2024, 14:10

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

13th July 2024, 14:10

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

13th July 2024, 14:12

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

13th July 2024, 14:24

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

13th July 2024, 15:04

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

13th July 2024, 15:27

This is my 3 chunks template:
https://mega.nz/file/QmUBCaAZ#1QDYp9PvO_1oQkMEaqLMr7gbta3qiirykD_K82TCGh8

:thanks: :)

guest

14th July 2024, 07:56

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

14th July 2024, 13:05

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

14th July 2024, 14:24

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

14th July 2024, 15:43

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

14th July 2024, 16:19

.......
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

14th July 2024, 16:26

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

15th July 2024, 01:46

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)