www.makemkv.com

ragico wrote: Thu Sep 04, 2025 10:30 pm @quietvoid
Will you implement AV1 codec support in your excellent dovi tool?

Eventually, very busy these days.

kazuma wrote: Sat Feb 22, 2025 3:28 pm what is better? a good 2160p DV webrip or 1080P remux file? Which one you guys will prefer?

Whichever is HDR.

Yeah, saw your patch there, thanks. What problem is it solving if the output RPU doesn't include the frame indices, and therefore doesn't care whether the shots start at 0 or at 86400 as long as the numbers are sequential?


It matters only for the generation code because the rest of the code ...

nekno wrote: Mon Jan 27, 2025 4:30 amSo, not clear on why it mattered for HDR10+ -> DV generation.

HDR10+ does have scene length, start indices. See https://github.com/quietvoid/dovi_tool/ ... 87b715344f

This title has authoring problems so the Dolby Vision might have issues on playback depending on how your device reacts.
Because the 2 videos have different timestamps, MakeMKV causes missing metadata for a lot of frames.

Hmm, that's strange. I wonder what it is then? Maybe there are multiple cases where RPU ends up incomplete? I'll make a bug report post one day if I have time and figure out the pattern. Do you know if quietvoid uses makeMKV and could advise at all?


There have been many different issues in the ...

Still, I don't understand how it is possible to change MDL or MaxCLL/FALL without re-encoding the video, but if it doesn't practically impact playback at all i think I'll get over this thought.


It's just SEI in the bitstream.

There's been some other people asking me for a tool to do it, and I ...

afarvvik wrote: Thu Feb 29, 2024 10:15 am could you please provide a link, it is not on the github page & googling did not help. thanks.

There are currently no Linux ARM64 builds.
Build it yourself.

RESET_9999 wrote: Wed Jan 10, 2024 5:11 pm thanks for confirming, it makes sense.

What is the internal config for tmax in our C2

It's apparently 810 nits AFAIK. 990 nits for the G2.
Mine measures around 815-825 nits IIRC.

I dont know much about calibration (i paid someone to calibrate my TV) but maybe in TV-LED, only the internal TV DV configuration is used and the EDID target brightness is ignored?? And the EDID is only useful to the player when it does LLDV?

That would explain the odd result I see when I use ...

Since it plays fine in players I doubt Arrow would do anything about it.

MakeMKV is pretty strict with timestamps when merging Dolby Vision tracks into one, where it drops a lot data if the two videos don't match as they should.
It shouldn't be dropping anything when possible but not much that can ...

The disc has authoring issues. It seems the timestamps in the m2ts are different for both tracks, but the underlying bitstreams have the same timestamps.
So when MakeMKV remuxes, it uses/copies the container TS which are wrong.

You can get broken timestamps by remuxing the m2ts with MKVToolNix as ...

RESET_9999 wrote: Tue Oct 24, 2023 11:22 pmNot true TV-LED and no 24fps support.

The new stick 4K Max 2nd edition (2023) does do 24 fps now.
But not much has changed otherwise, though others report all lossless passthrough to work with Kodi.

According to Plex it's supposed to support DTS too.

danbez wrote: Thu Sep 21, 2023 10:19 pm @quietvoid, can you explain your method ? Or send a link where I can learn about it? Thanks!

I don't provide support, it's in VapourSynth: https://github.com/OpusGang/awsmfunc/bl ... e.py#L1905

Did you check the whole clip ?? its just some random frame that flashes. The first flash happens at frame 68.
if yes then I don't see how its possible and why its happening ONLY with the transformers movies. As I said I checked hundred of movies with the same avs script.


Yes I see them with ...