KVR Audio

Caine123 · Post by **Caine123** » Thu Feb 19, 2026 9:28 am

hi, i just wanted to save my presets and saw the old school saving mechanic, i was like geeez 2026.... so you save 128 in 4 User banks, and what if you exceed them? then you need to replace the user banks and rename them? i dont have over 500 presets yet saved but maybe in future

.

im so happy Trinity is out as VST but why make such cumbersome preset management is out of my sense.

rafa1981 · Post by **rafa1981** » Thu Feb 19, 2026 1:19 pm

100% agree. Same with the wavestation, M1, etc.

Weasel-Boy · Post by **Weasel-Boy** » Thu Mar 05, 2026 1:14 am

Trinity was bumped to 1.1.3 yesterday. I have no idea what was added or fixed. And I agree with preset management on this unit. Needs work.

[nx] · Post by **[nx]** » Thu Mar 05, 2026 3:18 am

yeah they seriously need to improve the preset managment on their Korg Collection plugins.

tumface · Post by **tumface** » Thu Mar 05, 2026 4:10 am

You can save out the current state of the instrument as .vstpreset using your DAW. You can pretty much ignore the bank management, if you do that. Might be annoying in some DAWs, but saving/loading in that way is pretty easy in Live and Bitwig, for example.

EvilDragon · Post by **EvilDragon** » Thu Mar 05, 2026 6:06 am

Yup exactly, that's the way really.

DCrown · Post by **DCrown** » Thu Mar 05, 2026 7:50 am

In Reaper it is easy to save own presets without a plugin preset manager needed

rafa1981 · Post by **rafa1981** » Thu Mar 05, 2026 10:50 am

Nice workaround. I thought that .vst3preset wasn't standardized and could work between DAWs.

The Reaper's dropdown preset manager isn't stellar either

It's still very frustrating to see how their devs don't realize how pointless is replicating the pains of classic device UIs/ways for usage with screen, a keyboard and a mouse. Emulate the algorithms, do a clever readable UI with a color palette reminiscent of the original hardware (if the device isn't pink), done.

Even the "amateurs" (big quotes here) doing actual hardware emulations are doing a much better job with the UI and preset management.

EvilDragon · Post by **EvilDragon** » Thu Mar 05, 2026 11:19 am

.vstpreset IS a cross-DAW preset format.

Caine123 · Post by **Caine123** » Thu Mar 05, 2026 11:49 am

thanks, this cannot be a solution or defense however, you cannot share, manage the presets easily.... 2025/2026 this is just bad and should be definitely not around anymore. authentic emulations are nice but i dont need the cumbersome functions from the past especially with software nowadays.

EvilDragon · Post by **EvilDragon** » Thu Mar 05, 2026 2:04 pm

You definitely can share .vstpresets.

tumface · Post by **tumface** » Thu Mar 05, 2026 9:31 pm

rafa1981 wrote: Thu Mar 05, 2026 10:50 am Nice workaround. I thought that .vst3preset wasn't standardized and could work between DAWs.

The Reaper's dropdown preset manager isn't stellar either

It's still very frustrating to see how their devs don't realize how pointless is replicating the pains of classic device UIs/ways for usage with screen, a keyboard and a mouse. Emulate the algorithms, do a clever readable UI with a color palette reminiscent of the original hardware (if the device isn't pink), done.

Even the "amateurs" (big quotes here) doing actual hardware emulations are doing a much better job with the UI and preset management.

I believe the reason they fully emulate the old bank/patch workflow is so that you can send program change CCs to change between presets you've made, which the original hardware is also capable of.

EvilDragon · Post by **EvilDragon** » Thu Mar 05, 2026 10:53 pm

Yup, that's most likely the case.

rafa1981 · Post by **rafa1981** » Fri Mar 06, 2026 7:48 am

tumface wrote: Thu Mar 05, 2026 9:31 pm I believe the reason they fully emulate the old bank/patch workflow is so that you can send program change CCs to change between presets you've made, which the original hardware is also capable of.

Sounds reasonable. I hadn't thought about that.

From the product perspective that would assume that every user of the Korg Collection owns most of the emulated devices and wants to use them as an editor, which I guess is not the case and most users own zero hardware, while some 1-2 devices.

But I think that The Usual Suspect's emulations also solve this without the insanity. I'm not an expert on the hardware though.

IvyBirds · Post by **IvyBirds** » Fri Mar 06, 2026 6:53 pm

rafa1981 wrote: Fri Mar 06, 2026 7:48 am
tumface wrote: Thu Mar 05, 2026 9:31 pm I believe the reason they fully emulate the old bank/patch workflow is so that you can send program change CCs to change between presets you've made, which the original hardware is also capable of.
Sounds reasonable. I hadn't thought about that.

From the product perspective that would assume that every user of the Korg Collection owns most of the emulated devices and wants to use them as an editor, which I guess is not the case and most users own zero hardware, while some 1-2 devices.

But I think that The Usual Suspect's emulations also solve this without the insanity. I'm not an expert on the hardware though.

Korg software does a really good job with stand alone modes. These are EXTREMELY valuable for live playing. You can run the Trinity in stand alone mode without a DAW or Host and use any MIDI controller you want and have a Trinity for the stage that you can send CCs to change banks and presets with

With the new MIDI Tools in Windows 11 that allow multiple apps to share the same MIDI Ports and even share MIDI at the OS level between apps with no latency and Multi-Client ASIO drivers feeding audio to your interface you can launch multiple stand alone synth apps and place them all on individual unique MIDI channels.

When you do this each stand alone app will by default get its own dedicated core on your CPU (until you run out of cores) without the overhead of a DAW or other host, all handheld by your OS

Very very handy indeed and no need for the original hardware

Korg Trinity - Saving user presets, why so cumbersome?