2009/4/26 Andreas Pflug <[email protected]>
> Using the outline skin on Debian 5.0, I see mixxx consuming 13 % CPU, and
> xorg 32% even when there's no visual change.
>
> Digging a little on the performance issues mentioned in the wiki, I found
> that preventing ControlObject from changing unchanged values does the trick,
> see attached trivial patch against trunk. It reduces xorg CPU usage to a
> minimum when there's no display update.
>
> As soon as I play, the cpu usage rises again (mostly in xorg, caused by
> wVuMeter updates), which I reduced drastically by using repaint() instead of
> update() in WWidget::setValue().
>
> Regards,
>
> Andreas
>
>
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensign option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Mixxx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
>
This is a very interesting discovery.
See, at times, it happens that Mixxx visuals can barely keep up with me
while I'm mutilating the crossfader: suddenly I hear pops and clicks in the
music, so I quit sliding, and I see Mixxx is still "playing" the slider
animations... Slow display updates in the window (if any), basically
hanging the interface (interestingly the MIDI controller still responds, so
I can stop the music and wait for it to settle).
I have always wondered where that came from and you rinding pointed me into
the right direction (I think :P) I took this patch a little further, and
modified the wslidercomposed to call update() as well. I discovered the
fader no longer is desperately trying to keep up: me like. Me like a lot,
because I can now enable the Waveform display again that I had disabled it
to save some valuable CPU-ticks. :)
Now, scratching along to 3 to 4 tracks of Portishead [my usual "testing
session"] usually gets me aforementioned behaviour but just now I have
heavily scratched along about 8 (before it segfaulted because of another
thing that's plagueing me but I haven't yet figured out).
That update( ) in stead of repaint( ) does indeed make a noticable
difference for the problem I had with the cross-fader widget.. That waveform
display is soooo useful as a guidance, it's awesome I can have it back now.
:)
Perhaps it's a bit early days as I have only run it for few sessions now,
but I'll ride this patch out for a few days and give an update..
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
