Reply to thread

Message: [QUOTE="Bombastus, post: 91136, member: 2178"] Divisimate 2.1 lets one Multipad run two or three independent orchestrations across separate keyboard zones while their arpeggiators remain synchronized. Each zone keeps its own Divisi Engine and routing, so a chord played low can behave completely differently from notes played above the split. That is more powerful than a conventional keyboard split that merely sends fixed note ranges to separate sounds. Divisimate can analyze the notes inside each zone, divide them into voices, process those voices, and route the result through a prepared orchestration. [B]Separately routed performance zones[/B] are the real feature, not colored lines across a keyboard display. The distinction also separates Key Split from Divisimate's existing Low and Melody ranges. Those older ranges bypass the active Divisi Engine and pass their notes through to assigned ports, while every Key Split zone receives its own engine. Use a Low or Melody range for bass, leads, or keyswitches within one orchestration, and Key Split when each hand needs a different system. [HEADING=2]Strong presets make cleaner split zones[/HEADING] Build and test the component orchestrations before combining them in a Multipad. A left-hand setup might distribute a compact chord across low strings, while the right-hand setup routes a smaller voicing to woodwinds. If either preset sounds confused on its own, placing it beside another will only make the fault harder to trace. Inside the Multipad, choose the Key Split option and use two zones first. Three are available, but another boundary costs playable space and increases the chance of striking the wrong orchestration during a fast passage. Add the third only when the music has a stable middle role, such as chordal brass between a bass texture and a melody setup. Place boundaries from the notes your part actually uses, not from the visual center of the controller. Play the lowest melody note, the highest bass note, wide chord shapes, and every transition that crosses the proposed border. A split that looks balanced can still force awkward hand jumps or steal one crucial note from the wrong phrase. That preparation is the practical value behind [B][URL='https://goldmidi.com/community/threads/nextmidi-added-key-splits-to-divisimate-2-1.76472/']the Divisimate 2.1 keyboard-split update[/URL][/B], because one Multipad can hold a playable arrangement instead of demanding constant track changes. The result should feel predictable before it feels ambitious. [HEADING=2]Independent routing can create doubled instruments[/HEADING] Independence does not guarantee isolation. NextMIDI warns that two orchestrations can address the same instruments, which means a shared destination may receive MIDI from more than one zone. That overlap might be intentional for a common percussion layer, but it can also cause unwanted doubling, competing controller data, or confusing recordings. Audit destinations before rehearsing the combined Multipad. Compare the ports, channels, tracks, and multitimbral assignments used by every component orchestration, then mark deliberate overlaps in preset names or project notes. Do not trust different orchestration names to imply different routing. Test one zone at a time with the others silent, then play both together. Watch the receiving tracks while holding notes near each boundary, and check that only the intended instruments respond. If an instrument lights up from both sides, decide whether that shared routing serves the arrangement or merely survived from an older preset. Controllers deserve the same inspection. Independent Divisi Engines do not make a shared receiving instrument interpret two streams of expression, dynamics, or articulation data independently. When both zones need the same library patch, separate instances or clearly separated ports provide cleaner control than accidental convergence on one destination. [HEADING=2]Synchronized arpeggiators reward deliberate boundaries[/HEADING] Arpeggiators remain synchronized across Key Split zones even though their orchestrations and routing stay independent. That lets a bass pattern and a higher rhythmic texture share timing without forcing them through one Divisi Engine. Their note content, voicing, and destinations can differ while the pulse remains coordinated. Synchronization does not make mismatched patterns musical. Check step lengths, rests, note density, controller scaling, and octave movement in each orchestration before combining them. Two patterns can share a clock and still crowd the same register or strike together so often that the arrangement loses definition. Boundary tests matter most while both patterns are running. Move through inversions near the split and listen for notes jumping from one orchestration to the other, especially when a chord shape expands. If a phrase crosses the border, widen one zone, simplify the voicing, or return that role to a Low or Melody range. Save the finished Multipad only after testing quiet notes, dense chords, rapid releases, and transitions between the zones. Those checks expose routing overlap and uncomfortable boundaries before a live take does. A useful Key Split is not the one with the most instruments, but the one whose behavior you can predict under your hands. [/QUOTE]

Name