[Ardour-Dev] SuperRapidScreenUpdates are neither rapid, nor super.

John Emmas johne53 at tiscali.co.uk
Sat Mar 7 07:13:58 PST 2009

----- Original Message ----- 
From: "Paul Davis"
Subject: Re: [Ardour-Dev] SuperRapidScreenUpdates are neither rapid, nor
> are you talking about compiling with the option to leave the PH In the
> same place? none of ardour's developers are working with this mode, and
> there were many, many changes made to the canvas code to enable responsive
> GUI behaviour on OS X. this has vastly higher priority than this
> undocumented compile-time option, and its entirely possible that one or
> more of them have had a impact on that mode.
Yes, it looks like those changes have caused a major tradeoff problem.  I'm
only assuming (from names & comments in the code) that the canvas updates
were originally designed to happen every 1/100th of a second - but after
those changes, the canvas is now only able to update every 1/5th of a second
(in that particular mode, anyway).

> i suggest you look at your CPU meter first. if its not pegged at 100% then
> your guesses are not on target.
If you mean the readings at the top of Ardour, my 'c' reading is permanently
99%, my 'p' reading varies between 73% and 95% and my DSP reading is around
4%.  These are pretty much the same as they've always been.


More information about the Ardour-Dev mailing list