# ITUNESGAPLESS, ITUNESHDVIDEO, PODCAST fields do not accept 0

**URL:** https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [June 6, 2016, 4:29pm UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017 "2016-06-06T16:29:32Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![TOGETOGE](https://community.mp3tag.de/user_avatar/community.mp3tag.de/togetoge/32/388_2.png) [@TOGETOGE](https://community.mp3tag.de/u/TOGETOGE)
#### Post date: [June 6, 2016, 4:29pm UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/1 "2016-06-06T16:29:32Z")

</div>

very small bug

When I entered repeatedly [unsupported](https://docs.mp3tag.de/mapping/#tag-fields-exclusive-to-mp4) 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](https://docs.mp3tag.de/mapping)

v2.77  
Thank you very much for development.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [June 6, 2016, 4:51pm UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/2 "2016-06-06T16:51:43Z")

</div>

> [@SABOTEN](#):
>
> ...  
> Why is 0 unsupported? Is there any reason? I hope that 3 fields will accept 0.  
> ...

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](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.

---

<div class="post-metadata">

### Author: ![TOGETOGE](https://community.mp3tag.de/user_avatar/community.mp3tag.de/togetoge/32/388_2.png) [@TOGETOGE](https://community.mp3tag.de/u/TOGETOGE)
#### Post date: [June 6, 2016, 5:18pm UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/3 "2016-06-06T17:18:48Z")

</div>

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](https://dl.dropboxusercontent.com/s/4ssrvqlspl8oqpr/sample.txt)

And see [https://docs.mp3tag.de/mapping/#tag-fields-exclusive-to-mp4](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.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [June 7, 2016, 3:33am UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/4 "2016-06-07T03:33:58Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![TOGETOGE](https://community.mp3tag.de/user_avatar/community.mp3tag.de/togetoge/32/388_2.png) [@TOGETOGE](https://community.mp3tag.de/u/TOGETOGE)
#### Post date: [June 7, 2016, 4:01am UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/5 "2016-06-07T04:01:19Z")

</div>

I will wait for reply from developer, Florian.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [May 23, 2018, 9:30am UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/6 "2018-05-23T09:30:30Z")

</div>

I've fixed this issue with the latest Development Build [Mp3tag v2.87f](https://community.mp3tag.de/t/455).

Thanks for reporting!

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:08pm UTC](https://community.mp3tag.de/t/itunesgapless-ituneshdvideo-podcast-fields-do-not-accept-0/18017/7 "2018-12-28T14:08:48Z")

</div>

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