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