[ardour-users] mysterious xrun phenomenon

Florian Schmidt mista.tapas at gmx.net
Sat Feb 18 05:03:45 PST 2006

On Thu, 16 Feb 2006 18:43:17 -0500
Jonathan Murphy <typetosmurky at yahoo.com.au> wrote:

> > It's possible that gverb is going into denormal mode. This can bring a
> > powerful CPU to its knees. I've seen this effect when using (IIRC) the
> > GLAME highpass filter as a track plugin.
> >
> > Do the xruns start at a time when the vocal track goes very quiet? This
> > would point to a possible denormal problem.
> >
> > Try putting the reverb on a bus, instead of on the track. (Create a send
> > on the track, and route the send to the bus.)
> Yes, the xruns were actually starting after the recorded section of
> the track had finished, so gverb was totally out to lunch. Laziness
> always comes back to bite you in the arse. Thanks for the advice, I'll 
> put it on a bus. I think I also had the input bandwidth set to 1 so gverb
> was kind of hungry.

I always wondered whether ardour could include some bookkeeping on what
plugin eats how much cpu time. Then the culprit would be much easier to
find. And in the case that a plugin eats more than say 95% of the time
of a period, it could spit out a messagebox..


Palimm Palimm!

More information about the Ardour-Users mailing list