Omnisphere 3

[DrGonzo]

I bought the upgrade. Arriving tomorrow and I am very excited for it. Looks awesome.

But I have some (very selfish) disappointment that my three (personal) hopes aren’t there: hardware profile for the very knobby 3rd Wave, hardware profile for multi-page roto-control, and the ability to set loop points for user samples.

Check with Spectrasonics on that. I asked them for support for the MicroKorg 2 and they said it's definitely coming.

[inaheartbeat]

Now that I've had a few solid hours to play with this, my biggest complaints are the lack of drag&drop MSEGs, and no macro knobs. These are basic quality of life features in most modern synths.

Still a great synth, it'll get lots of use, but having those two additions would have really set it over the top.

Not sure what you mean by "drag and drop" msegs. You can create incredibly complicated, loopable and syncable msegs and save them as presets and you can copy and paste envelopes to other envelopes in Omnisphere. You can even use midi clips to define envelopes. Envelopes can also be polyphonic for MPE users.

As far as macro knobs, that is partially true, the new patch main screens contain several knobs that actually act like intelligent macro knobs which are defined per patch depending on what the most "interesting" things are that you likely would want to tweak. I get that it is not like Serum 2 or Pigments but still useful.

I personally like to run Omnisphere inside of Unify. The main reason is Unify is mulicore aware and allows you to run a lot of Omnisphere patch instances together way more efficiently. Also, Unify has up to 32 macros knobs that can be defined and the newest version of Unify which will be out in a couple of days has modulations internally for the macro knobs themselves if desired.

[jobinho]

Now that I've had a few solid hours to play with this, my biggest complaints are the lack of drag&drop MSEGs, and no macro knobs. These are basic quality of life features in most modern synths.

Still a great synth, it'll get lots of use, but having those two additions would have really set it over the top.

Not sure what you mean by "drag and drop" msegs. You can create incredibly complicated, loopable and syncable msegs and save them as presets and you can copy and paste envelopes to other envelopes in Omnisphere. You can even use midi clips to define envelopes. Envelopes can also be polyphonic for MPE users.

As far as macro knobs, that is partially true, the new patch main screens contain several knobs that actually act like intelligent macro knobs which are defined per patch depending on what the most "interesting" things are that you likely would want to tweak. I get that it is not like Serum 2 or Pigments but still useful.

I personally like to run Omnisphere inside of Unify. The main reason is Unify is mulicore aware and allows you to run a lot of Omnisphere patch instances together way more efficiently. Also, Unify has up to 32 macros knobs that can be defined and the newest version of Unify which will be out in a couple of days has modulations internally for the macro knobs themselves if desired.

Lots of modern synth UI's allow you to see a selection of modulators, LFOs/Envelopes as tabs on the interface, so it allows for super quick modulation and auditioning of different routings via a 'drag and drop'. This is something Omnisphere is still lacking in and makes the process of creating patches slower and less enjoyable than it could be, and perhaps should be in 2025.

[HydrogenHuman]

It looks like based on the library list here, that all the new categories are completely new and different sounds compared to Omnisphere 2. Which is completely insane, and impressive!

You can see it has the new library categories, but then has the legacy libraries.

https://www.spectrasonics.net/products/ ... ibrary.php

[db3]

Yes, they are claiming 26,000 new patches! I can only assume this includes remastered and reclassified presets as well as truly new ones.

[noiseboyuk]

Yes, they are claiming 26,000 new patches! I can only assume this includes remastered and reclassified presets as well as truly new ones.

This has been covered a lot but it's a long thread so it's okay! That 26,000 figure includes a lot of double counting - the same patch can exist in several directories and on their website they simply added it all up as unique patches.

Here's how it breaks down:

Total number of patches including duplicates and remastered legacy = 26.421
Total number of unique patches including remastered legacy = 13,915
Total number of remastered legacy = 9,242
Total number of brand new unique patches = 4,673

[HydrogenHuman]

Yes, they are claiming 26,000 new patches! I can only assume this includes remastered and reclassified presets as well as truly new ones.

This has been covered a lot but it's a long thread so it's okay! That 26,000 figure includes a lot of double counting - the same patch can exist in several directories and on their website they simply added it all up as unique patches.

Here's how it breaks down:

Total number of patches including duplicates and remastered legacy = 26.421
Total number of unique patches including remastered legacy = 13,915
Total number of remastered legacy = 9,242
Total number of brand new unique patches = 4,673

Ah, thank you! I figured I had missed it earlier in the thread.

Those are still some insane numbers. And the fact that all the legacy patches now have the useful macro controls makes them far more useful to just load up, play, and tweak.

[noiseboyuk]

Those are still some insane numbers. And the fact that all the legacy patches now have the useful macro controls makes them far more useful to just load up, play, and tweak.

Actually it's better than that. Those global controls are truly global - they work on everything. Trilian, Keyscape, Moog, the Sonic Extensions - there is a new toggle between the bespoke front page and the custom controls - user patches, all third party.

It's great with the new controller integration. If you are in Omni, your hardware controls should always work, no matter where you are in the plugin.

Tip - save a default Multi with your Hardwar Integration enabled, then the hardware profile will always load every time.

