-
Notifications
You must be signed in to change notification settings - Fork 91
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
Save ISRCs from CD TOC #320
Comments
Good suggestion! BTW: ISRC values, if available, are already included in whipper's generated cue sheets, right? |
Yes...
|
Also noticed that whipper is using |
Actually I think we're using both: Lines 97 to 141 in 542e071
Perhaps we should remove the |
I like the "slow" cdrdao reading TOC phase as I find the Q sub-channel CRC error log a good heuristic of how possibly damaged a CD is before ripping. Probably a "misuse" of this feature but it works for me. I was thinking for #299 of parsing the cdrdao read-toc output and printing a representation of the TOC data to console/log and something like |
Fixes #320. Signed-off-by: JoeLametta <JoeLametta@users.noreply.github.com>
Fixes #320. Signed-off-by: JoeLametta <JoeLametta@users.noreply.github.com>
Fixes #320. Signed-off-by: JoeLametta <JoeLametta@users.noreply.github.com>
If the CD TOC contains ISRCs we should save those in the ripped file metadata. We're already reading the CD TOC and thus getting the ISRCs, so we may as well store them.
The text was updated successfully, but these errors were encountered: