Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments field [COMM] not updating on iTunes/Apple Music #433

Open
puyan101 opened this issue Dec 17, 2024 · 3 comments
Open

Comments field [COMM] not updating on iTunes/Apple Music #433

puyan101 opened this issue Dec 17, 2024 · 3 comments

Comments

@puyan101
Copy link

Hey, love your application and feel like I've finally found the tool that will help me tackle my DJ library and re-structure it.

I've set up the Quick Tag Custom Notes, but I've noticed that anything (Vibe, Mood, etc.) that I assign to the Comments tag frame [COMM] does not update the Comments field on Apple Music.

I plan to use Apple Music's Smart Playlists to organise my music, then export to Rekordbox. However, I noticed that Rekordbox does read the updated values in the [COMM] field when I reload the tag, but Apple Music does not read any updates.

FYI - I currently use MixedInKey before tagging to overwrite the Comments field with Key/Energy. I then plan to add any descriptors after the Key/Energy in the Comments field.

Is this possible or should I amend this somehow to get Apple Music to show the descriptors in the Comments field? Otherwise I will resort to using another field like Grouping/Composer, but this is less preferable.

Thank you! And Happy Holidays.

onetagger.log

@puyan101
Copy link
Author

Uploading screenshots to show that Rekordbox is able to append the descriptors after the existing Key/Energy from MIK, but Apple Music does not.

Screenshot 2024-12-17 at 14 32 14
Screenshot 2024-12-17 at 14 32 55

@Marekkon5
Copy link
Owner

Seems to be similar issue to: #317

TL;DR:

  1. Try using latest development build from Actions tab
  2. Try setting the ID3 COMM Language to "eng" in Advanced Settings
  3. Try playing with ID3v2.3/v2.4 version (in Advanced settings)

@puyan101
Copy link
Author

Hey, thanks the fast reply and I'm happy to say you helped resolve my problem!
I didn't see #317 when I initially searched, but I tried each step one-by-one and it was the ID3 COMM Language that did the trick. I didn't change the ID3v2.3/v2.4 to even try that, but thanks for helping me out and now I can crack on with tackling my huge library!
Cheers,
P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants