yet another Omnisphere problem thread..
- yes, ive read the millions of threads already available here (thank you The Pirate for helping everybody)
- no, nothing from those threads fixed the issues for me yet (or for my friends)
- THIS THREAD IS ONLY FOR OMNISPHERE 2.6.4 USERS (THE LATEST VERSION ON SISTER SITE BY r4e) -
**update - i have gone legit since this thread lol**
- - - - - - -

now that we got that cleared.. and before you roll your eyes :
both on mac and windows, the last Omnisphere (2.6.4) available on sister site seems to have an issue, and i want to hear from you guys if you experience the same and if you managed to fix it.

1) Omnisphere would just stop outputting audio or generate audio, and that specific instance would just stop working even if you reload and project, and it basically has to be removed.
inserting a new Omnisphere instance would work fine however
2) Omnisphere would not recall presets when you open up a project (basically reseting like i described above)
3) those issues also occur on Keyscape and Trilian from the same release on sister site

is there a timebomb in the last release? is there anything i can actually try to fix it? or does these versions require an updated patch that will take care of those timebombs? (that probably only R2R themselves could fix?)

heres what i tried to do to fix the issue: (both on mac and windows)
- setting correct permissions on STEAM folder, also for everybody and every user, full read & write access, tried to have myself as the owner, and tried another time to have everyone as owner (applied to enclosed files and folders)
- same thing for the .dll on windows (both inside spectrasonics folder, and the vstplugins folder)
- on mac: make sure everything is de-quarantined, codesigned, batchmoded
- re-activate by deleteting the .DAT files, thus requiring re-activation
- re-patching original plugins .dlls and executables on mac

thanks yall and have an awesome day

 

Last edited: Jan 2, 2023

Rollback to the latest R2R release. If you want to remain on the latest version. I would say do a complete uninstall and reinstall from the ground while cleaning the directory. Although I have never seen Omnisphere TimeBomb seems kinda odd (either the patching wasn't correct or something I'm not aware of).

 

use .VST instead of .AU
solve the pb for me
Ableton 10 + Catalina

 

i do use the vst on legit FL Studio, however that still happens.
on another note, some of my friends are on Logic, so AU is their only option

do you use Omnisphere alot? does it not break for you at all?

 

Yes I can confirm the above issues. Windows 10 - FL Studio 20. Sometimes presets would not load. I didn't have this issue with older version. There is deffinetely something wrong with the latest update from r4e. Also my frined has the same problem.

 

The issue of not recalling presets with AU existed before 2.6.4 for me. My workaround is using VST or, if using AU, saving the preset as custom "Multi" preset before closing the project. For some reason "Multi" presets are loading fine when reopening the projects. No timebomb, though.

 

Nor have I, but I've had this problem with the latest Omnisphere, Trilian and Keyscape versions. I'm assuming it was only recently implemented, along with the "new" authorization process.
Running on Ableton in W10 BTW.

 

Last edited: Jan 29, 2021

and how long have u been using the VST version with no problem?

 

I have been experiencing the same problem with losing the preset in the FL Project..
I have a few older projects i have not opened and i hope they load long enough for me to note the preset.
I do save most presets I use in my own presets folder, but i will make note from here out.

 

For about two months on 2.6.4c

 

Can you guys force the issue with missing patches? Because to me it happened only unexpectedly. So whatever I change I can not test whether it has changed anything.

I can confirm issue 2) patches, BUT I am having these issues since Omnisphere 2.6.? (pirates release), not just the latest. That issue bugged me recently, as a patch went missing. There are legit omni owners experiencing the same. Went into reading threads over threads for 2 hours, for 5 years there doesn't seem to be a final solution, just workarounds.

Official support suggests to delete the registration file and reauthorize. If I remember right, your issue 1 also occurred to other users in those threads mentioned above, and I think they were on older versions.

I'll try that registration thing, if not rolling to
Spectrasonics.Omnisphere.v2.6.3c.Incl.Patched.and.Keygen-R2R
2020-10-04 47.68 MB
Spectrasonics.Omnisphere.Patch.Library.v2.6.3c.Update.WIN.OSX-R2R
2020-10-04 95.37 MB
Spectrasonics.Omnisphere.Soundsource.Library.v2.6.1c.Update.WIN.OSX-R2R
2020-10-04 953.67 MB

Edit: Why is that Spectrasonics.Omnisphere.v2.6.3c.Incl.Patched.and.Keygen-R2R missing on sister site??? Dang yous! You put up vento 14 Gigs to lure me, and woosh gone. Now I need that omni 263c and you provide the others and even older ones, and I am sure it WAS there. Could you please help before the conspiracy theory is evolving?

 

