Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
4th October 2022, 23:25 | #401 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
Normally you would export a Dolby Vision master with XML metadata. DEE seems to have a script allowing to encode both bitstreams from the master: https://professionalsupport.dolby.co...language=en_US Though obviously it's better if you contact Dolby about it, you would have to for DEE anyways. This is another guide from their documentation: https://professionalsupport.dolby.co...language=en_US
__________________
LG C2 OLED | GitHub Projects |
|
5th October 2022, 00:59 | #402 | Link |
Derek Prestegard IRL
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,989
|
Right, DEE can make any current flavor of DoVi, HDR10, and SDR from a DoVi master (Typically J2K or ProRes) - provided you're cool with having it do tone mapping in some of those cases e.g. SDR
__________________
These are all my personal statements, not those of my employer :) |
5th October 2022, 11:33 | #403 | Link | ||
Registered User
Join Date: Oct 2003
Posts: 157
|
Thanks for your feedback.
I'm trying to encode to HEVC sample using this command line: Quote:
Quote:
EDIT: A new test from another video sample worked without any error. The guilty was probably my source. Last edited by Lucius Snow; 5th October 2022 at 15:11. |
||
5th October 2022, 15:32 | #404 | Link |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
It means the video and the metadata are not the same frame count, so probably that the video being encoded has less frames.
__________________
LG C2 OLED | GitHub Projects |
5th October 2022, 17:36 | #405 | Link |
Registered User
Join Date: Jul 2022
Posts: 123
|
Talking about Profile 7, I've always converted the RPU of my BluRay re-encods to Profile 8.1 and then added them to the stream. Would it work (i.e. trigger DV on the player) if I just inject the original Profile 7? Does it matter if the Profile 7 is MEL or FEL?
|
5th October 2022, 19:07 | #406 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
There's no point in keeping the original MEL, it's equivalent to profile 8. For FEL, the processing probably wouldn't work correctly on a reencoded base layer and it might lead to incorrect rendered image. The only correct method is to process the FEL before reencoding (see https://github.com/erazortt/DoViBaker), and use a profile 8 RPU with the mapping metadata removed.
__________________
LG C2 OLED | GitHub Projects |
|
5th October 2022, 23:40 | #408 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
I don't think it does anything else with the RPU.
__________________
LG C2 OLED | GitHub Projects |
|
7th October 2022, 06:20 | #409 | Link |
Registered User
Join Date: Mar 2006
Posts: 45
|
Hi.
Got a question regarding dovi_tool. dovi_tool.exe -c -m 2 mux -b encoded_bl.h265 -d -e demuxed_el -o output_with_dv.265 Should that not give the same output file as this: dovi_tool.exe -m 2 -c extract-rpu demuxed_el dovi_tool.exe inject-rpu --rpu-in RPU.bin --input encoded_bl.h265 Should the two command lines not do the same thing? Except the first one doesn't extract the RPU file. Or am I misunderstanding something? When I do a binary compare of the two files, they are not identical at all. Thanks in advance. rco133 |
7th October 2022, 13:41 | #410 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
While the EL also contains RPU, it's a regular HEVC bitstream otherwise.
__________________
LG C2 OLED | GitHub Projects |
|
7th October 2022, 15:30 | #411 | Link | |
Registered User
Join Date: Mar 2006
Posts: 45
|
Quote:
The EL is a lot bigger than the RPU. But shouldn't the first command ignore the EL video, and just mux in the RPU into the bl since I am using the -d switch? The file size of the two resulting files are exactly the same down to the byte. But when I do a "fc /B file1 file2" it lists a ton of differences between the two files. I thought that using -d in the mux command line, would do the same as extracting the RPU from the EL and injecting it into the bl. So I guess my quation really is, why does using the -d switch in the mux command, not give the same result as extracting the RPU and injecting the RPU into the bl? In both cases I am using -m 2 to convert to Profile 8. rco133 |
|
7th October 2022, 15:43 | #412 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
The difference is that extracting the RPU reorders according to the source video file, while muxing the EL directly doesn't reorder anything. Now it should only make a difference if the BL you reinject into is different from the source. In your first post you said that the RPU is injected into a reencoded video, so everything seems to work as expected. When you mux the original EL, the RPU is going to be out of order with the reencoded video.
__________________
LG C2 OLED | GitHub Projects |
|
7th October 2022, 17:04 | #413 | Link | |
Registered User
Join Date: Mar 2006
Posts: 45
|
Quote:
Both output files say they contain: Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible So i guess even though they are not binary identical, they both should play back fine? The only difference between the two output files is that one is made with the mux -d command line, and the other file is made by extracting the RPU manually and then injection it manually. In both cases the BL (input file) is the same encoded BL. Just want to be sure that I am not messing something up, by using the mux -d line, since that saves me from actually extracting the RPU. rco133 |
|
7th October 2022, 22:51 | #414 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
The metadata will most definitely be in the wrong order, so playback will show noticeable brightness changes. You should be extracting the RPU and encoding with x265/ffmpeg directly with --dolby-vision-rpu, that way you don't need to inject.
__________________
LG C2 OLED | GitHub Projects |
|
8th October 2022, 07:00 | #415 | Link | |
Registered User
Join Date: Mar 2006
Posts: 45
|
Quote:
I don't understand that, and that is why I am asking, and really appreciate your expertise on this matter. I thought that when using the RPU only, I could mux or inject it into the original BL or the encoded BL without problems. I convert the RPU from Profile 7 to Profile 8 and then use just the RPU. I am not using the rest of the EL. Just the RPU. That way I thought that all would be good. But maybe that is not the case? rco133 |
|
8th October 2022, 08:12 | #416 | Link | |
Registered User
Join Date: Mar 2006
Posts: 45
|
Quote:
What if I do the following: dovi_tool.exe -m 2 -c extract-rpu -i demuxed_EL.h265 -o RPU.bin After this I should have a profile 8 RPU with no crop. dovi_tool.exe inject-rpu -i x265_encoded_BL.h265 -r RPU.bin -o output_wit_dv.h265 Will that work, or will there still be issues if I do that? rco133 |
|
9th October 2022, 13:34 | #419 | Link | |
QfG Group Germany
Join Date: Oct 2018
Location: Germany
Posts: 245
|
Quote:
No changes in functions lines, only reworked menu and adding the new feature in the hdr10+ area. Maybe you have () in your filenames? I tested succesfully with a spaced foldername.
__________________
Last edited by -QfG-; 9th October 2022 at 13:50. |
|
|
|