compilation = 1 vs compilation = yes (can't fix with id tags)

[inphobia]

I like the checkbox solution. However, I think that PerfectTunes should write "1" if checked and nothing at all if unchecked. Reason being some reports that odd players only look at the presence of the compilation tag, ignoring the actual value. So they would take both "1" and "0" (or any other value) as a compilation.

Because of that, I've always followed the defacto standard to use the compilation tag only for compilations. I think it makes sense, because no player should need this tag for non-compilations.

A minor issue with a checkbox though: How should PerfectTunes handle an existing value of "yes"? To me that's an incorrect value which should not render a tick in the checkbox. But, if you would tick the unticked checkbox, any existing "yes" would be overwritten by "1". Some people might not like their tags being overwritten (even if they are non-standard).

Perhaps an alternative grey background colour in the checkbox could indicate "yes" while the normal white background is reserved to indicate "1"? Other ideas? Or is this essentially a non-issue?

again i'm reluctant to reference this, but in the wall_of_text.txt i added i concluded:
"i do not know what framework or housestyle you use, so have no idea of the impact, but the safest & quickest option could be to just force compilation to only have 3 states: true/false/not present & an option to map true/false to either yes/no or 1/0. from what i've read that will cover most needs. you can always leave and advanced option to make it free input and let people shoot themselves in the foot :-D"

this was looking at it from a flac perspective, no idea what this does for other formats.

the reason for the "not present" option is because most of my albums just don't have the compilation tag at all since they're not compilations. "no" removing the tag instead of setting "0" or "no" seems a good alternative as well.

[inphobia]

square since i can only ediit my last post: it's pretty easy to see the difference when you add the compilation field to id tags album overview. as well as check the result (i do recommend pressing refresh since mutli track changes sometimes only change the first track) of changes. or change the value of 1 track (like 1 track set to yes with the others to 1) and see who that impacts things.

edit:
wait, you have "compilation" as a free input field it seems, for me it's always "yes/no" in the album overview. even if like you i change it to "maybe" on all tracks the album option only still gives me "yes/no".




same in the per track edit mode, setting album artists to various artists makes no difference in that.

clearing caches makes no difference.

[garym]

It seems that this issue is being over complicated. As noted, albums should have the field COMPILATION set to "1" if you want it to be treated as a compilation. Otherwise the COMPILATION tag field should not be used (not be present). Coding it a "0" works for some players/servers but is not necessary and can sometimes cause issues.

Use dbpa ID tag Update or mp3tag to load up all your compilation albums and delete the COMPILATION tag containing 'yes' or 'maybe' and then set the standard COMPILATION tag field to a "1". This is the approach I use with FLAC, mp3, and m4a/aac files. Works well in my ~9,000 album collection, that contains 551 compilation albums.

[garym]

It seems that this issue is being over complicated. As noted, albums should have the field COMPILATION set to "1" if you want it to be treated as a compilation. Otherwise the COMPILATION tag field should not be used (not be present). Coding it a "0" works for some players/servers but is not necessary and can sometimes cause issues.

Use dbpa ID tag Update or mp3tag to load up all your compilation albums and delete the COMPILATION tag containing 'yes' or 'maybe' and then set the standard COMPILATION tag field to a "1". This is the approach I use with FLAC, mp3, and m4a/aac files. Works well in my ~9,000 album collection, that contains 551 compilation albums.

I would also remove the COMPILATION tag field from any tracks/albums where the value is "0" or NO. Don't just delete the contents of the field. Remove the COMPILATION tag field entirely.

[square]

Perhaps an alternative grey background colour in the checkbox could indicate "yes" while the normal white background is reserved to indicate "1"? Other ideas? Or is this essentially a non-issue?

This underlines the complexity of the subject. Tag editing is always complicated because 1) you have so many different cases to consider, and 2) there is no common standard that player applications are obliged to follow. So no, I don't think it's a non-issue. For me, it would be sufficient to have it solved this way: Make the checkbox write the value "1" when checked and delete the entire tag when not checked (or write "0"; I don't know what most players support, but PerfectTunes' default behavior should maximize compatibility). Then, because there is plenty of room to the right of the checkbox, indicate with a text label if the COMPILATION tag has any non-standard value. For these, it's always possible to right-click and choose Edit Tags to directly modify the values on a direct input level if necessary.

wait, you have "compilation" as a free input field it seems, for me it's always "yes/no" in the album overview. even if like you i change it to "maybe" on all tracks the album option only still gives me "yes/no".

The difference is probably due to the fact that I use the macOS version and you use the Windows version of PerfectTunes.

[inphobia]

Use dbpa ID tag Update or mp3tag to load up all your compilation albums and delete the COMPILATION tag containing 'yes' or 'maybe' and then set the standard COMPILATION tag field to a "1". This is the approach I use with FLAC, mp3, and m4a/aac files. Works well in my ~9,000 album collection, that contains 551 compilation albums.

ahha, the tag update action could indeed be an option. i've settled on the official metaflac for me needs, but i was trying to keep the discussion away from 3rd party tools where possible.

[Spoon]

The latest release of PerfectTUNES >> ID Tags >> List and recommendation >> Compilation

It will show inconsistencies and allow correction with a single click.

[square]

I like how the solution turned out. PerfectTunes now correctly writes "1" when Compilation is set to Yes. And removes the tag when it's set to No. On macOS, it's no longer possible to enter arbitrary values, even in the Edit Tags dialog. I guess this behavior is the most compatible with players. I also reckon the idea to have the List & Recommendations feature handle inconsistencies with the Compilation flag. Well done, thank you so much for adressing this!

[square]

This is, by the now, now consistent with how Mp3tag handles the Compilation tag. Write "1" for yes, remove tag entirely for no.

[inphobia]

coolness.
just updated (windows version) but i can't seem to replicate the behaviour square mentioned: setting compilation to "yes" still writes "yes" instead of 1 (checked with metaflac), and setting it to "no" writes "compilation=no" instead of removing the tag.
via "lists and recommendations" however it does correctly find "yes" and "no", suggesting to change it to "1" and "remove tag".

to clarify: in "browse by file & folders" mode it's still using yes/no and also writing yes/no instead of 1 or remove tag.


am i missing something?

[square]

coolness.
just updated (windows version) but i can't seem to replicate the behaviour square mentioned

To be clear, I was only able to test this with PerfectTunes for macOS. I do not own or have access to a Windows machine, so I can't say anything about the Windows version of PerfectTunes. Sorry to hear that the new version didn't fix things for you. I was under the impression that the update was cross-platform (and still think it is), so I don't know what's going on.

[Spoon]

Did not make the Windows version on this release, only macos