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

[quietvoid]

AV1 isn't supported by dovi_tool. Only the internal library can handle AV1 RPUs for use in other software.

[Kuler087]

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

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

Just a comeback on this issue. It turns out that the problem was the avs_libplacebo(2023-06-27) I was using.

https://slow.pics/c/88LnYnGa (ps The comparison has HDR metadata and can be viewed in HDR on browser that supports it like Chrome)

It doesn't matter for the encoding workflows because they now use vapoursynth but it does matter for the screenshots workflow (7-2) when you work with P5 files.

Just replace replace your libplacebo with this one: https://drive.google.com/file/d/1DgsKbK92So5KZVU15zC2-qN_tVeqZ_Bj/view?usp=drive_link

This means you can use the old script version if you prefer avisynth for frameserver for whatever reason.

[frandan]

Hi Kuler excuse me but i have another question: i ripped 1000 frames from a movie for testing. Would i inject the rpu referred to this 1000 frames? How can i extract these metadata only for 1000 frames? Can Dovi Scripts help me?

EDIT: I tried with mkvtoolnix with split-parts: Is it a possible way?

[Kuler087]

I'm not sure I understand what you're trying to do. When you just want to read the metadata from a specific frame, you just have to extract the whole rpu and then input it in 2-2 which will ask you if you want to check a specific frame.

[frandan]

Excuse me: What i wrote isn't really comprehensible.
I try to explain better: I ripped 1000 frames from BL (HDR10) trimming with avisynth.
Now i would inject the DoVi metadata in this 1000 frames and i suppose that i should extract dovi metadata for this 1000 frames.
Is it correct?

[Kuler087]

Inject the metadata in the original/whole file and then split it with mkvtoolnix if you want to keep the RPU in sync.

If you split the first 1000 frames of a video and then inject the original RPU, it will be fine and dovi_tool will remove the extra frames at the end.
But if you split some random 1000 video frames in the middle of a movie, you have to also trim the RPU exactly the same to match the splitted video.

[frandan]

Thank you again.
My idea was to trim the EL via mkvtoolnix and then i extract the rpu from trimmed EL.
In this way i hoped to do some test without full encoding
I'll do how you suggest or i'll take frames at the beginning of the movie
Bye

[TheHooligan95]

I think you're a fantastic person and I wish I could have even a tenth of your knowledge. Thanks for your work, OP. Truly.

For anyone noob like me (I learnt today everything I know about DV), I didn't really understand the installation instructions. Here's what I did that ended up making it work on Windows 11.

1) Created a folder in the root of a different hard drive from C: e.g. D:\doviscripts\
2) Download latest dovi scripts and then dovi scripts beta aswell from the github and put them into the dovitools folder.
3) created a tools folder within dovitools
4) downloaded https://forum.doom9.org/showthread.php?t=183479 and copied the contents of the tools folder inside the tools folder
5) downloaded and installed all things pointed out in the github.
6) copied and pasted all files from all things installed from the github also inside the tools folder, just to be sure
7) added both user and system paths to all things installed from the github, as specified here https://github.com/R3S3t9999/DoVi_Scripts/blob/main/TOOLS%20%26%20INSTALLATION (of course, not to the tools folder but to their og folders, and I skipped DEE because you can't download it if you're not in the business of making movies)
8) downloaded and installed justdan96/tsMuxer from his github and put it inside the tools folder


I hope this will come in handy to any other desperate users like me. :thanks:

[guest]

Hi Kuler,

I grabbed this movie earlier today, and was surprised that MediaInfo stated it was a DV encode, but as it's was .mkv, I knew it wouldn't play on my LG, so I quickly ran it thru Mp4 muxer, and it changed completely, and doesn't display either HDR or DV on the LG, the original .mkv didn't display HDR either....what a mess, so I thought I'd share the before & after MediaInfo, info:-

