Log in

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


Pages : 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

quietvoid
7th March 2024, 20:55
@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
8th March 2024, 00:19
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
8th March 2024, 09:42
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
8th March 2024, 10:08
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
8th March 2024, 13:03
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
8th March 2024, 13:05
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
8th March 2024, 13:27
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
8th March 2024, 14:18
No idea, never tried... Configuring a plex server on your PC is easy and much more practical than using a USB drive.

Gatorman3385
9th March 2024, 19:56
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
9th March 2024, 20:01
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
10th March 2024, 00:01
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
10th March 2024, 00:05
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
10th March 2024, 19:05
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
11th March 2024, 19:40
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
11th March 2024, 22:37
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
11th March 2024, 23:40
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
12th March 2024, 00:00
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
12th March 2024, 00:09
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
12th March 2024, 00:10
Instead of going from hev1 to dvhe, do the opposite.


must be dvhe for 2018 LG OLEDs.

guest
12th March 2024, 00:21
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
12th March 2024, 01:01
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
12th March 2024, 01:27
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
12th March 2024, 01:37
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
12th March 2024, 01:48
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
12th March 2024, 11:04
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
12th March 2024, 13:00
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
12th March 2024, 13:07
This is the small error msg:-

did you install vapoursynth and python

Kuler087
12th March 2024, 13:09
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
12th March 2024, 13:30
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
12th March 2024, 13:31
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
12th March 2024, 20:18
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
13th March 2024, 00:20
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
13th March 2024, 01:50
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
13th March 2024, 02:18
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
13th March 2024, 02:30
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
13th March 2024, 02:39
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
13th March 2024, 05:35
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
13th March 2024, 13:59
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
13th March 2024, 14:29
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
13th March 2024, 14:35
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
13th March 2024, 14:40
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
13th March 2024, 14:46
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
13th March 2024, 14:49
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
13th March 2024, 14:53
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
13th March 2024, 15:03
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
13th March 2024, 21:45
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
13th March 2024, 22:25
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
14th March 2024, 08:18
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
14th March 2024, 12:03
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
14th March 2024, 13:22
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.