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.

 

Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)

Reply
 
Thread Tools Search this Thread Display Modes
Old 5th April 2021, 11:01   #41  |  Link
telemO
Registered User
 
Join Date: Oct 2020
Location: France
Posts: 7
Thanks a lot, dear quietvoid, for having replied quickly to me.
I'm trying again to post you a reply - few days after my first attempt failed (supposedly due to moderation filtering?)

Quote:
Originally Posted by quietvoid View Post
There's no simple way to use the tool for cropped video, you have to edit the code.
Erf... That is a matter for me: I'm not competent in programming neither compiling (and a bit allergic to it actually).
Is it abusive to ask you, theweasley or anyone else able to compile with this cargo thing, a "crop able" version of your DoVi tool?

Quote:
Originally Posted by quietvoid View Post
Also, using the RPU with x265 to transcode might end up with some desyncs due to the way x265 is inserting the metadata back.
See https://github.com/quietvoid/dovi_to...ment-803652617
I'm also having similar issues as your topic above, with "red flash" insertion before a fade out during the start credits (I'm working with a 2600 frames extract of a movie remux).
I've also detected a magenta flash on a white area (a reflection zone) during a real movie part.

Quote:
Originally Posted by quietvoid View Post
Unfortunately I don't think there is a solution for that, other than inserting the metadata after transcoding.
What do you mean by that exactly ?
To mux it with the yusesope tool or via mkvmerge + MakeMKV ? But how would you mux a RPU.bin with an hevc file ?

Quote:
Originally Posted by quietvoid View Post
For HDR10+ the same desync issue is present.
For cropped video, the metadata is supposedly resolution agnostic and hopefully the analysis is done on the active image area only.
So it should work in theory,
From an article I found about Metadata Levels on the Dolby Professional Support Knowledge, it is written "Ratio of canvas and image (active area)" as part of the Level 0.
This would mean the same as you mentionned for the HDR10+ theorical implementation, on the active area... and therefore no need to have a "crop-able" version?

Quote:
Originally Posted by quietvoid View Post
I'm curious to know how streaming services make use of x265's RPU insertion. There has to be some predicting the transcode's decoding order somehow, to make sure the RPU is synced throughout.
Though I've had artifacts with Dolby Vision on Netflix as well, so maybe they don't bother syncing either.
Probably someone knowledgeable in the video streaming domain, such as benwaggoner, would give you answer or at least some hints.
__________________
Ryzen 3950X w/ 64 Gb RAM on Win10 as transcoding rig (and daily use)
Panasonic HZ1000 (Oled HDR10+/DoVi TV) & Sony MDR-HW700DS (Audio decoder and headset spacialization)
telemO is offline   Reply With Quote
Old 5th April 2021, 14:40   #42  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Posts: 270
Quote:
Originally Posted by telemO View Post
What do you mean by that exactly ?
To mux it with the yusesope tool or via mkvmerge + MakeMKV ? But how would you mux a RPU.bin with an hevc file ?
I mean parsing the final HEVC and interleaving the metadata NAL units directly, it's still a raw bitstream.
Implies correctly decoding the frames in the right order though.

Quote:
Originally Posted by telemO View Post
This would mean the same as you mentionned for the HDR10+ theorical implementation, on the active area... and therefore no need to have a "crop-able" version?
Analysis for both metadata should be assumed to be done on the active area only, according to docs.
The only difference with Dolby Vision is that the active area is also present in the final metadata, while it's not in HDR10+.

As for a "croppable" version, I just have a Windows binary: https://mega.nz/file/dZ1mXQga#ve0Dwl...HweAXRg-BEXG7U
Maybe this is a feature I can add, since a lot of people have asked for it..
__________________
LG OLED C8 | madVR 870 DPL HDR curve
quietvoid is online now   Reply With Quote
Old 5th April 2021, 18:12   #43  |  Link
telemO
Registered User
 
Join Date: Oct 2020
Location: France
Posts: 7
quietvoid, you're the boss, man !
You're again replying quickly, and with a "croppable" release of your tool under Windows, perfectly suitable with my need as an end-user encoder.
I'm gonna try this within the coming days and let you know my result, as soon as possible, as I think I have a good sample to know if this croppable option would work.

I have to see how and where to share some samples for the community to test and tell about the syncs / artifacts issues.
And then to share my experience for the others to be able to do the same, as for the HDR10+ case.
__________________
Ryzen 3950X w/ 64 Gb RAM on Win10 as transcoding rig (and daily use)
Panasonic HZ1000 (Oled HDR10+/DoVi TV) & Sony MDR-HW700DS (Audio decoder and headset spacialization)
telemO is offline   Reply With Quote
Old 7th April 2021, 00:13   #44  |  Link
telemO
Registered User
 
Join Date: Oct 2020
Location: France
Posts: 7
"crop-able" version of the dovi_tool seems on the right path

Quote:
Originally Posted by quietvoid View Post
As for a "croppable" version, I just have a Windows binary: https://mega.nz/file/dZ1mXQga#ve0Dwl...HweAXRg-BEXG7U
Maybe this is a feature I can add, since a lot of people have asked for it..
Thanks a lot again for delivering so quickly this croppable version, and of course, I would encourage you to publish an updated version of the dovi_tool with this feature, whenever you've get the time to do it.

As mentionned before, a first return on the sample I tought about testing cropping:
  • cropped at 1632 instead of original 2160p, which is a FEL DoVi UHD-BD base material,
  • transcoded with x265 v3.4 Mod version from Staxrip 2.1.7.0 in DV profile 8.1, inputing the RPU converted to 8.1 by the quietvoid's dovi_tool,
  • encapsuled as a MP4 file, with mp4muxer, in order to test with the internal player of my Panasonic TV,