So this is the original .mkv

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, Profile 8, dvhe.08.06, BL+RPU, no metadata compression
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 18 min
Width : 3 840 pixels
Height : 1 604 pixels
Display aspect ratio : 2.39:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Writing library : x265 3.5+1-f0c1022b6:[Linux][GCC 7.5.0][64 bit] 10bit
Encoding settings : cpuid=1111039 (tl:dr)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

And then to this after MP4muxer:-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 2 h 18 min
Bit rate : 5 998 kb/s
Maximum bit rate : 32.6 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Original height : 1 604 pixels
Display aspect ratio : 2.39:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.041
Stream size : 5.78 GiB (94%)
Writing library : x265 3.5+1-f0c1022b6:[Linux][GCC 7.5.0][64 bit] 10bit
Encoding settings : cpuid=1111039 (tl:dr)
Default : Yes
Alternate group : 1
Encoded date : 2024-04-10 05:41:53 UTC
Tagged date : 2024-04-10 05:42:11 UTC
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : hvcC

[Boulder]

The transfer characteristics is incorrect in both files so it's no wonder the HDR mode is not switched on.

[guest]

The transfer characteristics is incorrect in both files so it's no wonder the HDR mode is not switched on.

Yeah, I knew that had to be wrong... I just wanted to post this to show how some people just get it all wrong.

It'll be "fun" fixing it :)

[Kuler087]

I think you're a fantastic person and I wish I could have even a tenth of your knowledge. Thanks for your work, OP. Truly.


Thanks :)

FYI, I did an installation tutorial video last night:

https://www.youtube.com/watch?v=6SLtsVDse2w


Hi Kuler,

I grabbed this movie earlier today, and was surprised that MediaInfo stated it was a DV encode, but as it's was .mkv, I knew it wouldn't play on my LG, so I quickly ran it thru Mp4 muxer, and it changed completely, and doesn't display either HDR or DV on the LG, the original .mkv didn't display HDR either....what a mess, so I thought I'd share the before & after MediaInfo, info:-

So this is the original .mkv




Yeah, this is not common. Maybe someone attempted to make a profile 8.2 rip if that even possible ?

https://i.imgur.com/IpE40nt.png

[guest]

Yeah, this is not common. Maybe someone attempted to make a profile 8.2 rip if that even possible ?

I had a bit of a play with this mess, and I'm not going to waste anymore time on it, it's not worth it.

I did a quick conversion to BT2020, but it's looks crap, too dark, too red'ish.

I'll just get a better "proper" copy.

[guest]

Hi Reset,

I have a question about a couple of settings..

I have been editing GoT episodes, and I have them looking pretty nice as HDR, however, after I run them thru 3-1, the video is noticeably brighter, which basically negates the adjustments I made prior.

The original video is:-

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0020 cd/m2, max: 1000 cd/m2

and the DS DV encode is the same:-

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0020 cd/m2, max: 1000 cd/m2

So what option do I need to use here:-

BL Mastering Display Luminance and Colors:
min: 0.0020 cd/m2, max: 1000 cd/m2 BT.2020
------------------------------------------------

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

I've been using.. 1000nits-BT2020= 21

I'm still using 2.0.3, not that that should matter with this.

Maybe a simple solution might be to not do any colour/brightness changes beforehand (with these files, anyway)..I guess I'll figure out what needs to be done before the DS DV conversion.

Regards

[Kuler087]

Yes you should always match your source mastering luminance and primaries so 21 is correct. Generataed DV is just brightness metadata for tone mapping, it doesn't touch the colors like the L2-L8 trim pass can do.
Maybe your TV is like my old LG C8 where OOTB, DV looked so much brighter than HDR10 regardless of the content.

PS This show already has DV, why are you generating DV?

[guest]

Yes you should always match your source mastering luminance and primaries so 21 is correct. Generataed DV is just brightness metadata for tone mapping, it doesn't touch the colors like the L2-L8 trim pass can do.
Maybe your TV is like my old LG C8 where OOTB, DV looked so much brighter than HDR10 regardless of the content.

