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

David Taht d at teklibre.com
Sat Mar 7 20:21:58 PST 2009

Hash: SHA1

Paul Davis escribió:
> 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.

I am going to disagree with this slightly. If you are doing different
kinds of updates to the screen it helps to be sending the draw commands
as fast as possible, so that the display hardware has smaller chunks to
render at a time.
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the Ardour-Dev mailing list