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 |
3rd February 2019, 17:08 | #1642 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
mediaarea.net/MediaInfoOnline <- any plans to show 'full' data?
Any plans to support HDR-10+ HEVC files? (I can create HDR10+ files using x265 and verify that the file contains HDR-10+ metadata using hdr10plus_parser, sadly mediainfo doesn't show any hints about the HDR-10+ data atm.) Cu Selur |
3rd February 2019, 17:15 | #1643 | Link |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
I didn't think it is useful and I saw no interest on my side, but if it is it should not be long to implement (note: at some point I may decide to offer options only to MediaArea members).
Provide files please. I was not finding HDR10+ specs, but as hdr10plus_parser is open source it should be easy to understand the new metadata parts.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
3rd February 2019, 17:20 | #1644 | Link | |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
Quote:
|
|
6th February 2019, 16:03 | #1645 | Link |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
OK, I was motivated, I started something, without being sure about what would be interesting to show e.g. only HDR10+ presence?
For the moment (work in progress, can change in the future), MediaTrace dump is Code:
0006733 sei (62 bytes) 0006733 Header (6 bytes) 0006733 size: 58 (0x0000003A) 0006737 nal_unit_type: 39 (0x27) - (6 bits) 0006737 nuh_layer_id: 0 (0x00) - (6 bits) 0006738 nuh_temporal_id_plus1: 1 (0x1) - (3 bits) 0006739 sei message - user_data_registered_itu_t_t35 - SMPTE ST 2094 App 4 (51 bytes) 0006739 sei message header (2 bytes) 0006739 payload_type_byte: 4 (0x04) 000673A payload_size_byte: 49 (0x31) 000673B itu_t_t35_country_code: 181 (0xB5) 000673C terminal_provider_code: 60 (0x003C) 000673E terminal_provider_oriented_code_message_idc: 1 (0x0001) 0006740 application_identifier: 4 (0x04) 0006741 application_version: 1 (0x01) 0006742 num_windows: 1 (0x1) - (2 bits) 0006742 targeted_system_display_maximum_luminance: 0 (0x0000000) - (27 bits) 0006745 targeted_system_display_actual_peak_luminance_flag: No 0006745 window (38 bytes) 0006745 max_luminance_r: 0 (0x00000) - (17 bits) - 0.00000 cd/m2 0006747 max_luminance_g: 0 (0x00000) - (17 bits) - 0.00000 cd/m2 000674A max_luminance_b: 0 (0x00000) - (17 bits) - 0.00000 cd/m2 000674C avg_luminance: 233 (0x000E9) - (17 bits) - 0.00233 cd/m2 000674E num_distribution_maxrgb_percentiles: 9 (0x9) - (4 bits) 000674E distribution_maxrgb - 1 (0x1) - 0 (0x0) (3 bytes) 000674E distribution_maxrgb_percentile: 1 (0x01) - (7 bits) 000674F distribution_maxrgb_data: 0 (0x00000) - (17 bits) 0006751 distribution_maxrgb - 5 (0x5) - 6886 (0x1AE6) (3 bytes) 0006751 distribution_maxrgb_percentile: 5 (0x05) - (7 bits) 0006752 distribution_maxrgb_data: 6886 (0x01AE6) - (17 bits) 0006754 distribution_maxrgb - 10 (0xA) - 88 (0x58) (3 bytes) 0006754 distribution_maxrgb_percentile: 10 (0x0A) - (7 bits) 0006755 distribution_maxrgb_data: 88 (0x00058) - (17 bits) 0006757 distribution_maxrgb - 25 (0x19) - 0 (0x0) (3 bytes) 0006757 distribution_maxrgb_percentile: 25 (0x19) - (7 bits) 0006758 distribution_maxrgb_data: 0 (0x00000) - (17 bits) 000675A distribution_maxrgb - 50 (0x32) - 146 (0x92) (3 bytes) 000675A distribution_maxrgb_percentile: 50 (0x32) - (7 bits) 000675B distribution_maxrgb_data: 146 (0x00092) - (17 bits) 000675D distribution_maxrgb - 75 (0x4B) - 412 (0x19C) (3 bytes) 000675D distribution_maxrgb_percentile: 75 (0x4B) - (7 bits) 000675E distribution_maxrgb_data: 412 (0x0019C) - (17 bits) 0006760 distribution_maxrgb - 90 (0x5A) - 858 (0x35A) (3 bytes) 0006760 distribution_maxrgb_percentile: 90 (0x5A) - (7 bits) 0006761 distribution_maxrgb_data: 858 (0x0035A) - (17 bits) 0006763 distribution_maxrgb - 95 (0x5F) - 1583 (0x62F) (3 bytes) 0006763 distribution_maxrgb_percentile: 95 (0x5F) - (7 bits) 0006764 distribution_maxrgb_data: 1583 (0x0062F) - (17 bits) 0006766 distribution_maxrgb - 99 (0x63) - 4170 (0x104A) (3 bytes) 0006766 distribution_maxrgb_percentile: 99 (0x63) - (7 bits) 0006767 distribution_maxrgb_data: 4170 (0x0104A) - (17 bits) 0006769 fraction_bright_pixels: 0 (0x000) - (10 bits) 000676B mastering_display_actual_peak_luminance_flag: No 000676B window (0 bytes) 000676B color_saturation_mapping_flag: No Code:
Format : HEVC Format/Info : High Efficiency Video Coding Commercial name : HDR10+ Format profile : Main 10@L5@Main Codec ID : hev1 Color range : Limited Matrix coefficients : BT.709 HDR_Format : SMPTE ST 2094 App 4 version 1
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
16th February 2019, 19:29 | #1647 | Link | |
Registered User
Join Date: Jan 2011
Location: France
Posts: 36
|
I'm trying to get the audio "Commercial name" field through the MediaInfo dll with this file: https://we.tl/O0BfDADZbu
MediaInfo gives me: Code:
ID : 2 Format : MLP FBA Format/Info : Meridian Lossless Packing FBA Commercial name : Dolby TrueHD Codec ID : A_TRUEHD Duration : 11 s 11 ms Bit rate mode : Variable Maximum bit rate : 6 423 kb/s Channel(s) : 8 channels Channel layout : L R C LFE Ls Rs Lb Rb Sampling rate : 48.0 kHz Frame rate : 1 200.000 FPS (40 SPF) Compression mode : Lossless Language : English Default : Yes Forced : No I'm using this request, is it right ? Quote:
|
|
17th February 2019, 21:21 | #1648 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
@Zenitram: When does MediaInfo report an jpg as Video and when as Image?
I got a folder with 431 images and when I analyse for example image 00001.jpg it's reported as Video, same for 00401.jpg but 004009.jpg and upwards is only reported as Image. -> this really is a pain, is there a way to force detecting jpg always as Image or Video ? |
26th February 2019, 22:24 | #1649 | Link |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
Suffering a bit with all the HDR metadata I have to handle.
Now moving to a dedicated line for HDR format. Below are some examples of the expected line for HDR10 (actually SMPTE ST 2086), HDR10+ (actually SMPTE ST 2094-40 with lot of restrictions, I finally got the specs so I have the exact restrictions), Dolby Vision, SL-HDR (1&2), any potential issues you see? Code:
HDR format : SMPTE ST 2086, HDR10 compatible HDR format : SMPTE ST 2094-40, Version 1, HDR10+ Profile A compatible HDR format : Dolby Vision, Version 1.0, dvhe.04.06, BL+EL+RPU HDR format : SL-HDR1, Version 1.0, Parameter-based, constant HDR format : SL-HDR1, Version 1.0, Parameter-based, non-constant HDR format : SL-HDR2, Version 0.0, Parameter-based - HLG is not listed as it is not additional metadata, "just" a specific transfer characteristics. - HDR10 & HDR10+ are actually commercial names, but other HDR formats have no difference between technical and commercial name (SL-HDR is listed in ETSI 103-433 but they stipulate the name in specs as they do with e.g AC-3 in ETSI 102-366) so I think it is not good to add a new line for HDR format commercial name, to be debated. - HDR10 & HDR10+ are listed also if other constraints are met e.g. PQ transfer characteristics. - I have constraints from sponsors so I'll not able to accept all advice even if I want to.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
26th February 2019, 22:28 | #1650 | Link |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
I have it fine when I test with latest DLL and the C++ interface (C++ interface should not change the content of the field compared to the programming language you use) so I don't plan to investigate more.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
26th February 2019, 22:33 | #1651 | Link | |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
Quote:
MediaInfo --File_TestContinuousFileName=0 YourFileName.ext (doable also with API with MediaInfo::Option())
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
|
27th April 2019, 03:26 | #1653 | Link |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
some words of appreciation
@Zenitram
I just want to let you know that I use MediaInfo in my recent project mpv.net (a media player for Windows) and there wasn't any problems and I don't remember any problems using it in staxrip all the years, it's fast and reliable. In staxrip it's used in countless locations, in mpv.net it is used to show some on screen info and to show info in the context menu. https://postimg.cc/t1NGJF1z https://github.com/stax76/mpv.net#context-menu https://github.com/stax76/mpv.net#architecture thanks, danke, merci!
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists |
14th May 2019, 11:40 | #1654 | Link |
Registered User
Join Date: Nov 2005
Posts: 583
|
HLG support
Greetings. The Japan Geographic youtube channel is now playing ARIB STD-B67 encoded streams. Other channels use PQ encoding. But mediainfo only show vp92 for the downloaded clips. Can such info be added in future versions? Many thanks and best regards, |
14th May 2019, 13:10 | #1655 | Link | |
Registered User
Join Date: Apr 2008
Location: Russia, Vladivostok
Posts: 2,787
|
Quote:
__________________
AMD Ryzen 5 3600 /GIGABYTE B450 Gaming X /Patriot 32Gb@3200 /Kingston 500Gb M.2 /RTX 4060 /Samsung U28R550UQI /OLED Philips 55OLED707 /Yamaha RX-V471 + NS-555 + NS-C444 + NS-333 + YST-SW215 |
|
15th May 2019, 08:53 | #1656 | Link |
Registered User
Join Date: Nov 2005
Posts: 583
|
JAPAN GEOGRAPHIC
https://www.youtube.com/channel/UCoq...fYnAk2g/videos |
15th August 2019, 16:09 | #1657 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
Since when and why did mediainfo change reporting TrueHD combi stream as
Code:
Format : TrueHD / AC-3 Code:
Format : AC-3 Cu Selur |
15th August 2019, 17:20 | #1658 | Link | |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
Quote:
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists |
|
15th August 2019, 21:55 | #1659 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Unlike a DTS core the AC-3 tracks in these streams are simply AC-3 tracks, there is nothing different about them. It really is just a second audio track muxed into the file along with the TrueHD one so it is better to report them that way. You can rip the AC-3 out and only have the TrueHD track or vice-versa.
__________________
madVR options explained |
21st August 2019, 19:01 | #1660 | Link | |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
Quote:
For pure TrueHD, they are listed now as: Code:
Format : MLP FBA Format/Info : Meridian Lossless Packing FBA Commercial name : Dolby TrueHD For interleaved TrueHD / AC-3, looks like we forgot this case while moving to the new display, I need to find a good way for displaying it. At whatever is the outcome, one thing sure is that MLP FBA should be displayed, the "best" stream should be listed for sure (here MLP FBA over AC-3 because lossless is better than lossy).
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
|
|
|