Notifications
Clear all
Topic starter
September 18, 2023 5:16 pm
You are dammed if you do and dammed if you don't
It is actually described in the Omnisphere trouble shooting guide. Omnisphere UI does not work when loaded as AU in the DAW while a wrapper software like Unify uses the VST version om Omnisphere. I use Omnisphere on more than half of my tracks and have just started using Unify
I tried to remove the VST version of Omnisphere in Unify and that works. But most of the patches I have bought from Pluginguru will not work then as they want VST. This is really bad. I have to give up on Unify for now.
Is there a solution to this?
September 18, 2023 6:33 pm
I agree this is frustrating, but it's a Spectrasonics bug. There's nothing I can do about it in Unify.
The only "solution" I can suggest is to load every instance of Omnisphere as a VST inside an instance of Unify in your DAW. This would sidestep the bug, and should not introduce any significant overhead.
However, I understand that you are adding Unify to existing DAW projects where you already have the Omnisphere AU loaded directly on some tracks, so this will involve a bit of extra work. For each track where you have loaded Omnisphere directly:
- Open Omnisphere GUI and save the sound you're using as a new Omnisphere user preset.
- Replace the Omnisphere AU instance with a Unify instance, then load the Omnisphere VST inside it, and recall the preset you saved.
A tedious process, to be sure, but would only need to be done once for each project.
