File: TODO

package info (click to toggle)
crip 3.7-3%2Betch2
  • links: PTS
  • area: main
  • in suites: etch
  • size: 200 kB
  • ctags: 10
  • sloc: perl: 2,030; sh: 289; makefile: 35
file content (59 lines) | stat: -rw-r--r-- 2,063 bytes parent folder | download | duplicates (3)
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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
To-Do list - (maybe one day, maybe never)
-------------------------------------------------------------------------------

More flexible filenaming conventions

Merge v1.0 code into v4.0 release for MP3 support?

bug:  crip will overwrite existing files if the filenames given happen
to be the same.  crip should warn if any 2 or more files are the same
name.

Handle FLAC .ogg files better

Support FLAC in the `editcomment` script

(re)rip and encode using filename/tag info from a specified directory (crip
 will search directory for .ogg files that have the same discid and tracknumber
 and pull the data from there)

<jomohke> charlton: A Possible idea is allowing a config file. It would be
          handy for people to set up their output settings eg. All files goto
          /media/{$artistname}/{$album}/{$track}-{$tracknum}.ogg This is
          flexible for the way certain people organise their music. Also a way
          to run the program using config file settings, so it doesn't ask you
          any questions. You can just set it and leave.
| jomohke (~jeremy@dyn-ctb-203-221-73-46.webone.com.au) (Australia)
: ircname  : jeremy
| channels : #gentoo
| server   : irc.freenode.net (http://freenode.net/)

Perhaps order the tag items a little better (i.e. put things like
"part=" right underneith "opus=")


Be able to parse CDDB track titles into "artist / title" (and others)


$settitle = "ask" (?)

Verbosity levels

Fork off an (interactive?) process that rips and encodes the files right
after the track selection is entered.  THEN ask for file/tag info while
it is doing this.

Track variations support (multiple tracks in one track / indexing / etc.)
(I don't know how I'd go about doing this,  so it'll probably never happen)

Simplify the structure of the whole script so that less code is repeated
(I still feel it should be possible without the use of subroutines).



*** If you can suggest any additional features or let me know a good way
 to implement the ones above,  please let me know.


Charlton Harrison
charlton@dynet.com