I am not incorrect.azreil24 wrote:Forgot I even wrote here, but you are incorrect. It won't be the same, even if the color mapping is done correctly, the profile settings of the TV are completely different from an SDR profile. Also, from it's not "supposed" to stretch the colors to how it actually works, it's a long way. Even if does work as you think it "should" work, you still have maxed out brightness settings and all, as the TV is running under a DV settings profile. So yeah, it's still crap and sad to not be able to make the player recognize DV content automatically like all other players from other companies do. But then again, it took Sony years to get DV sorted out for their TVs.HarperVision wrote: ↑Thu Apr 08, 2021 2:37 amThis is incorrect if the display maps the colors and dynamic range as it should. If it doesn’t that’s on the display you’re using, not the player.
Colors within any of the color gamuts will be completely identical whether they be Rec709, DCI-P3 or BT2020, up to each of their limits of course. So putting a Rec709 source into a wider P3 or BT2020 container should look and display identically when the gamuts are mapped properly since Rec709 is smaller than either of those wider gamuts. It’s not supposed to stretch the colors at all and if it does then your display is doing it wrong, not the source.
I have both an X700 and an X800M2 as well as an AppleTV 4K and they don’t have any of the issues reported with my displays because they map the signal correctly.
Dolby Vision now possible through MP4 Mux.
-
- Posts: 28
- Joined: Tue Feb 02, 2021 9:32 am
Re: Dolby Vision now possible through MP4 Mux.
Re: Dolby Vision now possible through MP4 Mux.
Hello! I used yusesope tool for demux an mkv file created with makemkv
I am trying to use dlb_mp4base to generate an mp4 file, but the program creates an empty file
"mp4muxer --dv-profile 7 --input-file bl.hevc --input-file el.hevc --input-file audio.ac3 --media-lang eng --output-file test.mp4"
I am trying to use dlb_mp4base to generate an mp4 file, but the program creates an empty file
"mp4muxer --dv-profile 7 --input-file bl.hevc --input-file el.hevc --input-file audio.ac3 --media-lang eng --output-file test.mp4"
Re: Dolby Vision now possible through MP4 Mux.
from the task manager it is clear if the muxing is in progressgalarond wrote: ↑Tue Sep 28, 2021 8:34 pmIf your getting the 2 layers correctly maybe you are not waiting enough for mp4muxer....in my flintstones laptop a movie can take up to 3 hours till the mp4 file goes from 0kb to something, then like 3 more hours till its finished.Kocal wrote: ↑Tue Sep 28, 2021 2:18 pmHello! I used yusesope tool for demux an mkv file created with makemkv
I am trying to use dlb_mp4base to generate an mp4 file, but the program creates an empty file
"mp4muxer --dv-profile 7 --input-file bl.hevc --input-file el.hevc --input-file audio.ac3 --media-lang eng --output-file test.mp4"
Also you can try with tsmuxer or Useac3to tools to demux and check if your getting the same (hevc/h265) layers.
I think the problem is in the demux, because from tsmuxer I only get a video track
Re: Dolby Vision now possible through MP4 Mux.
Yes I had already tried using tsmuxer "Blu-ray Folder", but it doesn't work on my sony x700galarond wrote: ↑Wed Sep 29, 2021 5:09 amyour getting 1 file with tsmuxer cause, if its a dv file, it must be a dual layer single stream, instead of going for the mp4 way just use tsmuxer to convert that original mkv into ts/m2ts and ull be able to play it fine as dv.Kocal wrote: ↑Tue Sep 28, 2021 9:03 pmfrom the task manager it is clear if the muxing is in progressgalarond wrote: ↑Tue Sep 28, 2021 8:34 pm
If your getting the 2 layers correctly maybe you are not waiting enough for mp4muxer....in my flintstones laptop a movie can take up to 3 hours till the mp4 file goes from 0kb to something, then like 3 more hours till its finished.
Also you can try with tsmuxer or Useac3to tools to demux and check if your getting the same (hevc/h265) layers.
I think the problem is in the demux, because from tsmuxer I only get a video track
Re: Dolby Vision now possible through MP4 Mux.
usually, with a full blu-ray, I always convert to Blu-ray folder
Last edited by Kocal on Wed Sep 29, 2021 7:24 pm, edited 1 time in total.
Re: Dolby Vision now possible through MP4 Mux.
-
- Posts: 2
- Joined: Sat Sep 25, 2021 10:56 am
Re: Dolby Vision now possible through MP4 Mux.
Can anyone help me how to use dlb_mp4base to create an mp4 dolby vision file that I can rewind on my LG C9?
Re: Dolby Vision now possible through MP4 Mux.
Hi !
Here I have used makemkv 1.16.4 for all my tittles. You can skip the next part and go directly to my question.
I have an Ugoos am6b+ ( only the wifi 6 chip is different vs am6b). I can use some app that use media codec to play mkv muxed with mkavemkv 1.16.4. They play fine, but I always found there was something wrong. Anyway
There native videoplayer is using differents codes etc, I believe this is the way to play dolby vision on this machine. This player does NOT play :
-stdl MKV (played ad hdr10)
-Any dualtrack (exept mkv) will play in dolby vision but only in 1080p . Must be a bug that take the wrong stream as an hint to change resolution, or maybe this is a certification issue and the machine is doing heavy downscale than upscale to 20160p , I don't know.
The native player DOES play :
stdl .ts
stdl .m2ts
Maybe stdl mp4, did not try
So, my questions,
Output file is stdl.
1- Does the output of a .mkv muxed with makemkv makemkv 1.16.4 > tsmuxer (ts or m2ts) the same as using yusesope'S beta 4 tool > tsmuxer (ts or m2ts) the same ?
- I have read somewhere that makemkv does remove nal 62-63 * but maybe this have been corrected.
- using yusesope's tool I can remove the hdr10+ metadata, does it improve something?
-using already muxed mkv instead of starting to rip from scratch would save me a lot of time, but if the quality/compatibility is better, i'll do it.
Thank you,
Sorry if the answer is in this thread , I have read a lot but this is a huge one.
Here I have used makemkv 1.16.4 for all my tittles. You can skip the next part and go directly to my question.
I have an Ugoos am6b+ ( only the wifi 6 chip is different vs am6b). I can use some app that use media codec to play mkv muxed with mkavemkv 1.16.4. They play fine, but I always found there was something wrong. Anyway
There native videoplayer is using differents codes etc, I believe this is the way to play dolby vision on this machine. This player does NOT play :
-stdl MKV (played ad hdr10)
-Any dualtrack (exept mkv) will play in dolby vision but only in 1080p . Must be a bug that take the wrong stream as an hint to change resolution, or maybe this is a certification issue and the machine is doing heavy downscale than upscale to 20160p , I don't know.
The native player DOES play :
stdl .ts
stdl .m2ts
Maybe stdl mp4, did not try
So, my questions,
Output file is stdl.
1- Does the output of a .mkv muxed with makemkv makemkv 1.16.4 > tsmuxer (ts or m2ts) the same as using yusesope'S beta 4 tool > tsmuxer (ts or m2ts) the same ?
- I have read somewhere that makemkv does remove nal 62-63 * but maybe this have been corrected.
- using yusesope's tool I can remove the hdr10+ metadata, does it improve something?
-using already muxed mkv instead of starting to rip from scratch would save me a lot of time, but if the quality/compatibility is better, i'll do it.
Thank you,
Sorry if the answer is in this thread , I have read a lot but this is a huge one.
-
- Posts: 9
- Joined: Sun Aug 29, 2021 11:31 am
Re: Dolby Vision now possible through MP4 Mux.
I guess you are trying to play a movie with FEL. Firestick can not play FEL. Convert it to MEL with yusesope's tool and try to play againHAK94 wrote: ↑Thu Sep 30, 2021 1:18 pmHey guys, sorry im new to this stuff. I want to remux DV from BDMV file and I tried using TSmuxer and MakeMKV so:
1- I downloaded the BDMV file and I used TSmuxer and I chose the first two HEVC the 4k and 1080p with TrueHD audio to make it ISO file.
2- After that I used MakeMKV and I chose the DV one and it was successful then I opened Mediainfo and it shows me its Dolby Vision Profile 7.
3- I used Plex from my firestick 4k and played the movie and it gave HDR not DV.
Please help again I'm new to this.
Re: Dolby Vision now possible through MP4 Mux.
Hi guys. Amazing thread. After trying to read all of it I got a few questions in my head. My setup is Shield 2019 Pro + several LG OLEDs in my family (C9, BX etc).
1.) I deleted the question as you can not make Profile 8 BL+EL+RPU copy of Profile 7 BL+EL+RPU as there is no EL in Profile 8. My mistake ![Smile :-)](./images/smilies/icon_smile.gif)
2.) I do also for some movies 2160p UHD Rips (re-encodes) x265 CRF 17 preset slower. I am able to watch them on 4K TVs around the globe whenever I travel and I want to play a movie as very often 20-40 Mbit connection is no problem in a modern hotele whereas 50-90 Mbit for remuxes is too much in 99% cases in public places. Now the question is. I am able to extract FEL or MEL layer and extract RPU. Usually I attach RPU layer to my 2160p re-encodes and it plays as Dolby Vision video (without EL layer) without a problem or any glitches. However I was thinking about adding EL track as well? I rather don't see a point in this as the goal to re-encode is to reduce the size and quality for lower bitrate (storage does not matter much for me) and then if I go from 60 GB to 25 GB what would be the point in increasing the size by 4-8 GB back only to get 12 bit video on something I anyway just reduced the quality already. Do you have any thoughts on this? So I rather just keep RPU only with 2160p re-encodes.
3.) How about MEL? If the EL layer is MEL. Does it make sense to add it? After reading this thread I understand MEL would not bring any value as well in my case (point 2)?
4.) One thing I don't understand. I join with dovi_tool original EL layer (for example 8 GB) with original RPU (upgraded to dvhe
. Then I mux it with mkvtoolnix with the re-encoded 2160p BL layer (let's say 25 GB). Then i have a mkv file with 2 HEVC tracks (25+8 = 33 GB mkv at this point). Then I go to MakeMKV, open it and save as MKV. I receive single layer dual track profile 8 Dolby Vision file. It plays correctly. But why total size of this file is around 29 GB and not 33 GB?
5.) Last but not least. A bit crazy question. Anyone has been playing with re-encoding FEL layer? I did some tests. For "Anna" I re-encoded 8 GB FEL layer to ca 1 GB (x265 17 slower). But for "Bravehart" it went from 8 GB to 13 GB (x265 17 slower). When I remux it and create dovi profile 7 compliant mkv it plays correctly on Shield as DoVI. To be honest I'm a bit curious what in fact I have created? 12 bit re-encoded file? How is the re-encoded BL matching the re-encoded FEL? During re-encdoding for sure the original BL:FEL won't match the re-encoded BL:FEL in terms of pixel-to-pixel match.
Anyway it works, it plays well on Shield. For movies like "Anna" increasing the 25 GB 2160p re-encode with 1GB re-encoded FEL is not a big deal. But for movies like "Braveheart" I would have to add 25 BL re-encode, the 8 GB original FEL. Anyway after MKV the "Braveheart" 2160p re-encode BL+EL(original)+RPU is not 33 GB but 29 GB (so plus 4GB) which, on the other hand, is not so bad after all (+13%).
Anyway the question is - does it make much sense? To be honest I can not see the difference on my LG OLED between re-encoded BL + RPU vs re-encoded BL + re-encoded EL + RPU vs re-encoded BL + original EL + RPU. Maybe someone else is more patient in this matter and can tell the difference?
And just to let you know in case anyone wondered. Yes, you can attach DoVi to 720p HEVC HDR re-ecodes. After merging with RPU it plays as 720p Dolby Vision. The quality is actually really nice on LG OLED for 3-4 MB/s 720p DoVi files. It really looks god
Yes, you can also re-encode FEL layer to 720p HEVC track. For example "Anna" FEL is reducing its size from 8 GB to 300 MB. For "Braveheart" it went down from 8 GB to 4 GB.
In the end you can mux it into 720p DoVi BL (re-encoded) + EL (re-encoded) + RPU and it also plays well
Regarding the file size. MKVtoolnix size is 5,7 GB for re-encoded BL + 4,5 GB for re-encoded EL which is 10,3 GB. However final MakeMKV Profile 7 file for 720p DoVi BL (re-encoded) + EL (re-encoded) + RPU is 7,9 GB in case anyone wondered.
So with movies like "Braveheart" it does not make sens or one would have to use more aggressive EL endcoding like CRF21/22? (then: how for example CRF21/22 EL will impact the BL+EL quliaty vs pure BL CRF17 - this might be interesting).
But with movies like "Anna" you could keep very low size files for DolbyVIsion comedies in 720p or 1080p - like for example "Spaceballs". For 5-8 GB you can have full BL+EL+RPU Dolby Vision comedy with "enough" quality for this kind of movie.
![Smile :-)](./images/smilies/icon_smile.gif)
2.) I do also for some movies 2160p UHD Rips (re-encodes) x265 CRF 17 preset slower. I am able to watch them on 4K TVs around the globe whenever I travel and I want to play a movie as very often 20-40 Mbit connection is no problem in a modern hotele whereas 50-90 Mbit for remuxes is too much in 99% cases in public places. Now the question is. I am able to extract FEL or MEL layer and extract RPU. Usually I attach RPU layer to my 2160p re-encodes and it plays as Dolby Vision video (without EL layer) without a problem or any glitches. However I was thinking about adding EL track as well? I rather don't see a point in this as the goal to re-encode is to reduce the size and quality for lower bitrate (storage does not matter much for me) and then if I go from 60 GB to 25 GB what would be the point in increasing the size by 4-8 GB back only to get 12 bit video on something I anyway just reduced the quality already. Do you have any thoughts on this? So I rather just keep RPU only with 2160p re-encodes.
3.) How about MEL? If the EL layer is MEL. Does it make sense to add it? After reading this thread I understand MEL would not bring any value as well in my case (point 2)?
4.) One thing I don't understand. I join with dovi_tool original EL layer (for example 8 GB) with original RPU (upgraded to dvhe
![Cool 8)](./images/smilies/icon_cool.gif)
5.) Last but not least. A bit crazy question. Anyone has been playing with re-encoding FEL layer? I did some tests. For "Anna" I re-encoded 8 GB FEL layer to ca 1 GB (x265 17 slower). But for "Bravehart" it went from 8 GB to 13 GB (x265 17 slower). When I remux it and create dovi profile 7 compliant mkv it plays correctly on Shield as DoVI. To be honest I'm a bit curious what in fact I have created? 12 bit re-encoded file? How is the re-encoded BL matching the re-encoded FEL? During re-encdoding for sure the original BL:FEL won't match the re-encoded BL:FEL in terms of pixel-to-pixel match.
Anyway it works, it plays well on Shield. For movies like "Anna" increasing the 25 GB 2160p re-encode with 1GB re-encoded FEL is not a big deal. But for movies like "Braveheart" I would have to add 25 BL re-encode, the 8 GB original FEL. Anyway after MKV the "Braveheart" 2160p re-encode BL+EL(original)+RPU is not 33 GB but 29 GB (so plus 4GB) which, on the other hand, is not so bad after all (+13%).
Anyway the question is - does it make much sense? To be honest I can not see the difference on my LG OLED between re-encoded BL + RPU vs re-encoded BL + re-encoded EL + RPU vs re-encoded BL + original EL + RPU. Maybe someone else is more patient in this matter and can tell the difference?
And just to let you know in case anyone wondered. Yes, you can attach DoVi to 720p HEVC HDR re-ecodes. After merging with RPU it plays as 720p Dolby Vision. The quality is actually really nice on LG OLED for 3-4 MB/s 720p DoVi files. It really looks god
![Smile :-)](./images/smilies/icon_smile.gif)
In the end you can mux it into 720p DoVi BL (re-encoded) + EL (re-encoded) + RPU and it also plays well
![Smile :-)](./images/smilies/icon_smile.gif)
Regarding the file size. MKVtoolnix size is 5,7 GB for re-encoded BL + 4,5 GB for re-encoded EL which is 10,3 GB. However final MakeMKV Profile 7 file for 720p DoVi BL (re-encoded) + EL (re-encoded) + RPU is 7,9 GB in case anyone wondered.
So with movies like "Braveheart" it does not make sens or one would have to use more aggressive EL endcoding like CRF21/22? (then: how for example CRF21/22 EL will impact the BL+EL quliaty vs pure BL CRF17 - this might be interesting).
But with movies like "Anna" you could keep very low size files for DolbyVIsion comedies in 720p or 1080p - like for example "Spaceballs". For 5-8 GB you can have full BL+EL+RPU Dolby Vision comedy with "enough" quality for this kind of movie.
Last edited by juzer7 on Mon Oct 04, 2021 2:01 am, edited 3 times in total.
Re: Dolby Vision now possible through MP4 Mux.
I'm not an expert, but I'll take a crack at those:
1) I believe the only advantage of converting to profile 8 is compatibility with devices that can't handle profile 7, so if your playback device can do profile 7 then I don't think there's anything to be gained by converting.
2-3) A MEL is essentially just the RPU, so if you you've added the RPU back to your re-encode then you've already added the MEL, in effect. I'll address the FEL case in answer 5.
4) pass
5) I don't think trying to re-encode the BL and FEL separately is a valid thing to do that will produce meaningful results. Remember that the video data in a FEL is an encoding of the difference between the HDR10 BL and the original DV source. But when you've re-encoded the BL, adding back the FEL video data no longer gets you to the original DV source, it just gets you a weird mix of things. I think it's a valid simplification to think of it like an equation DV = BL + FEL. If you change BL then FEL can no longer help you calculate DV.
What would be great is if we could decode the BL and FEL together to get the 12-bit DV source, and then we could re-encode that to whatever we wanted. But the trouble is, we don't know how to do that decoding step, because it's proprietary and only Dolby-licenced UHDBD players know how to do it. Perhaps one day someone will fully reverse engineer DV profile 7, but for now I think we're stuck with not being able to do anything with a FEL except for converting it to a MEL or playing it back on licenced (or cloned) UHDBD players.
1) I believe the only advantage of converting to profile 8 is compatibility with devices that can't handle profile 7, so if your playback device can do profile 7 then I don't think there's anything to be gained by converting.
2-3) A MEL is essentially just the RPU, so if you you've added the RPU back to your re-encode then you've already added the MEL, in effect. I'll address the FEL case in answer 5.
4) pass
5) I don't think trying to re-encode the BL and FEL separately is a valid thing to do that will produce meaningful results. Remember that the video data in a FEL is an encoding of the difference between the HDR10 BL and the original DV source. But when you've re-encoded the BL, adding back the FEL video data no longer gets you to the original DV source, it just gets you a weird mix of things. I think it's a valid simplification to think of it like an equation DV = BL + FEL. If you change BL then FEL can no longer help you calculate DV.
What would be great is if we could decode the BL and FEL together to get the 12-bit DV source, and then we could re-encode that to whatever we wanted. But the trouble is, we don't know how to do that decoding step, because it's proprietary and only Dolby-licenced UHDBD players know how to do it. Perhaps one day someone will fully reverse engineer DV profile 7, but for now I think we're stuck with not being able to do anything with a FEL except for converting it to a MEL or playing it back on licenced (or cloned) UHDBD players.
Re: Dolby Vision now possible through MP4 Mux.
In fact if anyone is curious you can download 720p versions of Braveheart:
https://drive.google.com/file/d/1E51NcN ... sp=sharing
- BL
- DoVi 7 BL + original EL + RPU
- DoVi 7 BL + re-encoded EL + RPU
- DoVi 8 BL + RPU
To me "DoVi 7 BL + re-encoded EL + RPU" looks really good with no artifacts. However I struggle to find differences between DoVi versions at all![Smile :-)](./images/smilies/icon_smile.gif)
https://drive.google.com/file/d/1E51NcN ... sp=sharing
- BL
- DoVi 7 BL + original EL + RPU
- DoVi 7 BL + re-encoded EL + RPU
- DoVi 8 BL + RPU
To me "DoVi 7 BL + re-encoded EL + RPU" looks really good with no artifacts. However I struggle to find differences between DoVi versions at all
![Smile :-)](./images/smilies/icon_smile.gif)
Re: Dolby Vision now possible through MP4 Mux.
Reencoding the EL makes no sense because you're losing the benefits of the original if you just do it blindly.
Also it's complicated to keep it in sync with the BL.
Also it's complicated to keep it in sync with the BL.
Re: Dolby Vision now possible through MP4 Mux.
Yeah as I mentioned previously, I have not been able to encode a single BL and mux back in its FEL (or even convert that FEL+then encoded BL to 8 ) without there being RPU sync errors/flashes in the file, somewhere, eventually (not always right at the start nor constant). I've tried x265/ffmpeg/though Staxrip UI/Handbrake/various encode settings multiple times/different rip and mux tools and differing versions of each program/yusesope's or quietvoid's tool - there's always a RPU errors eventually in a FEL title no matter what I do with it if I first encode the BL. MEL titles with encoded BL or 8 converted from 5 RPU + encoded HDR10 BL or HDR10+ to 8 with encoded BL - no problem whatsoever on any of those titles (I think I'm at mid-50s currently for native Dovi UHD titles I've added to Plex). I know others here say they're doing it, but I somehow am just SOL apparently. So any FEL title I just mux together and leave untouched - using external forced subs works fine in Plex so I don't need to worry about burning them in (main reason for encoding, secondary to the space saving aspect) - and being I have the source PGS subs, timing/spelling is accurate and all that jazz for my external subs, no worries.
Still, sucks being defeated
![Sad :(](./images/smilies/icon_sad.gif)
-
- Posts: 127
- Joined: Thu Oct 08, 2020 5:19 pm
Re: Dolby Vision now possible through MP4 Mux.
We are not defeated at all, there is a way,staknhalo wrote: ↑Mon Oct 04, 2021 9:35 pmYeah as I mentioned previously, I have not been able to encode a single BL and mux back in its FEL (or even convert that FEL+then encoded BL to 8 ) without there being RPU sync errors/flashes in the file, somewhere, eventually (not always right at the start nor constant). I've tried x265/ffmpeg/though Staxrip UI/Handbrake/various encode settings multiple times/different rip and mux tools and differing versions of each program/yusesope's or quietvoid's tool - there's always a RPU errors eventually in a FEL title no matter what I do with it if I first encode the BL. MEL titles with encoded BL or 8 converted from 5 RPU + encoded HDR10 BL or HDR10+ to 8 with encoded BL - no problem whatsoever on any of those titles (I think I'm at mid-50s currently for native Dovi UHD titles I've added to Plex). I know others here say they're doing it, but I somehow am just SOL apparently. So any FEL title I just mux together and leave untouched - using external forced subs works fine in Plex so I don't need to worry about burning them in (main reason for encoding, secondary to the space saving aspect) - and being I have the source PGS subs, timing/spelling is accurate and all that jazz for my external subs, no worries.
Still, sucks being defeated![]()
I have just created a flawless copy of power rangers just for this test. FEL is 7gigs on power rangers don’t encode it.
18 gig base layer encode with FEL & RPU
You have to edit the FEL (has the nal unit) in the Rpu to reflect the hevc bl encode and that’s it.
I get no flashes no pixilation perfect alinement. Perfect profile 7 with encoded base layer
Inject the new Rpu into the FEL.
Mux with base layer in ts muxer nightly build & your done.
The hard part is getting a new Rpu.
- Attachments
-
- BC96AF50-7120-4036-A9AE-A0CECD5B5961.jpeg (438.25 KiB) Viewed 15718 times
Last edited by Manixx2020beyound on Tue Oct 05, 2021 7:06 am, edited 1 time in total.