Parse "REM DISCID" and "REM COMPOSER" lines #71
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
Cycloctane
force-pushed
the
rem-discid
branch
from
0e76986 to
b51d5cd
Compare
as cdtext's "DISC_ID" and "COMPOSER" (cherry picked from commit a7a5b0c)
Cycloctane
force-pushed
the
rem-discid
branch
from
b51d5cd to
54a342c
Compare
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.
Some widely used software (like ExactAudioCopy) writes DISC_ID and COMPOSER to REM fields (as in
libcue/t/standard_cue.c
Line 15 in c901e16
This pr uses the fix similiar to #4 to make libcue also parse "REM DISCID" and "REM COMPOSER" fields and still store them in cdtext like DISC_ID and COMPOSER.
Fixes #58