Omnisphere is not really set up for NKS but I can still use my KK keyboard for controlling certain midi automation. Is there a way to set up a specific Omnisphere template in KK?
If so, how would I do that?
See our friends from Freelance Soundlabs. They have a fantastic (paid) NKS template that I use all the time.
There is also a thread somewhere on the boards here with updates etc.
VP
See here, fully up to date and covers all presets in Omnisphere factory and optionally the latest 2.5/2.6 updates with the "Hardware Library", all tagges and with sound previews.
I've just ordered Omnisphere 3. I presume you have plans to release an NKS version for this in the future?
See here
I have been using Omnisphere 3 for a few days - the Freelance patches for Omnisphere 2 do load so migration is working but I have had a few freezes - looks like the 'Main' page needs updating and probably some other parts
Honestly, I think the issue is Omnisphere more than anything at the moment, it runs terrible for me for some odd reason. Selecting a category takes 40+ seconds to work, switching banks often causes long freezes and a few times I have had Omnisphere just become unresponsive completely, and this is all using the standalone app since I have to test and report to Spectrasonics on the issues I am having. Was never an issue with Omnisphere 2 on 2 different machines and the one I have issues is running SSD formatted to NTFS already as per their recommendations.
I suspect they will have a few bugs to fix, looks like this was kind of rushed to some degree since many new patches have little to no tagging in them at all.
No updates will be happening any time soon to the old patches, at least not until all the new stuff is figured out and the changes to the way they now do the browser and the loss of the "Type" tag now means likely less tagging overall that can be pulled. The issue is I can't simply "update" the old patches with new mappings because Omnisphere requires parameters first be enabled for host automation before NKS files are saved which means every file needs to be loaded, have the parameters enabled and updated then resaved again. I already planned for this and have an idea on how to do that autonomously using a saved mapping via Omnisphere but it will likely need a week at least for a computer to run through every patch (not including 3rd party libraries) so it will really come down to how many people update to the Omnisphere 3 library version.
Sadly I am not as excited about Omnisphere 3 as I was when I first updated to Omnisphere 2. Certainly feels a little bloated now and far from optimal in performance. Currently for me it is completely unusable in how long it takes to click around the browser. I will start designing new scripts to do the patches but likely won't be able to make a start until I can resolve this 40+ second freezing issue which I hope is either a simple fix or an update.
omnisphere 3 is certainly turning heads in the audio world. Many including myself are now seriously considering getting into omnisphere now that so many useful features (including MPE, zones, better preset organization etc) have been added.
Coupled with an osmose and Kontrol S Mk3, it becomes an even better value proposition. It now also looks like NI might be closer to fixing the subbanks, which was one of the reasons I hadn’t even considered going near Omnisphere, so I’m feeling optimistic. Glad to see you are planning to work on Omnisphere 3 and found a way to automate some of that work otherwise you d be years indeed updating thousands of presets lol
Thanks so much for all the great work.
Yeah honestly the issue of sub banks has had me wanting to throw in the towel since I can make all the content nice and organised as it is in Omnisphere and it will work for Maschine and KK V2 owners just fine but if the majority of users on KK V3 cannot use it, I will just get hammered more than I do already about the inability to select banks to browse.
Progress so far is good, I have already generated a full database of all the new category tags that Omnisphere 3 uses and have started masking all that data to NKS compatible tagging. While it is a huge task, it was also a massive task to do IK Multimedia, Roland and all the UVI too so I am confident I will have this completed reasonably quickly, surely by the end of the year and I hope to also update the old library with new features too if my idea to update the files actually works. Fingers crossed!
If you have Kontrol Mk3 + FW v2.0 and your DAW has good support for customising the mapping of plugins (i.e. Bitwig, Live, or Cubase) then you don't really need NKS.
Actually in Bitwig at least it’s not as straightforward as it is with other plugins because of the dynamic way automation is assigned in Omnisphere. By default it has no pre-defined host automation targets, you have to set these up in Omnisphere first, then save them as a Omnisphere mapping template, then use that to create the Bitwig remote controls. Unfortunately you have to reload the Omnisphere template each time you load Omnisphere even if you create a remote control mapping for it. It does not save with the remote control. I have also tried saving this with a Bitwig preset and that loads the device mapping but still doesn't reload the Omnisphere template - I guess the only way you are meant to do that is by saving it with the project itself as a template
So NKS does have the edge here because a NKS preset saves the Omnisphere template mapping too - I guess because each .nksf file is kindof like a mini project file. Of course one could simply create a single NKS template for control purposes and forget about saving every single preset - I often do that myself
btw the Omnisphere template I made for Bitwig and Omnisphere 2 (VST2) does still work - it contains the Bitwig remote controls, a Bitwig preset and the Omnisphere controls template which is what must be reloaded into Omnisphere each time (unless saved a project template) - it just needs updating for the Omnisphere 3 extra params and VST3
https://www.dropbox.com/scl/fi/sfs4blv8ygzxdkz5udzx3/Omnisphere-Device-Template.zip?rlkey=46ys5i3ma6rfpvxmzq7jv083r&st=vocqobfb&dl=0
However, doesn't support preset browsing, or tagged filtering, previews, auto mapped parameters etc and as Kimeia mentioned, you have to enable host automation for a synth like Omnisphere first after launch which is impossible for blind users. there is the option for "hardware integration" but this offered MIDI only mapping of the main controls and requires a template to first be created and labelled.
All very well to suggest these options but not always clear cut so Omnisphere indeed benefits greatly from NKS as most synths do.
