HDR Renaming Tag for Movies/TV Shows Not Working?
#16
okay, but then your files https://paste.kodi.tv/exomesadeq and https://paste.kodi.tv/awusifarut are not HDR?!
looks like mediainfo is right here because it is only reporting HDR values where the colour_primaries have the right values
tinyMediaManager - THE media manager of your choice - available for Windows, macOS and Linux
Help us translate tinyMediaManager at Weblate | Translations at 66%
Found a bug or want to submit a feature request? Contact us at GitLab
#17
(2020-04-11, 20:15)mlaggner Wrote: okay, but then your files https://paste.kodi.tv/exomesadeq and https://paste.kodi.tv/awusifarut are not HDR?!
looks like mediainfo is right here because it is only reporting HDR values where the colour_primaries have the right values
Indeed it seems to be that .. These are films that was marked HDR when I got them, but if they are encoded with BT709 so HDTV quality and the color resolution is 10bits can we say that it s Is HDR?
For mediaInfo the answer is no, I have the impression that mediainfo only detects HDR10 and HDR10+ 
It would be good for other people to express themselves on the subject, however it may be when I retrieve the films, they were stipulated encoded in HDR.10bit.
I don't really know what to think about it ..
#18
Seems if it finds <HDR_Format_Compatibility>HDR10</HDR_Format_Compatibility> would be the key to work off, whatever is in that field then can be labeled?

Here is mt XML file for spiderman2
https://paste.kodi.tv/zojutuqoge

<HDR_Format>SMPTE ST 2086</HDR_Format>
<HDR_Format_Compatibility>HDR10</HDR_Format_Compatibility>

Has the codes we can use maybe?
#19
HDR10 will be usable with ${hdrFormat}
tinyMediaManager - THE media manager of your choice - available for Windows, macOS and Linux
Help us translate tinyMediaManager at Weblate | Translations at 66%
Found a bug or want to submit a feature request? Contact us at GitLab
#20
Yes but I do not have the impression that we can only use $ {hdrFormat} because according to the films we do not have the same 'value'
Looked for example the star wars which is in HDR10 + https://paste.kodi.tv/igozinomek, there is two "value" with hdr
<HDR_Format>SMPTE ST 2094 App 4</HDR_Format>
<HDR_Format_Version>1</HDR_Format_Version>

In addition, kodi skin which uses the HDR, HDR10 and HDR10+ tags requires a very precise file naming, in my case with aeon mq8, the file must be '-hdr' or '.hdr' to display the HDR tag And '-10bit' or '.10bit' to display the 10Bits tag.

Use a condition of presence of any HDR 'value' given by mediainfo which certifies that we are in HDR then added the 'value' ${movie.mediaInfoVideoBitDepth} followed by bit ...
this seems to be the right way ..

Then I come back to the fact that a good number of films are encoded in 10bits but not necessarily in HDR because it uses an encoding in BT709 (standard for HDTV) .. and therefore after passage in the rename function I find myself with a lot of Movie marked '-sdr-10bit' whereas the encoders of these files marked them at the start '4K.hdr.10bit' I am a little lost .. should we have marked HDR a movie encoded BT709 with 10bit resolution Color ??
Anyway, we are moving forward ..
Have a nice day..
#21
(2020-04-13, 09:47)MX10.AC2N Wrote: Use a condition of presence of any HDR 'value' given by mediainfo which certifies that we are in HDR then added the 'value' ${movie.mediaInfoVideoBitDepth} followed by bit ...
this seems to be the right way ..

I've just designed it this way:
${HDR} is true if one of the three mediainfo fields is filled (HDR_Format, HDR_Format_Commercial, HDR_Format_Compatibility).
${hdrFormat} contains the content of the first found mediainfo tag in the following search order:

1. HDR_Format_Commercial
2. HDR_Format_Compatibility
3. HDR_Format

dunno if we should do more logic inside tmm because there is _no real_ standard/logic how to follow
tinyMediaManager - THE media manager of your choice - available for Windows, macOS and Linux
Help us translate tinyMediaManager at Weblate | Translations at 66%
Found a bug or want to submit a feature request? Contact us at GitLab
#22
(2020-04-13, 14:26)mlaggner Wrote:
(2020-04-13, 09:47)MX10.AC2N Wrote: Use a condition of presence of any HDR 'value' given by mediainfo which certifies that we are in HDR then added the 'value' ${movie.mediaInfoVideoBitDepth} followed by bit ...
this seems to be the right way ..

I've just designed it this way:
${HDR} is true if one of the three mediainfo fields is filled (HDR_Format, HDR_Format_Commercial, HDR_Format_Compatibility).
${hdrFormat} contains the content of the first found mediainfo tag in the following search order:

1. HDR_Format_Commercial
2. HDR_Format_Compatibility
3. HDR_Format

dunno if we should do more logic inside tmm because there is _no real_ standard/logic how to follow 

Indeed, I think that it is necessary to indicate HDR when one of the 3 conditions is met and add behind the 'value' of color resolution, and add just behind 'bit'. In order to have 'my movie'-hdr-10bit.mkv
No need for more .. I am surprised to see so many films marked HDR.10bit by the people who do the encoding and who are finally detected as SDR-10bit by mediaInfo since they are encoded with BT709 ... 
Or maybe we should consider
SDR => BT709 with 8 bit color resolution
HDR => BT709 with 10 bit color resolution 
HDR10 => As soon as we have one of the 3 conditions $ {HDRFormat ... fulfilled
HDR10+ => if ${HDRFormat} say SMPTE ST 2094 App 4

Logout Mark Read Team Forum Stats Members Help
HDR Renaming Tag for Movies/TV Shows Not Working?0