Dont worry about 2.5. With 2.6 you DONT need 2.5. Grab everything I have said before and install 2.6. Not just the software update. EVERYTHING. If you continue to have problems send me a PM, open a thread or go to one of the Omnisphere threads. I dont want to get off topic here with your issue.

 

Last edited: Mar 29, 2019

Ok sorry
I'm going to revise the rules
Thanks

 

For me, 2.6.0e isn't reliable from REAPER (lastest 5.973), having many crashes - in particular when browsing multis. Seems to work better from Studio One 4.1.3. OS is Windows 7 Pro SP1 x64.

 

Hello,

I use Windows 7 Pro 64 Bit and I have a problem with the latest Omnisphere update (2.6.)
With 2.5. everything worked perfectly in my DAW (Studio One 4).
I did not uninstall Omnisphere 2, I simply wanted to upgrade from 2.5 to 2.6.

This is what I've done:
I installed these files:
Omnisphere_Software_Update_Win_2_6_0e
Omnisphere_Soundsource_Library_Update_2_6_0c
Omnisphere_Patch_Library_Update_2_6_0c

With the KG 2048 I patched the following two DLLs sucessfully:
C:\ProgramData\Spectrasonics\plug-ins\64bit\Omnisphere.dll - PATCHING SUCCESSFUL
C:\Program Files\vstplugins\Omnisphere.dll - PATCHING SUCCESSFUL
C:\ProgramData\Spectrasonics\plug-ins\Omnisphere.dll - PATCHING FAILED
(When I used the three 2.5. DLLs, I could patch all THREE files successfully...)

After creating a new instance of Omnisphere within my DAW, I receive the following error message:
This patch library requires a newer version of Omnisphere.
Visit the Spectrasonics web site to check for updates.

Omnisphere Software 2.5.0d 64 bit
Omnisphere Soundsources v2.6.0c
Omnisphere Patches v2.6.0c

I thought the KG would also work for the 2.6. DLLs?
Can you help me please?

Best regards!

 

Remove that dll. That is not even needed. First, Omnisphere is only a 64 bit plugin. Second, Studio One only works with a 64bit version of plugins. That is the 32bit version of Omnisphere left there from previous versions. Third, some times it takes a while for Spectrasonics to catch up with your recent updates. Finally, what are you doing connected to the internet?

 

Last edited: Mar 30, 2019

@SAiNT, @Andrew, @Olymoon RED ALERT! Repeat RED ALERT! @LightSound has gained access to your server and is going to change the rules.

@LightSound while you are revising the rules, how about implementing a NUKE button?

 

Last edited: Mar 30, 2019

Thank you for the fast response, The Pirate.

After I deleted that DLL (and all the backed up dll files), I had to paste the response code 2 times.
(The first time S1 crashed, so perhaps some data got lost.)
Anyway, now it works perfectly!

If some day there's a voting for the best user in this forum, you'll get my voice.

Best regards

 

That leftover dll has been driving people crazy. Im glad I was able to help you.

 

Try running Omnisphere in separate process or dedicated option. It used to solve similar problems.

 

Last edited: Mar 30, 2019

there is an option to have only 1 dll and a symbolic link to it...to avoid such problems...

 

Yes Liberators Master of sounds RED ALERT! RED ALERT! RAINBOW ALERT !!!
The Pirate ... when I get to create a NUKE button seen your head I do not think it will be a problem!

No seriously thanks SAINT, Andrew, Olymoon, The Pirate and the others for what you do and share!

 

Last edited: Mar 31, 2019

you are going to have lots of friend with that.

Check your PM my friend.

 

Thank you for this tip The Pirate, I'll test this setting from REAPER as soon as possible. edit: test was done.

ADDED: yep seems more stable (no crash occured) but unfortunately, it's a pain to access to Omnisphere dialog boxes! (focus problem when bridged - both by separate process or dedicated process) However, also from REAPER, I've tested (deeply) Omnisphere 2.6.0e inside Blue Cat Audio PatchWork v2.2, and... it works fine! (no crash during 2 hours session)

 

Last edited: Mar 31, 2019

have you guys with problems abt scaling issues und visual glitches noticed, that there is a Windows size option hidden?
http://prntscr.com/n6wyue << this is the utility cogwheel to open
i have no problems with win7 /64 ulti and Omni but i think on default its on a 120% size, but i dont remember cuz it was already added in 2.5

 

No problems here on Windows 7 Lite and a Windows 7 original ISO. However, the GUI has been Omnisphere's Achille's tendon.

 

Hi VolkovV Ihave the same problem with segglyuk so I stopped updating Omni after 2.4. What is this UpdatePack7R2-19.1.12?

 

del

 

Last edited: Apr 8, 2019

del

 

Last edited: Apr 8, 2019

Appreciate the advice! Got Omnisphere 2.6 running smoothly!! Im running macOS High Sierra 10.13.4 Here's some things that I wish I knew during the proccess:

1. It doesnt matter what order you install the updates.
2. Ignore the STEAM folder within the Updates and dont try to manually switch out the old/new files. Go straight for the update.
3. The software update will give you the 2.6 Component and VST plugins so it's best to delete the old ones beforehand to cut out confusion on which one is which.
4. If you then try to patch the 2 .dll's and it says in the 2048 KeyGen "the file is write protected" simply click "Show Package Contents" and right click the folder within and change permissions to "read and write" then click the (+) sign underneath and apply all changes to folders within. Def do that to your STEAM folder to have read and write permissions for all files.
5. You need ALL 3 Updates (Software, Patch, SoundSource)
6. Relax, take a deep breath you're not downloading R2R 2.0 all over again it's just a simple update that you practically can't mess up. I was worried the entire time that I might do something wrong and have to delete everything and download 2.0 from scratch and manually merge all 8 isos to a STEAM folder. I'll probably dream about that tonight ahhhhh

It's my 3rd day on this site and I've learned so much from everyone's amazing advice! Thank you all!

 

Last edited: Aug 2, 2019

Hello, I'm having problems with Omnisphere since when I run the program it tells me that "STREAM folder is not writtable".
I tried to mark the folder as "writable" but I couldn't do that.
Sorry for my bad english, hope you've understand everything!