Dolby Vision now possible through MP4 Mux.

[coopzr]

2. static tone mapping is used on top of the dynamic metadata in DV. A 4000nits MDL looks much darker than a 1000nits MDL with the same dynamic metadata. Also, with a 4000nits MDL, Level 1 starts dimming with lower values. It starts at 400nits on my C2 while with the 1000nits MDL, it starts dimming only at 850nits.

I think I understand what you are saying. However, can you please elaborate on my question? Is mediainfo simply wrong sometimes or is there a technical reason that 'mastering display color primaries' and 'mastering display luminance' should be ignored?

[RESET_9999]

Is mediainfo simply wrong sometimes

mediainfo is ok and there's nothing wrong in grading 200nits (for example) on a 4000 monitor. You can use the original MDL if you doubt my reason, it's fine.

is there a technical reason that 'mastering display color primaries' and 'mastering display luminance' should be ignored?

No other reason than the one I already told you.

A 4000nits MDL looks much darker than a 1000nits MDL with the same dynamic metadata

[darrrkmanxxx]

Hey guys,

at which step davinci rersolve does a bad job with hevc?

Scene detection or the analyzing itself?

[RESET_9999]

both

[nekno]

Hey guys,

at which step davinci rersolve does a bad job with hevc?

Scene detection or the analyzing itself?

IME, it isn't the scene detection or CM analysis, per se, it's that the frames are decoded inaccurately from the start, so bad data is fed to both algorithms, making both inaccurate as a result. Garbage in, garbage out.

In my testing, the HEVC decoding in Resolve was inserting additional frames, so as a result the scene starts and durations were all inaccurate, not because the scene detection algo is bad, but because (as you can see when scrubbing through the video) the scenes actually do start and end at inaccurate frames. And the DV CM algo is based on scenes and frames, so if it doesn't get accurate data, it's going to start and stop scenes at inaccurate times.

For example ---

3 actual scenes:
(1) Start frame: 0, Duration: 100; (2) Start frame: 100, Duration: 100; (3) Start frame: 200, Duration: 100

Resolve-decoded HEVC:
(1) Start frame: 0, Duration: 101; (2) Start frame: 101, Duration: 103; (3) Start frame: 204, Duration: 100

So all the scenes in the DV metadata start sliding later by a couple/few frames each time another frame decoding error is introduced (in scenes 1 & 2).

[darrrkmanxxx]

Hey guys,

at which step davinci rersolve does a bad job with hevc?

Scene detection or the analyzing itself?

IME, it isn't the scene detection or CM analysis, per se, it's that the frames are decoded inaccurately from the start, so bad data is fed to both algorithms, making both inaccurate as a result. Garbage in, garbage out.

In my testing, the HEVC decoding in Resolve was inserting additional frames, so as a result the scene starts and durations were all inaccurate, not because the scene detection algo is bad, but because (as you can see when scrubbing through the video) the scenes actually do start and end at inaccurate frames. And the DV CM algo is based on scenes and frames, so if it doesn't get accurate data, it's going to start and stop scenes at inaccurate times.

For example ---

3 actual scenes:
(1) Start frame: 0, Duration: 100; (2) Start frame: 100, Duration: 100; (3) Start frame: 200, Duration: 100

Resolve-decoded HEVC:
(1) Start frame: 0, Duration: 101; (2) Start frame: 101, Duration: 103; (3) Start frame: 204, Duration: 100

So all the scenes in the DV metadata start sliding later by a couple/few frames each time another frame decoding error is introduced (in scenes 1 & 2).

got it. I really appreciate your explanation.
Honestly I'm getting exactly the same behavior with Prores422 on macos in resolve when I let it do it the background while working with other apps.
I have radeon 6900 xt 16gb vram as gpu.
Resolve only does it's job when I leave the computer completely untouched. So resolve is very unreliable in that way.

[darrrkmanxxx]

Is there any release group that does proper fel baked hdr12 remuxes?

[RESET_9999]

Baking FEL requires re-encoding so what you're asking is not possible.
An untouched FEL remux can only be played properly on a device that can decode it.

Just get the Ugoos if you want the best quality without compromise.

[nekno]

Honestly I'm getting exactly the same behavior with Prores422 on macos in resolve when I let it do it the background while working with other apps.
Resolve only does it's job when I leave the computer completely untouched. So resolve is very unreliable in that way.

That's odd. Once transcoding to ProRes I haven't had any issues with Resolve on Windows or macOS, but can't say whether I specifically foregrounded another app. I definitely did while transcoding with FFMPEG, but that's it.

[valington]

Baking FEL requires re-encoding so what you're asking is not possible.
An untouched FEL remux can only be played properly on a device that can decode it.

Just get the Ugoos if you want the best quality without compromise.

Reset which workflow for container mkv p5 profile dolby vision to make container mp4 p5 profile dolby vision

[RESET_9999]

all the workflows are explained on the github or doom9 website...

https://forum.doom9.org/showthread.php?t=185317

MODE.B (5) =
BATCH MUXER

Can batch mux any DV source to TS or MP4
MKV/MP4 to TS
MKV/TS to MP4

[powdeau]

If a video has this static metadata,

would it be more accurate to watch it on G4 in HDR10

or in generated DV?

[RESET_9999]

low nits dolby vision metadata like this won't have any effect on a bright TV like the G4 so it doesn't matter.

[staknhalo]

in case anyone didn't hasn't noticed - hdr10plus tool now has an editor like dovi_tool for syncing/adding/removing metadata - thanks quietvoid

[Donpoku]

low nits dolby vision metadata like this won't have any effect on a bright TV like the G4 so it doesn't matter.

Hi with coreelec cpm test build which option allows L5 metadata & can still see osd/subtitles on an old lg c6. I.e source, 0 etc. I tried few of those options but can't get osd to show.. and do we still need autostart.sh cmd? Thanks.