Hi!

I'm opening a project from another computer and Bitwig is saying this:



The thing is that I looked for that file on the other PC and searched for it on this PC so I could binary compare both of them and they're binary same... VST state loads flawlessly but not on this PC. Could anybody shed some light on this, please?

Thanks!

 

The image isn't displayed. Please re-upload.

Plug-in Handling and Options ---> www.bitwig.com/userguide/latest/vst_plug-in_handling_and_options

I consulted the AI, so I can't guarantee its accuracy.

Spoiler: Source: Grok KI

First, make sure the exact same version of the plugin (and Bitwig itself) is installed on both machines—mismatches are a common cause of state loading failures, even if the state file itself is identical. If the plugin is from a different vendor or has any dependencies (like libraries or authorizations), double-check those match too.

In Bitwig, head to Dashboard > Settings > Plug-ins. Look for the plugin in the list and see if it shows any errors or warnings. Click "Show plug-in errors" at the bottom if available, then try the rescan button to force a refresh.

If that doesn't help, try reloading the specific plugin instance in the project: Right-click the device in the chain and look for a "Reload Plug-in" option (or "Reload All" if multiple are affected).

As a stronger step, close Bitwig and reset the plugin cache to force a full rescan on restart. Delete the contents of these folders (back them up first if you're cautious):

• On Windows: C:\Users[YourUsername]\AppData\Roaming\Bitwig\Plugin Database
• On macOS: ~/Library/Application Support/Bitwig/Plugin Database
• (Optionally, also clear C:\Users[YourUsername]\AppData\Local\Bitwig\Cache or ~/Library/Caches/Bitwig for waveform/analysis cache, but that's less relevant here)

Finally, experiment with changing the Plug-in Hosting Mode under Settings > Plug-ins (try "Together," "With Bitwig," or "Individual")—sometimes sandboxing issues prevent states from loading properly on certain setups. Save a backup of the project first, then reload it after the change.

If none of that works, it could be an OS-specific quirk (e.g., Windows vs. macOS file handling or permissions)—share more details like the plugin name, Bitwig versions, OS on each PC, and the exact error text/file path for better troubleshooting.

Spoiler: Source: ChatGPT KI

You're encountering the "Could not load initial plug-in state" error in Bitwig when opening a project on a different computer, even though the VST plugin files themselves appear to be binary identical between the two machines. This issue typically points to problems outside of just the plugin .dll file itself.

Here's a breakdown of what might be going wrong and how to troubleshoot it:

Likely Causes & Fixes
1. Missing or mismatched plug-in versions

• Even if the .dll file is identical, other components (e.g. support files, presets, config files, or dependencies like shared libraries) may differ.
  
  
• Some plugins rely on AppData, registry entries (on Windows), or installed runtimes.

Fix:

• Ensure the exact same version of the plugin is installed. If possible, reinstall it using the original installer rather than copying the .dll.
  
  
• If the plugin has a standalone version, try launching it standalone first to let it initialize its settings.

2. Preset or state file missing

• Bitwig saves the "state" of a plugin separately from just the plugin binary — this might include initialization parameters, factory presets, or user presets that the plugin expects.

Fix:

• On the original machine, look for folders like:
  • C:\Users\[User]\Documents\[PluginName]
    
    
  • C:\Users\[User]\AppData\Roaming\[PluginVendor]
• Copy over any relevant folders to the same locations on the second machine.

3. Bitwig plug-in sandboxing issues

• If Bitwig's plug-in sandboxing is enabled, some plugins might behave differently, or fail silently when their dependencies are missing or blocked.

Fix:

• Try toggling sandboxing for the plugin:
  • Go to Settings > Plug-ins in Bitwig.
    
    
  • Find the plugin and try disabling sandboxing, then re-load the project.

4. System-specific dependencies (like iLok, eLicenser, etc.)

• If the plugin uses a license system (iLok, eLicenser, or online activation), the state might not load if the license isn't properly validated.

Fix:

• Ensure the plugin is fully activated and authorized on the second machine.

5. Bitwig Cache Issues

• Sometimes Bitwig’s plugin database or cache can get corrupted or out of sync.

Fix:

• Force Bitwig to rescan all plug-ins:
  • Delete the index folders:
    
    
    C:\Users\[User]\AppData\Local\Bitwig Studio\cache\index\
    
    
  • Restart Bitwig and let it re-index your plugins.

✅ Summary Checklist
✅ Step Action
Reinstall plugin Use official installer, not just file copy
Sync support files Copy AppData, preset folders, or settings from original PC
Disable sandbox In Bitwig settings for the plugin
Check licensing Ensure plugin is authorized and activated
Clear cache Remove Bitwig's plugin cache and re-scan
If you've gone through all of that and it's still not working, you can also try:

• Creating a new project and loading that same plugin to see if it loads normally.
  
  
• If it loads fine in a new project, the issue may be with how the project file references the plugin — e.g., corrupted metadata in the .bwproject file.

Let me know which plugin this is — some have known quirks — and I can give you more targeted help.

 

Last edited: Sep 7, 2025 at 3:15 PM

Hi PulseWave!
Thanks for your answer. I include image again, hope it's showing now. I've checked plug-in versions and I see the project was using v1.13 and what I have now is v1.30 so I think that would be the problem, though I don't understand really well why.

I've moved 1.30 version into another folder and installed 1.13, now it loads the plugin-state:



And, again, YOU'RE BRILLIANT! A thousand TY!

 

Just to add some more info:

Got another project which used FabFilter Saturn v1.13 and since I had installed v1.24, it was showing the same error as well. Got to fix it by the same method, moving the v1.24 dll/vst3 file/s into another folder named "FabFilter Saturn v1.24" and installing version 1.13.

Hope it helps somebody!

 

Ok, here we go again...
Got a project using NUGEN Audio Stereoizer 3 (VST3, x64).

I installed v3.5.0.4, didn't load, same again: Could not load initial plug-in state: Error loading VST3 preset: C:\blablablabla.vstpreset

Tried with older v3.4.0.1, neither,

Tried v3.3.0.0, neither,

Tried v3.2.9.3, neither,

Can't find any other version to try with. I have no idea on how to fix this and make it load the VST3 preset...
I've tried to find same file .vstpreset in old computer, but it is not there. If I copy the file from this laptop to the correct folder of the old computer, it does not work, either, same error.

Deleted cache and index folders of Bitwig. Changed extension of .vstpreset file to .BAK in a crazy attempt to see if it did something, but same error.

 

Spoiler: Source: ChatGPT KI

Thanks for the clear rundown — you're troubleshooting thoroughly, which helps a lot.
The error you're hitting:

"Could not load initial plug-in state: Error loading VST3 preset: C:\blablablabla.vstpreset"

suggests that Bitwig is trying to load a preset file that either:

• Is corrupted, incomplete, or mismatched for the current version of the plugin,
  
  
• Does not correspond to the plugin's expected format or state,
  
  
• Or the plugin itself is failing to parse the .vstpreset for internal reasons (e.g., version mismatch or missing dependencies).
  

✅ Here's a step-by-step plan to resolve this:
1. Check if the Plugin Loads Without a Preset
Open Bitwig and create a fresh project. Drop in Stereoizer 3 (any version that loads). Does it open without error?

• YES → The plugin itself is okay.
  
  
• NO → Plugin might be failing due to system compatibility or install issue.
  

⚠️ If it doesn’t load even in a blank project, stop here — the problem is with the plugin, not the preset. Reinstall or check dependencies (Visual C++ Redistributables, etc.)

2. Locate & Inspect the .vstpreset File
You mentioned:

"C:\blablablabla.vstpreset" — you tried copying it over, renaming, etc.

Try this:

• Make a backup copy of the file.
  
  
• Open the .vstpreset file in a hex editor or text editor (like Notepad++) just to verify it's not an empty or 0-byte file.
  
  
• Also make sure it’s not a renamed file from another plugin or corrupted export.
  

3. Try Manual Plugin Reset in the Project
If the plugin works in a blank project but not in the original project:

1. Open the project but disable plugin sandboxing temporarily in Bitwig preferences (if enabled).
   
   
2. Try to disable the broken instance of Stereoizer.
   
   
3. Delete the plugin track, or replace the plugin manually with a fresh instance.
   
   
4. If you have automation or routing you don’t want to lose, try to duplicate the track, then replace the plugin only.
   

4. Try Loading the Preset Manually

• If Bitwig is trying to load the .vstpreset automatically and fails:
  
  1. Open Stereoizer 3 manually in a new track.
     
     
  2. Try using its internal preset browser (if it has one).
     
     
  3. Try dragging the .vstpreset file into the GUI (some VST3s support this).
     
     
  4. Or place the .vstpreset in:
     
     
     C:\Users\<YourUser>\Documents\VST3 Presets\NUGEN Audio\Stereoizer 3\
     
     And see if it shows up in the DAW preset browser or inside the plugin.
     

5. Try Rebuilding the Preset Manually
If the .vstpreset file doesn't work:

• You may be stuck recreating the settings from scratch.
  
  
• If you have access to the original machine/project where it did work, try:
  
  • Opening it there and saving a fresh preset inside the plugin itself, not just exporting it.
    
    
  • Or take screenshots of the plugin settings and replicate.
    

6. Check for Plugin Compatibility Issues

• NUGEN plugins sometimes don’t handle version downgrades well — even within the same major version.
  
  
• A preset saved in v3.5 may not load in 3.4 or earlier due to internal changes (even if the .vstpreset exists).
  
  
• Confirm you’re using exact same plugin version as the one that saved the preset.
  

7. Clean Slate Install of NUGEN Stereoizer 3

1. Fully uninstall the plugin.
   
   
2. Delete leftover plugin data:
   
   • VST3 folder: C:\Program Files\Common Files\VST3\Stereoizer 3.vst3
     
     
   • User presets: Documents\VST3 Presets\NUGEN Audio\Stereoizer 3\
     
     
   • Possibly: C:\Users\<YourUser>\AppData\Roaming\NUGEN Audio\Stereoizer 3\
     
3. Reinstall same version that saved the preset.
   

Worst-case: Recovery Plan
If nothing works, and the preset is lost or unparseable:

• Open the project on your old system (if possible), freeze or bounce the track.
  
  
• Then re-import into the new system and recreate the settings manually later.
  

✅ TL;DR Checklist:
Step Action
1 Does plugin load in a new project?
2 Is the .vstpreset file valid (non-empty, correct path)?
3 Can you load the plugin manually and skip auto-loading the preset?
4 Try saving a new preset in the plugin directly
5 Use same plugin version that created the preset
6 Clean install the plugin
7 As fallback, bounce or freeze track on original system
Let me know which version originally saved the preset, and I might be able to help locate that specific installer if NUGEN no longer provides it.

Spoiler: Source: Grok KI

It looks like you're running into a common issue with Bitwig where it fails to load a VST3 plugin's initial state due to a problematic or inaccessible preset file. This can happen if the .vstpreset is corrupted, incompatible across versions, has permission issues, or if Bitwig's plugin cache is messed up. Since you've already tried multiple Stereoizer versions, file copying, cache deletion, and renaming, here are some targeted troubleshooting steps to try next. I'll prioritize ones that build on what you've done.

1. Delete the Problematic .vstpreset File

• Renaming to .BAK might not prevent Bitwig from referencing it (as it could be cached or hardcoded in the plugin state). Instead, fully delete the file at the path shown in the error (e.g., move it to your desktop as a backup first if you're worried).
• After deletion, restart Bitwig and try loading the plugin fresh. This should force it to use a default state instead of the faulty preset.
• If the file doesn't exist at that path already, that's likely the root cause—Bitwig is trying to load something that's missing or was never created properly.

2. Reset Bitwig's Plugin Cache More Thoroughly

• You've mentioned deleting cache and index folders, but let's ensure you're hitting the right spots (assuming Windows, based on the C:\ path). Close Bitwig first.
  • Navigate to %APPDATA%\Bitwig\Bitwig Studio\ (paste this into File Explorer's address bar).
  • Delete the entire plugin-storage folder (this holds plugin states, including .vstpreset files for initial loads).
  • Delete the indexed-plugins.bwindex file (forces a full rescan).
  • If there's a Plugin Cache folder in %APPDATA%\Bitwig\, clear its contents too.
• Restart Bitwig—it will rescan all plugins, which might take a few minutes. Then try adding Stereoizer to a new project.
• Note: This resets states for all plugins, so you might need to reconfigure others, but it often fixes corrupt preset issues.

3. Adjust Plugin Hosting Settings (Disable Sandboxing)

• In Bitwig, go to Settings > Plug-ins.
• Find NUGEN Stereoizer in the list, select it, and set "Plug-in host process" to "Together" (or disable sandboxing entirely if available). This runs the plugin in the same process as Bitwig, which can bypass loading errors tied to isolated environments.
• Save changes, restart Bitwig (or hit "Restart All Plug-Ins" if prompted), and test.
• If the error persists, experiment with other hosting modes like "Separate" to see if it isolates the issue.

4. Check Permissions and Run as Admin

• Right-click the .vstpreset file (if it exists) > Properties > Security tab. Ensure your user account has full read/write permissions.
• Launch Bitwig as administrator (right-click the executable > Run as administrator). This can resolve file access errors, especially if the preset path is in a protected folder.
• Also, verify the Stereoizer installation path has no permission restrictions.

5. Reinstall Stereoizer and Test in a Clean Environment

• Uninstall the current version completely (use something like Revo Uninstaller if remnants linger).
• Download and reinstall v3.5.0.4 (latest as of now) from your NUGEN account or official site.
• Create a brand-new Bitwig project (don't open old ones) and add the plugin there first. If it loads, the issue might be project-specific—try exporting/importing elements from your old project without the plugin state.
• Test in another DAW (e.g., Reaper or Ableton trial) to confirm if the preset loads elsewhere. If not, the file itself is likely bad.

6. Other Quick Checks

• Ensure your Bitwig version is up to date (check for updates in the app or on bitwig.com).
• If the error dialog has a "Restart All Plug-Ins" button, use it repeatedly—some users report it eventually kicks in.
• Disable any antivirus/firewall temporarily during loading, as they can interfere with file access.

If none of this works, the preset might be version-incompatible or fundamentally corrupted. Reach out to NUGEN Audio support (via their site, include your error log and versions) or Bitwig support (they have a ticket system). Provide the exact error path and what you've tried—they might have plugin-specific fixes. Hang in there; this is fixable with persistence!

 

Well, after a lot of attempts to get it working (followed those guidance lines) I opened the plugin state file with notepad++, checked the lines, saw the values for every each parameter and in the end, I copied and pasted those values into Bitwig's new plug-in instance, saved the project and deleted old .vstpreset, keeping the new ones (there were a few instances of that plugini not loading).

Thanks a lot for all your suggestions, they helped a lot to guess out what to do next and what way to go.