id3v1: save comment when COMM frame is stored under its HashKey#709
Open
SAY-5 wants to merge 1 commit into
Open
id3v1: save comment when COMM frame is stored under its HashKey#709SAY-5 wants to merge 1 commit into
SAY-5 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
COMM frames are stored in ID3Tags under their HashKey (
COMM:desc:lang), soMakeID3v1never finds them via the bareCOMMkey and the comment is dropped from the resulting ID3v1 tag. Fall back to scanning for aCOMM:-prefixed entry when no plainCOMMkey exists.Closes #660