PS This show already has DV, why are you generating DV?

Thanks for the reply, so as a reference, moving forward, I will match the source with the options available.

I will have to compensate my color corrections, prior to running DS.

I generally like to reduce any redness, and maybe brightness, a little, more than anything.

Yes, I'm sure that GoT is available with DV, but the 4K copies I have are a little old, so I'll just convert them, thanks to DS :)

Cheers.

[Kuler087]

Instead of touching the BL , you could add some desaturation in the L2 trims like this:

change the duration("duration": 120000,) value to match your RPU framecount and run:
dovi_tool.exe generate -j X:\edits.json -o X:\P8_generated.bin

Then copy the generated L2 to your generated RPU from 3-1. You can do that with workflow 2-6


{
"cm_version": "V29",
"profile": "8.1",
"long_play_mode": false,
"source_min_pq": 7,
"source_max_pq": 3079,
"level5": {
"active_area_left_offset": 0,
"active_area_right_offset": 0,
"active_area_top_offset": 0,
"active_area_bottom_offset":0
},
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 20,
"max_content_light_level": 0,
"max_frame_average_light_level":0
},
"shots": [
{
"start": 0,
"duration": 120000,
"metadata_blocks": [
{
"Level1": {
"min_pq": 0,
"max_pq": 2081,
"avg_pq": 1229
}
},
{
"Level2": {
"target_max_pq": 2081,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1950,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2000,
"ms_weight": 2048
}
}
]
}
]
}

you can play the the trim_saturation_gain values. Values under 2048 desaturate.

[guest]

Instead of touching the BL , you could add some desaturation in the L2 trims like this:

change the duration("duration": 120000,) value to match your RPU framecount and run:
dovi_tool.exe generate -j X:\edits.json -o X:\P8_generated.bin

Then copy the generated L2 to your generated RPU from 3-1. You can do that with workflow 2-6


{
"cm_version": "V29",
"profile": "8.1",
"long_play_mode": false,
"source_min_pq": 7,
"source_max_pq": 3079,
"level5": {
"active_area_left_offset": 0,
"active_area_right_offset": 0,
"active_area_top_offset": 0,
"active_area_bottom_offset":0
},
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 20,
"max_content_light_level": 0,
"max_frame_average_light_level":0
},
"shots": [
{
"start": 0,
"duration": 120000,
"metadata_blocks": [
{
"Level1": {
"min_pq": 0,
"max_pq": 2081,
"avg_pq": 1229
}
},
{
"Level2": {
"target_max_pq": 2081,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1950,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2000,
"ms_weight": 2048
}
}
]
}
]
}

you can play the the trim_saturation_gain values. Values under 2048 desaturate.

:thanks:

Might take me a while to figure out how to do this ...

How do I check the RPU's framecount ?

[Kuler087]

input a rpu in 2-2

https://i.ibb.co/74VyCdj/Capture-d-cran-2024-04-24-085433.png

[guest]

input a rpu in 2-2

:thanks:

[guest]

OK, I have kind of figured out what to do with this, (I created the .json file) but you say to load the RPU from the original video, well, what if it isn't DV ?? where does the RPU come from ??

