[linux-audio-dev] ardour, LADSPA, a marriage

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: [linux-audio-dev] ardour, LADSPA, a marriage
From: Paul Barton-Davis (pbd_AT_Op.Net)
Date: Thu Nov 09 2000 - 05:38:26 EET


i am pleased to mention that after a pleasantly short amount of
hacking, ardour CVS now has preliminary support for *real-time* LADSPA
plugins applied to EDL-based data streams. its far from where i want
it to be but right now you can:

   * within the editor, right click on a track to get the track edit menu
   * select "Plugins" from the track edit menu
   * dbl-click on the desired plugin
   * a plugin is instantiated, and a default GUI constructed for
        all input control parameters
   * track playback then uses the results of the plugin output, realtime.

my test case has been Freeverb, which is what I am most interested in
of the current CMT set, and it worked pretty flawlessly first
time. its definitely a very nice reverb. i have to say that i grinned
fairly broadly when the code to actually apply the plugin not only
compiled right after i wrote it, but worked too!

one glitch in this scheme right now is that the plugin is applied when
the audio data is read from the disk, not just before it is sent to
the audio interface, which results in rather large parameter-setting
latency. i have a strong feeling that this can be fixed very easily,
probably even before i do the next commit.

the other problem is that most of the current CMT plugins are stereo,
but ardour deals with mono tracks, thus doubling the compute time for
the plugin. when i get some time, i will try to construct some mono
versions of the plugins that seem most useful.

but anyway, the main thing i wanted to say was "its exciting". i was
demoing ardour in the studio yesterday to a young guy who worked with
protools when he was doing a training course in sound engineering. his
comment was "oh yeah, this looks just like a protools thing".

he has the right idea :)

obviously, there is a lot more to do, but just in case anyone wants to
get on board with the coding part of this project (ardour), i'd
thought i'd mention it. i could use the help! we're going to kick
protools' derriere, within a year at least :)

short-term goals:

        * build plugin chains
        * apply plugin chains to a track or a region within it
        * use Pixmap graphic controllers for the plugin GUIs
        * implement mono plugins

--p


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Thu Nov 09 2000 - 06:19:31 EET