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

Paul Davis paul at linuxaudiosystems.com
Sat Mar 7 08:00:46 PST 2009

On Sat, Mar 7, 2009 at 10:13 AM, John Emmas <johne53 at tiscali.co.uk> wrote:

> ----- Original Message ----- From: "Paul Davis"
> Subject: Re: [Ardour-Dev] SuperRapidScreenUpdates are neither rapid, nor
> super.
>> 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

there is no point in ever trying to do screen updates faster than the
monitor refresh rate, which is typically 60-80Hz. it was reduced to 80 and
then 40 because in reality, film projection at 30FPS is indistinguishable to
the human eye from continuous motion. the honest truth is that it could
probably drop to 20 before anyone would even notice.

> - but after
> those changes, the canvas is now only able to update every 1/5th of a
> second
> (in that particular mode, anyway).

seems possible, though rather odd given the nature of the changes. but i'm
afraid that you'll be on your own debugging this. nick (who did the canvas
changes) has gone for a while, and this simply isn't high priority - that
scrolling mode was an experiment, nothing more.

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.

none of those numbers are CPU meters john. your system undoubtedly has at
least one system monitor utility that will include a CPU meter.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20090307/a62e6435/attachment-0002.htm>

More information about the Ardour-Dev mailing list