[jbraner]

Is it normal, that I need to choose libraries and categories again and again after each restart? Why not just "All" is set for both?

It seems to be - unless somebody knows better...

There is a setting to optionally recall the previous state, but that's all. There's no way to set a permanent default.

Ahh that's good enough (sorry - there are already plenty of similar replies)

CUSTOM VIEWS
This is, I think, the best we can hope for in this brave new world. Group together any directories / libraries you like - have, say, 8 sets.

That would be perfect!

[noiseboyuk]

CUSTOM VIEWS
This is, I think, the best we can hope for in this brave new world. Group together any directories / libraries you like - have, say, 8 sets.

That would be perfect!

I hope it's okay to post this here, but I've worked on the idea a little more and started a thread on it at VI-C - https://vi-control.net/community/thread ... er.167319/

[dune_rave]

Ok, was not able to wait so upgraded.
i have a s61 mk2 keyboard from NI.
Using this in HW integration, i'm not too satisfied. Will try again that feature later.
For example filter res was mapped, but cutoff not....

[aMUSEd]

Ok, was not able to wait so upgraded.
i have a s61 mk2 keyboard from NI.
Using this in HW integration, i'm not too satisfied. Will try again that feature later.
For example filter res was mapped, but cutoff not....

Yeah I tried it but it’s very basic and you can’t browse so will stick with the Komplete Kontrol version - I know Freelance will be updating their NKS library asap and it already seems to migrate fine - except it needs a new ‘Main’ page in the template

[soundman007]

Any idea what the upgrade price in Euros is going to be? Purchasing it new costs $499 / €399, so I hope $199 is going to turn into €159.

Agree 100%. Only in case of that honest price setting will I consider upgrading.

BUMP this inquiry.

Why is there this 499/399 difference between the dollar price and the Euro price for the full boxed version, and no difference in price for the upgrades? And if I buy the upgrade in Europe with PayPal will the dollar price be adapted to about 160 Euro, following the current exchange rate?

[IvyBirds]

Ok, was not able to wait so upgraded.
i have a s61 mk2 keyboard from NI.
Using this in HW integration, i'm not too satisfied. Will try again that feature later.
For example filter res was mapped, but cutoff not....

You have to put your s61 mk2 into MIDI Mode and you will find the following mappings

Knob 1 (CC#14) – Global Controls Cutoff
Knob 2 (CC#15) – Global Controls Resonance
Knob 3 (CC#16) – Global Controls Filter Envelope Amount
Knob 4 (CC#17) – Global Controls Vibrato Depth
Knob 5 (CC#18) – Global Controls Ambience Amount
Knob 6 (CC#19) – Global Controls Ambience Length
Knob 7 (CC#20) – Global Controls Unison
Knob 8 (CC#21) – Global Controls Glide

Cut off is the first knob and the factory default on your control issues CC#14 for that

Since your controller only has 8 knobs it can only have 8 things in the hardware profile for the Global Controls in Omnisphere

[jbraner]

And yes, I would want all my own sounds to be within the same searchable pool.

This.
It doesn't matter if the user patches live in the same folder as the factory ones - but some of us would like to "see them" together.
This could also pertain to the mutations.

I agree, if your "edited" patch is completely different than the original - then it doesn't matter. But if you make a few different, similar *versions* called:
patchname (the factory one)
patchname-2
patchname-3
Then you'd like to see them all together. It doesn't matter where they live - but the browser is a query of certain presets.

The only other way around this (which I've done in other plugins) is to save the (unedited) original in the user folder - before you make your "variations".

EDIT - I still think that "whatever category/folder" + user is something that might make everybody happy

This is a great case for the "Attributes" tag

https://support.spectrasonics.net/manua ... ags-page01

And the assignments tag
https://support.spectrasonics.net/manua ... ags-page01

You would create an attribute called "User Tweaked Presets" or whatever

Then under that select and assignment called "Patchname"

Like you said it doesn't matter where they are stored in your example

So under the "patchname" attribute you can tag as many variations of that factory preset as you want and of course call them whatever you want

The upside to this is you don't clog up the factory library with tons of variations of the same patch which can add up over time and you are not limited to using a common naming scheme for the patch itself even if it's that bass sound. Why? Because maybe you then want to tweak that bass sound into something else and that bass sound shouldn't be in the Ambient Dreams factory library

So instead of having to resort to
patchname (the factory one)
patchname-2
patchname-3
All the way to
patchname-754

You can call them whatever you want with more useful names and even tag your deeper derivates and mutations

So if you turn that ambient pad into a bass sound you can search for that ambient pad and all it's derivatives no matter what they are or where they are stored

The alternative is every increasing lists of patch names in your factory folders that just keep on getting larger and larger by the hundreds and then the thousands

OK - everything's different after a good nights sleep.
This is a pretty good solution, but you still have to view "all directories".

Having said that, it's still handy to have this new Attributes tag. The last nagging part is - how do I get the full browser to pull up this view (using this attribute tag) by default.

It insists on coming up with the default filters:


But I would like it to come up like this:

(change third column to "TYPE" and use my attribute for the 4th column)

does anyone know how to make this the default filters/view?