Old projects with Omnisphere screwed up

[tusio]

So I just discovered that none of my old projects will play Omnisphere track.

I get an error message complaining and asking to install v3. The major problem is that I can't figure out what patch was on that track. Unless there is some quick solution to that, this is a total disaster. I also noticed that there were a dozen of users having the same or similar issue.

I cannot go back and install v2 , because then none of my new projects will play.

Reported this to Spectrasonics, but so far no fix (as they ask million irrelevant questions,...)

Any ideas for fix ?

[Dirk Diggler]

I believe the problem is that you uninstalled v2.
All the old projects pointed to that install and those specific presets or multis.

The new install won't know anything about the old presets and the order of them.

That's my theory, I'd let the Spectro folks provide the complete answer.

Well I guess it's time to consider rendering out the old project VSTi's somehow, other wise you're starting from ground zero.

Does your DAW give warnings? Or perhaps replacements VSTi suggestions?

[tusio]

OK, so I am unsure what to do, perhaps somebody have gotten through the same problems, and can advise:
- should I go and reinstall v2
- should I uninstall v3 first and install v2
- should I uninstall v3 first and install v2 and then,...what about v3

Spectrasonic has created very much the same mess, similar to what happened recently to KONTAKT and KK. All my old projects stopped working.
I used to be a web developer programming in PHP/SQL/JS. I understand that sometimes new software simply cannot be compatible with the old version , but Spectrasonics assured us it is.
They also have not posted any warnings about old projects, and this makes me (first time) extremely pissed of about this company.

[tusio]

It is worse than I thought.
Ableton-LIVE12/Win10


- I created a custom patch.

- placed Omnisphere3 on the track

- grouped the track

- saved the track (Ableton) instrument preset (with Omnisphere3 inside)

-------------------------

When I open that instrument preset (rack) Omnisphere3 preset is empty.
What is going on here ?

[Dirk Diggler]

OK not sure what the problem with Ableton and Omni3, I'm sure it's related.

In any case I would re-install Omni2, and then try opening your old projects.
Unless you created your own instruments and presets, all should work.

Then you might have to look into the issues with 3, but I wouldn't install it, the installs should be in different folders I believe. It could be your Steam folders got deleted perhaps?
I saw some online mentions of Steam fixes for Omni3, I'm still on Omni2.

Then when you have v3 up and running you can replace the old v2 with the new v3 in the old projects, save them. Then you could consider uninstalling v2.

Good luck.

[rizetmusic]

Same here...
As far as I know Omnisphere 3 is supposed to replace Omnisphere 2 and fully backwards compatible.
The problem is somehow Omnisphere 2 plugin still exists and cause DAW open old projects with Omnisphere 2.
So In my case I located the Omnisphere 2 dll file and deleted it.
That forces Cubase automatically switch Omnisphere 2 instances with Omnisphere 3 and should be good to go.
I am using Cubase Pro though and not sure about yours.
Hope that helps!

[IvyBirds]

Same here...
As far as I know Omnisphere 3 is supposed to replace Omnisphere 2 and fully backwards compatible.
The problem is somehow Omnisphere 2 plugin still exists and cause DAW open old projects with Omnisphere 2.
So In my case I located the Omnisphere 2 dll file and deleted it.
That forces Cubase automatically switch Omnisphere 2 instances with Omnisphere 3 and should be good to go.
I am using Cubase Pro though and not sure about yours.
Hope that helps!

I saw this addressed on another forum a while back by someone with official word from Spectrasonics but can't find it or remember where

Essentially when you install Omnisphere 3 and already had Omnisphere 2 installed on the same system, the installer is supposed to replace everything and delete everything from Omnisphere 2 off your system, that way when you run older projects made in Omnisphere 2 it will automatically launch and run that patch in Omnisphere 3. The Legacy Library in Omnisphere 3 has all of the Atmosphere, and Omnisphere patches from 1&2, included with the same exact filters, effects, etc so they sound exactly the same and is 100% backwards compatible.

This is also why you don't want to touch "The STEAM" folder when you go to install 3 as it still needs all the resources inside of it

However sometimes that process of deleting the old Omnisphere 2 files isn't 100% and it leaves a file behind, and that file is now pointing at something that is there but won't load and that is the issue

Support will walk you through where the files are and they are supposedly working on ways to improve it

Of course if you are doing a fresh install on a computer that never had Omnisphere 2 on it, it's not going to be an issue

[tusio]

Support will not walk me anywhere, because they are not responding.
I am completely stuck on more than a dozen of projects. THIS IS RIDICULOUS!

