Mixxx

  1. Bug #1194456
  2. Comment #4

Comment 4 for bug 1194456

Revision history for this message
Daniel Schürmann (daschuer) wrote :

> 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).

Can't believe, have you mad the posit check, just comment the calculation code?

We have also a nice benchmark feature in Mixxx.
If you start Mixxx with --developer, you can use ScopedTimer in src/util/timer.h for measurements.

Your idea is not bad, but I would prefer a balanced CPU solution where only the part is calculated or redawn, that is new for every frame.