Comment 5 for bug 1194456

Hey Xorik,

In fact, it's the opposite! We pre-calculate the entire waveform during
analysis. All of the CPU usage you are seeing is from the drawing code.
(There is some glue code that helps the drawing figure out what to draw,
though).

On Tue, Jun 25, 2013 at 9:00 AM, xorik <email address hidden> wrote:

> Other waveforms is ~20-40% of my CPU on 30 FPS.
>
> >you could make a pure GL HSV version
> I think MOST part of CPU using not for the drawing, but for the
> calculations (it is easy to check, just comment the drawing code and
> compare CPU usage).
>
> I think we can create arrays in memory for needed song parts (which
> visible in this moment) e.g. each array contain 1second of song's
> waveform data. Is song is paused, we don't need to do the calculations,
> but if song is playing, we will be calculate every 1 second of song,
> when we need. I think this saves big amount of CPU%.
>
> What you think about this?
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1194456
>
> Title:
> Waveforms needs some optimization/caching
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1194456/+subscriptions
>