Fix JUCE 6 performance regressions

bepzi / helm

A custom fork of Matt Tytel's Helm synthesizer

GNU General Public License v3.0

7 stars 0 forks source link

Fix JUCE 6 performance regressions #4

Open bepzi opened 3 years ago

bepzi commented 3 years ago

When building the Standalone in Release mode, the UI is a bit laggy. I've determined that this is a regression from JUCE 5, and is not related to any changes in the DISTRHO fork (it happens with vanilla JUCE 6 too.)

The correct way to fix this might just be to rewrite the UI/OpenGL code and solve #1 in the process.

Given that there's a known-good Projucer build at 512c219de4fb33a889874a759515c216c07749b1, I may want to try bisecting with different releases of JUCE until I find the version that introduced the regression.

bepzi commented 3 years ago

Update:

It's not caused by the DISTRHO fork of JUCE 6
It's not caused by building with CMake instead of the Projucer

I strongly suspect it's just a JUCE 5 -> JUCE 6 regression, although I'm having difficulties building a Projucer JUCE 5 build, and I'm not really willing to bisect JUCE commits.

On the off chance anyone sees this issue and knows what might cause UI jank, I'd be interested to hear ways to debug this.

bepzi commented 3 years ago

It's also worth noting: Helm is actually quite usable even with the slight increase in UI jank. It is definitely less smooth than it was in JUCE 5, but for right now it's good enough, and I can spend some time trying to improve it later.