Very low FPS on a 2018 MB pro.

(redhoot) #1


I tried searching, but all other posts that are somewhat in line with my issue are years old. Not sure if there’s been any improvements.

The GUI lags significantly on OSX Mojave on a brand new 2018 MB Pro, no plugins all native stuff only, I’m guessing its 8-14 FPS. Which makes it quite nasty to work with.

Is this still a known issue ? If so, any workarounds ?


(jasonwuest) #2

Maybe try this recnt thread:

(ffx) #3

What a pity, Apple ruined it once again. Not helpful for you, but maybe for others: Stay where you are, best is to stay at Sierra, if you want working audiounits, and stay High Sierra, if you don’t want low fps. Until there is any sign of life from the devs.

redhoot: The only idea I have is that you try low resolution mode, you can set it in the properties.

(redhoot) #4

@ffx , thanks. Launching in low resolution solved my issue!

Hopefully we can get native retina support in the future.

(wahrk) #5

Thank god for this thread. Ugh.

(downloadthepark) #6

Exactly same issue. Under preferences I changed default 60fps to 30fps. Restarted and GUI rendering perfect.


Funny, I got one for Christmas and experience a similar thing with Logic running Alchemy on it. It was slower than my old one so I just returned it. It seemed like the issue might have been that I ported all data from the old one onto the new one and but the old one had glitches on it which the new one didn’t know how to deal with. When I opened up the laptop clean without all my ported data Alchemy ran fine. Never tried running Renoise on it, though.

So you might want to start from scratch on the new one and see if you still have these problems.

(ffx) #8

When I opened up the laptop clean without all my ported data Alchemy ran fine. Never tried running Renoise on it, though.

I think you experienced a “random” kind of change, e.g. Spotlight was not indexing in the background, so more cpu was available, or similar. The current and last macbook (pro) generation has some real design flaws (too thin and poor thermal ventilation). It is said to be not capable of running the cpu at maximum speed for more than 1 minute, then the thermal control in the device will already downclock the cpu quite drastically. Since the Renoise GUI is basically drawn by CPU (I proofed this by doing some tests, although I found CoreGraphics and Quartz? references in the code), the lower the CPU speed, the less fast the GUI will be. Single core speed is the key.

I also have this (maybe totally wrong) theory: Apple once did gpu accelerate CoreGraphics or Quartz. But with the introduction of the new Metal framework, they switched CoreGraphics to CPU, since also older Macs will then “feel” older, too. Esp. if you are using a normal CoreGraphics GUI with Retina, and the system doubles the pixels, it seems to be done fully by CPU. Only if the developer now completely switches to Metal 1/2, it will be fixed (OpenGL was discontinued by Apple, too). This is kind of loose/loose-situation for all developers targeting macOS: Supporting another proprietary Apple graphics API has been proven as not a good idea. Apple could decide in 3 years that Metal 2 is outdated. I think in a situation like Taktik is with Renoise, he seemed to write the whole GUI system himself, it must be pretty frustrating. Such amount of extra work, only because Apple does very bad decisions.


That second part kind of went over my head, but yeah, it’s pretty shocking that they could get away with shipping a device that is straight up worse in most situations. Thankfully If I end up sticking with Renoise (it’s been 4 months now) I won’t have a reason to get another macbook unless I really miss the timestretch options Logic offers.