# Is OpenGL still a good decission?

**URL:** <https://forum.juce.com/t/is-opengl-still-a-good-decission/48951>\
**Category:** Audio Plugins\
**Created:** [November 26, 2021, 8:51am UTC](https://forum.juce.com/t/is-opengl-still-a-good-decission/48951 "2021-11-26T08:51:57Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![kunz](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@kunz](https://forum.juce.com/u/kunz)\
**Post date:** [November 26, 2021, 3:27pm UTC](https://forum.juce.com/t/is-opengl-still-a-good-decission/48951/7 "2021-11-26T15:27:20Z")

</div>

Looks like there are some workarounds to move more work to the GPU, but when I tested it, things like plugin scaling didn’t work anymore as expected. And CPU load was still high if I remember right:

> [@Ableton Windows OpenGL "freeze-out" on high work load and multi-instance](https://forum.juce.com/t/ableton-windows-opengl-freeze-out-on-high-work-load-and-multi-instance/48675/2):
>
> I have had similar issues in Cubase on Windows. Every component repainting (especially moving) on the OpenGL-thread requires there MML-lock. (And something like painting complex shapes, will also involve the CPU, because JUCE renders the shape into edge-tables first on the CPU) I guess because there is only a limited time on the message-thread - which is also shared with the host - this can cause unresponsive behaviour. (And too much OpenGL time, also) Besides things what the JUCE-Team can do…

---

_[View the full topic](https://forum.juce.com/t/is-opengl-still-a-good-decission/48951)._
