On 15/12/05, federico <address@hidden> wrote:
how can one identify those realtime-capable plugins?
maybe some visual information in the plugin list (color? flag?) could
help to identify them? is this possible?
If we're talking about ladspa plugins, most are realtime-safe
(that doesn't mean that you can't overtax your cpu with
them, though, it just means that they take a fixed number
of cpu-cycles per sample, so the number of cycles won't
balloon out unexpectedly).
You can get info on a plugin called x in file y with the
command analyseplugin y x. For example
# analyseplugin caps.so Plate2x2
Plugin Name: "Versatile plate reverb, 2x2"
Plugin Label: "Plate2x2"
Plugin Unique ID: 1795
Maker: "Tim Goetze <address@hidden>"
Copyright: "GPL, 2004-5"
Must Run Real-Time: No
Has activate() Function: Yes
Has deativate() Function: No
Has run_adding() Function: Yes
Environment: Normal or Hard Real-Time
Ports: "in:l" input, audio, -1 to 1
"in:r" input, audio, -1 to 1
"bandwidth" input, control, 0.005 to 0.999, default 0.502
"tail" input, control, 0 to 0.749, default 0.3745
"damping" input, control, 0.0005 to 1, default 0.250375
"blend" input, control, 0 to 1, default 0.25
"out:l" output, audio
"out:r" output, audio
(the analyseplugin tool comes with ladspa and should
find the plugins directory, but you do have to know what
file the plugin is in.)
Notice in the above, the line
"Environment: Normal or Hard Real-Time"
The "Hard Real-Time" is what you're looking for.
Another way is to load the plugin up in jack-rack, which
will issue a warning if the plugin isn't realtime compatible.
Non-ladspa plugins, I've no clue about (as yet) I'm afraid :)