ITUNESGAPLESS, ITUNESHDVIDEO, PODCAST fields do not accept 0

Bug Reports Fixed Bugs
1

very small bug

When I entered repeatedly unsupported value 0 to ITUNESGAPLESS(pgap) / ITUNESHDVIDEO(hdvd) / PODCAST(pcst) field,

Mp3tag creates duplicate atom to the m4a file.

Why is 0 unsupported? Is there any reason? I hope that 3 fields will accept 0.
COMPILATION(cpil), ITUNESADVISORY(rtng) field accept 0/1 value (off/on) correctly.
https://docs.mp3tag.de/mapping

v2.77
Thank you very much for development.

2

these fields were more or less invented for iTunes. They are there to indicate that a file has a certain property like being a podcast, for instance.

See https://docs.mp3tag.de/mapping/#podcast that only 1 is a valid value. Otherwise you have to delete it.
This is no bug, this is the way that iTunes uses this unofficial field extension.

3

Yes, I know.
But Mp3tag creates duplicate atom box. I think this is a small bug or problem.
Check box structure.
https://dl.dropboxusercontent.com/s/4ssrvql...oqpr/sample.txt

And see https://docs.mp3tag.de/mapping/#tag-fields-exclusive-to-mp4
ITUNESHDVIDEO | hdvd | Boolean flag for HD video (0/1)← 0 is available
Now iTunes use 1 for HD, 2 for FHD.

4

ITUNESHDVIDEO is described as boolean - which is probably not true any more. And the 0 should be treated just like the other iTunes proprietary fields.
For iTUNESGAPLESS you get the description
"Syntax: Set value to 1 or delete the field."
The same applies to
"PODCAST
Syntax: Either enter the value 1 or delete the field"

For boolean values you can generally claim that any value that is not 0 is treated as true.
So entering 0 for ITUNESHDVIDEO creates a statement that "this is no HD video" - which is probably true for most files in a library. So to save space, the 0-value is not stored.

And again: even though MP3tag can create a non-standard field or atom, it is not responsible what the target application makes of it. The advice "Syntax: Set value to 1 or delete the field." indicates that other values are possible but that they are possibly invalid syntax.
If you do not follow the syntax rules, you will not get the desired results.

5

I will wait for reply from developer, Florian.

6

I've fixed this issue with the latest Development Build Mp3tag v2.87f.

Thanks for reporting!

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.