asked Oct 28 '17 at 21:20 by gilesdickerson (11)

edited Oct 28 '17 at 21:50

I'm on a late 2013 macbook with 16 gigs of ram, memory isn't too much of a problem. Since I upgraded to 2.2.2 I can barely run the app. I've shut off all plugins, and it still runs choppily sounding like the memory is just about to overload. What are these updates? Things were running really smoothly before.

The worst part is any time I open a file now it takes a really long time to open, and then I get this message bar saying "plugins loading" that has me sitting for at least 5 minutes.

Also, randomly my D16 punchbox plugins stop working. Turning them off or on does nothing. This behavior is all super erratic and completely new to the 2.2.2 update.

What's going on here? Feels SUPER unstable to me.

I'm bummed that I have to go back to Ableton for the afternoon, I had a song started that I loved. Can someone help? Bitwig's unusable in this state.

In the past when I have had these type of issues I have contacted bitwig tech support and they have helped me resolve it. They requested a copy of a project where I was having problems and helped me isolate a plugin that was causing problems. Your problem is likely to be different to mine, but as well as any advice you might get here, you should let the support guys have a look as well.


answered Oct 29 '17 at 08:48 by djx (315)

I was experiencing this VERY frustrating problem opening files with remarkably few plugins. I’ve found a workaround for the time being which works perfectly for me, reducing load time to ten seconds. When opening bitwig, disable your audio engine before you load the desired track. When it loads (which should be instantly, more or less) delete all tracks. Enable audio engine, wait for it to settle, and UNDO until your session is fully restored. Just, be careful not to accidentally save it beforehand!


answered Mar 28 '18 at 11:05 by Vessel (11)

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: Oct 28 '17 at 21:20

Seen: 1,701 times

Last updated: Mar 28 '18 at 11:05