you can now donate with bitcoin or your bank card by clicking the piggy icon under the logo

  • Get the best VPN on the market with 66% Discount!
Software, Windows, Mac OSX
Spectrasonics - Omnisphere 2 Software Update 2.6.3c / Patch Library Win / Mac screenshot
NU DiSCO | 4.06.2020 | Win / Mac | 195 MB
Omnisphere® is the flagship synthesizer of Spectrasonics - an instrument of extraordinary power and versatility. Top Artists all over the world rely on Omnisphere as an essential source of sonic inspiration. This award-winning software brings many different types of synthesis together into one amazing-sounding instrument that will spark a lifetime of exploration.

Includes the following features and fixes:
Fixes issues with host automation parameters in Logic Pro 10.5
Fixes bug where existing automation assignments were deleted after Unlearning an automation assignment
Fixes bug where new automation IDs were incorrectly assigned after Unlearning an automation assignment
Fixes intermittent crash when opening saved Logic Pro X projects on macOS 10.15
Fixes issue where Omnisphere could freeze Live 10.1 on macOS 10.15
Fixes crash when deleting a track containing Omnisphere in Reason
Improved Authorization process and GUI layout


Reuploaded. PiRAT

download from any file hoster with just one LinkSnappy account
download from more than 100 file hosters at once with LinkSnappy.
audioz mirror
http://http://peeplink.in/0e1a1122d459 Peeplink password: 2~#SRfTA

comments

  Resident 23.11.2016 5 665
+462
IT WORKED!
I'm usually the codesign master (using it for every install) but for some reason it didn't cross my mind here!

To be clear guys: I used deep codesign for both component AND vst.
Cheers Vaiman!
  Member 14.02.2015 16
+1
What do you mean by "Patch" the "Omnisphere 2 Keygen" from this page https://audioz.download/software/win/90840-download_spectrasonics-omnisphere-v20-patch-and-keygen-only-r2r.html doesn't open on my machine (MBP 2019 16' 10.15.4). Or do you mean replacing the AU and VST files?
Also, what should I do with the .dmp?
Thanks for your help
  Resident 28.08.2009 32
+3
Yes, use the keygen to patch the required plugins you want. I used the keygen on Windows from this post (Step 6 is link you need for just the keygen):
https://audioz.download/software/win/154796-download_spectrasonics-omnisphere-26-complete-winmac.html

Once, they are patched, put them back to original location (overwrite) on your Mac.
Then run that code. Both the install command & second command.
  Member 14.02.2015 16
+1
It worked! Thank you so much for your help!

The only thing is, now I have all of the Keyscape sounds in double, they seem to be exactly the same but they all appear twice in my browser, do you know how to get rid of them?

Thanks
  Member 1.02.2020 4
0
Hi Vaiman - didn't work for me. 262 ran great until upgrade to Catalina. Ran the 263c process as described. Patched AU/VST (2048 running in Parallels Desktop). Successfully Codesigned the AU. Rebooted. Fired up the Standalone - Challenge/Response completed. Restarted Standalone - no joy (several times).
Any ideas? What permissions on which objects are required to complete Authorization, do you know (beyond the AU and VST)?? Thanks for the help.....
Update: Also tried via Logic X ... no joy there either....
  Member 20.05.2014 756
+117
Hey Guys after patching, in logic, stereo version is working but not 16Xstereo and 25stereo versions ? why ?
  Member 4.06.2020 4
0
It worked! You're a legend!
Many thanks
  Resident 27.01.2015 114
+23
Worked great on High Sierra. Nice find!


  Member 16.11.2013 30
+3
When I try to code sign I get "error: The specified item could not be found in the keychain."
I installed the .pkg and have done this several times before. I did install Xcode CLI Dev Tools.

I did not have to code sign the last release (Omnisphere 2.6.2c ) on Catalina just patch the binary, fix permissions. Any suggestions?
  Member 16.11.2013 30
+3
I got this working!!!

For any one stuck with the code sign make sure you have the extra "-" after "-f -s" and before "--deep"

It should be "codesign -f -s - --deep /Library/Audio/Plug-Ins/VST/Omnisphere.vst"
  Member 30.12.2018 3 50
+200
thanks a lot it worked
  Member 12.07.2020 2
0
Hey, guys, sorry, but I'm a little lost here.
I have a new machine, MAC Catalina 10.15.5 with Logic 10.5.1 and I don't know exactly what steps to follow.

1.- I start with this latest version 2.6.3, if so... what do I do

You can explain it to me here, previously everything worked well in my previous MAc Mojave and Logic, but now I don't know what to do.

Thank you very much and greetings
  Member 14.07.2020 16
0
Please help me. I did patching components and vst and pasted in the original folder. The only thing is when I try to type the "sudo codesign" you gave, the response is "unrecognized option `--deep/......" am I missing something? when I tried to do the "xcode-select --install" there's just an error. It says there is no xcode software installed. so I got the command line tools. please help me with this. Thank you in advance!
  Member 13.12.2012 63
+1
please a current key now. We are dealing with the 2015 key and it is difficult. As soon as I enter the key, the cubase shuts down.
  Member 19.10.2016 55
+19
It crashes several times, until i finally register with the kg. It's working now, but a very sluggish in Ableton LIve 10, Windows 10 2004. Anyone experiencing this?
  Resident 18.11.2017 1 520
+202
try and patch it until you don't have to write in the licence code. So patch the two plugins .dll again
  Resident 23.11.2016 5 665
