On 04/21/2013 07:33 PM, J. Liles wrote:
Ed, the reason the current release is 'slow', as you discovered, is
that some drawing operations in Cario are 100s of times slower than
their X11 counterparts. In the new branch, I avoid these operations.
I guess you're talking about drawing to a cairo_xlib surfaces. The xlib
backend
is slow. To get speed use an image surface as a backbuffer and 'xputimage'
it ( or parts of it ) to a window.
Still, it was merely 'slow' as in slower than it used to be. Not slow
as in having to wait 2 seconds.
I rebooted my pc this morning and things are faster now.
(less than a sec. for a redraw with only jack/zynn/non-mix and
non-seq running).
When it took 2 sec.'s ( and 3+ when zoomed out ), the x-server
was using 98% cpu while updating and every other gui action was very
slow. But
it looks like the cause was not ( only ) the seq-gui doing a lot of
server requests.
Non-seq. is much more responsive now, but still not fast.
If you indeed tried the
'non-sequencer-reimplement-canvas' branch and it's still slow, then
there is definitely something else going on that has nothing to do
with Cairo. 2 seconds is rather extreme.
I did compile and run it but there were no cells visible so i
couldn't try. Should the cells be visible ? I assumed it was in a to
early stage.
I need to know more about
your environment. Are *all* FLTK1.3 and NTK applications slow for you?
What video card and driver are you using? What version of X? Have you
tried switching between EXA and XAA? Have you tried the
XAAOffscreenPixmaps = "no" Xorg option?
Zynn is OK , non-mixer is always running and when i switch desks
from mixer to sequencer and back i see a blank mixer-window for
1/4 - 1/3 of a second ( not really a pain ) and a blank seq. window for
about 3/4 - 1 sec.
I have an NVIDIA card with prop. driver and X.Org X Server 1.9.5.
and never tried or needed other options than standard.
I'll be playing around with the sequencer and see if it gets slower
while using it. It's rather addicting and i haven't connected my
keyboard yet.
Looking foreward to your new implementation,
Thanks,
Ed.
