Omnisphere 3 (vst3) multi output problem

[F.J. Lamela]

Hello, I've been using Omnisphere 2 for years and never had a problem.
After updating to version 3, I'm encountering an issue with Omnisphere's multi-outputs.
To explain, the synth has 8 independent outputs (A, B, C, D, E, F, G, H), but unfortunately, only output A is working. The rest show a signal in the plugin, but the sound doesn't reach Sonar.
I've tested it in another DAW, and it works perfectly.
Can anyone confirm this or has anyone experienced a similar problem?

Thanks.

[Igor]

1 hour ago, F.J. Lamela said:

The rest show a signal in the plugin, but the sound doesn't reach Sonar.

Check which inputs (tracks) are receiving signals from outputs B, C, D, etc.? Perhaps you simply haven't configured the routing within Sonar for multi-channel operation? I always set up the routing manually when using instruments with multi-outputs (mainly Kontakt), and everything works fine. Each output in Omnisphere must have an input to a track; otherwise, you'll only be listening to output A.

I don't have Omnisphere 3 yet, but everything is set up the same in version 2 as in version 3. I've already watched many Youtube reviews and haven't seen any significant differences in functionality.

[F.J. Lamela]

1 hour ago, Igor said:

Check which inputs (tracks) are receiving signals from outputs B, C, D, etc.?

Thanks for your recommendation, they've been thoroughly checked.
Also, since it's "backward compatible" with projects that previously used version 2, the projects don't work correctly when loaded; as I mentioned, the multiple outputs don't work.

[Andres Medina]

Hi,

I do have Omnisphere 3.

At the moment I have no issues with the Omnisphere multi outputs feeding the corresponding audio tracks in Sonar (latest version 2025.09 Build 038).

You said you already double checked the I/O configurations in Omnisphere and Sonar right?

I did have a problem accessing the Envelopes sections in the patches view. O3 crashed. I contacted Spectrasonics customer support and they found a bug, that was fully corrected in a newer version (still not available for the general public).

 

 

 

Edited 5 hours ago by Andres Medina