I have sent an Email about other issues two weeks ago (i.e. not being able to switch and load patches from certain 3rd party LIBs). They asked me million questions and after I replied about a week ago, I have zero response. I then sent them 2 Emails about this particular case 4 days ago and so far no response of any kind.

Today I tried to call the number posted on their main page and there is only an answering system (no human), despite I called within their advertised work hours. So far I called twice, left a message and have not heard from them.

I use this program for about 15 years and my opinion about SPECTRASONICS so far was very good. Never had any issues with the support, but this time it is really, really bad.

When upgrading the V3, there was no question whether to leave or uninstall version2, which is very bad idea. Also if the STEAM Lib is fully backwards compatible, then how can I read and figure out what patch was loaded on the track (beofre I get the error message) (?). Not unsure about other DAW's, but I see no way to do this in Ableton-LIVE12.

If I knew what patch was user I could easily replace instance of Omni v2 with v3, select correct patch and be good to go.
If anybody knows how to find it I wild be happy to hear that,...

[tusio]

I just tried to download Omnisphere2. Installed the downloader. Got to about 90% and had to PAUSE for few min. as I was transferring some files over LAN with high priority. When I clicked RESUME the download had reset and started again from ZERO, despite 90% was already on my HD.
I called another Spectrasonics number , which I've found on their page. No human, just answering machine. NO RESPONSE.

Now, I finally downloaded their installer for Omnisphere2. I started and noticed there is no option to disable installation of RTAS and AAX, but I decided to install anyway. In a few seconds I noticed that installer froze.
Restarted PC, and tried again, ...no success. windows the task manager shows 7% on CPU and no HD activity. The installation DEAD, developer not responding. What else could be worse ? this is a F.CKEN DISASTER.

[tusio]

UPDATE:
Finally I got in touch with SPECTRASONICS REP.
Of course they lied to me about trying to call me (and no answer), sending me Emails and no response) etc. Typical lies!

FINALLY:
We did remote session. Unfortunately he seemed to be not really well-educated on the product. I wasted 4-5 hours following his advice to uninstall OMNISPHERE (both v2 and v3), downloading new files (despite none of my HD files were corrupted and removing any kind of SPECRASONICS references.
After all this time I got to SQUARE ONE. I get same errors. All OMNISPHERE-2 tracks do not make sound or I get a message to replace the plugin with v3. They guy assured me the STEAM folder is compatible with v2 and v3 but obviously it is not.
At certain point after a first phase, and installing OMNISPHERE-2 only, I was able to open the old projects and the patches loaded as expected (at least on one project I tried). The moment I installed version 3 everything got messed up again.

I am writing this so if you have this same problem, do not make this mistake. Do not install version 3. In my case I do not have any choices and this makes my just furious. If I keep v2 only all me new projects from last 6 weeks will now work, and if I install version 3 all my old projects will not work.
I really do not understand how such a well known developers could release such a CRAP well - somehow they did.
BASICALLY AFTER 10 DAYS PROBLEM STILL UNRESOLVED AND I AM STUCK with few hundred dollars invested into SPECTRASONICS to destroy my work!

[IvyBirds]

UPDATE:
Finally I got in touch with SPECTRASONICS REP.
Of course they lied to me about trying to call me (and no answer), sending me Emails and no response) etc. Typical lies!

