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. |
7th September 2019, 16:10 | #81 | Link | ||
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
Quote:
|
||
24th September 2019, 17:50 | #84 | Link |
Registered User
Join Date: Oct 2007
Posts: 385
|
hi quietvoid
I was playing around with a recent hdr10+ disc I got. The tool dialog added something called "Mastering peak flag enabled": Code:
Parsing HEVC file for dynamic metadata... [00:02:25] 100% Reading parsed dynamic metadata... Mastering peak flag enabled Mastering peak flag enabled Mastering peak flag enabled Mastering peak flag enabled Mastering peak flag enabled Done. Writing metadata to JSON file... Done. Then I tried to serve the json to x265 and encode the vid. Looked at the MediaInfo report and it shows just this: Code:
HDR format : SMPTE ST 2094 App 4, Version 1 Code:
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible Code:
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible Last edited by mini-moose; 24th September 2019 at 17:53. |
24th September 2019, 18:40 | #85 | Link | ||
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
That part of the metadata was not implemented, I can't remember whether it was in the specs sheet I was using. If it was, I did note that it was not supposed to be enabled in the version's specs. So it is possible there is a new version of the spec, where some of these flags are actually being used now. I had received some feedback regarding a disc failing to parse recently, but I have not had the time to look into it. Can you share the title? If I remember correctly it was Shaun of the Dead. Thanks. Edit: I have done a bit of research and it seems the HDR10+ LLC alliance has published a press release on 2019/09/04. Quote:
Last edited by quietvoid; 24th September 2019 at 19:06. Reason: Info |
||
24th September 2019, 19:51 | #86 | Link | |
Registered User
Join Date: Oct 2007
Posts: 385
|
Quote:
Last edited by mini-moose; 24th September 2019 at 20:09. |
|
27th September 2019, 22:19 | #87 | Link | ||
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
Updated the parser to 0.2.4 Quote:
|
||
28th September 2019, 12:25 | #88 | Link | |
Registered User
Join Date: Oct 2007
Posts: 385
|
Quote:
Edge case you mean why I couldn't get x265 to identify hd10+ without cutting out the first second? |
|
28th September 2019, 13:47 | #89 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
So now if the parser doesn't error, the metadata should be valid. Last edited by quietvoid; 28th September 2019 at 14:13. |
|
10th November 2019, 09:42 | #90 | Link |
Registered User
Join Date: Oct 2019
Posts: 2
|
problem with American Gangster UHD BluRay
Hi all,
First of all let me thank quietvoid for the hdr10+ parser, works great and very easy to use! My only issue is the same that mini-moose mentioned a few posts back. I'm trying to encode the quite recent American Gangster BD which has hdr10+. I used the parser as advised to get the json file with the metadata, but after encoding the movie, the resulted file doesn't have the hdr10+ flag in mediainfo. It shows: SMPTE ST 2094 App 4. What can be the issue, maybe the parser needs another update? Thanks in advance! |
20th November 2019, 20:42 | #91 | Link |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Sorry, I hadn't seen your post.
As far as I'm aware, HDR10+ is a format in conformance with SMPTE ST 2094 App 4. MediaInfo sometimes includes a HDR10+ profile compatibility, but I have no idea what they mean. The "HDR10+ profile A/B compatible" flag seems to be lost after reencode sometimes, however the presence of ST2094 App 4 metadata is still detected. It mostly happens with titles released after the September 4 2019 specifications release. If anyone has information regarding the HDR10+ profiles, it would be useful. Otherwise I don't really know what is missing for HDR10+ profiles compatibility. Last edited by quietvoid; 20th November 2019 at 20:45. |
20th November 2019, 21:26 | #92 | Link | |
Registered User
Join Date: Oct 2007
Posts: 385
|
Quote:
|
|
20th November 2019, 22:46 | #93 | Link |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Well, the metadata gets parsed correctly.
There might be some data missing (in the JSON or after x265's encode) but without the new specifications or an updated example JSON I don't know what the difference would be. |
21st November 2019, 07:25 | #94 | Link |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Sorry for the double post.
I've tested with the x265 example and it always has HDR10+ Profile B compatible. Turns out it's not being flagged if there is no BezierCurveData object in the JSON. So added it (it used to only be added when there is actual data for it), and refactored the code to be more readable. Also improved the JSON to be properly generated. Fixed the cargo run not working, tested that all the input/output arguments work just like before. Hopefully nothing breaks. Updated to 0.2.5 https://github.com/quietvoid/hdr10plus_parser/releases Last edited by quietvoid; 21st November 2019 at 07:35. |
22nd November 2019, 01:09 | #96 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Further more, I just stumbled across this in the September 2019 White Paper from https://hdr10plus.org/wp-content/upl...WhitePaper.pdf
Quote:
|
|
22nd November 2019, 01:16 | #97 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Actually with cropping you would need to adjust the metadata, but resizing should be fine, as long as the relative dimensions and aspect ratio stay the same (but to change that you would probably crop anyway).
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
22nd November 2019, 03:06 | #98 | Link | |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 574
|
Quote:
The Bezier curve data specifies info for the curve generation only. The processing windows (which do mention pixel coordinates) are not in this version. The only thing that might need adjustment is the average/max RGB values if they were calculated with the black bars not accounted for. Unless I'm missing something.. |
|
22nd November 2019, 09:45 | #99 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Oh, I didn't check what might be in there, I only remember from implementing HEVC metadata parsing that it contains the processing windows - on second thought they would probably also need adjustment for scaling, but thats easier since you just have to scale their coordinates.
But even then, resizing the processing windows is trivial, what the Whitepaper refers to would indicate actually having to determine full new metadata, which can be avoided that way.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
31st December 2019, 16:26 | #100 | Link |
Registered User
Join Date: Dec 2014
Posts: 240
|
just a question... shoudn't be then all HDR video encoded without cropping? average CLL and MAX-CLL are calculated with the black bars, if I am right. so without it, it could cause playing somehow different, as with black bars... it's just my quess...
__________________
AMD Ryzen 9 5950X, 32GB DDR4-3200 CL16, RTX 3060, 2TB NVMe PCIE4.0, NAS with 8x16TB HDD |
Thread Tools | Search this Thread |
Display Modes | |
|
|