Omnisphere 2. 1 Keygen Mac
Otniel Doetzel
Just installed Logic X and tried to open up my go-to synth VST, omnisphere, only to find out that logic x will not recognize omnisphere with the rest of the audio units. All my native instruments plugins work fine and were validated upon install of logic x but it won't even detect omnisphere. It's worth noting I did not delete logic 9 from the Mac after completed install of Logic X. Could that be the issue? Any help would be greatly appreciated! Thanks!
I also cannot locate Omnisphere in Logic Pro X. I suspect I must have the 32 bit version. Is the 64 bit version a free download/upgrade? I know Spectrasonics has since released Omnisphere 2, so I'm really late to the party.
Same issues here......I called Spectrasonics to check on compatibility of current version of Omnisphere with Logic Pro X and they said there should be no problem, as it is audio units based. Omnisphere shows up in the list of audio units when I scan for it, but nowhere can I access it in Logic Pro X. I also kept Logic Pro 9 on my Mac Pro, and it loads Omnisphere just fine. Guess I will call Spectrasonics back again on Monday, and Apple as well. You have to wonder how much testing Apple does for third party products before releasing a new version. Being that I paid two and a half times more money for Omnisphere than Logic Pro X costs, I'm not a happy camper. Wish I could be optimistic for a quick fix of this, but considering there are still major unresolved issues in Mountain Lion and Photoshop CS6 after a whole year, it doesn't bode well.
Check you're running the latest version. AFAIK Omnisphere has been 64bit for as long as I have owned it, but the External Memory Streaming feature in it suggests it once had to endure a plugin memory limit, leading me to think earlier versions may have been 32bit.
Well now the interesting part is that omnisphere is working fine with Logic X on my iMac. I can't even seem to find my omnisphere library in the Finder on my MacBook. The only place it seems to exist and work on my MacBook is in Logic 9 so I'm trying to figure out what went wrong.
Yes, I'm running the latest, 64bit version. I think the issue may be that with the rearrangment of things I was looking in the wrong place. Going to check it out now. Thanks to all for your suggestions. Interface changes do tend to throw me for a loop sometime.
Thank you. I suspect I was confused and not looking in the right place. I''ll check it out now. I appreciate your help. Interface changes often challenge me, as I grow accustomed to things being in one place and they get moved to another. Hopefully this is the case.
Essentially, I had installed Omnishpere on my macbook air with my old discs without ever going to update it, writing the updates off based on the fact that they came out much before I purchased my Macbook Air. In doing that, I was running an out of date version of Omnishpere.
When I use omnishere instrument in my arrangement it randomly, without any warnings shuts my computer down. It happens only when I use omnisphere. But when I freeze this truck and mute omnisphere truck, then everything works fine. It comes completely unexpected, so sometimes I lose some material.
There was an issue a while back, where Spectrasonics instruments were crashing Cakewalk after they changed the number of outputs. The solution to that one was to remove the instance of Omnisphere (or Keyscape or Trillian) and insert a new one.
If that is the case, there is an advanced Windows setting to prevent automatic restarts after a BSOD, that should leave the error screen in view in case you happen to miss it. If you change that setting, you would need to manually restart.
When a computer unexpectedly shuts down and reboots, it's most often a failing power supply. I have also seen it happen when there was a shorted decoupling capacitor on the motherboard that overheated the power supply. Either way, it's gonna take a trip to your local computer fixit guy.
It should not be possible for a software instrument to power down and reboot the computer. At worst, it will only crash the DAW and leave a crash dump for analysis. It could be coincidence that there appears to be a correlation to Omnisphere.
You might want to take a look in %appdata%\cakewalk\cakewalk core\minidumps and see a dump file is there with the date and time of your shutdown. Although unlikely, it's possible there's a clue in there. It's also worth scrolling through the Windows Event Viewer to see if there are any entries in the System Log that correspond to the date and time of your shutdown.
I'm only going by what Yury stated, that the shutdown only happens when using Omnisphere. If that's true, was thinking that maybe Omnisphere is stressing something in his system that is marginal and that it tips things over the edge.
Omnisphere is memory intensive, so it's possible it could be a bad memory. This has happened to me in the past and is very difficult to identify. If you're lucky, you might see some discrepancies in the BIOS when it's reporting the speed of your memory modules - i.e. if one looks different from the other, that's a good indication that one has gone bad.
Alternatively, Windows 10 has a built in memory checker: -check-your-pc-memory-problems-windows-10
That was my thought as well. And as Mark suggested, memory could be a thing. An area of memory that doesn't get touched until you run something that eats up a lot of it. That could be RAM, or maybe there's paging going on to a disk that has bad sectors. Even with 32G of RAM, Windows will allocate page file in case it needs it, not necessarily as it needs it.
It could also be other components, any of which can be stress tested. I like Kombustor for graphics. There are others for CPU, which can flush out problems with cooling (dust on the cooler fins, dried out paste, etc.).
DAW work tends to be very heavy on AVX operations, which can really cook the CPU. Omnisphere, I would hope, is probably making a lot of use of AVX, so it could be heating up the processor to the point of protective shutdown.
My favorite tool for monitoring heat, fan speed, etc. is HWINFO64. Start that, look at the CPU and graphics temps and processor speed, then start Cakewalk up with Omnishpere and keep an eye on it. If the CPU temp climbs fast, you might be in for some blowing dust off your cooler and/or putting new paste between the cooler and the CPU.
"Intel's latest CPUs provide a series of updated AVX (opens in new tab) instructions, which are designed to accelerate audio, video, and image processing functions. However, these greatly increase the power usage and heat produced by a CPU.
To prevent AVX power spikes from limiting general overclocking potential, Intel introduced the AVX offset in the BIOS. This feature detects AVX workloads and adjusts the multiplier downward by a specified value to maintain system stability, so a system overclocked to 5GHz with an AVX offset of 2 would adjust to 4.8 GHz automatically during AVX enabled workloads and switch back again when completed."
I still have this problem. The only new is that I don't think its Omnisphere because lately I had same thing happened with other soft running. Even not musical soft. So I think its something with hardware in my computer. I built this computer myself and its been working fine for a long time. May be some of the hardware comes to the end of its life, or some drivers don't like other drivers at certain situations. Random problems is a very difficult problems to fix or find the reason why. So I have to live with this problem until something breaks for good.
7fc3f7cf58