Last edited: Jan 29, 2021

Omni not producing any sound actually happends on legal version aswell from time to time but it seems to be connected to some presets and combination of fx, sound sources from 3rd part banks. Just so you know it doesnt have to be connected to what veriosn you use but more what banks is involved..

 

i cant believe they charge $500 for it and its still broken, wouldnt expect this behavior at this price tag lol

 

same for me, i tried to replicate the issue myself but no luck, it really feels like a matter of time, and closing the plugin and opening it i think

 

Hm strange, I'm not able to reproduce that behaviour, my projects in FL just load fine but I also just use the basic library.
Will see if I can reproduce it on my other machine.

Also don't think that it's related to the patches but I'm not 100% sure (have to test it first with some additional libraries).
The patches itself don't modify the program code, they just replace Spectrasonics RSA keys with the ones by R2R that work with their keygen.

 

thanks for chiming in, for me this happened both on my macbook pro Mojave, and on my windows 10 pc.

could it be possible that theres more patching/new patching needed in these new versions?
im trying to really find the source of the issue.

yesterday for example it just stopped outputting audio mid-session that was wild weird.. and if i open a new instace of it and load the same preset - it works normally

 

R2R, MASTER of matemathics, still dont know that, Spectrasonics cracks based on public key, is faulty because the developer changed the protection silently long time ago...

 

Also appreciate your help. I guess when you say "patches don't modify the program code" you are talking about the Patch function of the 2048 keygen, correct?

Not being able to reproduce the problem is my main barrier of moving forward as it only occurs in unexpected events (for instance I have saved and loaded a project on 4 different days without issues. Then suddenly, empty patch in omni. (maybe I should be able to recover an older project backup by FL and see if the "omni patch" is empty there, too.)

I learned yesterday, that I am on the last R2R version of 263c. So the issue #2 omni patches is not rooted exclusively to the newer versions. I somehow guess it is related to the update / R2R Patch procedure. Did the last software-update again 263c and when R2R patching the dlls it turned out, that I have a second omnisphere.dll that is R2R unpatchable due to error. I deleted that one and patched the 263c dlls with success (program data & vst plugins). When starting Omnisphere I was NOT asked to authorize, as it was successfully authorized with pirates release and all above updates did not require authorization! This is known but maybe here we might have a root.

I'll put up what I learned so anybody interested can follow along:

1. official spectrasonics advice of deleting the auth file and have re-authorization within omni again: done

2. read/write permissions on steam folder: weird anomaly. On WIN10 Lite+ Oprekin here. Even Win10-Super Admin is not totally able to apply this. Right clicking folder to properties, the square for the permission is like half checked. It's like a grey square within the checkbox. Removing it, applying the change to all subfolders and files the process takes like 2 minutes and leaves the exact property checkbox empty, looks like it worked. Closing the window and checking the properties again it turns out to be the same half checked grey square again.

Setting security settings of the steam folders via Win10 SuperAdmin did change some properties to read/write to all users etc., so maybe this could have helped. But checking the above half checked property again it is still half checked.

3. Workaround -> paper pen and bouncing for security. I don't use Omni regularly. Tried renaming MIDI tracks etc. like others did, but I consider notes on some paper a lot easier to handle.

4. Forcing the issue was not possible. Maybe Step 1 did it for me. I'll have confirmation only if nothing occurs.

I understand what you are saying, is there any source to that information?

How are certain users able to use it without any "empty patch" issues? Why is Spectrasonics official support aware of this issue for over 5 years and gives advice on that to nonR2R users? Appreciate a good answer.

 

The second dll could be from the 2.6.4 update or another one which is already patched.

Btw. if it's a bug, then this explains why it also happens in Trilian and Kescape.
Most recent Keyscape and Trilian updates were made based on the Omnisphere binaries. You can see it when you take a look into the
program code or even simpler when you use a resource editor and browse through the skin files. In Keyscape.dll and Trilian.dll you still can
find png images from Omnisphere.

I think we'll see it on the next updates if it's a bug or related to the RSA key.

 

Hey hope you are doing all good.


I opened a thread a couple a days ago with the same subject…

Here is what is going on with my system….

I am on Win 10 and using Cubase 11 both latest versions.

Bevor the last update I never had this issue on this system everything was recalling great…

Now I have problems with Omnisphere and Trilogy not recalling patches…

But I had recall issue on my old Mac using Logic and never found a solution…

I hope there will be a fix or something….