Closed lazka closed 8 years ago
Original comment by Sophist UK (Bitbucket: Sophist-UK, GitHub: Sophist-UK):
Yup - have already done that.
Original comment by Sophist UK (Bitbucket: Sophist-UK, GitHub: Sophist-UK):
Ah yes - though for COMM, USLT tags, a newline character might make more sense.
Original comment by Christoph Reiter (Bitbucket: lazka, GitHub: lazka):
I am not sure what currently happens if you have a multi-string ID3v24 COMM tag and then try to save it as ID3v23 where the spec does not support multiple strings.
See the v23_sep argument on save() https://mutagen.readthedocs.org/en/latest/api/id3.html#mutagen.id3.ID3.save
Original comment by Sophist UK (Bitbucket: Sophist-UK, GitHub: Sophist-UK):
ID3v2.4 spec says "There may be more than one comment frame in each tag, but only one with the same language and content descriptor."
The example above shows multiple comments with the same language (eng) and content descriptor [].
I would support loading tags saved in this way, treating them as if they had been a single id3v24 COMM tag with multiple null-terminated strings as per spec.
However mutagen should (IMO) always write tags which conform to the specification, and so should not write tags in this way.
I am not sure what currently happens if you have a multi-string ID3v24 COMM tag and then try to save it as ID3v23 where the spec does not support multiple strings.
Original comment by Christoph Reiter (Bitbucket: lazka, GitHub: lazka):
current foobar2000 at least doesn't create such files when adding multi value tags and switching to id3v2.4
quodlibet supports reading them using the ID3hack subclass: https://code.google.com/p/quodlibet/source/browse/quodlibet/quodlibet/formats/_id3.py#28
I tend to agree that we should read them.
Originally reported by: Christoph Reiter (Bitbucket: lazka, GitHub: lazka)
From dgasa...@gmail.com on March 12, 2014 05:02:32
Original issue: http://code.google.com/p/mutagen/issues/detail?id=172