asked Jul 30 '14 at 22:06 by mischifnmonster (76)

edited Mar 25 '15 at 13:34

riot ♦♦ (1.8k)


Had bitwig for a while. Just started a new session and I have 6 instrument tracks with maybe one vst on each as the main synth and maybe the bitwig transient designer on one of the tracks following the vst. When I play back it crackles a lot showing cpu overload and my sample rate is all the way up and I'm running an Apollo. This shouldn't be happing. Any suggestions as to why this is happening?

Hi mischifnmonster, can you provide this community some more information? Are you on windows, osx or linux? What kind of hardware do you use etc...

  — (Aug 05 '14 at 13:27) Solidtrax

I use this workaround and it works for me:

delete "info.plist" from "users/[yourusername]/Library/Application Support/Bitwig/Bitwig Studio/Applications/Bitwig Plug-in Host" and from "Bitwig Plug-in Host" and " Bitwig Studio"

  — (Jan 09 '16 at 12:40) PCZ

perhaps these are related. the problem is driving me crazy. as i get closer to completion, i.e. more clips and stuff going on i start experiencing all these hiccups/dropouts/crackles. I am also using an apollo i have an antelope clock, am running at 48khz, with my settings are the same, session is at 48 and apollo is at 48 word clock enabled. as stated in the link below it has something to do with edges of regions, although when consolidating the regions the clicks are still there, not always repeatable but almost

  — (May 27 '16 at 21:26) gunslunglow

"I use this workaround and it works for me: delete "info.plist" from "users/[yourusername]/Library/Application Support/Bitwig/Bitwig Studio/Applications/Bitwig Plug-in Host" and from "Bitwig Plug-in Host" and " Bitwig Studio" — (Jan 09 at 12:40) PCZ "

PCZ this has worked brilliantly for me. thought i heard one in my last session, but all in all 99 percent of them are gone, perhaps something i need to do everyday.

  — (May 29 '16 at 19:02) gunslunglow

Please always make sure you use the same buffer and sample rate settings in your driver as well as Bitwig Studio. We're preparing a fix that will make this obsolete, but currently, having different settings can be possible and in some rare cases, that can produce crackling via buffer underruns and other symptoms.

Another thing: Solidtrax is absolutely right, please provide a few system specs, so we have a chance to pinpoint and reproduce such issues, if they can't be fixed by adjusting settings - thanks!


answered Mar 25 '15 at 13:32 by riot ♦♦ (1.8k)

Lol so nice... Most of the questions lie here unanswered forever... What's this Q&A support for?


answered Feb 25 '17 at 11:20 by CanoP (123)

if u on Mac or linux u shliud not have pb.

if on Windoxws systems....

just set the cache to NEXT SSD drive u got.

(it solves all pb.)

'SSD have a durity along time... but not for this.)


answered May 28 '16 at 03:46 by -Chr1sMK2 (suspended)

I've had a crackling, CPU spikes issues that were caused by plugins going in and out of power-saving sleep mode. It's been solved by disabling the Auto-Suspend mode on every single plugin and the seeing which ones cause problems. Don't know if that's anyone else's problem, but give it a try if you haven't already.


answered Jun 03 '16 at 19:28 by gruzmusic (11)

that's simple : everytime i laucnh it, got my template :

my 4 hardies a drum rack a serum track

4-5 fx tracks with delays reverb, springs... my master with my normal "pre-mastering" chain, ~7 plugs.

(all my stuffs are legit, was hard to private from goin out... to buy them i need.)

so it crashes at laucnhes... and always when i reactivate audio engine.

tried auto suspend in past, but nothing....

if u can explain me how and where to analyse what .dll caused issue... please ?

i saw in another topik that on windows u go in event viewer > search for "engine.dll" (??? dont remember exactly name... the name of audio engine hosting dll.)

then u can see inside if L1.dll or IzotopeVinyl.dll etc crashed...

but could not find that personnaly.

(will post later i'm very tired, could not sleep yesterday, i'm on again but tired...)

edit: when engine is crashed "grey button"... i manual suspend my L1's... then when i reactivate it seems ok, but suxx somes VSTs not working properly even all last version / legit. (L1 is 9.2.0 i think)


answered Jun 04 '16 at 00:04 by -Chr1sMK2 (suspended)

edited Jun 04 '16 at 00:13

I've had Bitwig for a couple of months now and am getting crackling during playback every now and then. One bigger project I worked on for a long time had none of this until now. I have restarted Bitwig several times and worked on other songs in between and I've definitely have not changed any settings. But sure enough I started getting serious crackling and even the song slowing down.

So is this problem solved somewhere already since it's been a while since the last message?

Here's some system info:

Ubuntu 16.04 LTS 64-bit
AMD Athlon 64X2 Dual Core 6000+
7,8 GiB RAM

Version: 1.3.15
Revision: release/1.3 47461
Revision Id: a017b4cd16e95f9efb2ecea10e2389f26fdb50d5
Build date: Thu Dec 08 16:25:09 CET 2016
Build type: release
Heap memory: 247 MB
Native memory: 8 MB
Streamed native memory: 0 bytes
Shared memory: 128 MB
Java Version: 1.8.0_101


answered Feb 11 '17 at 20:49 by Hietala (21)

edited Feb 11 '17 at 20:50

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: Jul 30 '14 at 22:06

Seen: 5,601 times

Last updated: Feb 25 '17 at 11:20