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