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

[Kuler087]

only minor changes so far, no changelog yet

Originally Posted by Kuler087

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

Originally Posted by 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 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]

Originally Posted by 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

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]

Originally Posted by Gatorman3385

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.

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 I have. I even have one dedicated to my temp folder so any remuxing/demuxing is crazy fast (1-2gb/s)

Originally Posted by Kuler087

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

Originally Posted by TDS

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

Originally Posted by Kuler087

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]

Originally Posted by TDS

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.