Dolby Vision now possible through MP4 Mux.

[sw5163]

You may also wanna answer sergonnn111's question? He's been asking a several times.

yeah I don't answer those questions anymore
All he has to do is to check the Playback Device sheet in my signature.

Right, @sergonnn111 maybe do more research before asking? I actually tested all profiles and codecs I could think of before posting the Apple MEL thing. I even tried to hybrid a p5.dvh1 and concat a FEL track to it to see if Apple indeed doesn't support FEL, LOL.

[RESET_9999]

concat a FEL track to it to see if Apple indeed doesn't support FEL, LOL.

yep, i tried that too in the Windows 10 app LOL.

about mp4box, I wonder if we should use:

-brand mp43isom -ab dby1

I have no idea what it does but i always used it with mp4box. I got that from yusesope a long time ago i think.

[sw5163]

about mp4box, I wonder if we should use:

-brand mp43isom -ab dby1

I have no idea what it does but i always used it with mp4box. I got that from yusesope a long time ago i think.

I don't know what that is either. I never used them, but seems everything is fine so far.
I like to use as few command as possible and left other things I don't know for the tool to decide.
I actually have tried yusesope's tool back in 2020. Back then there is no way to "remove_mapping" so I got green screen on iPad. But I knew DV on Apple is possible, it's just we didn't know how to modify RPU yet. Just like we just don't know how to do PCM/atmos now.
Look how far we've come from there.

update: they set the brand of file, so I don't think they will affect final image.

屏幕截图 2022-07-18 203947.png (19.5 KiB) Viewed 11183 times

[sw5163]

i tried:
-map 0:AUDIO_STREAM_ID -c pcm_s24be -ar 48000 -rf64 auto \path\to\audio.mov
and
-map 0:AUDIO_STREAM_ID -c pcm_s24le -ar 48000 -rf64 auto \path\to\audio.mov

How do you decide what pcm encoder to use?
My logic here is ffmpeg show:
Stream #0:2[0x1100]: Audio: truehd (AC-3 / 0x332D4341), 48000 Hz, 7.1, s32 (24 bit)
s̶3̶2̶ ̶(̶2̶4̶ ̶b̶i̶t̶)̶ ̶I̶ ̶t̶a̶k̶e̶ ̶t̶h̶a̶t̶ ̶a̶s̶ ̶2̶4̶ ̶b̶i̶t̶ ̶a̶u̶d̶i̶o̶ ̶+̶ ̶8̶ ̶b̶i̶t̶ ̶a̶t̶m̶o̶s̶
S̶o̶ ̶w̶o̶u̶l̶d̶ ̶i̶t̶ ̶b̶e̶ ̶c̶o̶r̶r̶e̶c̶t̶ ̶t̶o̶ ̶u̶s̶e̶ ̶p̶c̶m̶_̶s̶2̶4̶l̶e̶ ̶o̶r̶ ̶p̶c̶m̶_̶s̶3̶2̶l̶e̶?
Use pcm_s24le (little endian for compatibility)
If we are going to lose atmos anyway.

If we don't set -ar 48000 manually, will it chose proper sample rate automatically?
Also may I ask what does -rf64 auto mean?
Okay, found it:https://en.wikipedia.org/wiki/RF64

[RESET_9999]

i tried:
-map 0:AUDIO_STREAM_ID -c pcm_s24be -ar 48000 -rf64 auto \path\to\audio.mov
and
-map 0:AUDIO_STREAM_ID -c pcm_s24le -ar 48000 -rf64 auto \path\to\audio.mov

How do you decide what pcm encoder to use?
My logic here is ffmpeg show:
Stream #0:2[0x1100]: Audio: truehd (AC-3 / 0x332D4341), 48000 Hz, 7.1, s32 (24 bit)
s32 (24 bit) I take that as 24 bit audio + 8 bit atmos
So would it be correct to use pcm_s24le or pcm_s32le? (little endian for compatibility I think)
If we are going to lose atmos anyway.

If we don't set -ar 48000 manually, will it chose proper sample rate automatically?
Also may I ask what does -rf64 auto mean?

I have no idea, I ended up using your command line in my script. I'm really not an expert with audio encoding.

I got those cmd lines from yusesope as well:
https://mrmc.tv/forum/viewtopic.php?f=1 ... &start=310

[Mithrandir]

Hello, I've tried latest DoVI scripts (1.4.6).

Did the following:
1. Extracted all scripts and tools to C:\Temp\Dovi_Scripts
2. Commented out Dolby Encoder because I don't have it (line 59) ::set DEE_path=D:\other\DEE5.2.0\dee.exe
3. set tsmuxer.popup=YES and mkvtoolnix.popup=NO
4. Started .bat file and pointed it to network share

I did the following workflow 1-7-2-2

What happened is that whole TEMP folder was completely deleted.
This was an error message:
The process cannot access the file because it is being used by another process.
The system cannot find the path specified.

I didn't have anything critical in Temp folder so complete disaster was avoided (thank god I didn't run it from Program files).

But why it did delete the folder below where scripts are run (it also deleted scripts and folder itself).

[RESET_9999]

