asked Feb 21 '15 at 17:36 by Rodneymcq (51)

edited Feb 22 '15 at 16:57

I just updated to version 1.1.6 and now my audio engine never seems to activate. I have uninstalled nd reinstalled the applicaiton. I also let it run overnight, but it never connected. The app just continues to show" audio engine is connecting to this document. please wait...". Any suggestions?

Seems the issue was compatibility with the AVID coreaudio driver and OSX 10.10. I had a similar issue with Native Instruments Maschine software. Removal of this driver from Macintosh HD>library>audio>plugin>HAL resolved he issue. Both applications work fine with the driver removed.


answered Feb 24 '15 at 19:30 by Rodneymcq (51)

I'm also told that this is a common issue with users on a 2013 Macbook pro or air.

  — (Feb 24 '15 at 19:31) Rodneymcq

Avid has just released a driver update that attempts to fix this issue:

  — (Dec 01 '16 at 15:56) dom ♦♦

Happens to me from time to time as well, since I downloaded latest version....

Help... Its kinda annoying..... the funny thing is when i start with a new project first, the audio engine starts.... if ia m on one that i am currently working at it seems total random..... Help would be appreciated


answered Feb 21 '15 at 18:56 by Sargsaft (11)

I have this occurring now also; need to find a resolution if I'm to continue experimenting with Bitwig. All other DAWs have not issues - mentioning this as I was concerned maybe coreaudiod had hung. In fact had restarted the coreaudiod as I was experimenting. Do have a MBox 3 Pro so figured, maybe it was that - changed to the default input/output, same issue. It's the weekend so hoping you guys have a resolution this week.

Thank you in advance.


answered Feb 22 '15 at 16:41 by ssissa (11)

That did it for me and here is the link from Bitwig support too:

Hope that helps others in the thread.


answered Feb 24 '15 at 23:31 by ssissa (11)

Avid CoreAudio plugin causing this issue on my Mac. I removed it and Bigwig went right back to normal. Open the Finder and locate the following folder: Macintosh HD > Library > Audio > Plug-Ins > HAL Delete (move) the “Avid CoreAudio.plugin”. Restart your computer.


answered Mar 09 '15 at 18:47 by bassniko (11)

edited Mar 09 '15 at 18:49



answered Mar 08 '16 at 20:51 by salganikas (51)

Just had the same problem in OS X 10.9.5 (Mavericks).

Running Bitwig Studio through Avid HD Native Thunderbolt & HD Omni interface using the Avid HD Driver 11.3.1 (legacy/Pro Tools 11) caused Bitwig Studio's Audio Engine to crash right away when trying to enable "Avid HD Native Thunderbolt" as Input/Output device.

Running Bitwig Studio with the Built-in Input/Output worked just fine with those Avid Core Audio Drivers installed.

Upgrading to Pro Tools 12.6.1/12.7, which have been released just recently (december 2016) and installing the 12.7 HD Drivers resolved all my previous Core Audio problems with any DAW/software, as promised by Avid/Pro Tools in the driver release notes.

Especially good for users like me, who own Native Instruments Maschine Studio, Kontrol S49 & Komplete Ultimate 10, which previously would not function properly with Avid's old (version 11.x.x) Core Audio drivers installed in OS X Yosemite or later.

This fix (using the 12.6.1 or the 12.7 version of the Avid HD Drivers) should, according to Avid, also solve any Core Audio related problems on Yosemite, El Capitan and Sierra (haven't tested them, since I'm still running Mavericks because of it's reliability/stability).


answered Jan 03 '17 at 02:01 by xazqe (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: Feb 21 '15 at 17:36

Seen: 4,268 times

Last updated: Jan 03 '17 at 02:01