Quote:
Originally Posted by Zenitram
No, that is the issue: it is in the stream only; and HDR10 says that a stream should have a constant value; so from MediaInfo developer (me) point of view, it is not worth it to scan the entire stream just for checking that the stream is conform to HDR10 specs else show the maximum value.
Technically not the most difficult in MediaInfo, just need to load in memory the whole file for a very corner case.
|
No problem, I think the job should be do by the muxer, this is why I asked to cool advertise to try it
When the muxer does the job, it could analyze the max values for each M2TS and keep the higher values as default value ?!
But the values will be wrong for 3 or all M2TS segments, so is it useful to use that when encoding to x265 ?