Re: [TEAR-Devel] tear-redesign: first snapshot is availabe

[<tea...@li...>]

> > I'm not afraid...
> > I realize this is still apha
> I'm not so fast in programming...
You're fast enough :)

> > Make sure you leave room for two more encoders: oggenc and lameogg.
> Encoders will get an "API", so no problems for others.
Cool, that's what I thought.

> > MUNGING is when all of the spaces are replaced with '_'s in a
> > filename.
> Ok, but not used in 0.9.1
Yeah, it wasn't a high enough priroity for my to worry about yet.
> Any template code available? Should only the filename be treated or
> also the subdirectories?
It works in 0.4.X, but you wont need that, wherever you are going to
search for proper names (so people don't pass characters that will kill
the shell, etc.) just replace ' ' with '_', it should also be used for
subdirectories if the option is selected.

> > Instead of PRGRAM_LAME_OPTIONS, you can make it
> > PROGRAM_ENC_OPTIONS, that way we can have configurable options for
> > all of them with no special code for each.
> Hmm, options will be too different.
>
> 2 ways possible:
> a) Each encoder get his own additional options (if not "simple mode"
> is choosen) - currently implemented
>
> b) abstract options which are parsed per encoder, generating warnings
> or errors, if encoder has not this capability.
>
> examples:
> bitratetype=constant, bitrate=256
> bitratetype=variable, bitratemin=32, bitratemax=256
>
> and so on....
>
> b) is sure nicer, but more work. a) already exists, so I can add b)
> to the ToDo list.
I was just going to rely on the user knowing what (s)he wants to add.
We can do all of the above though, have a per-encoder list of options, and
a generic option for the "power user" to add even more functionality.
Lame (not to mention every other encoder) supports a lot of stuff and we
are not going to want to offer all of those options... this way we can
support the important ones AND allow other things generically.
So, both is the answer?

> the filename/fileform of the playlist. I/We need to get
> > a good working form for playlist... the 0.4.X code was barely
> > functional.
> Does this mean that sample code is found in 0.4.x?
NO! I don't want anything to do with that particular piece of code, all it
does is make a file and put in the full path name to the mp3, of course
that's all a playlist is, but we ne3ed to add things like appending to
existing files, etc.

Greg
----
T.E.A.R Encodes And Rips
http://tear.sourceforge.net