Hi all,

my Omnisphere V3 is running fine VST2 and vst.3
The only thing is :
If i enable Host automation for a specific Parameter in Omni and want to modulate it with one of the many modulators from Bitwig everything works fine.

BUT when i reopen the Project and reopen the GUI from Omni (VST2 or vst.3) the Bitwig modulator changes its value.
In FX-Omnsiphere everything is working great with the Bitwig Modulators when i reopen the GUI !!!

Does anyone have an idea how to fix that ?

Thank you in advance

 

Perhaps AI can help you:

Spoiler: Source: Grok KI

It sounds like you're encountering an issue where, after reopening a project in Bitwig, the modulation values from Bitwig's modulators are not recalled properly when you reopen the Omnisphere VST2 or VST3 GUI, but they work fine in the FX-Omnisphere version. Here are a few things to try that might help fix or work around this issue:

1. Update Omnisphere and Bitwig:

• Ensure that you have the latest version of Omnisphere and Bitwig installed. Sometimes issues like this are addressed in newer updates.
  
  
• Since you're using Bitwig 6 Beta 6, it might be worth checking if there are any known issues with that specific version, as beta releases can sometimes have bugs that aren't present in the stable version.
  

2. Check Automation Settings:

• When you automate a parameter in Bitwig, make sure you're automating the correct control within Omnisphere. Sometimes, if the wrong parameter or automation type (like host automation vs. internal automation) is used, it may not properly sync when reopening the project.
  
  
• You might want to try to disable and re-enable the Host Automation setting after reopening the project to see if that triggers the proper recall of the modulation values.
  

3. Try Using FX-Omnisphere:

• Since you've mentioned that the FX-Omnisphere instance works fine with modulators when reopening the project, you could consider using the FX version of Omnisphere instead of the regular Omnisphere VST.
  
  
• FX-Omnisphere seems to handle automation and modulations better in your case, so sticking with it for now could help avoid issues with the VST versions.
  

4. Bitwig Modulator Settings:

• Double-check the settings on the Bitwig modulator you're using (e.g., Envelope Follower, LFO, etc.). It could be that a specific setting or behavior in Bitwig's modulator is causing the issue when reopening the project. For instance, check if any reset or retrig options are affecting its state when the project is loaded.
  

5. Check the Automation Lane:

• In Bitwig, verify if the automation lane for the parameter is properly saved and that it’s linked to the modulator when reopening the project. Sometimes, automation lanes might be unloaded or improperly linked when reopening, which could cause the issue you're seeing.
  

6. Clear Cache and Preferences:

• Clear any Bitwig cache files and reset your preferences (in case there’s something corrupted there). It might help if there's a setting or file that isn’t being recalled properly after reopening the project.
  
  
• In Bitwig, go to Settings > General > Clear Cache to reset the project settings.
  

7. Check for Parameter Mismatch:

• If there’s a parameter mismatch between how Bitwig is sending the automation and how Omnisphere is receiving it, that might cause the values to change unexpectedly when reopening the project.
  
  
• Make sure there’s no conflict in how Bitwig sends the automation (VST3 might handle things differently than VST2).
  

8. Omnisphere Patch Save and Load:

• When working with patches in Omnisphere, make sure you’re saving the Omnisphere patch and not just the Bitwig project. Sometimes a parameter change might not be fully saved within the patch itself.
  
  
• Try re-saving the Omnisphere patch after modulating and automating parameters, and see if it helps preserve the modulation values when reopening.
  

If none of these steps resolve the issue, it could be a specific bug or compatibility issue between Bitwig 6 Beta 6 and Omnisphere. Since you're using a beta version of Bitwig, it might be worth reporting the issue to both Spectrasonics (for Omnisphere) and Bitwig's support team, as they may have additional insights or fixes specific to that version.

Let me know how it goes or if you need more suggestions!

 

Thanks PulseWave
Funny AI

the best answer that i can give is :
Use the internal modulation possibilities of Omni ;O)
Sad that FX-Omnisphere has NO Modulation possibilities in it