I run 3-1 to get the framecount (this test I'm doing had 7209 frames) it's a sample chunk generated with 8-5.


Which RPU level(s) do you want to copy and press enter... (Choices are 1 2 3 4 5 8 and you can select multiple values) ??

I used "8"..

Also, where do I change the trim_saturation_gain values ?, there's several to choose from (or all of them) ?

Can brightness/luminance be changed ?

Using 2-2 to check each .bin, (until there are any saturation changes, etc), they should be exactly the same ??

So once the "new" .bin is generated, how is it injected info the converted video ??

I'm thinking it might still be a better option to compensate for what DS does, with the previous adjustments..we'll see, I guess.

[Kuler087]

1- Generate DV with 3-1

2- create json with the framecount from the rpu generated in 3-1 step one
the json has three targets of metadata for Level 2 (not L8): 100(2081), 600(2851), and 1000nits(3079). You can use the json exactly as provided or edit it as much as you want.
Value under 2048 desaturates and usually, the 100nits trim has the stronger values followed by the 600 and 1000nits trims. The value at each target should be different for the interpolation to work properly.

3- run the cli to generate the RPU with L2 adjustments

4- Workflow 2-6, input 1 is rpu from step one and input 2 is the rpu from step 3. Select ''2''

5- inject the final rpu (the one with ''l2 copied'')


If you want to do the same for the CMv4.0 bloc (your tv is cmv2.9):

{
"cm_version": "V40",
"profile": "8.1",
"long_play_mode": false,
"source_min_pq": 7,
"source_max_pq": 3079,
"level5": {
"active_area_left_offset": 0,
"active_area_right_offset": 0,
"active_area_top_offset": 0,
"active_area_bottom_offset":0
},
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 20,
"max_content_light_level": 0,
"max_frame_average_light_level":0
},
"shots": [
{
"start": 0,
"duration": 120000,
"metadata_blocks": [
{
"Level1": {
"min_pq": 0,
"max_pq": 2081,
"avg_pq": 1229
}
},
{
"Level2": {
"target_max_pq": 2081,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 2851,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1950,
"ms_weight": 2048
}
},
{
"Level2": {
"target_max_pq": 3079,
"trim_slope": 2048,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 2000,
"ms_weight": 2048
}
},
{
"Level8": {
"length": 19,
"target_display_index": 1,
"trim_slope": 1950,
"trim_offset": 2048,
"trim_power": 2048,
"trim_chroma_weight": 2048,
"trim_saturation_gain": 1900,
"ms_weight": 2048,
"target_mid_contrast": 2048,
"clip_trim": 2048,
"saturation_vector_field0": 128,
"saturation_vector_field1": 128,
"saturation_vector_field2": 128,
"saturation_vector_field3": 128,
"saturation_vector_field4": 128,
"saturation_vector_field5": 128
}
}
]
}
]
}

[guest]

1- Generate DV with 3-1

2- create json with the framecount from the rpu generated in 3-1 step one
the json has three targets of metadata for Level 2 (not L8): 100(2081), 600(2851), and 1000nits(3079). You can use the json exactly as provided or edit it as much as you want.
Value under 2048 desaturates and usually, the 100nits trim has the stronger values followed by the 600 and 1000nits trims. The value at each target should be different for the interpolation to work properly.

3- run the cli to generate the RPU with L2 adjustments

4- Workflow 2-6, input 1 is rpu from step one and input 2 is the rpu from step 3. Select ''2''

5- inject the final rpu (the one with ''l2 copied'')

Oh, RPU's are the .bin files.

Step #2 (have no idea what that's about)

OK, I'm good 'til step #5...what workflow do I use to inject ??

