Divisimate 2.1 removes certain extreme waits when switching between presets with different Arpeggiators and improves synchronization with Repeater plugins. The update also changes Arpeggiator controller initialization and repairs two editing behaviors.
Those changes do not describe one fault. A delayed preset, a drifting pattern, an unexpectedly scaled velocity lane, and a misplaced transposition marker arise from different parts of the system. Treating them as one timing problem can send you toward the wrong repair.
Divisimate's Arpeggiator builds patterns, textures, and melodies from routed notes, while the older Repeater adds rhythm to static chords. Both refer to the global tempo, and presets can replace their configurations during performance. Timing and controller-state failures become easier to isolate when each transition is tested under identical input.
One configured behavior can preload a preset while notes or the sustain pedal remain active, then complete the change after everything is released. That wait protects a musical transition rather than exposing the repaired Arpeggiator fault. Release all keys and the pedal before deciding that a switch remains abnormally slow.
Test the same pair of presets in both directions because their Arpeggiator configurations may differ. Measure from the pad press to the visible and audible change, first with no notes held and then during the intended passage. A delay that disappears after release points toward transition settings, while an extreme idle delay belongs closer to the fixed behavior.
The narrower scope of Divisimate 2.1's arpeggiator reliability fixes matters when diagnosing an old project. Updating should remove the specified pathological wait, but it does not replace deliberate transition choices or make a heavy instrument template load instantly.
Check synchronization against Divisimate's global tempo before editing individual patterns. Confirm that the Arpeggiator and Repeater start where expected, maintain their relationship through several cycles, and remain aligned after a preset change. Different pattern lengths can create musical displacement even when technical synchronization is correct.
Controller scaling is another state entirely. On preset load, Divisimate 2.1 now gives Arpeggiator plugins an initial scaling CC value of 100. That provides a defined starting value before new data arrives from the selected controller.
Do not confuse that initialization with the control that blends entered velocity-lane values against the chosen scaling source. The Arpeggiator can scale its lane from key velocity or a specified CC, and later incoming controller data still changes the result. A pattern can be perfectly synchronized while its attacks feel unexpectedly strong or weak.
Record the controller stream when the first cycle after a preset change differs from later cycles. Compare the initial value, the first received CC message, and the Arpeggiator's scaling-source selection. That separates the new value of 100 from automation, a physical fader position, or a controller that sends nothing until it moves.
Inspect any old expert pattern that was edited by widening steps. Verify the audible pitches, the step widths, and the displayed transposition markers separately. A corrected marker may reveal the existing musical setting more accurately without requiring you to redraw the pattern.
The update also lets you enter the Arpeggiator's scaling CC number by double-clicking. That improves value entry, but it does not choose the correct controller for the instrument. Confirm the number against the actual MIDI source rather than assuming successful text entry proves the mapping.
Use one recorded chord and controller pass for the final test. Replay it at a fixed global tempo through the original preset, the transition, and the destination preset while monitoring both rhythmic plugins. Consistent input exposes changes in loading, alignment, scaling, and displayed step data without adding performance variation.
When only one symptom remains, keep the repair equally narrow. Adjust Performance transition behavior for release-dependent waits, pattern design for musical displacement, CC mapping for dynamics, and expert-step data for pitch. Rebuilding every Arpeggiator hides the evidence that identifies which 2.1 change actually affected the project.
Those changes do not describe one fault. A delayed preset, a drifting pattern, an unexpectedly scaled velocity lane, and a misplaced transposition marker arise from different parts of the system. Treating them as one timing problem can send you toward the wrong repair.
Divisimate's Arpeggiator builds patterns, textures, and melodies from routed notes, while the older Repeater adds rhythm to static chords. Both refer to the global tempo, and presets can replace their configurations during performance. Timing and controller-state failures become easier to isolate when each transition is tested under identical input.
Switching delays need the right diagnosis
Version 2.1 specifically fixes extreme wait times that occurred in certain situations when presets contained different Arpeggiator plugins. NextMIDI does not claim that every preset change must now happen immediately. Divisimate still follows the transition behavior selected for the current Performance.One configured behavior can preload a preset while notes or the sustain pedal remain active, then complete the change after everything is released. That wait protects a musical transition rather than exposing the repaired Arpeggiator fault. Release all keys and the pedal before deciding that a switch remains abnormally slow.
Test the same pair of presets in both directions because their Arpeggiator configurations may differ. Measure from the pad press to the visible and audible change, first with no notes held and then during the intended passage. A delay that disappears after release points toward transition settings, while an extreme idle delay belongs closer to the fixed behavior.
The narrower scope of Divisimate 2.1's arpeggiator reliability fixes matters when diagnosing an old project. Updating should remove the specified pathological wait, but it does not replace deliberate transition choices or make a heavy instrument template load instantly.
Synchronization and scaling are separate states
NextMIDI also improved synchronization between Arpeggiator and Repeater plugins within presets and across preset changes. A rhythm can therefore involve both plugin types without treating their alignment as unrelated clocks. The change remains relevant to older Performances because Repeater is retained for compatibility with legacy presets.Check synchronization against Divisimate's global tempo before editing individual patterns. Confirm that the Arpeggiator and Repeater start where expected, maintain their relationship through several cycles, and remain aligned after a preset change. Different pattern lengths can create musical displacement even when technical synchronization is correct.
Controller scaling is another state entirely. On preset load, Divisimate 2.1 now gives Arpeggiator plugins an initial scaling CC value of 100. That provides a defined starting value before new data arrives from the selected controller.
Do not confuse that initialization with the control that blends entered velocity-lane values against the chosen scaling source. The Arpeggiator can scale its lane from key velocity or a specified CC, and later incoming controller data still changes the result. A pattern can be perfectly synchronized while its attacks feel unexpectedly strong or weak.
Record the controller stream when the first cycle after a preset change differs from later cycles. Compare the initial value, the first received CC message, and the Arpeggiator's scaling-source selection. That separates the new value of 100 from automation, a physical fader position, or a controller that sends nothing until it moves.
Editor repairs prevent false musical fixes
Expert mode lets each step activate routed voices and transpose them independently. Divisimate 2.1 fixes transposition markers so they follow correctly while steps are enlarged. This is an editor-display repair and should not be mistaken for a general change to arpeggiated pitch behavior.Inspect any old expert pattern that was edited by widening steps. Verify the audible pitches, the step widths, and the displayed transposition markers separately. A corrected marker may reveal the existing musical setting more accurately without requiring you to redraw the pattern.
The update also lets you enter the Arpeggiator's scaling CC number by double-clicking. That improves value entry, but it does not choose the correct controller for the instrument. Confirm the number against the actual MIDI source rather than assuming successful text entry proves the mapping.
Use one recorded chord and controller pass for the final test. Replay it at a fixed global tempo through the original preset, the transition, and the destination preset while monitoring both rhythmic plugins. Consistent input exposes changes in loading, alignment, scaling, and displayed step data without adding performance variation.
When only one symptom remains, keep the repair equally narrow. Adjust Performance transition behavior for release-dependent waits, pattern design for musical displacement, CC mapping for dynamics, and expert-step data for pitch. Rebuilding every Arpeggiator hides the evidence that identifies which 2.1 change actually affected the project.
