Hi guys,
I have a problem with Korg plugins both in Ableton 12.2 and Reaper 7.50: the GUI takes more than 5 seconds to open on all vsts from Korg Collection 6. Even M1 that would usually open quickly is affected.

My system specs are:
i5 9600k
32 GB RAM
Samsung 990 pro 2 TB
Radeon RX 580
RME FF 800
WIN 11 PRO

All other vsts from any other developer open pretty much instantly.

Do anyone have any clue to what could be the problem?

 

Here in Studio One with Windows 11, they take a bit longer than other plugins; for me, it's about 3 seconds.
Let's wait and see if Korg can optimize this in newer versions.

 

unfortunately with every update it seems worse: previous versions loaded almost instantly and now they take so long, I'm not sure this is normal

 

Korg also uses more elaborate graphics, the LED monitors have gotten bigger and bigger, and the GUIs are also getting larger. Some of the presets are huge, but Korg really needs to improve and optimize them. They've only just been released, so give Korg a chance to fix their product... Be patient... until the next update.

Spoiler: Source: Grok KI

The KORG Collection plugins (which include emulations like the MS-20, MiniKORG, and others—assuming "KORG 6" refers to this suite, possibly version 6 or a specific bundle) are well-known for slow GUI loading times, often taking 5–10 seconds or more per instance. This has been a persistent complaint across DAWs like Ableton Live, Reaper, Logic, and Cubase, on both macOS and Windows systems. It's generally not a sign of a failing hardware or installation issue but rather a design quirk in how these plugins initialize their interfaces and audio engines.

Common Causes
Based on user reports and forum discussions:

• Plugin Architecture: KORG's Legacy Collection and newer native plugins use resource-intensive frameworks (e.g., for vector graphics and preset browsing) that rasterize on load, causing delays. The "Legacy Cell" multi-plugin exacerbates this by loading multiple synths/FX at once.
• DAW-Specific Bugs: In Ableton Live (especially versions 11–12), VST3 formats can trigger slow parameter scanning or preset changes, particularly with controllers like Push. This is improved in Live 12 but still affects some users.
• System Interference: Antivirus software (e.g., Windows Defender or macOS equivalents) scans plugin files on-the-fly, adding 2–5 seconds. High CPU/GPU usage during idle can also stem from this.
• Hardware/Optimization: Older systems (e.g., pre-2012 Intel Atom equivalents) or non-SSD storage amplify the issue, but even high-end setups (i9 CPUs, 64GB RAM) report it. It's not tied to one OS—Windows VST3 resizable GUIs and macOS AU/VST loads are both culprits.

Troubleshooting Steps
Try these in order—many users resolve it with the first few:

1. Switch Plugin Formats:
   • Use VST2 instead of VST3 if your DAW supports it (e.g., in Ableton or Reaper). VST2 often loads 2–4x faster for KORG plugins.
   • Rescan plugins in your DAW after switching.
2. Create a Default Device Configuration (Ableton-Specific):
   • Load the plugin in Ableton Live.
   • Right-click the device > "Edit Parameter Mapping" > Map 128 parameters (you can do this quickly by selecting all and assigning sequentially).
   • Save as a default configuration. This bypasses slow preset/program changes in Live 11/12.
3. Disable Antivirus Scanning:
   • Windows: Add your plugin folders (e.g., C:\Program Files\Common Files\VST3\KORG) to Windows Defender exclusions. Also exclude the DAW executable.
   • macOS: In XProtect or third-party AV, whitelist KORG directories.
   • Restart your system and DAW after changes.
4. Optimize DAW Settings:
   • Increase buffer size (e.g., 512–1024 samples) during loading to reduce CPU spikes.
   • Close unnecessary tracks/plugins before instantiating KORG ones.
   • In Reaper/Ableton, disable "Plugin Window OpenGL" if available—some GUIs load faster without hardware acceleration.
