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

Paul Davis paul at linuxaudiosystems.com
Sat Mar 7 05:48:42 PST 2009

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

> A couple of weeks ago I updated my copy of Ardour 2.4 to the latest svn
> (2.7.1).  I must say that I was very disappointed at how horrible and
> clunky
> the "moving timeline" display mode has become.

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.

> Now here's the thing....  visually, there seems to be very little going on
> in 2.7 that wasn't already going on in 2.4. This has got me wondering if
> there's a lot of stuff being done on in the UI thread that shouldn't really
> be there.  If this problem isn't already being ivestigated (and there's a
> list somewhere of the changes between those two versions) I'd be happy to
> see if I can track down the culprit.  Or has the UI thread just reached te
> limit of what it can do?

i suggest you look at your CPU meter first. if its not pegged at 100% then
your guesses are not on target. It would certainly be interesting to know
where the performance comes from, but expect to find the code paths very
complex. anything involving the canvas is, just because of the asynchronous
nature of its drawing model.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20090307/32c3dbd6/attachment-0002.htm>

More information about the Ardour-Dev mailing list