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.

 Register FAQ Calendar Search Today's Posts Mark Forums Read

14th April 2018, 22:39   #1621  |  Link
LoRd_MuldeR
Software Developer

Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 12,906
I'm using MediaInfo with XML output to analyze media files and extract the cover artwork.

But, unfortunately, I noticed that latest MediaInfo (v18.03.1) does not output <Cover_Data> tag anymore, even with --Full option set

I suspect this has something to do with:
Quote:
 Attachments: do not provide anymore attachments content in XML by default, reducing XML output size
What CLI option do I have to set to get the cover data again?

__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.

Last edited by LoRd_MuldeR; 14th April 2018 at 22:42.

15th April 2018, 13:16   #1622  |  Link
Zenitram
Registered User

Join Date: Aug 2002
Location: France, Paris
Posts: 657
Quote:
 Originally Posted by LoRd_MuldeR I'm using MediaInfo with XML output to analyze media files and extract the cover artwork. But, unfortunately, I noticed that latest MediaInfo (v18.03.1) does not output tag anymore, even with --Full option set I suspect this has something to do with: What CLI option do I have to set to get the cover data again?
Right, I removed the presence of cover data by default, as it is not often used and make MediaInfo creating big XML files and with some (little) performance impact by default.

But it definitely lacks of documentation about how to active it, [documentation is on my ToDo-list](https://mediaarea.net/Vote/Mediainfo...umentation-127).

Magic hidden setting: add " --Cover_Data=base64" (or MediaInfo::Option("Cover_Data", "base64").

As usual when there are lot of users, a change in default value has some impact on a couple of users , sorry for that.
__________________

15th April 2018, 14:21   #1623  |  Link
LoRd_MuldeR
Software Developer

Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 12,906
Quote:
 Originally Posted by Zenitram But it definitely lacks of documentation about how to active it, [documentation is on my ToDo-list](https://mediaarea.net/Vote/Mediainfo...umentation-127).
Yeah, writing documentation is pain. Not only it takes a whole lot of time (if you want to do it properly), it tends to be outdated the very next day

Quote:
 Originally Posted by Zenitram Magic hidden setting: add " --Cover_Data=base64" (or MediaInfo::Option("Cover_Data", "base64").
Thanks for the quick reply. That works like a charm!

Quote:
 Originally Posted by Zenitram As usual when there are lot of users, a change in default value has some impact on a couple of users , sorry for that.
No problem. I understand why the "new" default makes sense for most use-cases. And with the "magic setting" all is good for my use-case.
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.

Last edited by LoRd_MuldeR; 15th April 2018 at 14:23.

 23rd May 2018, 08:32 #1624  |  Link Selur Registered User     Join Date: Oct 2001 Location: Germany Posts: 5,597 @Zenitram: Small follow-up question regarding 'Mastering display color primaries'. So far we know that'Display P3' <> 'DCI-P3 D65' <> 'R(x=0.680, y=0.320), G(x=0.265, y=0.690), B(x=0.150, y=0.060), White point(x=0.3127, y=0.3290)' 'DCI P3' <> 'DCI-P3 Theater' <> 'R(x=0.680, y=0.320), G(x=0.265, y=0.690), B(x=0.150, y=0.060), White point(x=0.314, y=0.3510)' But now I encountered a source where 'Mastering display color primaries' just states 'BT.2020'. What values does this refer to? Also are there other constants used? Cu Selur __________________ Hybrid here in the forum, homepage
23rd May 2018, 09:29   #1625  |  Link
Zenitram
Registered User

Join Date: Aug 2002
Location: France, Paris
Posts: 657
Quote:
 Originally Posted by Selur But now I encountered a source where 'Mastering display color primaries' just states 'BT.2020'. What values does this refer to?
From H.265 specs:
Rec. ITU-R BT.2020-2
primary x y
green 0.170 0.797
blue 0.131 0.046
red 0.708 0.292
white D65 0.3127 0.3290

Quote:
 Originally Posted by Selur Also are there other constants used?
For the moment, no more values are mapped, but hypothetically all values from H.265 (and more) could be mapped.
__________________

 23rd May 2018, 09:30 #1626  |  Link Selur Registered User     Join Date: Oct 2001 Location: Germany Posts: 5,597 Thanks! __________________ Hybrid here in the forum, homepage
 12th August 2018, 12:09 #1627  |  Link Murvel Registered User   Join Date: Aug 2018 Posts: 1 Suggestion for MediaInfo Thanks for a great app. I use it sometimes to compare different edits of the same clip, and I think it would be helpful if the app would always report the exact duration of a clip, down to seconds or even frames. As of now, you see duration in seconds for shorter clips only, whereas hours and minutes is all you see for longer clips. Thanks again.
12th August 2018, 12:31   #1628  |  Link
LoRd_MuldeR
Software Developer

Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 12,906
Quote:
 Originally Posted by Murvel Thanks for a great app. I use it sometimes to compare different edits of the same clip, and I think it would be helpful if the app would always report the exact duration of a clip, down to seconds or even frames. As of now, you see duration in seconds for shorter clips only, whereas hours and minutes is all you see for longer clips. Thanks again.
Try with options --Full and --Language=raw, which should give you output like this:
Code:
.\mediainfo.i686.exe --Full --Language=raw "C:\Path\to\Movie.mkv"
General
[...]
Duration                         : 5764920
Duration/String                  : 1h 36mn
Duration/String1                 : 1h 36mn 4s 920ms
Duration/String2                 : 1h 36mn
Duration/String3                 : 01:36:04.920
Duration/String4                 : 01:36:04:23
Duration/String5                 : 01:36:04.920 (01:36:04:23)
[...]
Or, alternatively, use --Output=XML option:
Code:
.\mediainfo.i686.exe --Output=XML "C:\Path\to\Movie.mkv"
<?xml version="1.0" encoding="UTF-8"?>
<MediaInfo
xmlns="https://mediaarea.net/mediainfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://mediaarea.net/mediainfo https://mediaarea.net/mediainfo/mediainfo_2_0.xsd"
version="2.0">
<creatingLibrary version="18.05" url="https://mediaarea.net/MediaInfo">MediaInfoLib</creatingLibrary>
[...]
<FileSize>4334673157</FileSize>
<Duration>5764.920</Duration>
[...]
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.

Last edited by LoRd_MuldeR; 12th August 2018 at 12:35.