On Fri, 31 Dec 2004, Aaron Heller wrote:
> --On Friday, December 17, 2004 10:30 +0200 Kai Vehmanen <kvehmanen@email-addr-hidden> wrote:
>> As a more general comment, I do admit that maintaining support for these
>> external tools is a difficult task and most of the (maintainable) ways to
>> work with them are more fragile than native support via libraries. OTOH,
[...]
>> Good ideas on how to improve the situation are very welcome. :)
>
> You could have a way to specify a number of "presets" for these external
> tools, which would have things like bitrate or quality specified literally.
> Then, the number (or string) after the filename on the commandline would
> simply select that preset. E.g,
>
> ext-cmd-ogg-output,vbrlq = oggenc -q 0 --raw --raw-bits=%b --raw-chan=%c
> --raw-rate=%s --raw-endianness 0 --output=%f -
That's not a bad idea. Unfortunately the current resource file mechanism
is not flexible enough to support the "key,preset" syntax. But OTOH, it's
always possible to extend the interfaces. Another problem is that there is
still the problem of how to handle different versions of the tools (which
might use different syntax for command-line options). :( But anyways, some
kind of preset mechanism is probably needed...
-- http://www.eca.cx Audio software for Linux! ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Ecasound-list mailing list Ecasound-list@email-addr-hidden https://lists.sourceforge.net/lists/listinfo/ecasound-listReceived on Sun Mar 27 00:15:05 2005
This archive was generated by hypermail 2.1.8 : Sun Mar 27 2005 - 00:15:05 EET