the DoVi logo is showing on as well as the picture menus and parameters related to it are activated (such as Dolby IQ):
  1. with the RPU extracted by the github version 0.1.2 of dovi_tool, the TV displays the cropped sample with black bars lapping over the 1632-high area, i.e. it is like "over-cropping" the already cropped picture.
  2. with the RPU extracted by the unofficial "crop-able" version of dovi_tool, the TV displays the cropped sample with black bars as expected.
To mitigate this test case, I tried with another DoVi FEL UHD-BD base material, and whatever I use the "crop-able" or not version of dovi_tool, both of my cropped test samples are displayed correctly the same by my TV.
I deduce that the metadata where containing some information of an higher area on the first sample material and not on this other one.

I'm now thinking that I read something about subtitles mattering, and that I should have a look at the consequences of cropping for diplaying these.


For information about artifact or sync pbs, I also notice a "red flashy" insertion on a text animation just before a fade out (as for the first sample).
I've tried many x265 parameters change, such as chromaloc=0 or 2, ref=6 (as you mentionned), scenecut=0, hrd-concat, no-open-gop, uhd-bd : none of these solved the issues.
__________________
Ryzen 3950X w/ 64 Gb RAM on Win10 as transcoding rig (and daily use)
Panasonic HZ1000 (Oled HDR10+/DoVi TV) & Sony MDR-HW700DS (Audio decoder and headset spacialization)
telemO is offline   Reply With Quote
Old 25th April 2021, 02:11   #45  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Posts: 270
I just released 0.2.0 with metadata reordering according to the frames display output order instead of decoded order.
As well as adding the --crop flag for setting active area offsets to zero.
__________________
LG OLED C8 | madVR 870 DPL HDR curve
quietvoid is online now   Reply With Quote
Old 6th May 2021, 04:14   #46  |  Link
telemO
Registered User
 
Join Date: Oct 2020
Location: France
Posts: 7
Quote:
Originally Posted by quietvoid View Post
I just released 0.2.0 with metadata reordering according to the frames display output order instead of decoded order.
As well as adding the --crop flag for setting active area offsets to zero.
Thanks a lot again for taking your time to update and improve the tool.

I'll have to test if this new parsing method removes the artifact/sync issues I've noticed on my test sample.

Few questions to you, quietvoid :
- I'm confused for some time now with the convert option FEL to MEL: what is the use case? To encode in DV profile 5 ?
- What is the use case(s) of the new command "inject-rpu"? Would it mean that I can inject the RPU into my transcoded hevc file afterwards and not during the x265 process anymore (with the --dolby-vision-rpu command)?
__________________
Ryzen 3950X w/ 64 Gb RAM on Win10 as transcoding rig (and daily use)
Panasonic HZ1000 (Oled HDR10+/DoVi TV) & Sony MDR-HW700DS (Audio decoder and headset spacialization)
telemO is offline   Reply With Quote
Old 6th May 2021, 04:26   #47  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Posts: 270
Quote:
Originally Posted by telemO View Post
- I'm confused for some time now with the convert option FEL to MEL: what is the use case? To encode in DV profile 5 ?
No, the profile 7 stays except compatibility is better for devices that cannot play FEL files.

Quote:
Originally Posted by telemO View Post
- What is the use case(s) of the new command "inject-rpu"? Would it mean that I can inject the RPU into my transcoded hevc file afterwards and not during the x265 process anymore (with the --dolby-vision-rpu command)?
It's still experimental, but the basic of it is to be able to add Dolby Vision metadata to an existing HDR10 file.
However I'd still suggest using the RPU with x265 instead.
YMMV.
__________________
LG OLED C8 | madVR 870 DPL HDR curve
quietvoid is online now   Reply With Quote
Old 6th May 2021, 06:57   #48  |  Link
telemO
Registered User
 
Join Date: Oct 2020
Location: France
Posts: 7
I made a test with one of my samples that was displaying artifacts, i.e. wrong color inserts ("flashes") in some areas : there are all gone with your last tool revision.
Wonderful !!!
I still have to test with another sample that such artifacts are gone as well, and then I'll become very confident using your parsing tool (which I did use anyway to share already some content in DoVi 8.1)

Quote:
Originally Posted by quietvoid View Post
No, the profile 7 stays except compatibility is better for devices that cannot play FEL files.
Am I understanding correctly that the file will still be made of BL+FEL as profile 7 but the FEL will contain an MEL type RPU so that the devices which cannot handle FEL would decode in MEL mode?

Quote:
Originally Posted by quietvoid View Post
It's still experimental, but the basic of it is to be able to add Dolby Vision metadata to an existing HDR10 file.
However I'd still suggest using the RPU with x265 instead.
YMMV.
Oh, that would be great ! I don't have the time to test in the coming weeks to make some mileage but it would worth some tries.
__________________
Ryzen 3950X w/ 64 Gb RAM on Win10 as transcoding rig (and daily use)
Panasonic HZ1000 (Oled HDR10+/DoVi TV) & Sony MDR-HW700DS (Audio decoder and headset spacialization)
telemO is offline   Reply With Quote
Old 6th May 2021, 13:30   #49  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Posts: 270
Quote:
Originally Posted by telemO View Post
Am I understanding correctly that the file will still be made of BL+FEL as profile 7 but the FEL will contain an MEL type RPU so that the devices which cannot handle FEL would decode in MEL mode?
Yes that's how it should work.
__________________
LG OLED C8 | madVR 870 DPL HDR curve
quietvoid is online now   Reply With Quote
Reply

Tags
dolby vision, dovi, hdr, rpu, x265

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 20:57.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.