# Retina flickering MBP, workaround

**URL:** <https://forum.juce.com/t/retina-flickering-mbp-workaround/14852>\
**Category:** General JUCE discussion\
**Created:** [May 27, 2015, 5:24am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852 "2015-05-27T05:24:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sundhage](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sundhage/32/162_2.png) [@sundhage](https://forum.juce.com/u/sundhage)\
**Post date:** [May 27, 2015, 5:24am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852/1 "2015-05-27T05:24:49Z")

</div>

Hi,

We're currently having an issue with graphics flickering/low framerates&nbsp;on Macbook Pro (retina) and need some kind of workaround. The plug-in has no performance issues what so ever on the same machine in native resolution.

The UI has a lot of drawing going on and when a user moves a slider, a big portion of the screen has to be repainted. Since we're not officially supporting retina (yet) the best way for us would probably be to not support retina, but I can't find any way to do this. Is it possible at all?

Another way would be trying to change the lowlevel renderer to OpenGL and mess around with pixelscaling (or something, it's been a few years since I worked with OpenGL). I've been looking around but can't find&nbsp;any way to do this.&nbsp;

Any kind of help would be much appreciated!

---

<div class="post-metadata">

**Author:** ![otristan](https://avatars.discourse-cdn.com/v4/letter/o/f0a364/32.png) [@otristan](https://forum.juce.com/u/otristan)\
**Post date:** [May 27, 2015, 7:13am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852/2 "2015-05-27T07:13:24Z")

</div>

We have currently the same issue and didn't found good ways to get rid of those.

Try seting some setOpaque(true) when possible to avoid some uneeded redraw.

Switching to an opengl renderer helped us though.

&nbsp;

---

<div class="post-metadata">

**Author:** ![sundhage](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sundhage/32/162_2.png) [@sundhage](https://forum.juce.com/u/sundhage)\
**Post date:** [May 27, 2015, 7:22am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852/3 "2015-05-27T07:22:12Z")

</div>

Thanks. Does switching to an opengl renderer mean that you have to use re-implement the whole UI drawing parts or is it possible to just globally change renderer? If so, how do I do that? :)

---

<div class="post-metadata">

**Author:** ![otristan](https://avatars.discourse-cdn.com/v4/letter/o/f0a364/32.png) [@otristan](https://forum.juce.com/u/otristan)\
**Post date:** [May 27, 2015, 8:01am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852/4 "2015-05-27T08:01:51Z")

</div>

Just switching the default renderer

&nbsp;

Create an&nbsp;OpenGLContext as a member variable of your main component then do

mOpenGLContext.attachTo(\*getTopLevelComponent());

&nbsp;

and voila !

---

<div class="post-metadata">

**Author:** ![sundhage](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sundhage/32/162_2.png) [@sundhage](https://forum.juce.com/u/sundhage)\
**Post date:** [May 29, 2015, 9:37am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852/5 "2015-05-29T09:37:36Z")

</div>

Aha! :D Thanks. Now things works much better.

---

<div class="post-metadata">

**Author:** ![ndika](https://avatars.discourse-cdn.com/v4/letter/n/c6cbf5/32.png) [@ndika](https://forum.juce.com/u/ndika)\
**Post date:** [May 31, 2015, 11:33am UTC](https://forum.juce.com/t/retina-flickering-mbp-workaround/14852/6 "2015-05-31T11:33:26Z")

</div>

Just wanted to mention that this may not be a Retina bug exactly, as I and others have flickering issues in standard resolution as well on 10.10. It may just be that whatever you're doing is not causing enough stress to reproduce the glitch until you start pushing all of those pixels to fill that lovely retina display :)

See this thread:&nbsp;http://www.juce.com/forum/topic/repainting-glitches-mac-os-1010#comment-310588

Anyway, I am also using the OpenGL renderer as a workaround for this, and so far that works just fine here.&nbsp;

-n
