# GUI really slow on VST3 Cakewalk on Windows

**URL:** <https://forum.juce.com/t/gui-really-slow-on-vst3-cakewalk-on-windows/36424>\
**Category:** Audio Plugins\
**Created:** [November 30, 2019, 10:39am UTC](https://forum.juce.com/t/gui-really-slow-on-vst3-cakewalk-on-windows/36424 "2019-11-30T10:39:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![skoleyuno](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/skoleyuno/32/8355_2.png) [@skoleyuno](https://forum.juce.com/u/skoleyuno)\
**Post date:** [November 30, 2019, 10:39am UTC](https://forum.juce.com/t/gui-really-slow-on-vst3-cakewalk-on-windows/36424/1 "2019-11-30T10:39:37Z")

</div>

Hi

I am finding that my VST3 versions are really slow in Hosts like Cakewalk. It takes seconds to load and in some cases, gui changes happen seconds later. Has anyone else experienced this?  
I read a previous post about typeface loading causing some issues, however, my plugin has no custom fonts.

Any help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![ttg](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ttg/32/14456_2.png) [@ttg](https://forum.juce.com/u/ttg)\
**Post date:** [November 30, 2019, 7:53pm UTC](https://forum.juce.com/t/gui-really-slow-on-vst3-cakewalk-on-windows/36424/2 "2019-11-30T19:53:41Z")

</div>

I’ll first try JUCE wonderful `JUCE_ENABLE_REPAINT_DEBUGGING` and see if you’re doing a lot of things before doing ‘tricks’ that could reduce the symptom but not find the cause.  
([Debugging Tool: Paint Rectangle Around Components](https://forum.juce.com/t/debugging-tool-paint-rectangle-around-components/9283))

---

<div class="post-metadata">

**Author:** ![skoleyuno](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/skoleyuno/32/8355_2.png) [@skoleyuno](https://forum.juce.com/u/skoleyuno)\
**Post date:** [December 1, 2019, 6:15am UTC](https://forum.juce.com/t/gui-really-slow-on-vst3-cakewalk-on-windows/36424/3 "2019-12-01T06:15:50Z")

</div>

Thanks @ttg

I will give that a try to optimise further. I was able to resolve most of my issue by removing a heap of repaint() calls which I had in my custom look and feel implementations.
