You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm working on a sample project to read FLAC audio tags and I'm encountering an issue with the "comments" tag. Despite there being comments in the FLAC files, tags.metadata.comment is returning nil.
I would really appreciate your insights or any suggestions you might have on how to resolve this issue.
Thank you so much for your help!
The issue is that the file contains a field named COMMENT while the canonical name for a comment in a Vorbis comment field is DESCRIPTION. Perhaps it would be better to look for a COMMENT field if a DESCRIPTION field is absent but you can access the other fields via the additionalMetadata dictionary.
The issue is that the file contains a field named COMMENT while the canonical name for a comment in a Vorbis comment field is DESCRIPTION. Perhaps it would be better to look for a COMMENT field if a DESCRIPTION field is absent but you can access the other fields via the additionalMetadata dictionary.
I just wondering why TagLib reads this... so logically its wrapper in this repo should too, but it's not. Maybe as fallback?
Anyway, users reported me this problem, telling me that some files missing that comments filed, but other audio apps reads it.
It's somewhat a question of mapping. The higher-level TagLib accessor for Xiph comments use DESCRIPTION if found, COMMENT next, or "" if neither are present, joining multiple fields with the same name using /. I use the raw fields directly and follow the Xiph spec with regard to naming.
It's somewhat a question of mapping. The higher-level TagLib accessor for Xiph comments use DESCRIPTION if found, COMMENT next, or "" if neither are present, joining multiple fields with the same name using /. I use the raw fields directly and follow the Xiph spec with regard to naming.
Hey @sbooth, will this issue be resolved anytime soon?
I suppose I need to be convinced this is an actual issue first.
In the meantime it's simple enough to test if the format is FLAC, and if so, check the additional metadata for the COMMENT field if the DESCRIPTION field is empty.
Activity
sbooth commentedon Nov 4, 2024
The issue is that the file contains a field named
COMMENTwhile the canonical name for a comment in a Vorbis comment field isDESCRIPTION. Perhaps it would be better to look for aCOMMENTfield if aDESCRIPTIONfield is absent but you can access the other fields via theadditionalMetadatadictionary.sbooth commentedon Nov 4, 2024
It also seems that Picard uses
COMMENTso perhapsDESCRIPTIONis outdated despite what the spec says.Anywhere-Music-Player commentedon Nov 4, 2024
I just wondering why TagLib reads this... so logically its wrapper in this repo should too, but it's not. Maybe as fallback?
Anyway, users reported me this problem, telling me that some files missing that comments filed, but other audio apps reads it.
sbooth commentedon Nov 4, 2024
It's somewhat a question of mapping. The higher-level TagLib accessor for Xiph comments use
DESCRIPTIONif found,COMMENTnext, or""if neither are present, joining multiple fields with the same name using/. I use the raw fields directly and follow the Xiph spec with regard to naming.Anywhere-Music-Player commentedon Nov 17, 2024
Hey @sbooth, will this issue be resolved anytime soon?
sbooth commentedon Nov 18, 2024
I suppose I need to be convinced this is an actual issue first.
In the meantime it's simple enough to test if the format is FLAC, and if so, check the additional metadata for the
COMMENTfield if theDESCRIPTIONfield is empty.