Bug#600981: ITP: lv2file -- A command-line program to apply LV2 effects to files

[Jeremy <jeremybubs@gmail.com>]

On Fri, Oct 22, 2010 at 11:39 PM, Gunnar Wolf <gwolf@gwolf.org> wrote:

Jeremy dijo [Fri, Oct 22, 2010 at 04:14:35PM -0400]:

> LV2 is a standard for audio processing plugins (http://lv2plug.in/).  There
> are numerous packages already in the debian archives containing LV2 plugins
> which will work out of the box with lv2file.  For example, the prototype
> package I and building suggests the following packages containing LV2 files:
> lv2vocoder, vocproc, invada-studio-plugins-lv2, lv2fil.  These plugins also
> work with most major audio processing software on linux, such as qtractor,
> ardour, and traverso.
>
> In order to create these effects (as a developer) you should install lv2core
> and read the included documentation.  However, unless you are experienced
> with audio programming, you usually would only use other people's plugins,
> and simply adjust the parameters (for example, the volume parameter on an
> amplifier plugin).  Lv2file (and most other programs which work with LV2
> plugins) allow you to control these parameters directly.

Oh - Thanks for telling me (as this is clearly targetted as a reply to
the human questioning you). It is usual for Debian people to answer to
ITP bugs stating what they think should be added to the description
(or any other comments).

Greetings

Should that all be included in the description?  I think it's a little bit too much information for the package.  Anyone who is using this program should know what LV2 plugins are, because this is really a tool for people who know what they want to do.  It helps you do things faster, and automate them.  It doesn't provide any new *functionality* per say, but it allows you to do things from the command line, instead of having to open up a GUI and click around.  You could do anything with lv2file instead with a daw.  The difference is that with lv2file, you apply effects from the command line (quicker), and you can automate the process with normal bash scripting tools (i.e. apply the same effect to 100s or 1000s of files, or apply different effects to each one based on some formula, or apply the same effect 100 times each time with slightly different parameters, and output to 100 different files.)  That is, nothing you can do with this would be desirable if you aren't familiar with the specific effect you want to use, and the landscape of linux audio processing in general.

Jeremy