An instrument such as Omnisphere is mostly inaccessible for a blind user, where there are more than you would think. This is now even more important now there is an ability to add FX from the NKS browser.
Yes there will never be "one size fits all" kind of template but there are some points to be made about what suits who and why.įX were added in (with a huge amount of extra work since every patch needed to be updated with new host automation mappings) because of many requests from blind users to be able to (at a minimum) disable FX such as reverb in favor of adding their own flavour. If you come up with a map you think would be decent then post it back here or just PM me.
I won't go into detail on recommendations on how to do mapping or what is officially recommended by NI in terms of pages and placement as it's interesting to see what people's mindset is with this kind of thing. Keep in mind that there is code handling the highlighting of things so don't do Cut/Paste, always copy/paste then just delete if needed Not every control is listed but the majority of common controls should be available to pick from.Ĭheck it out and if you have a Google account and want a copy of it to use and contribute a template then just choose File > Make Copy and it will unlock so you can start to edit and make changes. The main focus should be on what controls you would need access too to instantly change a sound or automate a sound, not design it from scratch because that is far beyond the scope of 8 controls per page. Keep in mind everyone is different and everyone has their own idea on what is "good". The main point is to whittle down the enormous amount of possible controls into something that fits most peoples workflows. As controls are selected they are highlighted on the control data page as being used and if you select 2 duplicate controls on the designer page they are highlighted red The data is read from the "Control Data" page where the names of all controls need to be listed. The designer page simply lets you select controls using a dropdown menu where you would like them and apply labels as you would want on the hardware. I have a view only copy of the template creator here:
I have designed a control template creator I use to design maps for NKS before wasting days of time trying to lay things out correctly (using google sheets) and for Omnisphere I have decided a MAX of 25 pages (less would be better) would be the goal but I am no sound designer so don't really get too deep with omnisphere so not sure in some cases what controls would best be left out. I have looked at a few attempts at creating templates for 2.5 but none cover things in enough detail to suit both my needs and the needs of blind users out there (such as being able to switch FX modules off from the hardware). Part of the issue is NONE of the patches released prior to 2.5 make use of layers C and D so only a few from the hardware layer make use of the extra layers and in many cases, are just stereo spread layers.
I have been working on an update for Omnisphere 2.5 to release the Hardware library but have spent a LOT of time trying to ponder just how to best tackle the insane amount of control there is in 4 layers. Omnisphere 2.5 Control Template Designer!