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

guest

18th June 2024, 00:14

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

18th June 2024, 01:30

You can't go wrong with LG C or G series.
I have an LG C2 77'' and I love it.

guest

18th June 2024, 01:36

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

18th June 2024, 02:16

Samsung is not Dolby Vision friendly. They're HDR10+ only.

guest

18th June 2024, 02:40

Samsung is not Dolby Vision friendly. They're HDR10+ only.

Yes, I have found that...

Seems only LG & some Sony's are...

Kuler087

18th June 2024, 03:14

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

18th June 2024, 08:41

guest

18th June 2024, 09:01

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

18th June 2024, 11:48

I love my g2 77.

Sent from my SM-S928U1 using Tapatalk

guest

19th June 2024, 03:38

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

19th June 2024, 11:57

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

19th June 2024, 12:11

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

19th June 2024, 12:18

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

19th June 2024, 12:25

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

19th June 2024, 13:06

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

20th June 2024, 06:41

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

25th June 2024, 04:51

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

25th June 2024, 11:56

NEW mp4muxer mode is faster and preserves the BL compatibility ID when muxing subtitles/lossless audio.

CineManiac

26th June 2024, 23:12

Kuler087

26th June 2024, 23:18

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

26th June 2024, 23:49

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.

26th June 2024, 23:49

Kuler087

26th June 2024, 23:52

@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

2nd July 2024, 11:18

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

2nd July 2024, 12:15

You have to generate the metadata (json) in Resolve and then you can inject with workflow 1-1

Black Ops

2nd July 2024, 13:50

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

2nd July 2024, 14:07

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

Black Ops

2nd July 2024, 17:17

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

2nd July 2024, 17:38

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

2nd July 2024, 20:35

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

2nd July 2024, 21:48

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

3rd July 2024, 16:25

rwill

3rd July 2024, 17:16

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

3rd July 2024, 17:18

I could be wrong but I think they have fees to pay to use HDR10plus on bluray and streaming

Black Ops

3rd July 2024, 19:25

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

3rd July 2024, 22:40

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

4th July 2024, 00:01

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

4th July 2024, 08:23

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

4th July 2024, 11:47

sometimes detectborder doesnt work. It's always better to do it manually.

guest

5th July 2024, 02:06

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

5th July 2024, 02:48

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

5th July 2024, 06:15

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

5th July 2024, 12:00

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

6th July 2024, 03:05

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

6th July 2024, 04:06

try the latest beta

guest

6th July 2024, 04:09

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

6th July 2024, 04:11

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

6th July 2024, 04:18

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

6th July 2024, 07:51

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