Would you mind saving, closing the DAW and reopening the project with an Ominsphere patch and verifying if the patch would load?

And if it does, could you also post your Soundsources and Patches versions?

 

reopening doesn't change the patch. patch library 2.8.0c soundsource 2.6.1c

 

Sounds great, thank you!

 

Apart from giving full permissions to STEAM folder, anybody that has any solutions for the init preset issue, can you please post your fix or any other diagnoses? I do think one or two people may have either resolved, or not been affected by this. I rolling with it either way, as I have tried a number of configurations to no avail.

Running Mac OS, Big Sur
Omni 2.8.1c, all patches sound sources up to date.

 

Yes that would be great. I am wondering why this is not the biggest topic when speaking about Omnisphere. Literally everybody once had this issue, many never solved it. Some did.

For now I can only confirm the patches being saved when reopening the project on this built:
Omnisphere: 2.6.4c(v)
Soundsources: 2.6.1c
Patches: 2.6.3c

You might wanna try out this combination, just to verify if that works for you.
When I did the 2.8.0 update yesterday and hadn't the patcher so nothing was working, I was easily able to jump back to my old built simply by installing the old patches. So it should be no problem to jump back and forth between different versions just for testing issues. Didn't mess up my STEAM folder at all.

If it works, than you know for sure that it's not any system related bug causing the issue. Then it's probably just not the perfect cracked version to go for. If that doesn't work for you then I have no clue what's causing the issue but we know for sure that it has to be system related. Then we should stark troubleshooting (no idea where to start though).

 

Omnisphere 2 - Saving and Managing Sounds

NOTE: Patches and Multis must be saved into a Category folder inside a user Patch Library —you cannot save at the User folder level itself. This folder can be in an existing user directory, a newly created sub-folder inside the User folder, or a new user directory. There is no need to press the “Refresh” button in the Full Browser after saving a new Patch or Multi.

PROHIBITED TEXT CHARACTERS
NOTE: There are certain text characters that are OS-prohibited and if included in a Patch Name will cause problems when searching.

MacOS prohibits:

• : (colon)

https://support.spectrasonics.net/manual/Omnisphere2/25/en/topic/browser-page02


Omnisphere forgets the presets and just shows a blank space

1.)
So from now on I use separate instance of Omnisphere for every patch.
Name the instrument track with the patch name. Also Bounce into audio track for back up.
Hopefully like this should be safer. Even thou now I have 15+ Omnisphere instrument tracks.
I think this is the safest solution for now

2.)
so my advice until you have this figured out is:

1 - load individual Omnisphere instances for each patch/preset if possible or at max [...if possible.. ]
use as little of the multi slots... i have 2 reasons for this advice

1.1 (in my opinion) It saves CPU since that fully multi loaded instance all falls under the same CPU core, at least with cubase and with most DAW under my knowledge.... so even if your other cores are at 10% that one core load will screw you up...

1.2 if it breaks down you'll be able to fix it more easily

2- Save the patches/presets @ -> Utility -> Save patch as -> and create a new Folder
**Note you don't need to fill out all that info/categorys/etc in preset/patch save....
just choose a name for the preset and press save... done

if you just want to overwrite a presets just select --> Utility -> Save patch quick
Hope it helps

I hope to be able to help some with this and ask for your indulgence for the original posters that I publish here! Thank You!
Source: www.kvraudio.com/forum/viewtopic.php?t=482961

 

Last edited: Nov 17, 2021

Thanks for your long explanation. The method with renaming the tracks is what I did in the past when proper loading a project with Omnisphere patches didn't work.

But even though thats the best workaround if nothing else works, I'm not satisfied with this workaround anymore after I got 2.6 stable and running without issues for over 2 years.

 

I hear you bro. For me too, never encountered this until I went to 2.7. Rolled back to 2.6.4 and it was still playing up, so I just gave up and decided to brave it! I guess somebody has to take the plunge. Also, at the expense of all of the new features, its a trade off, I am willing to bare. Also, as I bought all the NKS files for Komplete to map it all out, backtracking isn't an option. The Sonic Extensions NKS files are being created as we speak, so I may invest in that too. I am just grateful that it works and since the Keyscape patch updates recently, my audio is running pretty sweet (had a few clicks n pops, here and there). I give thanks for the tools and to all of the forum heads, for their patience and time.

 

dude how do I decode this url using the decoder? it's still not letting me authorize : https://auth.spectrasonics.net/user....8.1c&ch=St5%25D9KYPq3ePEzChFQSnkqT%2b%3d%256

 

Look for the akSOund post on the sister site.

 

go to this site https://www.urldecoder.org/
copy code on the first box(Remove from https to c&ch= part) and click decode decoded one will appear on the box below. both are identical but little bit different.

 

Last edited by a moderator: Nov 22, 2021

ty

 

It's wrong. They have never resolved this issue. For the moment, there is only two solutions: buy the legit omni or download vkDanilov version. But it remains time bomb inside his version (preset vanished when the DAW is opened). But not the recall issue...

 

Do not be happy so quickly.
Even R2R 2.6.4 has this time bomb issue...

 

It's a myth.
Nobody has managed to solve this problem using R2R cracks.

 

Used omnisphere 2 for sometime on my mac. I couldn't experience the preset vanishing issue on logic pro. But i didn't use it that much tbh.

Btw i saw some comments about omnisphere release by moria. Users commented that presets didn't vanish after reopening projects(i think you can get rid of this issue by giving full permission to steam folder with batchmod or permission reset). But some reported crashing daw after sometime. Can't confirm because i didn't check. But feel free to check. Much easier to install than existing method.

Most omnisphere 2.8 releases not worked perfectly well. Only the vkdanilov's release seems good.even the latest r2r release has issues.this issue exists not only for mac but also for windows.

 

Last edited by a moderator: Nov 29, 2021

If it's a myth and everybody is experiencing this issue, why does it work on my system flawlessly for over 2 years now. No timebomb waits that long. The most patient timebomb I've come across was from earlier u-he cracks, which activated on 10/03 and 07/04 (synched with system clock).

 

I also can confirm 2.6 release works fine. but when it comes to newer versions lots of users experienced issues. If you need those new extensions you need the latest version.

The only proper working omnisphere 2.8 is the vkdanilov version. But for mac i can't confirm moria also released a new bundle release same install method no need of keygen or patching,users commented that daw crashing issue was gone.

 

Thats a pitty. I was going to give it another try with 2.8 to get the new expensions, but I think if the price is getting back this preset loading bug, I would skip it. Unless something has changed in the last four months?

Also good to know that there is a 2.8 Windows version that solved the issue - maybe it's just a matter of time for us mac users.

 

I dont have any problems with 2.8 on mac