[ardour-users] ardour timed ou

Kjetil Svalastog Matheussen k.s.matheussen at notam02.no
Sun Jul 11 09:42:25 PDT 2004

On Sun, 11 Jul 2004 skrot at fsb.x86.no wrote:

> On Sat, Jul 10, 2004 at 10:29:31PM -0500, Jan Depner wrote:
> > Some of the effects are not real time.  I think you can check them with
> > jack-rack.  It lists whether they are RT or not.  Try removing effects
> > until the problem clears up and then replace them one at a time. 
> > Freeverb should be OK.  A couple of the TAP plugins aren't RT I think.
> > 
> > Jan
> Thanks, that solved it, the valve saturation effect was the showstopper.
> jack-rack does warn about non-RT effects when you load them, but did not 
> warn when i load "valve saturation".

You can get very good realtime performance with a plugin that has 
correctly not set the RT_CAPABLE flag. Its full name is 
LADSPA_PROPERTY_HARD_RT_CAPABLE and the requirements for setting this flag 
goes for allocating memory, sockets, pipes, etc. It might not be that 
this flag is not set is the source of your problem. It can just as well 
be a bug in the "valve saturation" plugin.

> Using Jack-rack is not an easy way to find non-RT effects. There must be 
> a better way.

Oh well, I just had to do it. :)

Cut and paste into snd:

(for-each (lambda (l) (if (= 0 (logand LADSPA_PROPERTY_HARD_RT_CAPABLE 
(.Properties (ladspa-descriptor (car l) (cadr l))))) (format #t "~A/~A\n" 
(car l) (cadr l)))) (list-ladspa))


More information about the Ardour-Users mailing list