The MODX is easily capable of splitting/layering as many as eight sounds in a single program, called a Performance.
This is PART-level splitting. And is an easy way to accomplish more than 3 splits.
With slightly more difficulty, you can split each PART into 8 different splits using elements and element note limits. By using this technique, you could end up with as many as 64 splits.
Yes, good point, but Part-level splitting... because “splitting” at the Element-level of the architecture can be some what less flexible as it is not always possible to separate controllers as you might desire — often, exactly what you want in a ‘split’. Sure, it makes a great specification to say “64 splits’ but it should appear with a very large
asterisk denoting it’s esoteric nature. Creating a piano/bass split at the Element-level could be clever, to be sure - but trying to defeat the Sustain pedal for the Bass Elements while getting full Sustain Pedal use from the Piano Elements within the same entity, a simple thing at the Part-level, becomes true rocket-science at this level of the architecture.
The sheer abundance of control you have at the Part-level make it the ‘go to’ place when creating splits/layers.
I guess you could say “a Drum Kit is a 72-way split”, because of its independent instrument per Key layout but it’s semantics at this point.
So by “easily capable of splitting/layering as many as eight” means just what it says. It would be a hard specification to promote “the synth can do as many as 64 Splits!”* *but only if you....
Now that said, it’s a good point because it points to the depth of programming available, particularly for layering certain sounds, this Element-level of the architecture become a bit more practical... simply because in a layer situation you often select two or more sounds that you want them to *share* behaviors, where in a split, more often than not, you want each to do something different in each range.
EXTRA CREDIT:
The
Element (which is the basic playable AWM2 Sample-based entity) is a complete synth engine in miniature, capable of containing 256 samples, mapped horizontally and vertically on the Keyboard; It has its own volume, pan position, Note region, Velocity region, pitch envelope generator etc.; It has its own Filter, and filter envelope generator, etc.; It has its on Amplitude envelope generator, LFOs, etc.; It has its own routing to either or both or neither of the Dual Insertion Effects... so you can think of each Element as a complete “Synthesizer” path capable of creating a complete playable instrument (even though it most often used as just one component building block in the development of a sound). Some times an Element can be a sound effect (like the felt dampers dropping back on the strings of an acoustic grand) and some times it is the entire string section of a world-class symphony orchestra!
Yes, there exist in the Wave ROM, a single Stereo Element with some 250 samples that are used to make a full concert grand piano... it already has multiple velocity switches built into it. It can be recalled as a single Element piano. Likewise, as pointed out in the “scuba level” tutorial articles, there is a String Orchestra Element that captures the entire ensemble in one Stereo Element. If you are looking to build a piano, string, electric piano, and pad layered Performance... knowing about these “skinny” but very powerful Elements, can be very useful. Skinny from the number of construction components it uses, but full sounding because of what it is a sample of...
When building your own custom instruments, knowing the power within a single AWM2 Element is a great place to begin (when you’re ready). If you start with Seattle Sections, for example, as your strings (56 Elements) you’re gonna possibly get into trouble, if you then want to add a Multi Part piano, and a Multi Element electric piano and a Pad... but knowing about the Stereo Elements that the programmer’s use as the basic backbone of most Performances using string orchestra as a component, is priceless.
This is why the tutorial articles take you through “exploring” existing programs...as a method to learn the architecture.
Today’s knowledge point: Before you can create a Split, you need to learn to Layer
In other words, explore and learn how layering takes place at all levels of the architecture.
