c9c2ca27 |
1 | TODO: |
2 | ---- |
8063c20f |
3 | * ReplyGain support |
4 | * flacdecode (to extract files from a -1 flac file) |
5 | |
9f659ada |
6 | * Get the echo instances to behave consistently |
7 | |
c9c2ca27 |
8 | * move the wav files to a different dir if the user wants to keep the tracks |
9 | * read the TOC and CDTEXT files and store them |
81bc6204 |
10 | |
c9c2ca27 |
11 | * read_and_encode_and_tag? :) |
12 | * Customizable post-read/encode/tag hooks |
13 | (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=114851) |
14 | |
15 | * Separate local/dist tagging: if local encoding, the tags are added on the |
16 | encoding phase. If remote, the tracks need tagging. |
17 | And also add the possibility to add this information via oggenc directly |
18 | instead of explicitly invoking vorbiscomment. |
19 | |
20 | * Maybe repair files when they have the same name in the original CD? |
21 | (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=205634) |
22 | |
23 | * Separate the different output encodings, so a user can read and encode one |
24 | format and then encode another one, later, from the same wavs. Right now, |
25 | the same status line is used for all formats, so a re-encoding is rejected |
26 | since abcde sees the encoding already finished. Same with tags and moves. |
27 | |
28 | * Support UTF-8 tags |
a2052a00 |
29 | |
30 | * From slashdot: IMHO the most important aspect of an auto-ripper, is its |
31 | error-handling: what happens if a CD is too scratched to rip? How should it |
32 | react if someone tries to rip the exact same CD? make a new rip with another |
33 | name ? silently overwrite the old rip? etc. |
34 | |
35 | Review the things that abcde does ;) |