FINALLY:
We did remote session. Unfortunately he seemed to be not really well-educated on the product. I wasted 4-5 hours following his advice to uninstall OMNISPHERE (both v2 and v3), downloading new files (despite none of my HD files were corrupted and removing any kind of SPECRASONICS references.
After all this time I got to SQUARE ONE. I get same errors. All OMNISPHERE-2 tracks do not make sound or I get a message to replace the plugin with v3. They guy assured me the STEAM folder is compatible with v2 and v3 but obviously it is not.
At certain point after a first phase, and installing OMNISPHERE-2 only, I was able to open the old projects and the patches loaded as expected (at least on one project I tried). The moment I installed version 3 everything got messed up again.

I am writing this so if you have this same problem, do not make this mistake. Do not install version 3. In my case I do not have any choices and this makes my just furious. If I keep v2 only all me new projects from last 6 weeks will now work, and if I install version 3 all my old projects will not work.
I really do not understand how such a well known developers could release such a CRAP well - somehow they did.
BASICALLY AFTER 10 DAYS PROBLEM STILL UNRESOLVED AND I AM STUCK with few hundred dollars invested into SPECTRASONICS to destroy my work!

I am sorry you are having this issue, but let's not forget that this issue is not being experienced by anyone else

So let's also not forget that the issue is probably something specific to your machine and setup

Because I experienced nothing like you suggested and talk about Omnisphere on many different groups all over the net and no one has even suggested anything like what you have

So no Spectrasonics didn't release a crap product, they released a phenomenal product enjoyed by thousands of people none of which have your issue, but like all software made by all manufacturers might run into something user or machine specific

[Ah_Dziz]

I'd use v2 and open all the old projects, save all the presets from v2 and bounce audio, then uninstall and move to v3. I've alhad a few major hiccups while updating/ upgrading software, and sometimes you have to do a bunch of irritating extra steps to properly back up your old stuff.

[Dirk Diggler]

I think it all stems from the original un-install of v2.
Did they have you do any registry editing?
Or perhaps checking for registry keys left over?
You've now got 2 multi installs that could easily leave all kinds of registry keys behind.
It might be worth trying something like Revo uninstaller, it will get rid of any and all related registry entries.

And one last thing, remember NAMM is going on, so all the knowledgeable folks will be at the show not doing customer service.

If this were a widespread issue we'd be seeing tons of complaints by now.

[tusio]

I am IT guy with 40yrs experience and know very well how registry operate.
Omnisphere (as opposed to other software) does not do anything with the registry during installation. If one wants to uninstall it, he would not even find this program in the Windows software list. You just need simply go, and delete specific folders and files, that's all.


They claim 100% backwards compatibility and that is a LIE!

Another problem is that Omnisphere v2 and v3 use the same .DLL file places in VST folder, which prevents user from keeping both version. That is simply stupid idea and should have been avoided.

Installation program however is completely unaware of old Omnisphere, and the STEAM folder. It does not ask if you want to keep old version or not. Then one part of this problem is that whoever created the installer is an absolute ignorant, because this installer is only OK, for a brand-new installation.
Most people who install version 3 for the first time will have no problems of any kind, but the rest will.
I am only talking from the standpoint of Ableton/Fender Studio user. Not sure about other DAW's and would not make any statements about these.
NAMM is not an excuse to not provide the support. It is also not an excuse for the support person to be under educated about the product.

At the present moment I have found some workaround the problem but it is very time consuming. Here is what I do:
- open existing (old) project
- select Omnisphere track and try to open the plugin
- Omnisphere 2 opens up with the error (asking to install v3)
- close it and read the patch name
- then use LIVE12 track information field and place the Omni patch name in there
- after that I delete Omnisphere-2 and replace with Omnisphere-3
- locate and load the noted in "Info Field" patch

Not sure how this would work with custom patches and multi's, so this is something to test,...

Now,... going through several dozens of projects and multiple Omni- tracks in each of them still seems to be a nightmare.

After doing this same installation 3 times and watching closely every step I can clearly state that upgrade from v2 to v3 process is messed up (at least for Ableton users who have old projects with Omnisphere2 tracks).





Weather it is or not widespread it irrelevant. Just the fact that somebody wasting money and then time on things which could have been easily avoided it enough reason to be super frustrated.

[IvyBirds]

I am IT guy with 40yrs experience and know very well how registry operate.
Omnisphere (as opposed to other software) does not do anything with the registry during installation. If one wants to uninstall it, he would not even find this program in the Windows software list. You just need simply go, and delete specific folders and files, that's all.


They claim 100% backwards compatibility and that is a LIE!

Another problem is that Omnisphere v2 and v3 use the same .DLL file places in VST folder, which prevents user from keeping both version. That is simply stupid idea and should have been avoided.

Installation program however is completely unaware of old Omnisphere, and the STEAM folder. It does not ask if you want to keep old version or not. Then one part of this problem is that whoever created the installer is an absolute ignorant, because this installer is only OK, for a brand-new installation.
Most people who install version 3 for the first time will have no problems of any kind, but the rest will.

Again you are saying things that are simply not true and saying that people who install version 3 will have issues. Sorry that is a lie

I have personally installed Omnisphere on my 4 music PCS two laptops and two desktops all of which had version 2 and none of them had any issues, and everything is 100% backwards compatible

But you must recent rant has most definitely shown us all what is wrong. You are an IT guy who poked around the install rather than just letting it run as intended, and you screwed it up, and in the process you caused your own issues

because it absolutely is aware of what was previously installed and it absolutely does show up in the registry

Nothing you have said in this thread makes any sense in the real world, other than you messed up the install and are installing it on a system you have made non typical and as I said earlier it's user error on your part and issues specific to your machine