Hello, I've tried latest DoVI scripts (1.4.6).

Did the following:
1. Extracted all scripts and tools to C:\Temp\Dovi_Scripts
2. Commented out Dolby Encoder because I don't have it (line 59) ::set DEE_path=D:\other\DEE5.2.0\dee.exe
3. set tsmuxer.popup=YES and mkvtoolnix.popup=NO
4. Started .bat file and pointed it to network share

I did the following workflow 1-7-2-2

What happened is that whole TEMP folder was completely deleted.
This was an error message:
The process cannot access the file because it is being used by another process.
The system cannot find the path specified.

I didn't have anything critical in Temp folder so complete disaster was avoided (thank god I didn't run it from Program files).

But why it did delete the folder below where scripts are run (it also deleted scripts and folder itself).

yeah do not place the dovi_scripts folder into a folder named TEMP because the script will always delete it. The script make a folder called TEMP for the temporary file in the same drive you place the doviscript folder and when the script is done, it delete the temp folder.

C:\Dovi_Scripts or C:\folder.not.named.temp\Dovi_Scripts

(thank god I didn't run it from Program files).

lol

[Mithrandir]

yeah do not place the dovi_scripts folder into a folder named TEMP because the script will always delete it

I've read the source of the script and seen that it's hardcoded to temp folder for every workflow.
I think you should put disclaimer in the readme that temp folder will be erased.

And it would be great if temp folder could be parametrized like output folder

[RESET_9999]

And it would be great if temp folder could be parametrized like output folder

sure, i can do that.

[RESET_9999]

The only problem I see with this method is that the static MDL metadata seems messed up now.

What's that? Will that cause a problem in DV play? If it doesn't affect final image, I wouldn't bother to change it.

Mastering display luminance : min: 19.6608 cd/m2, max: 4000 cd/m2
MasteringDisplay_Luminance_Original : min: 0.0050 cd/m2, max: 4000 cd/m2

Use hdr=none when muxing.

Unfortunately, "hdr=none" cause the LPCM audio to play as stereo so I guess Apple users will have to live with the messed-up static MDL.
the ATV is REALLY picky!!!

[RESET_9999]

I think I found a huge bug on the x700/ x800m2 / C2, even worse than the red push or the lack of FEL support
The L1 brightness changes are totally different than the C2 internal plex and the Shield(which have newer DV engine) but L2 looks exactly the same on all the devices.
By different I mean they are much much less noticeable on the x700/ x800m2 . like 400% difference, no exaggeration. Even less noticeable than Windows 10 HDR10 P8 playback lol.

If you take the out-of-sync version of the Spears and Munsil clip, because the trim passes are active with L1 at the same time, you can barely see a difference between all the devices.
But if you strip out the trims by generating new metadata with madVR (just L1), then again a big difference in the L1 brightness changes.
Tried MP4 / TS, and it makes no difference.cmv2.9, cmv4.0, old mp4muxer, new mp4muxer.

maybe the newer DV engine of the C2/shield vs the older one from x700/x800m2 cause the issue?
I guess I have to connect my old C8 to find out...

pattern to reproduce:
quietvoid's rpu test: https://drive.google.com/file/d/1hAv4eJ ... sp=sharing
SM clip out of sync original: https://drive.google.com/file/d/1BxsK7- ... sp=sharing
SM clip out of sync no L2 (madvr): https://drive.google.com/file/d/1CuWlHK ... sp=sharing

########################################################################################################################
EDIT: no issue on the C8 + x700/x800m2 vs internal player, L1 changes as pronounced as on the C2/shield.
so it looks like there's something going on when using a CMv2.9 HDMI device to a CMv4.0 TV... Or maybe just something with my C2, I hope people with C1,CX will do the same test
I guess I just lost fel and lossless audio support

bug confirmed on:
LG C2 + x700 + x800m2
LG G2 + oppo: viewtopic.php?p=124746#p124746
LG C1 + x800m2: viewtopic.php?p=124868#p124868
LG C9 + x700: viewtopic.php?p=124959#p124959
Sony X900H + x800m2 https://www.avsforum.com/threads/offici ... t-61832553


videos showing the L1 issue on LG C2:
https://www.youtube.com/watch?v=TJtwu1bwlug

[sofakng]

This stuff is incredibly confusing...

If you can explain the test I can test using both an LG CX and LG C1.

Regardless ... does this mean the "chinoppo"/oppo are pretty much the best players?

[RESET_9999]

I dont know about the oppo but we're about to find out. please try quietvoid's rpu test file and compare the L1 reaction with your oppo and TVs internal player. If it's as different as my C2, you cant miss it.

mp4 version: https://drive.google.com/file/d/1HMU790 ... sp=sharing
ts version: https://drive.google.com/file/d/1hAv4eJ ... sp=sharing

[sofakng]

Oh, sorry... I don't have the oppo player yet. (I've order the chinoppo m9201 but it hasn't shipped)

[RESET_9999]

Oh, sorry... I don't have the oppo player yet. (I've order the chinoppo m9201 but it hasn't shipped)

if it's not just an issue related to the C2 only, I expect the same issue because I think the oppo and the x700 have the same SOC.