Samplitude Music Studio Vst Plugins Not Loading

Posted on  by

Steinberg updated the VST interface specification to version 2.0 in 1999. One addition was the ability for plugins to receive MIDI data. This supported the introduction of Virtual Studio Technology Instrument (VSTi) format plugins. VST Instruments can act as standalone software synthesizers, samplers, or drum machines. Wow in 2019 i still need help. How does one verify file integrity in steam? I have been exploring MAGIX Samplitude Music Studio 2017, and I thought I'll share some of the included VST instruments demo audio, to give you some idea of.

I had a 15 hour struggle in the studio recently. All my Cubase 7 (64 Bit) projects refused to load without crashing. Even projects that I was working on the very day before.

I re-installed, searched, cleaned, refreshed preferences, you name it, I tried it…

15 hours later I was still unable to load any of my projects without Cubase disappearing into the dark depths where all dead project go.

Melodyne Studio Celemony 5.0.1.003 (Aug/2020) 64-bit (Standalone, VST, VSTi, VST3, AAX) Windows 7,8 and 10 Instructions: Run the installer and enjoy Direct Download (24MB) August 1, 2020 12 Arturia Analog Lab (Mac). Not in standalone mode because it refuses to use my audio interface's native ASIO driver and not as a VST plugin because I can't find the right files to drop in my host plugins folder. My primary concern right now is getting Amplitube 4 to work as a VST plug-in, so can someone please tell me which AmpliTube VST-related files I need to be. These are VST / AU plugins with known problems in FL Studio, and the solution(s). The list is not complete, but we add problem plugins as we find them. If you have a plugin that you fixed a problem for, that isn't currently listed here, please report it in the Technical Support Forum and inform us about the issue so that we can add it to the KB. How to setup the VST plug-in path so it is recognised in Samplitude or Sequoia.

The next morning I woke up and with a fresh head, found myself a cure within 30 minutes (based on the research I had done the day before). So I thought this would be worth sharing, as during my search I found many folks with similar trouble and no solution.

The first step was realising that if I removed the Waves plugins from my system the problem went away.

Symptoms:

  • Windows 64 Bit System
  • 64 Bit DAW Host
  • Usually Windows 8 but can be Windows 7 – Must be 64 Bit
  • Cubase crashes when loading a project that contains ANY Waves plugins
  • Cubase crashes when inserting ANY Waves plugin into a fresh project
  • I am using Cubase here but it could be any 64 Bit DAW host application

I found a post related to a different issue that suggested renaming the WaveShell-VST3 9.2_x64Best free amb iet vst. file. This file is found here and this put me on the right path:

C:Program FilesCommon FilesVST3

I renamed the file to WaveShell-VST3 9.2_x64_BLAH.vst3

Wow! Success!

Samplitude Music Studio Vst Plugins Not Loading Software

All my projects loaded again… But it is not over yet.

Waveshell crashes again and now the projects will not load again even with the renamed file, unless it was renamed yet again. Renaming it back to the original WaveShell-VST3 9.2_x64.vst3 still causes crashes… What is going on?

I had already done a clean install of all related applications, Waves, Cubase etc., And also cleaned registry of everything that mentioned Waves before re-installing…

Finally I decided to search the registry for WaveShell-VST3… Low and behold the solution – A very odd registry key gets added if the Waveshell crashes. After which, any subsequent load of the Waveshell causes the host (Cubase) to crash.

Full Solution:
  • Windows 64 Bit is affected (although it mentioned 8 it can also be 7)
  • Waves (shell) crashes once
  • Waveshell gets added to the reg key with “IgnoreFreeLibraries” with reference to Cubase (or whatever caused the crash).
  • Waveshell will now crash every time it is loaded / used (unless the shell is renamed)
  • Solution – DELETE the registry DATA contained in this key (as highlighted in my screenshot) that relates to your DAW host

How to find the key: Search registry for “WaveShell-VST3 9.2_x64” and you will find the odd key with IgnoreFreeLibrary associated.

Do not search for AppCompatFlags as it will bring up tons of irrelevant stuff.

Here is my reg key area:

This may of course be different for another machine so it probably better to use the search method as mentioned above. Notice in my screenshot that Wavelab also had the same problem.

Bookmark this key and if you suffer this problem go back and DELETE the registry DATA contained in this key that relates to your DAW host.

Back It up first if you are concerned.

So anyone on Win 64 experiencing Waves crashes – And I mean total Waves crashes – ie. Nothing VST3 works. It may be worth checking.

I have contacted Waves and they are working on a solution.

OK that is all. Thank you and goodnight.

Samplitude Music Studio Vst Plugins Not Loading Plugin

  1. We're currently conducting systematic tests with the release version of macOS 11 (Big Sur) in order to offer full compatibility of our products as soon as possible. You can find our latest compatibility status - here


    Please note that although announced at the same time as macOS Big Sur, Apple Silicon processors are an independent release with separate compatibility concerns for NI products. Compatibility with macOS Big Sur will not yet ensure compatibility with Apple Silicon processors. At the moment, Native Instruments products are not supported on computers with Apple Silicon processors. Read more - here

    Dismiss Notice

Discussion in 'KOMPLETE KONTROL SERIES' started by terrybritton, Dec 1, 2016.