UI appearing black in Windows / VST2

Using JUCE 8.0.3 in Windows / VST2, sometimes the UI is black (FL Studio), sometimes it doesn’t resize properly (Cubase). Not using OpenGL. Haven’t been able to reproduce myself, but getting reports from beta testers. Anybody else seeing this?

I hope folks are aware that the work being done on JUCE 8.0.x is really bleeding-edge development and projects based on JUCE 8.0.x should not really be considered ‘settled’ yet for distribution. The bugfix festival that is going on with the develop branch is quite energetic.

1 Like

Every version of JUCE has a lot going on in the development branch. We are using the latest development version of JUCE for our commercial releases (always have) because critical fixes are often kept there for weeks or even months before making it to the main branch.

We use our own fork, which auto-merges the development branch with our changes.

I noticed the same and tend to take the development branch most of the time because of the critical fixes, but you can also have bad luck with this strategy and add bugs from new features and other changes that aren’t production-ready. This isn’t always a good idea and not a good practice.

I would like to see critical bugs merged into the master as soon as possible within days as soon as they are tested. I still can’t believe that we have had unusable JUCE versions on the master branch for weeks (Linux repaint issue, Direct2D buffered image, and still some unresolved regressions…). People download and use it and all run into the same problems.

I would also strongly recommend getting away from these big, marketing-driven JUCE releases and release new features continuously between releases as they are ready. We could have feature toggles to enable/disable new features like D2D rendering or UTF8 text support until they are 100% stable.

1 Like

100% this. It’s the one thing that frustrates me with JUCE, I don’t like using develop. I’m even wary of moving to JUCE 8 for my products still after months of its release, but I just bought an M4 Mac Mini and can’t even run JUCE 7 any more because of juceaide incompatibility, and I’m really not sure if should just apply the 3 diffs mentioned in order to backport to JUCE 7 and carry on there until I’m satisfied mirgration to JUCE 8 isn’t going to cause me more problems than benefits. :frowning:

1 Like