aMUSEd wrote:I wonder if the problem with Omnisphere is that it doesn't actually have any automation assignments by default, you have to set them up per project. They do persist in that if you save a template made in something like NI Kore or Kontrol it will reload next time with the same params setup, but since Panorama's interaction with plugins is mediated by the host they can't do that.
This is their recent reply on the subject:
Kontakt and Omnisphere are two tricky cases. These plug-ins can change their list of automatable parameters from one patch to the next. For this reason, any mapping we create may only be correct for one patch. The plug-in map we created for use with Cubase and Reaper integration basically give the user the ability to map parameters to a few template ages (similar to what you can do with Bitwig's device panel mapping).
I don't see why it's such a big deal. Once parameters are enabled for host automation, it's easy to save a template with these assignments, which persist when changing patches. And it doesn't have to be set up per project, it can be the default when you load Omnisphere. If Nektar were to make a template, all they would have to do is provide the Omnisphere template to load so that the automation IDs line up with the Nektar mapping. As with any multi-timbral plug-in, it wouldn't be possible to map out all 8 instruments, but they could throughly do one instance, which is often how people use Omnisphere anyways.
This would be the same with a Kore or Machine template or anything automation ID based mapping. Once the automation template is done then it's just like any other plug-in.
This is a block of text that can be added to posts you make. There is a 255 character limit. Once I have something clever, I will certainly fill it in.