+462
Guys, it looks like the major driving factor of having a working Omnisphere on macOS Catalina is how proper the AU component is prepared. For me, Omnisphere standalone would crash until I properly deep codesigned the component. It didn't matter if the VST was codesigned properly or not, it appears the main app (standalone) is tied to the component, so be sure to deep codesign the component as vaiman points out above.
  Resident 17.04.2008 306
+32
Why is that I gotta be cued in on updates for my legit software on this site? You'd think these companies could simply send email alerts (only one or two do)

Having to do a checkup on any possible updates every once in a while becomes a flippin' day long chore. heh
  Member 7.04.2019 61
+4
So if Im on PC Windows 10 I just install over old version? Thanks
  Member 5.06.2020 14
0
Please excuse my dumb question, but while installing the Library-Update a window pops up telling me "Ready for next volume. Please insert" and I don’t know what to insert? Last time I installed Soundsource Library Update 2.6.0 without any such troubles. I’m on OSX 10.11.6. Any ideas what’s going wrong?
  Member 5.06.2020 1
0
How to authorize that update?
I was 2.6.0c worked perfectly and now i don't know how to authorize that last update
  Member 1.03.2014 128
+14
OMG need serial
  Member 9.03.2020 4 54
+46
have done the update its now asking for a serial number and its stopped working same as serum. please help wonderful friends...
  Member 9.09.2019 12
0
Hi everyone, I managed to get this to work standalone and AU in Logic, but only in regular plugin mode, not multi-output. When I tried to load 16xStereo, it says:

"Failed to load Audio Unit “Omnisphere”, please contact the manufacturer for an updated version or further assistance."

I did patch the AU and VST with old keygen and used the generated code, and used terminal to codesign AU, then restarted, and re-scan. So it accepts the code and pretty much works but I really use the multi in all my projects, so anyone knows what's the issue?

After reading this thread, I used terminal to codesign with the "deep" part too (I did it first without it but dragging the component, as I read in other page before), but it made no difference.
  Member 27.06.2013 62
+18
Not worked here!

I got back to the previous update!
  Member 6.03.2018 224
+24
I somehow succeeded to update Omnisphere 2.6 Windows but are confused by the update files and their date which refer to 2016 and are older than the ones I have with version 2.6.2.

This is what I see on the initial screen of Omnisphere 2.6

- Omnisphere Software 2.6.3c
- Omnisphere Soundsources 2.6.0c
- Omnisphere Patches 2.6.0c
- Moog Tribute Patches 1.4e

Should Omnisphere Soundsources 2.6.0c and Patches 2.6.0c also have been updated and which of the provided files do I need.

Can someone shed some light on this?
Thanks in advance.
You only live once and that's forever.
  Resident 24.03.2020 40
+7
Finally...Success! Hope this process helps For Mac users:

Installed library, soundsource etc and software updates then copied component and vst files to desktop. Used keygen to patch both files then moved back and replaced. Standalone and vst worked but AU (Component) did not. I used the two codes mentioned by vaiman in terminal and the first one did not work neither did the second. I looked up the problem ("Resource fork, finder info or similar detritus not allowed) and had to install extra xcode tools. Once I did this I found out that when we "Show package contents" it adds something to the bundle so I used code xattr -cr /Library/Audio/Plug-ins/Components/Omnisphere.component then pressed enter. Type password and repeat for vst file. Then open DAW (Mine is Logic Pro X v10.4.4 (OS High Sierra 10.13.6) and boom worked for me.

Hope this helps,

Cheers
  Member 9.09.2019 12
0
Hey, thanks for the info, I tried that code in terminal, but it made no change in my case: Omnisphere does work in Logic BUT only in regular AU, NOT multi-output (either 16 or 25). Can anyone tell me if it does work in multi-output mode for you?

Maybe I did something wrong, but as I said in another comment, I patched, used terminal codes for codesign (both regular and deep) and now that last one, too. Here is my AU report from Plug-In Manager:

Omnisphere Audio Validation Result

Also, when loading Omnisphere, it shows:
Omnisphere Software 2.6.3c
Omnisphere Soundsources v2.6.1c
Omnisphere Patches v2.6.3c

Just so you know, it does work in Standalone mode and VST in Ableton Live.

If anyone can help I would really appreciate it !
  Resident 24.03.2020 40
+7
Not sure but on the validation report it says something about 32bit and I think Logic is now only 64bit. That wouldn't explain why it's working in regular AU. Mine does work in multi-mode in Logic so not sure I can help further, sorry.

I explained incorrectly above (Edited now) as I used that xattr code on the component and vst files in their folders i.e library/Audio/Plug-ins/Component and vst.

Try this one as I used lower case i incorrectly above:

xattr -cr /Library/Audio/Plug-Ins/Components/Omnisphere.component

Hope this helps
  Member 9.09.2019 12
0
Thanks for the reply, I tried that code too but didn't work. I ran the .pkg again, copied, successfully patched both VST and Component, replaced back to folders, used xattr codes, then codesign (deep) codes, and got the same result: Omnisphere AU works only in stereo output, not multi-output.

Can anyone tell me what would be the best way to downgrade back to 2.6.2? I do have the installers.
Or am I missing something for this to work completely? Thanks for the help so far

related posts

Spectrasonics Omnisphere v2.8.3d WiN [MORiA]Spectrasonics Omnisphere Software 2.8.0d Patches 2.8.0c Mac Win UpdatePro Sound Library 3D Sound Effects Pro Collection Vol.1-4 FLACSpectrasonics Omnisphere 2.6 Complete WIN\MACSpectrasonics Omnisphere v1.0 with ALL Updates (AIRISO)

Spread the Word