c7a423bb246e35938cee50b97a6dabbc20f0b617
Comment out number of track setting on tag for now. MusicBrainz can give us dates in YYYY, YYYY-MM, and YYYY-MM-DD format, so convert to YYYY-MM-DD always. Unmount the data part of the CD we want to rip if it is mounted. Adapt to peak level change. Don't try to write data tracks to the m3u file. Resolve the device path to the actual device path.
goals
-----
- support one-command automatic ripping
- support offline ripping (doing metadata lookup and log rewriting later)
- separate the info/result about the rip from the metadata/file generation/...
rip command tree
----------------
rip
offset
find
find drive's read offset using AccurateRip
verify
verify drive's read offset using AccurateRip
cd
rip
rip the cd
htoa
find
rip
rip the htoa if it's there
image
verify
verify the cd image
style guide
-----------
To avoid confusion:
- cuefile is used for the CueFile object, which wraps/parses an existing .cue
file on disk
- tocfile: same
- toc: table of contents of a CD; instance of Table
test: single rip of kings of leon - only by the night
track 1: frame start 0, 17811 CD frames,
track 2: frame start 17811, 18481 CD frames
ARCue.pl says 2c15499a
track 11: frame start 166858, 25103 CD frames (14760564 audio frames)
191961 total CD frames
Languages
Python
93.6%
TeX
4.7%
C
0.9%
Dockerfile
0.5%
Shell
0.3%