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 > Capturing and Editing Video > New and alternative a/v containers

Reply
 
Thread Tools Search this Thread Display Modes
Old 18th September 2017, 20:40   #1581  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
Can somebody point me to a sample containing:

MaxCLL - Maximum Content Light Level
MaxFALL - Maximum Frame-Average Light Level
stax76 is offline   Reply With Quote
Old 29th October 2017, 12:27   #1582  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
MediaInfoXP v2.27 (MediaInfo v0.7.99):
https://sourceforge.net/projects/mul...9.zip/download

Quote:
* MediaInfo updated to v0.7.99 (2017-09-11)
* Build environment upgraded to Visual Studio 2017 (15.4)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

Last edited by LoRd_MuldeR; 29th October 2017 at 12:53.
LoRd_MuldeR is offline   Reply With Quote
Old 29th October 2017, 16:41   #1583  |  Link
StainlessS
HeartlessS Usurer
 
StainlessS's Avatar
 
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
Praise the Lord
Thanx
__________________
I sometimes post sober.
StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace

"Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???
StainlessS is offline   Reply With Quote
Old 2nd November 2017, 21:59   #1584  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
It looks like that method of numbering versions has been changed to YEAR.MONTH
https://sourceforge.net/projects/med...ary/mediainfo/
Atak_Snajpera is offline   Reply With Quote
Old 12th November 2017, 10:33   #1585  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 1,531
Hi Zenitram !
Many thanks for your continued work !
While going through my testfiles I found mediainfo recognising multichannel MPEG Audio Layer 2 streams
(I got 4-CH, 5-CH, 6-CH as 5.1, up to 8 shall be possible) as 2 channel streams.
I can supply some testfiles, if needed.
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're that issue working on. Synce invntoin uf lingöage..."
Emulgator is offline   Reply With Quote
Old 12th November 2017, 14:36   #1586  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
Quote:
Originally Posted by Emulgator View Post
Hi Zenitram !
Many thanks for your continued work !
While going through my testfiles I found mediainfo recognising multichannel MPEG Audio Layer 2 streams
(I got 4-CH, 5-CH, 6-CH as 5.1, up to 8 shall be possible) as 2 channel streams.
I can supply some testfiles, if needed.
AFAIK, MPEG Audio Layer II only supports channel modes "Stereo" (00), "Joint Stereo" (01), "Dual Channel" (10) and "Single Channel" (11). Same for Layer III, by the way.
https://web.archive.org/web/20150208...at/mpeghdr.htm

The so-called "MPEG Multichannel" extension uses a “channel matrixing scheme, where the additional channels are mixed into the two backwards compatible channels”, similar (but apparently not compatible to) Dolby Pro Logic.

So, technically, this would still be a Stereo file, just with the signals for the additional "sourround" channels mixed into the actual two (Stereo) channels...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊

Last edited by LoRd_MuldeR; 12th November 2017 at 14:44.
LoRd_MuldeR is offline   Reply With Quote
Old 12th November 2017, 20:25   #1587  |  Link
Emulgator
Big Bit Savings Now !
 
Emulgator's Avatar
 
Join Date: Feb 2007
Location: close to the wall
Posts: 1,531
Ah, thank you, that clears it up and at the same time explains why these multichannel files can be decoded with a stereo decoder.
I found Center mixed 50/50 into L/R, SL into L, SR into R.
__________________
"To bypass shortcuts and find suffering...is called QUALity" (Die toten Augen von Friedrichshain)
"Data reduction ? Yep, Sir. We're that issue working on. Synce invntoin uf lingöage..."
Emulgator is offline   Reply With Quote
Old 18th December 2017, 14:40   #1588  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
What are string codes for these items?

Code:
Mastering display color primaries        : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000
Mastering display luminance              : min: 0.0050 cd/m2, max: 4000.0000 cd/m2
Maximum Content Light Level              : 1529 cd/m2
Maximum Frame-Average Light Level        : 380 cd/m2
I'm checking list of parameters in documentation (Developers\List_Of_Parameters\Video.csv) and I can't find anything related to above items.

Last edited by Atak_Snajpera; 18th December 2017 at 14:48.
Atak_Snajpera is offline   Reply With Quote
Old 18th December 2017, 16:55   #1589  |  Link
Zenitram
Registered User
 
Join Date: Aug 2002
Location: France, Paris
Posts: 672
Quote:
Originally Posted by Atak_Snajpera View Post
What are string codes for these items?

Code:
Mastering display color primaries        : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000
Mastering display luminance              : min: 0.0050 cd/m2, max: 4000.0000 cd/m2
Maximum Content Light Level              : 1529 cd/m2
Maximum Frame-Average Light Level        : 380 cd/m2
I'm checking list of parameters in documentation (Developers\List_Of_Parameters\Video.csv) and I can't find anything related to above items.
they are currently not MediaInfo "standard" (they could in the future, maybe slightly modified). Field names can be seen with command line and " --Language=raw" or XML output in the GUI, e.g.:

Code:
<MasteringDisplay_ColorPrimaries>R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000</MasteringDisplay_ColorPrimaries>
<MasteringDisplay_Luminance>min: 0.0050 cd/m2, max: 4000.0000 cd/m2</MasteringDisplay_Luminance>
<MaxCLL>10000 cd/m2</MaxCLL>
<MaxFALL>111 cd/m2</MaxFALL>
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo
Zenitram is offline   Reply With Quote
Old 19th December 2017, 17:41   #1590  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
What is equivalent of

Code:
Transfer characteristics                 : PQ
in x265 settings

Code:
--transfer <string>           Specify transfer characteristics from bt709, unknown, reserved, bt470m, bt470bg, smpte170m,
                                 smpte240m, linear, log100, log316, iec61966-2-4, bt1361e, iec61966-2-1,
                                 bt2020-10, bt2020-12, smpte2084, smpte428, arib-std-b67. Default undef
According to this I'm guessing that smpte2084.

Last edited by Atak_Snajpera; 19th December 2017 at 17:44.
Atak_Snajpera is offline   Reply With Quote
Old 19th December 2017, 17:44   #1591  |  Link
Zenitram
Registered User
 
Join Date: Aug 2002
Location: France, Paris
Posts: 672
Quote:
Originally Posted by Atak_Snajpera View Post
What is equivalent of

Code:
Transfer characteristics                 : PQ
in x265 settings

smpte2084
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo
Zenitram is offline   Reply With Quote
Old 19th December 2017, 17:58   #1592  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
It would be much easier for user if you used well known values like in x264/x265 documentation. In this case smpte2084 instead of PQ,
bt2020nc, bt2020c instead of BT.2020 non-constant/constant.

Code:
--colorprim <string>          Specify color primaries from  bt709, unknown, reserved, bt470m, bt470bg, smpte170m,
                                 smpte240m, film, bt2020, smpte428, smpte431, smpte432. Default undef
--transfer <string>           Specify transfer characteristics from bt709, unknown, reserved, bt470m, bt470bg, smpte170m,
                                 smpte240m, linear, log100, log316, iec61966-2-4, bt1361e, iec61966-2-1,
                                 bt2020-10, bt2020-12, smpte2084, smpte428, arib-std-b67. Default undef
--colormatrix <string>        Specify color matrix setting from undef, bt709, fcc, bt470bg, smpte170m,
                                 smpte240m, GBR, YCgCo, bt2020nc, bt2020c, smpte2085, chroma-derived-nc, chroma-derived-c, ictcp. Default undef

Last edited by Atak_Snajpera; 19th December 2017 at 18:09.
Atak_Snajpera is offline   Reply With Quote
Old 19th December 2017, 20:25   #1593  |  Link
Zenitram
Registered User
 
Join Date: Aug 2002
Location: France, Paris
Posts: 672
Quote:
Originally Posted by Atak_Snajpera View Post
It would be much easier for user if you used well known values like in x264/x265 documentation. In this case smpte2084 instead of PQ,
bt2020nc, bt2020c instead of BT.2020 non-constant/constant.
I am in good mood, so let's go.

Sure, as soon as you can prove that what x264/x265 do is "well known" for all people involved with colors.
Spoiler: you won't be able to prove that, as I already had the opposite complain ("please use PQ wording, please use well know values, instead of this crazy SMPTE number") during some beta version.

Ho, BTW, please hint x265 people to change their name, because they do HEVC, look at the URL here https://en.wikipedia.org/wiki/High_E...y_Video_Coding , "265" is not known by everyone, look it is not in the URL of Wikipedia English (but it is in the French version, funny isn't it?), why do they mislead people with "265" thing? (I use "HEVC" word, sorry "H.265" people)

