Reply to thread

Message: [QUOTE="Bombastus, post: 91547, member: 2178"] Tresse 1.2.3 gives its two oscillator layers either one shared sequence in JOIN mode or two complete sequences in SPLIT mode. The switch looks small, but it changes how much rhythmic and melodic independence you can get from a single plugin instance. JOIN keeps the layers locked to the same note stream, while SPLIT lets the second layer run its own notes, pattern length, swing, and related sequence settings. JOIN is useful when the two layers are supposed to behave like one instrument. With [B][URL='https://goldmidi.com/community/threads/v%C3%A5ld-labs-debuted-the-tresse-hybrid-synth-plugin.76928/']Tresse's dual-layer synth architecture[/URL][/B], you can give each layer a different synthesis engine and sound design while both still receive the same sequence. A bass-heavy engine can sit under a brighter layer, or two contrasting timbres can follow identical chord and note changes without you having to keep separate patterns aligned. SPLIT is the more radical option because OSC 2 stops borrowing the first layer's sequence. Its notes, length, swing, and other sequencer settings become independent, and both patterns remain visible together. You are no longer just changing the sound stacked on top of a pattern, but the musical part itself. [HEADING=2]JOIN keeps harmony and timing deliberately coupled[/HEADING] A shared sequence removes one source of drift between the layers. Both synth parts receive the same generated note information, so changes to the pattern affect the pair together rather than creating two unrelated movements. For layered patches, this is often the cleaner choice because rhythmic edits stay coherent even when the oscillator engines, filters, envelopes, or effects are pulling the timbre in different directions. Tresse still gives you plenty of movement inside the shared structure. Its sequencer can run patterns from one to 32 steps, use different playback directions, quantize notes to scales, place chords on steps, and vary probability, density, note length, swing, and humanize. None of those features require SPLIT, since JOIN simply makes both oscillator layers respond to the same generated result. The distinction matters when you randomize a sound or reshape a pattern during playback. In JOIN, one sequence remains the common musical spine. You can make the two layers sound extremely different without also creating a second rhythm or melody that needs its own space in the arrangement. [HEADING=2]SPLIT turns one instance into two sequenced parts[/HEADING] SPLIT gives OSC 2 a complete sequencer rather than a copy of OSC 1's pattern. Separate note content is the obvious difference, but independent length and swing are just as important. A short repeating figure can run against a longer phrase, while different swing settings let the layers lean into the beat differently instead of moving with identical timing. [B]Separate layer timing control[/B] matters more here than simply stacking two synth sounds. One layer can hold a slow harmonic figure while the other produces a busier pattern, yet both still live inside the same Tresse instance. Since the sequencers are presented side by side, the relationship stays visible instead of being buried across two plugin windows. Randomization also behaves differently once SPLIT is active. The commercial version randomizes both parts when you are working in split mode, so a single randomization pass can disturb the relationship between the two sequences rather than altering only one side. Useful results can appear quickly, but the behavior also means you should not expect OSC 2 to remain untouched while you roll new material for OSC 1. Preset sharing preserves the split arrangement too. Tresse's preset keys carry the second sequencer state, so sending a patch can include both sequenced parts rather than only the synth settings and first pattern. Older keys remain compatible, which matters if you already collected patches before the second sequencer arrived. [HEADING=2]External MIDI makes the split more than an internal trick[/HEADING] Tresse also exposes the layers separately to external MIDI. Channels 15 and 16 can address the two layers individually, giving you another route when you want a DAW, controller, or external sequencer to take over note duties. SPLIT is not limited to patterns generated inside the plugin. Host synchronization stays separate from preset recall in the current version. FREE, SLAVE, and MASTER are treated as operating settings rather than values a preset can overwrite. In a DAW, Tresse starts in SLAVE mode and follows the host, while the standalone application starts in FREE mode. A small transport readout shows the active sync state, and it pulses when the sequencer is armed while waiting for the host to run. This becomes more useful with two independent patterns because both parts can remain prepared without starting at an arbitrary moment against the project timeline. JOIN and SPLIT solve different arrangement problems rather than acting as simple and advanced versions of the same feature. JOIN is strongest when two sound layers should behave as one musical voice. SPLIT earns its place when the layers need independent notes, timing, pattern lengths, or externally addressed MIDI parts inside one synth. [/QUOTE]

Name