Symptom When using a Native Instruments VST plug-in in your 64-bit host sequencer, the application freezes or produces crackling sounds. Cause Most NI VST plug-ins offer 32-bit and 64-bit versions. VST plug-ins may cause performance issues if a 32-bit plug-in is loaded into a 64-bit host sequencer.

Solutions We recommend to only use 64-bit plug-ins in your 64-bit host sequencer. Follow these steps: 1.

Verify if you Loaded a 32-bit Plug-in your 64-bit Host Sequencer. Start your sequencer, create a new project and load the VST plug-in that is causing the issue. Open the Windows Task Manager and select the tab Processes. Check the list for 'bit bridge' processes. A running bit bridge process indicates that a 32-bit plug-in is loaded in your 64-bit host. For example, the Cubase bit bridge process is named VSTBridgeApp.exe: 2. Fix the Plug-in Path in your Host Sequencer In order to load a VST plug-in, the host sequencer needs to be pointed to the folder the plug-in is located in.

To find out if you assigned the correct VST 64-bit folder in your 64-bit host sequencer, follow these steps:. Open Native Access Installed products. Click on the product that is causing the issues and choose Installation Path. The tab shows the VST32 location and the VST64 location:. Check if the directory below VST64 location is selected as a VST folder in your 64-bit host sequencer.

If not, add it. Here are articles / videos that show the process:.

If your host sequencer is not listed here, refer to the sequencer's manual. Provides useful information about VST plug-in administration. Rescan your plug-ins in your host sequencer. Fix the VST Plug-in Directory To verify if your plug-in files are located in the correct plug-in folder, follow these steps: 3.1. Determine the Version of the Plug-in File.

Open Explorer and navigate to your VST64 location folder. Right-click the.dll file for the product whose plug-in is causing these issues to open its Properties. In the Details tab of the Properties window, note the expression in brackets next to the Product version number. The below example shows the Properties of both the 32-bit ( IA32) and the 64-bit ( x64) versions of the Battery 3 plug-in.

Relocate the Plug-in File. If the plug-in version of the file is 32-bit ( IA32), it was probably moved from the original installation folder. There are two ways to resolve this issue:. Move this file to your VST32 location folder, find the 64-bit plug-in file and move it to the VST64 location folder. Reinstall the product and assign the VST64 location in your host sequencer as explained in chapter 2.

Describes how to reinstall a product with Native Access. If you found the 64-bit plug-in and want to keep its location, you can relocate it with Native Access as explained in. Rescan your plug-ins in your host sequencer. Note: If you find plug-in files from the same product with different version numbers (e.g.

Zfx Plug-in Host For Mac Pro

MASSIVE 1.4.0 and MASSIVE 1.5.1), only keep the file with the highest version number and delete the others.