(A bit) more seriously, please don't do assumption that x265 people have the "real truth", they are not the center of the universe and they don't represent the industry as a whole (because the industry is not a whole), and in the case of "PQ" it is the "well known value" used by one of my sponsor, a lot known in this industry, and actually my policy is to try to avoid SMPTE number (side note: this is "SMPTE ST 2084", not "SMPTE 2084") when I can because they are difficult to memorize (and are less known than the BT ones), beside prioritizing American names (MPEG ones: AVC, HEVC...) other ITU names (H.264, H.265) when it is a joint venture with only different names in their respective standard bodies.
Warning, in the next release there is a change in order to meet this policy, as I was not aware of "well known names" (remark: someone complained about the exact opposite of your remark when he indicated new names, because I was using SMPTE numbers, the ones used by x265, and not "well known names" from his point of view, he wanted me to replace by his "well known values"), I used SMPTE numbers 431-2 and 432-1 (funny isn't it that such numbers are difficult to differentiate? Worse, one is "RP" and the other is "EG" and 431 alone does not exist, it is 431-2) only because I was not aware of "well known names" and I'll replace them by "DCI P3" and "Display P3" (commit).

summary: your "well known values" are not the "well known values" of some other people, and whatever I choose, someone will complain, this is not the first time and it will not be the last time, as MediaInfo is used by a lot of very different people in this industry, each "community" having different "well known value", when I choose a name I am sure another "community" will complain. I may add option "choose your community" in the future if people are crazy enough for paying for seeing their "well known values" instead of the ones I chose.

PS: bt2020nc means exactly "BT.2020 non-constant", I just show something more "readable", why should I limit the display to a limitation of the command line? I may use "codes" (short names without spaces) internally in the future, but nothing says that I would use x264/x265 choices vs other tools choices.

PPS: in an ideal world, everyone would speak the same language and everyone would use the same "well known values", unfortunately we are not in this ideal world so if you don't do any "translation", someone else will do the same remark about his need to have a translation between your values and his values.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo
Zenitram is offline   Reply With Quote
Old 19th December 2017, 20:40   #1594  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
Do you have a full list of "your well known codes" so I could translate them to "my well known codes" for x264/x265 use?
I just need to know that I pass correct codes to encoder. That's all.

Last edited by Atak_Snajpera; 19th December 2017 at 20:48.
Atak_Snajpera is offline   Reply With Quote
Old 19th December 2017, 21:06   #1595  |  Link
Zenitram
Registered User
 
Join Date: Aug 2002
Location: France, Paris
Posts: 672
Quote:
Originally Posted by Atak_Snajpera View Post
Do you have a full list of "your well known codes" so I could translate them to "my well known codes" for x264/x265 use?
I just need to know that I pass correct codes to encoder. That's all.
Here for MPEG related value, Here for DPX values.

but right, definitely a need of better doc (not in code)
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo
Zenitram is offline   Reply With Quote
Old 20th December 2017, 18:17   #1596  |  Link
Kurtnoise
Swallowed in the Sea
 
Kurtnoise's Avatar
 
Join Date: Oct 2002
Location: Aix-en-Provence, France
Posts: 5,191
#MediaInfo users, we need some testers of #MediaInfoOnline technology preview.

MediaInfo in your browser, without installing any software and everything stays on your machine.

mediaarea.net/MediaInfoOnline
Kurtnoise is offline   Reply With Quote
Old 21st December 2017, 14:59   #1597  |  Link
Q-the-STORM
Registered User
 
Join Date: Sep 2012
Posts: 174
Quote:
Originally Posted by Kurtnoise View Post
#MediaInfo users, we need some testers of #MediaInfoOnline technology preview.

MediaInfo in your browser, without installing any software and everything stays on your machine.

mediaarea.net/MediaInfoOnline
what kind of testing do you need? Testing various files and comparing to local mediainfo output, or testing with various browsers, OS, etc...

Text output slightly differs from v17.12 in this line:

v17.12
Format settings, RefFrames

online
Format settings, ReFrames
Q-the-STORM is offline   Reply With Quote
Old 21st December 2017, 15:03   #1598  |  Link
Zenitram
Registered User
 
Join Date: Aug 2002
Location: France, Paris
Posts: 672
Quote:
Originally Posted by Q-the-STORM View Post
what kind of testing do you need? Testing various files and comparing to local mediainfo output, or testing with various browsers, OS, etc...
testing with various browsers and report if something does not work, ideas for improvement...

Quote:
Originally Posted by Q-the-STORM View Post
Text output slightly differs from v17.12 in this line:

v17.12
Format settings, RefFrames

online
Format settings, ReFrames
Hum... old bug, should not be there anymore, we'll work on that, thanks.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo
Zenitram is offline   Reply With Quote
Old 21st December 2017, 16:51   #1599  |  Link
Q-the-STORM
Registered User
 
Join Date: Sep 2012
Posts: 174
I tested a few more files just to see if I could find more differences, only found two:

I got an old folder with 8 calibration mp4s.
Online doesn't show x264 settings and nominal bitrate on 7 of them
https://www.diffchecker.com/oUUJHGmc
the 8th does correctly show x264 settings and nominal bitrate, it's the only one of them that is larger than 1MB, the rest are smaller than 1MB.

This one doesn't show source duration and Source stream size online
https://www.diffchecker.com/cgPO4RsV
though in this case source duration and duration are the same so it doesn't matter much, though it would be nice to have the exact same output online if possible.

I tested old youtube downloads, some old xvids, vobs from DVDs, some more recent x264 mkvs, hevc hdr video, TV recordings, and some more unusual video like vfr cellphone video, unusual framerates, various containers (mp4, mkv, ts, flv, m2ts), also besides video, some flac, mp3, png, gif and some other files, all had the same output as 17.12.

btw I'm using Win 10 + chrome x64
Q-the-STORM is offline   Reply With Quote
Old 21st December 2017, 16:55   #1600  |  Link
Zenitram
Registered User
 
Join Date: Aug 2002
Location: France, Paris
Posts: 672
Quote:
Originally Posted by Q-the-STORM View Post
I tested a few more files just to see if I could find more differences, only found two
Thank you for the test, it is useful. Is it possible to get the file?

Quote:
Originally Posted by Q-the-STORM View Post
(...) though it would be nice to have the exact same output online if possible.
We agree! It is the goal.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo

Last edited by Zenitram; 21st December 2017 at 17:40.
Zenitram is offline   Reply With Quote
Reply

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 10:42.


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