Just getting into using Focus Quick Controls on Omnisphere. When I have an instrument track set up with Omni (Midi channel 1) then add 7 midi tracks underneath to control each of the remaining 7 patches, it seems that when I record FQC info on any of these midi-channels, the only way to see that info is underneath the Instrument track. Am I doing something wrong? Is there any way that FQC automation info can show up underneath the midi track it was recorded on? There has to be another way to do this.
I’m afraid not. The automation tracks belong to the instrument defined on your instrument track. A MIDI track doesn’t have VST capabilities. It only outputs MIDI data that can be routed to a MIDI port or a VST plugin.
So Focus Quick Controls and Quick controls are only good for the first channel of an Instrument Track? For those of you using Omnisphere or any other multi-timbral synth or sampler, like Halion, how are you controlling the other midi channels, just with midi CC?
Hi, one way to go, except of course from direct midi learning, is to enable host automation for the parameters of interest: Right click on the parameter you want, and then click on “Enable Host Automation”.
Then, we can map these parameters to the instrument quick controls (and the first 8 to focused quick controls).
Here’s a screenshot demonstrating setting up our first 8 encoders to 4 parameters for the first 2 parts:
Hi, yes I understand you can map whatever control you want to the instrument quick controls. But when you record that on a midi track (say midi channel 2, not the instrument track) that Quick control info appears underneath the Instrument Track, not the midi channel you’re recording on. So if you have 7 added midi tracks and you’re recording all kinds of different Quick Control info on them, they all show up on the Instrument track, even if on different channels? That would make it VERY hard to organize and keep track of?
Yes.
But… Mind asking why you need to record all these tracks in one Omnishere instance? I mean, most guys I know (including myself) we’re using different instrument tracks all the time, and for each track we create “mega” patches using these 8 parts. And though it seems that Omnisphere can be hard on CPU, I personally never encountered something problematic, in my 16-24 instrument tracks I usually add it, even if I don’t have a high-end PC.
I already have 16 instances of Omnisphere with all 8 channels loaded because I like to have different Omni’s all at the ready with different categories of sounds. To have all that available would mean having 128 instrument tracks. Looks like using midi cc is the only way.
True, but why should that be a problem? You can Disable & Hide them until needed. Don’t you need 128 MIDI Tracks now?
Using Instrument Tracks with only one Virtual Instrument each will simplify lots of tasks in Cubase - for example using Quick Controls. Plus it can even improve your computer’s performance.
Instrument Tracks let you use Track Presets (or its routing retaining cousin Import Tracks from Project…) for alternative workflows. Instead of having 128 different Virtual Instruments pre-configured in your Template, you could have 128 Track Presets and use those to create new Instruments as needed.
There are some tasks where MIDI Tracks are the best choice. But for most day-to-day stuff using MIDI Tracks instead of Instrument Tracks is just creating unnecessary extra work for yourself.
The performance impact of having multiple instances as opposed to midi tracks really is negligible. I’d say you’re making things incredibly hard on yourself.
Alright then, something to think about, just seems strange to me but I was used to using VEP to host all my Omni’s and having them loaded up, without having so many separate Instrument tracks. I’ll give it a whirl, thanks.
Well, yes, VEPro is the usual way to do what you’re trying to accomplish, i.e. have a bunch of instruments always instantiated, loaded with patches, and standing by ready to use. However, even when using VEPro, Raino’s advice is still worth following.
Gotcha 
It is counterintuitive.
Sometimes there seems to be topic trends on the forum. I wrote this yesterday.
1 Like
Also of note: I made sure when designing Omnisphere that as many resources as possible are shared across instances. So, not only the sample library, but even things like graphics are shared. That minimizes the additional memory required for additional instances.
Ok, interesting, thanks for that info.