5. Update and Reinstall:
   • Ensure you're on the latest KORG Collection version (check KORG's site for updates—recent ones improved load times for Triton/Modwave).
   • Reinstall via Native Access (KORG's manager) to rule out corrupted files.
   • Test in standalone mode: Launch a KORG plugin outside your DAW—if it's still slow, it's plugin-side.
6. System Tweaks:
   • Run your DAW as administrator (Windows) or ensure high-priority process settings.
   • Free up RAM/CPU: Close background apps; aim for <70% usage.
   • If on an older Mac (e.g., Intel), test on Apple Silicon—some report 20–30% faster loads.

Is It Normal?
Yes—delays of 5–8 seconds are "normal" for these plugins, as confirmed by KORG support and long-term users. Once loaded, performance is solid (low idle CPU). If it exceeds 10–15 seconds consistently or causes crashes, contact KORG support with your system specs/DAW version for a deeper diag.

If this doesn't match your setup (e.g., specific "KORG 6" details or error logs), provide more info for tailored advice!

 

Last edited: Nov 3, 2025 at 6:49 PM

Unfortunately it's not a matter of giving time to Korg to fix their product. It's been years (and many software versions) that vsts like triton show this behaviour on my PC and now pretty much all of korg vsts have slow GUIs. I want to know if it's something on my system or not. I already checked by myself all the fixes/optimizations that your AI copy/paste suggest. I wrote here to see if someone has a real clue of what could possibly cause this or have the same problem as mine. Thanks anyway for your reply

 

Year 2020 = KORG has finally updated their legacy synth plug in collection to have resizable GUIs!

Spoiler: Source: Grok KI

Your issue—Korg Collection 6 plugins taking over 5 seconds to open their GUIs in both Ableton 12.2 and Reaper 7.50, despite other plugins opening instantly—is shared by multiple users and appears to be a known problem rather than a flaw in your system setup. This delay seems to specifically affect the Korg line, as other VSTs are not similarly impacted.

Possible Causes

The issue does not seem tied to overall system performance, storage speed, or RAM, as users with high-end hardware and SSDs still experience the long load time.

The problem persists across DAWs, indicating it is related to the way Korg plugins manage their GUI or initialization, rather than the DAW itself. Historical posts show similar issues on both older and newer versions of the Korg Collection plugins, making it a long-standing concern.

Community Suggestions and Temporary Workarounds

There are currently no proven solutions that eliminate the slow GUI load entirely for Korg plugins.
Some users found performance to slightly improve after updating all DAWs and plugins, and ensuring graphics drivers are fully up to date, as Korg GUIs rely heavily on GPU acceleration.

Disabling unnecessary background applications, especially those that might interact with audio or GPU resources, can help marginally, but does not resolve the underlying problem.

In rare situations for other VSTs, removing duplicate or legacy versions (VST2 vs VST3) and doing a clean plugin rescan have been reported to help loading/resource conflicts.

Known/Reported Korg Issues

Korg's support and user forums contain multiple threads about GUI and loading performance, but no official fix has been announced as of late 2025.
Some forum users suggest this issue could be exacerbated by certain versions or graphics drivers, but there’s no definitive driver/plugin combination that solves it completely.

Recommendations

Keep your Korg Collection plugins, DAWs, and graphics drivers updated to the latest versions.

Monitor Korg’s official support channels and user forums for potential patches or updates addressing this exact issue.
If possible, contact Korg support with system details to add your case to reported issues, as developer attention is sometimes guided by user reports.

In summary, the slow GUI loading appears to be a recurring issue tied to the Korg plugins themselves, and not unique to your setup. Community workarounds provide only marginal improvements; only direct updates or patches from Korg are likely to fully resolve the problem.

 

Maybe they do not optimize them further, because they think you can just go get a new computer as fast as the ones they are developing plugins on. For me, when there is an Arturia emulation and a Korg version, performance-wise it has always been a coin flip which to delete. My normal course of action lately is to delete both.

 

I just noted that "opsix native" loads nearly instantly so it's something related to Korg Legacy collection. I'll try to reinstall it from scratch and delete all leftovers from previous versions and see if something changes

 

I tried it but nothing changed.

I installed an old version (1.7.0) of the M1 and it loads instantly. What a shame!
I simply can't believe that these vsts are simply slow like that and it's not a fault on my system: how can you sell a product in this state?

Can someone with a powerful system report how much time it takes to simply open the GUI of the M1 from Korg Collection 6.0.0?

I'm not talking of the first time you load it but also simply closing and reopening the GUI after it has been already opened.

 

Last edited: Nov 3, 2025 at 11:42 PM

There used to be an issue in Live, basically if you did not have all parameters mapped presets would be slow to change not sure if its related. The newer synths are pretty fast loading for me , legacy synth are slower.

 

I remember that issue but this is another problem unfortunately. How much does it take to you (in seconds) to open the GUI of a legacy synth?

 

Test Korg - Trinity (Collection 6) ---> Windows 11 / PreSonus - Studio One 7 / SSD / AMD - Ryzen 7 5800X3D

So, the initial loading took 5-6 seconds, and closing and reopening the plugin in Studio One takes 1 second.

Conclusion:
Since all other installed plugins (and I have many) don't have any waiting time, the problem lies with the Korg Collection itself.

Whether Korg has been notified of the problem and whether they will do anything about it will be revealed in the next updates.

 

Thanks for your test, it matches my loading and reopening time for the Trinity vst. I will just wait for updates and in the meantime I'll live with it.

 

Trinity takes about 3 seconds.
Triton is 8 seconds.
PS3300 is immediate
ARP 2600 immediate
Odyssey 6 seconds