Omnisphere 1.2.0n

[Amyris]

Please read this:
"Omnisphere requires a VST 2.4 host. Forte seems to be relying on a part of the VST protocol (wantEvents) that was deprecated in version 2.4. If you know how to contact the developer of Forte, let them know that's the problem."

Is it possible that Forte does not fully support VST 2.4?

[Dirk Offringa]

Forte is VST 2.4. I would be surprised if it was only partially 2.4 compliant.

Dirk

[Greedo]

Woow, i allso have the same problem with Spectrasonics Stylus RMX 1.9.0e

Rolf

[MartiBlartFast]

I have Omni and Stylus, I haven't upgraded to latest versions so no problems for me yet.

Mike, any chance you could give us your thoughts on this?

[JeffB]

Still nothing from support!

[Dirk Offringa]

Forte is a VST2.4 host. It does not rely (solely) on the plugin's wantEvents() call, it implements VST2.4 sendVSTMidiEvents().
Maybe there's another problem, but it's not the one the good folks from NorthernSounds pointed out. Is Forte the only host that shows this behaviour?

Dirk

[Volker Grosch]

Hi Dirk,

I did some testing: Cubase, Live Professor and Ableton work without a problem. Vstack (beside Forte) is the only host at the moment that doesn`t work here, but I`m pretty sure it doesn`t support VST2.4 as it is years since it was updated last time.

regards, Volker

[Amyris]

Same here. I've only got Forte and Cubase 4 and 5 to do some testing (do not own any other VSTi host). The result is - as Volker has said already: Cubase and Omnisphere 1.2.0n are working well on all plattforms (different PCs with Windows XP and Windows 7, different audio interfaces, etc.) but the plugin is silent in Forte (on all plattforms, too). And the reason why must have something to do with one or more changes that Spectrasonics did in this new patch because any older version of the plugin runs fine in Forte.

[Dirk Offringa]

I insist that it's highly unlikely that this is a VST 2.4 incompatibility issue. Would Spectrasonics code this very new synth for VST2.3 (dating from 2003) in 2009 (1.1.4 worked), and then all of a sudden, in 2010, for a 1.2.0 release, port the code to VST2.4 (dating from 2006) while at the same time removing all backwards compatibility, which needs extra coding, without warning the end user, ? I don't think so.

There is another problem going on here. Sorry, I can't test it, they have no demo available for download.
I mentioned this thread in the beta forum, in case Mike missed it. Let's wait and see what he thinks about it. The fact is: "Spectrasonic's Omnisphere broke when it upgraded from 1.1.4 to 1.2.0", the rest is speculation!

Dirk

[JeffB]

Omnisphere 1.20n works in Sonar, Cubase, Nuendo, Cantabile, SaviHost and VST Host but not in Forte so there obviously is something broke in Forte!

[Dirk Offringa]

If it pleases you to think so, please do. This can be anything, including issues with copy protection.
I would like however to repeat, if you don't mind, that this issue was introduced by a Omnisphere update, not by a forte update, and that no other plugin exhibits the same problem in forte as far as I know of, so it seems reasonable to wait for Mike to be able to check this out. Please be patient: the fact that Spectrasonics decided to not offer a demo version for download reduces greatly the chance that this issue will be adressed promptly...

Dirk

[JeffB]

If it pleases me to think so?

Get off your high horse will you!

Fact is fact!!

[JeffB]

Just heard back from Mike that a copy of Omnisphere is on it's way to him so hopefully all will be revealed soon.

Spectrasonics seem confident that all is well at their end.

I've been using the Cantabile demo since this started but will be glad to get back to Forte!

[Amyris]

Easy boys, calm down please! No one really thinks that this is all Forte's "fault" since - as Dirk said correctly - the bug came by an Omnisphere update, not by a Forte update. But there has to be something in the "teamplay" between the plugin and Forte, that Forte has to handle slightly different in comparison to other hosts such as Cubase, simply because there are no problems in these hosts. So I'm really looking forward what's the problem about.
And do not forget: Omnisphere is not completly useless within Forte! Simply don't install the update and everything ist just fine.

[mgarrett]

Hi all,

Yes, indeed. I'm supposed to be getting this plugin and I'll check it out.

I normally do not "spring into action" the moment someone says a plugin doesn't work because...let's face it...there's alot of plugins out there. The plugin support policy is on this forum and it basically says Forte is not attempting to be compatible with all plugins.

However, there's alot of interest in Omnisphere here, and apparently its replacing the older popular Atmosphere, so I will do my best to get this one working.

Forte is at a point now where its VST support doesn't change very often. Its mature code, so I'm more confident these days in not assuming its a forte bug when some plugin doesn't work. I've seen alot of weird stuff. Atmosphere itself had a big fat bug around multi-threading. If you use more than one instance, you had to tell Forte to not use more than one processor. Spectrasonics makes great sounding plugins, but in my experience, at least some of them couldn't pass the Forte stress test.

Mike