DeBleeder FAQ

  1. Is my system / DAW Supported?

Debleeder is currently supported on Win XP, Win 7 and Win10, and OSX Snow Leopard up until Catalina. (see Catalina section for support information)

VST, VST3 and AU are supported for both 32 and 64bit flavors making them compatible with most DAWs which use these formats.

Native AAX is supported for modern Avid systems (Protools 10.3.7 and above).  AAX DSP is not supported at this time.

  1. Limited OSX Catalina (and Mojave) Support

OSX Catalina and to some extent Mojave included additional security measures and requirements to install 3rd party software.  In addition, the loss of 32bit support means many DAWs are no longer supported or awaiting patches.  As such, we don’t provide formal support yet either. 

However, Debleeder should work in DAWs that are supported, so long as you can add permissions.  It should be possible to grant a permission exemption for only DeBleeder.  See the end of the linked Apple Support article:

"How to open an app that hasn’t been notarized or is from an unidentified developer"

While we have not tested ourselves - other customers have reported it works for them (sometimes after a few tries).  If you are still having trouble please let us know what error messages you are receiving and what DAWs you are trying it with.

  1. Do I need a network connection or internet connectivity to use DeBleeder

No.  Other than downloading the installation package and/or moving that to the installation machine, you do not need internet connectivity or network during installation or to run the plugin. 

  1. Do I need an iLok or other software key

 While DeBleeder carries digital signatures to work with Avid Products – it does NOT have any special security requirements or need hardware or software keys to run on your system. 

  1. Does DeBleeder Support AAX DSP / Avid Venue SL6 or other consoles

At this time, AAX DSP or console installation is not supported.

  1. Logic:X: Can’t find DeBleeder

While it should just be a matter of copying DeBleeder into the correct folder, LogicX is dependent on validated AU cache (rather than just being present the folder like other DAWs).  Here are some notes if you are having trouble with detection:

  • LogicX in particular is 64bit only, so only copy the 64bit version. The 32bit version may prevent detection/validation of the 64bit plugin it needs. 
  • Make sure to try the MacHD library folder. It may not always cache from a user library folder. (see:
  • After copying, you may need to do a full restart - the cache does not always get rescanned and Logic does not just search the folder when launching. 
  1. Protools: Can’t Find DeBleeder

If you did not get an error message when launching ProTools, but the plugin is still missing from your plugin list – then you did not likely copy to the correct folder.  Please see: for the correct installation folder.

  • When Pro Tools launches. I get an  Error “it is not a 64bit compatible plugin”.

If you see that message starting Protools, the plugin is in the right place, but it was modified and has lost the digital signature.  Did you decompress the archive on another machine?  Please try a clean download to the install machine (or copy the whole archive), unzip and replace the copy you have.  It should then authenticate correctly.  

  • Using Side Chains with Debleeder
The external sidechain for Debleeder works the same in all DAWs.  However, to make that happen, we had to use the main input bus.  This is also why it is is not supported on the mono track instances. 
On stereo or quad tracks, enabling the EXT splits the inputs.  So in stereo mode the first input (L) is input and second (R) is the EXT trigger.
The trigger is filtered from the output which is leveled so you can mix from there with a stereo panner.
Quad tracks just allow stereo processing and stereo (treated as L+R) trigger.
This means the routing of the trigger is up to your session, but keeps a uniform behavior for all the plugin formats.
  • How do I see hidden files on OSX Catalina
A quick way to see hidden folders is as follows. This only works on Sierra or later. Quite useful for when you need to copy files to your hidden Protools directory. All hidden files/folders should be able to be seen.
  1. Open the Finder
  2. Go to your Macintosh HD folder (access this from Devices or Locations in the left column - it may have a name you gave it, e.g. "[your] MacBook Pro").
  3. Click on Home.
  4. Hold down Cmd + Shift + . (dot)
  5. All the hidden files will become visible.
  6. Hold down Cmd + Shift + . (dot) a second time to hide the files again.
  • Cubase on OSX is blacklisting the Debleeder files

We had a customer report this to us and he figured out that he needed to the do the following to enable it to work.

I figured it out. I had to go into terminal and type in:

'sudo spctle --master-disable'
to allow apps from "anywhere" to be installed on my computer. I then opened up Cubase and Debleeder was in there (though for some reason 3 vst2 versions(?) are still blacklisted). I then went back and 'enabled' and opened Cubase and Debleeder stayed in the plugins folder. Problem solved I think!