Tresse 1.2.3 can package both oscillator layers, sequencer state, modulation, and effects into a shareable preset key or QR code. The point is broader than saving a synth tone. A patch can arrive with much of the movement that made it interesting in the first place.
Earlier Tresse builds already used compact text keys, but the format has grown with the instrument. The commercial version carries the second sequencer introduced by SPLIT mode, while older keys still load normally. Someone can send you an older sound without rebuilding it, and a newer patch can arrive with both sequenced parts intact.
This makes Tresse's portable patch-sharing system unusually practical for forum posts, messages, and quick exchanges between musicians. You do not need a separate preset file just to pass an idea around. Copy the key, paste it into Tresse, and the stored state is reconstructed inside the instrument.
The sequencing part matters because a generative patch can depend heavily on pattern settings. Two sounds with identical oscillator parameters can behave very differently once note generation, pattern length, swing, modulation, or the second sequence changes. Sharing only the tone would strip away part of the patch's musical identity.
SPLIT mode made that problem more obvious. Tresse now lets OSC 2 keep its own sequencer, and current preset keys preserve that second part. A layered patch built around two independent phrases therefore arrives as a two-part construction instead of collapsing back to one shared sequence.
Våld Labs has also kept backward compatibility for older preset keys. You can still paste a key created before the split sequencer was added, while newer keys carry the expanded state. For a synth that changed quickly during beta, portable full-state patch recall is more useful than forcing everyone to rebuild or convert early presets manually.
This is particularly handy when the source and destination are different devices. A patch displayed on one screen can be scanned from another, and a printed QR can serve the same purpose. The iOS implementation can also generate a portrait social card containing the code, which makes visual sharing more useful than a screenshot of knob positions.
Text keys still have an advantage when you are working in a forum, chat, notes app, or desktop workflow. A short block of text can be copied, archived, searched, or pasted alongside a patch name and credit. QR codes make transfer quicker across cameras and screens, while text remains easier to store anywhere plain text survives.
Tresse also has ordinary preset management inside the interface, including saving, loading, renaming, and deleting. QSAVE gives you a faster route by storing the current sound under a generated two-word name. The sharing key sits beside those tools rather than replacing a normal preset library.
This changes the role of a shared key. A patch pasted into a discussion can be auditioned immediately, then potentially move into a curated factory bank with its author credited. The transfer format therefore works for casual swapping and for collecting reproducible user patches without asking contributors to package files for different operating systems.
The current factory bank is read-only, so bundled presets stay separate from the patches you save yourself. On iOS, standalone and AUv3 use the same preset library, which removes another small bit of housekeeping when you move between the app and a host. A shared sequence does not need to be recreated just because the surrounding session changed.
The useful boundary is worth knowing. Preset sharing is designed to recall the patch, sequence, and modulation state, while operating choices such as FREE, SLAVE, or MASTER sync are kept outside preset recall in the commercial version. Loading somebody else's sound therefore does not silently replace the transport behavior you already chose for your own session.
Earlier Tresse builds already used compact text keys, but the format has grown with the instrument. The commercial version carries the second sequencer introduced by SPLIT mode, while older keys still load normally. Someone can send you an older sound without rebuilding it, and a newer patch can arrive with both sequenced parts intact.
This makes Tresse's portable patch-sharing system unusually practical for forum posts, messages, and quick exchanges between musicians. You do not need a separate preset file just to pass an idea around. Copy the key, paste it into Tresse, and the stored state is reconstructed inside the instrument.
A preset key carries more than oscillator settings
Tresse's sharing format stores both synth layers rather than only an engine choice and a few front-panel values. It also includes all three LFOs, the delay and reverb setup, the sequencer system, and both MOD lanes. In practice, this means the receiving player gets the designed motion as well as the underlying timbre.The sequencing part matters because a generative patch can depend heavily on pattern settings. Two sounds with identical oscillator parameters can behave very differently once note generation, pattern length, swing, modulation, or the second sequence changes. Sharing only the tone would strip away part of the patch's musical identity.
SPLIT mode made that problem more obvious. Tresse now lets OSC 2 keep its own sequencer, and current preset keys preserve that second part. A layered patch built around two independent phrases therefore arrives as a two-part construction instead of collapsing back to one shared sequence.
Våld Labs has also kept backward compatibility for older preset keys. You can still paste a key created before the split sequencer was added, while newer keys carry the expanded state. For a synth that changed quickly during beta, portable full-state patch recall is more useful than forcing everyone to rebuild or convert early presets manually.
QR sharing turns the same state into a visual transfer
The QR system does not create a different kind of preset. It is another way to move the same stored patch state. On supported versions, the Share view can render the key as a QR image, while scanning a patch QR loads the encoded setup without requiring you to type or manually copy the text.This is particularly handy when the source and destination are different devices. A patch displayed on one screen can be scanned from another, and a printed QR can serve the same purpose. The iOS implementation can also generate a portrait social card containing the code, which makes visual sharing more useful than a screenshot of knob positions.
Text keys still have an advantage when you are working in a forum, chat, notes app, or desktop workflow. A short block of text can be copied, archived, searched, or pasted alongside a patch name and credit. QR codes make transfer quicker across cameras and screens, while text remains easier to store anywhere plain text survives.
Tresse also has ordinary preset management inside the interface, including saving, loading, renaming, and deleting. QSAVE gives you a faster route by storing the current sound under a generated two-word name. The sharing key sits beside those tools rather than replacing a normal preset library.
The community bank gives shared patches a second life
Våld Labs opened a community preset-bank invitation on September 9, 2026, asking users to post patches made with Tresse 1.2.3. Submissions can include a sound with or without a sequence, along with a preset name and the creator's preferred credit. The developer is selecting contributions for possible inclusion in the factory collection.This changes the role of a shared key. A patch pasted into a discussion can be auditioned immediately, then potentially move into a curated factory bank with its author credited. The transfer format therefore works for casual swapping and for collecting reproducible user patches without asking contributors to package files for different operating systems.
The current factory bank is read-only, so bundled presets stay separate from the patches you save yourself. On iOS, standalone and AUv3 use the same preset library, which removes another small bit of housekeeping when you move between the app and a host. A shared sequence does not need to be recreated just because the surrounding session changed.
The useful boundary is worth knowing. Preset sharing is designed to recall the patch, sequence, and modulation state, while operating choices such as FREE, SLAVE, or MASTER sync are kept outside preset recall in the commercial version. Loading somebody else's sound therefore does not silently replace the transport behavior you already chose for your own session.
