Great article as always, Bad Mister!
One question though - is it possible to assign the main volume for a performance to a slider/encoder/controller? It seems that this may greatly simplify the levels setup before recording audio to Cubase.
The article simply is pointing out the logic in learning to combine MODX audio signals to OUTPUT buses as an early skill. The fear is that too many first timers will accept the default setup of the “Quick Setup” Template without considering simple Part Output assignments. Why record a stereo acoustic piano to four stereo tracks, when a single stereo track provides the results required?
Unless you have specific need to record the multiple Parts separately (which of course, in a different example, is a possibility) - but recording the soft strike Piano Elements to a separate stereo audio track from the medium and hard strikes seems overkill, and isolating the KeyOff Sound (which uses Part 4) of the hammers and felts to its own stereo track, simply seems like severe overkill. Now, if there is reason to isolate the components of a Multi Part instrument to their own stereo track, by all means do so. But, in all likelihood you’ll combine all acoustic piano component Parts to the same stereo bus (thus the example).
We just wanted to point in the article, that the AUDIO “Quick Setup” template does NOT always make sense. Audio output assignments is a very important skill to develop early on. The “Audio Rec on DAW” template makes the most sense when you are setting up to record Single Parts from each program slot, not necessarily when recording one instrument that spans multiple Parts.
Hope that helps. Of course, when performing a multiple Part instrument you can control all of the Parts together (absolutely, that’s a key point with sound construction in MODX Motion Control engine: you can use as many as eight internal Parts which you can play and control simultaneously... you do so by activating the KBD CTRL (Keyboard Control) icon, thus linking them to your real-time interaction via the Keys.
Additionally, while eight Parts can be played simultaneously, the aptly named Super Knob can Control all sixteen Parts - for example, the Super Knob could be used to fade out all Parts (whether or not you are playing them directly). You can simultaneously control scores of Oscillators, Filters, amplifiers, across several Parts... these Parts can be separate instruments, or combined into one multi-instrument with very fine detail.
As you’ll see, the Control engine goes far beyond what perhaps you’re used to... not only can Parts be isolated on individual audio buses, individual drum sounds from within a DrumKit can routed (isolated or combined as necessary) on buses to your DAW. The main point of the article is to stress that learning to manually route Parts to Outputs is a skill you need right from the start (Do not just follow the template, specifically if it does not apply to what you want to accomplish).
You’d be amazed how many users automatically assume that any Template provided will automatically work for them. And that is the problem with providing Templates... they often require an explanation. It’s generally a good rule: Avoid using any template until you’re clear that it does what you require. As you’ll see all the Quick Setup Templates are user customizable... once you develop your own workflow method you can name and store your own Quick Setup templates.
As you’ll see all the Quick Setup Templates are user customizable... once you develop your own workflow method you can name and store your own Quick Setup templates.
For some reason, when I create my own user template - and name it something recognizable - the default template for that slot replaces my custom template upon next power cycle. This is as reported by another recent thread - but I wanted to dig up some older threads that covered this topic to see if one would expect the user templates are saved through power cycles. I do not yet see any indication that they are expected to be lost.