Re: [TEAR-Devel] tear-redesign: first snapshot is availabe
Brought to you by:
devduck
|
From: <tea...@li...> - 2001-11-27 17:08:43
|
--On Tuesday, November 27, 2001 10:37:44 AM -0500
tea...@li... wrote:
> I'm not afraid...
> I realize this is still apha
I'm not so fast in programming...
> Make sure you leave room for two more encoders: oggenc and lameogg.
Encoders will get an "API", so no problems for others.
> MUNGING is when all of the spaces are replaced with '_'s in a
> filename.
Ok, but not used in 0.9.1
Any template code available? Should only the filename be treated or
also the subdirectories?
> 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.
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?
Peter
|