First things first, I hope this thread is posted where it should be.

I'm having issues lately with Omnisphere (first in 2.6.1 and since a couple days in 2.6.2) in Logic Pro X 10.4.4 (on Sierra 10.12.6). The most common scenario is when I'm navigating through the patch browser (with autoplay enabled) until I choose this venomous patch (a random patch in fact) and it just crashes and shuts the entire DAW all in a sudden as if it was the minesweeper leaving the OS X message to notify Apple about the problem, relaunch the app, and so on.

I tested if the error happened in the standalone version also but it's working flawlessly, no crashes. From my ignorance I could relate the bug to the latest updates and their behaviour in LPX but just saying.

UPDATE:
Just made a fresh install of 2.6.0 and it works almost perfect.
However there are still 2 issues that completely freeze Omnisphere both in standalone and vst: When clicking Install .omnisphere and when trying to import User Audio.

Have you ever experienced this? Sometimes google is just not enough

Thank you!

 

Last edited: Aug 18, 2019

I have the same problem every time I try to install a new sound when i click install.omnisphere it freeze.
I can't find a solution, have you already solved the problem or not yet?

 

Go to STEAM/Omnisphere/Defaults/ and delete UserSettings.xml (I made a backup of it just in case but haven’t needed it) and start Omnisphere again.

 

thank you very much

 

Hi I am running omnisphere 2.6.3 on my mac OS 10.15.6. I tried to open omnisphere in Logic but it instantly crashes my DAW. I tried again with the standalone vst and same results. However, when I tried opening it with FL studio on my mac it loads up fine and everything. Anyone knows why this is happening?

 

Did it initially pass validation with Logic's Plugin Manager?

 

I have the same issue in 2.6.3 and it crashes auvaltool, so it doesn't pass validation because of that. So I had to roll back to 2.6.2.

Os: 10.5.6
Tested on both Logic Pro 10.5.1/ 10.4.8 and the same issue.

 

I think your situ is different.
Your options are the normal codesign:

Code:

sudo codesign -f -s - 

in Terminal, and then drop the AU in Terminal after. Notice there is a space at the end of the command.
But firstly try this; go into Plugin Manager when in Logic, and tick and/or rescan the offending plugins.
One of these should work. Let me know.

 

i Just Signup for say thanks to you,you are a Hero ,now my version 2.6.3c of omnisphere works thanks to you and the command in terminal :DDD,
before it crashed logic, but remember for other people remember of Disable SIP (COMMAND R For boot mac in recovery mode ,after recovery loading, go on utilities>>Terminal write csrutil disable...click enter,restart mac, and use a software that you can find on google for forcing validating of AU),after doing this you can use the command in terminal of Smoove Grooves
"sudo codesign -f -s - "and then drop Au from components folder

.......,

for re-enable SIP(,reboot mac in recovery,go on utilities,terminal<<write csrutil enable )and reboot..

 

Hello,

I have the same problem I think but i can't seem to understand what you guys are suggesting to do. If you can tell me step by step what to do that would be great.
Just to make sure my issue is the same as in this forum, when I open Omnisphere in Logic it crashes instantly (it has been validated before) and works fine in FL.
SIP is desactivated, but i can't seem to understand wheere to put the codesign-f-s thingy ? and how do i drop the AU components folder ? and where to ?

Thanks in advance

 

Type into Terminal.
And then you drop the component into Terminal, not the whole folder!

 

Here's what is says :/

 

any idea what to do to fix it ? :/

 

Please, Dear God, why are you ONLINE when installing warez???

 

WT actual F.
Anyway, your picture is strange. You are doing something wrong.
in Terminal, I do not know what the reference to "your account" meant. Maybe you need the developer tools from Xcode to be able to use Terminal properly on whatever macOS you are on?
Huh. Anyway, Terminal looks like it worked...

 

well, thanks anyway

 

Hey @keygen.exe Just realised:

Huh?

 

10.15 lol small typo

 

Thanks for proposing a solution. But I have to admit, it is hard, or let say, tricky for people like me (just regular musicians using audio units to make arrangements) to understand the procedure without any coding background or Mac Os deeper experience. I'm facing the same issue with Omnisphere and Logic constantly crashing upon opening the plug-in. Latest updates are done, running on Catalina. Can't make this work yet and it is very frustrating and stressful as recordings must be done on schedule. I try to understand things like " drop the component into Terminal, not the whole folder "means. Btw english isn't my main language. Any possibility for an explanation easier to understand or developed ? thanks ; )

 

So why have you jumped to new hardware and/or a new macOS and created this problem in your professional life?
And using Terminal is just like knowing how to open the bonnet of your car. It's simple.
You can't use a computer and not know basic things like this.

Thanks for quoting me and thanking me personally, but next time maybe just Like the comment instead of dragging me back here!

It is the most developed. And the way I explained it was the easiest to understand.
Please create your own post with your specific details. Don't jump on this person's thread.
Cheers.