Komplete Kontrol 3 can't open up Absynth anymore....
i tried several things rescanning the plugins etc. as a standalone app or vst absynth works fine on my win 10 PC....
i think i'll go back to KK 2.9.
Have you added VST2 plugins to the plugin paths?
As far as I know the KK 3.0 do not support VST2 but the KK 3.0.1 update ought fix that (give VST2 support) , however the VST2 support will be phased out in some later versions (updates) of KK , so well , either you have to revert to KK 2.9.xx or stay at the KK 3.x.x version that will have VST2 support !
No KK3 does support VST2 plugins (although on Apple Silicon Mac only in Rosetta mode). What is being phased out is the VST2 version of KK3
Thank you for pointing that out. Perhaps people ought to be more specific when posting because I got completely confused with respect to VST 2 from the other discussion over here : https://community.native-instruments.com/discussion/17915/komplete-kontrol-vst2-missing-after-3-0-0-update
The discussion at places gives the impression that it is general VST2 support hat is discussed though at some places specifies KK VST2...
This shows it can work but you do need KK3 to scan VST2 as well as VST3 plugins for them to show
I did the vst 2 scan 2 times on my main win 10 pc and it is still not opening up absynth. I just get a pop up to go to standalone and to just rescan but it doesn’t work… I did do the scan in standalone. It‘s like it’s looking for a vst3 version and can’t find it. It shows up in the scan as being scanned so no idea why it’s not working
Are you trying to load Absynth by loading a preset from the browser or by loading the VST directly?
--Mike
There isn’t a VST3 on Mac but I’m not sure if there is on Windows? Or if there is does it support migration?
if you check if you do have a VST3 version you can try temp moving that version out of the plugin folder to see if it forces loading in the VST2, also try the opposite
there is no VST 3 on windows either.
i was trying to open up presets.
i went back to 2.9.6. for now. there it works fine again...
don't have the time for the hassle.
i have to keep the studio running,
fixed with the latest 3.0.3 Update after a long back and forth with customer support.