I haven't done these steps before, so I'm a little lost :(

Sorry.

[Kuler087]

you inject the final rpu with 1-1

[guest]

you inject the final rpu with 1-1

:thanks:

[guest]

If I have a DV movie that I want to filter, etc with RipBot264, and I extract the RPU.bin beforehand, then inject it after the filtering etc, would it be compatible ??

Not really wanting to do any Resolve fiddle.

Also, earlier today I started 3-1'ing an edited episode of GoT, and it was going to take, I'm guessing at least 3 - 4 hours to convert, I think I know why, but I had to stop it part way thru, just WAY TOO LONG :(

I was using CUDA on an RTX3060 (not fast enough), but would the 7950X or the 13900KF be faster than CUDA ??

Shame :(

[Kuler087]

If I have a DV movie that I want to filter, etc with RipBot264, and I extract the RPU.bin beforehand, then inject it after the filtering etc, would it be compatible ??
Depends on what filtering you do. If you change blacks or brightness, the metadata are no longer valid.

Not really wanting to do any Resolve fiddle.
Also, earlier today I started 3-1'ing an edited episode of GoT, and it was going to take, I'm guessing at least 3 - 4 hours to convert, I think I know why, but I had to stop it part way thru, just WAY TOO LONG
I was using CUDA on an RTX3060 (not fast enough), but would the 7950X or the 13900KF be faster than CUDA ??

CM_analyze is inconsistent and there's nothing we can do about it. Resolve (or MACos?) is the only other option.

[Gatorman3385]

CM_analyze is a great option if you don't own Resolve. However, using Resolve to generate DV was enough for me to make it a worthy investment.

Am I correct that CM_analyze is more consistent with Intel + CUDA than with AMD + CUDA?

[Kuler087]

supposedly

Am I correct that CM_analyze is more consistent with Intel + CUDA than with AMD + CUDA?

[jayper]

Reset, are these the steps you followed to get your Ugoos up and running? https://discourse.coreelec.org/t/guide-ugoos-am6b-coreelec-installation/51231

It looks like my device is set to be delivered today!

[Kuler087]

Yes, except that I'm still using an old 20.5 build because I have some movies that won't resume in v21.

[jayper]

Yes, except that I'm still using an old 20.5 build because I have some movies that won't resume in v21.
Thank you so much!

[Balthazar2k4]

Is it possible to batch process the 8-2-3 ProRes workflow? I would like to queue up some titles to convert to ProRes overnight so that I can run them through Resolve that next day.

[Kuler087]

You can use Staxrip for that. Here's my prores template: https://drive.google.com/file/d/1KUsOsSS-4NnXhDxqJMF4yOCwtprfZkxZ/view?usp=sharing
Put it in StaxRip\Settings\Templates

[Balthazar2k4]

Awesome! Much appreciated! I'll give it a try.

[jayper]

When you want to create a ST-DL MKV from a disc with FEL/MEL, what process do you recommend? Rip with MakeMKV, or with MKVToolNix? I am particularly curious about discs with seamless branching? I used to demux everything with TSMuxer first, now I am not so sure if there's a better/recommended route.

[Kuler087]

I've always used tsmuxer to demux the audio from seamless branching discs. Then mkvtoolnix to mux the video + demuxed audio + subs.
dgdemux or the latest eac3to might be even better, I don't know but I never had issues using tsmuxer on my x800m2. So far so good on the Ugoos but I'm not sure if I've watched a SB rip yet.

[jayper]

I've always used tsmuxer to demux the audio from seamless branching discs. Then mkvtoolnix to mux the video + demuxed audio + subs.
dgdemux or the latest eac3to might be even better, I don't know but I never had issues using tsmuxer on my x800m2. So far so good on the Ugoos but I'm not sure if I've watched a SB rip yet.
Thanks, appreciate the response and the perspective. I'll give that a try. I also had great luck with tsmuxer and my Oppo, so I was inclined to stick with it.

[jayper]

The only times I generate DV for a movie that has retail DV are:

1- static L1 and L2. (Static L1 + dynamic L2 is fine.)
2- P5 web-dl is a different grade and cant be injected into the bluray
3- The original DV was done in cmv2.9(2.5nits avg floor) without any manual trims
4- if the bluray is cmv2.9 MEL and web is 4.0, I injected the web metadata like in: Aquaman and the Lost Kingdom, Migration.2023, Wonka.2023, The.Hunger.Games.The.Ballad.of.Songbirds.and.Snakes.2023
Why? because cmv2.9 content has crushed/clipped black and cmv4.0 does not. It also has better tone mapping.


PS Ugoos AM6B+ has arrived and looks VERY promising: https://www.youtube.com/watch?v=4QUURfLy5ew

I'm guessing that all the Star Wars D+ shows fall into this camp. Spot-checked a few Andor episodes and it looks like static L2. Thinking about generating DV using cm4.0 and the newly released discs.

[Kuler087]

No, Andor is not static, at least not in this episode:

https://i.ibb.co/fCxJmwV/Star-Wars-Andor-S01-E02-That-Would-Be-Me-2160p-DSNP-WEB-Do-Vi-L2-PLOT-600nits-trim.png

[jayper]

OK, good to know. I was clearly looking in the wrong place. Thanks!

Also, curious to know if this warning is anything to be concerned with:

plugin_manager: ←[33;1mWARNING←[0m ←[Kplugin does not contain dlb_plugin_file_io_init_v1

[Kuler087]

You can ignore it.

[jayper]

Thank you so much!

[TheHooligan95]

sometimes ffmpeg gives me (running the script in 4-1 mode), during the first part of the process:

Application provided invalid, non monotonically increasing dts to muxer in stream 0: (number)>=(number)

It seems to depend on sync issues of the source (framerate?). The result will infact have audio and subtitles out of sync with the video, which will anticipate the audio and the subs. Asked on ffmpeg irc and almost got laughed at, they told me that it would be much easier to make dovitools better than to make ffmpeg fix this :(

[Kuler087]

You can disable ffmpeg piping when it causes issues.

line 171
set ffmpeg_pipe=YES

[guest]

Hi Reset,

I updated to 2.0.5, and downloaded the newer tools.7z, etc, yesterday, got everything sorted out (didn't want to overwrite anything in the 2.0.3 folders.

And it's performing well, but I just wanted to tell you of a strange thing that happened when attempting a 5 minute chunk with 8-5 (I think)...

I had 4 movies I wanted a chunk of, and this one movie "Kate & Leopold", threw up some really strange errors msg's, and would fail...

Part of the error msg was Leopold, so I changed the name, and it showed the same error, so I shortened the name even more, same msg, so I decided to run it thru MKVToolNix, stripped out everything I didn't want, the error msg was not displayed, and I got my chunk....so there must have been something DS didn't like.

BTW, is there a simple way to change the 5 minute chunk to something a little shorter, like 2 minutes ??

Cheers

[Kuler087]

The only change is the mkvtoolnix files are in a separate folder so you probably had the same MSG in the previous version. You can provide a sample and I'll have a look.
You can change the 8-5 sample timestamp at line: 125

:: choose the timestamp for the sample maker workflow (8-5) (default=5m)
set timestamp=00:00:00-00:05:00

[guest]

The only change is the mkvtoolnix files are in a separate folder so you probably had the same MSG in the previous version. You can provide a sample and I'll have a look.
You can change the 8-5 sample timestamp at line: 125

Yes, I'm sure I would have had the same error...this movie in question had many subtitles..it must have something to do with one of them...problem has been solved, I don't really think there's any need to provide a sample..unless you really want one !

I'd have to do it MKVToolNix.

:thanks: for the tip on the chunk size :)

[jayper]

Did you install avisynthplus?

https://github.com/AviSynth/AviSynthPlus/releases/download/v3.7.3/AviSynthPlus_3.7.3_20230715.exe

If it's for a profile 5 webdl, your GPU must support Vulkan.

Sorry, all is well. I mistakenly had a space in my new install folder location. I deleted my prior comment, hoping that you wouldn't have seen it.

[jayper]

Sorry to ask this here, but I haven't been able to find a clear answer on the CoreELEC forums. For the Ugoos AM6b+, I understand that the device hardware is fixed at outputting a rec709 flag.

But there are two options presented to change this via ssh:

echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_no_colorimetry
echo Y > /sys/module/hdmitx20/parameters/dovi_tv_led_bt2020

I have an older TV, TCL 65R617 (2018 Model), is it best to send out no colorimetry flag? Or send bt2020? It sounds like newer TVs it doesn't matter, but I was curious if you had thoughts on this? Appreciate your time!