asked Apr 05 '15 at 23:45 by kzantow (346)


I just purchased a UHD monitor, running full resolution (3840x2160) with a DisplayPort connection on my 2014 MacBook Pro, OSX 10.10.2. Everything is great except Bitwig, when full-screen (or expanded very large), which has very bad performance issues. I could play back some tracks with less than 1/4 of the CPU meter when Bitwig is fullscreen on the MBP itself (with a resolution of 2560x1600), but when Bitwig is full screen on the UHD monitor, it cannot playback correctly, sputters terribly and the CPU meter stays at 100% completely. If i shrink the size of the UI down things are back to normal again. This is discouraging, as the only real reason I bought the display in the first place was to use a sequencer on it (which currently is Bitwig, for me obviously)...

Is this an OSX/hardware issue somehow? Anyone have any recommendations how I might fix it so I can use Bitwig fullscreen on this UHD monitor?

Hi there,

Well, I've upgraded to 1.2, unfortunately, it's made the problem worse. The issue is directly related to the size of the display. I can no longer play back tracks that I could play fine in 1.1.11. I've adjusted all the settings for the audio latency and buffering (the same as I used in 1.1.11 and also the larger 2k buffers, tried every setting to be honest) used both the Focusrite Forte (garbage) and internal Mac audio, but nothing alleviates the problem except shrinking the size of Bitwig's UI. I can literally get a 50% performance boost by shrinking to the smallest size possible, at which point my tracks are able to play back without issue. The same track, with the UI expanded to just the full-screen MacBook Pro size, or even windowed near it results in the CPU meter at 100% and awful stuttering/playback issues, entire computer is somewhat sluggish to respond.

I hope this can be remedied. I really just can't use the DAW and I've swapped to Ableton at least temporarily, which sucks because Ableton really is nowhere near as great. But at least it works and is usable (and the pitch/time stretching is much better in Ableton... sorry couldn't resist that one).

I've created a quick video to show the issue (sorry no audio, I'm a screencasting noob). Suffice to say, when the screen is large, audio cuts out awfully, as the cpu meter is spiking. Check out at about :20, I minimize it... you can see the CPU meter go from 91% -> 78%, this isn't due to random parts of the track using more CPU... I'm not making this stuff up. Seeing as I can't even run maximized on the MBP pro screen, full screen on the UHD monitor is obviously right out.

Any suggestions to fix this is much appreciated, I really don't like using Ableton or any other DAW these days.


answered Oct 05 '15 at 06:03 by kzantow (346)


I bought a Samsung UD590 Series U28E590D today and got the same problem with Display Port on a Macbook pro :-( The problem really seems to be related to Bitwig because Logic in comparison doesn't deliver this high CPU peaks. Come on, more than a year now and still no fix?? Kind regards,


answered Dec 12 '16 at 14:27 by carstino73 (11)

My issue seems to be similar than yours and the sequencer / piano roll performance is still bad in Bitwig 2.2.2.


answered Nov 30 '17 at 23:18 by Rokka (101)

Hi kzantow,

I also have a Macbook Pro Mid 2014. i7 + 16 GB of RAM and a UHD monitor connected via DisplayPort.

Still with version 2.2.3 I have this issue. But also with my previous monitor with much lower resolution I had this issue. Were you able to solve the issue? Is it maybe the Intel Iris Pro 1536 MB graphics card?


answered Jan 25 '18 at 21:58 by reneeijzenga (30)

+1 affected by same issue


answered Feb 01 '18 at 02:20 by zezic (21)

According to the following ticket the GPU rendering will hopefully solve this issue in the future:


answered Feb 13 '18 at 22:58 by Rokka (101)


Hey there,

Sorry to hear you've been having these problems :/ I can't really offer a fix right now, BUT when Bitwig Studio 1.2 gets released soon, it will features full UHD support and I'm quite confident these issues you're having will be fixed at this point.

Must admit, I'm kind of jealous of your monitor though ;) Hope this gives you something to look forward to in 1.2 (among many other things!) take care :)


answered Apr 06 '15 at 11:22 by Unc (124)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Apr 05 '15 at 23:45

Seen: 3,278 times

Last updated: Feb 13 '18 at 22:58