Putting aside the strange Gamergate "devs are lazy" comment, "multithreading ON in plugin" doesn't mean too much. There is no standard way to implement threading within a VST plugin itself. And due to thread synchronization overhead, it's often not efficient to try to do this. There is one case where it makes sense, and it's the reason in-plugin multithreading was in Diva years ago -- when you want to use a single instance of a synth, and play multiple notes on it, and you have multiple cores in your computer, but each core individually is too weak to run the number of voices you want to play in the synth, and you are running your DAW with enough latency to overcome the thread syncing overhead during the audio rendering callback, and you are not near total CPU utilization with the other things going on in your DAW and other plugins.frag wrote: Sat Jan 18, 2025 11:59 am Dune multi-threading sucks, you know why? Because it's written on a system with Core parking enabled, which is absurd! There's NO way plugin can know what will OS do with threads!
So it's hyperthreading ON in BIOS, Core parking OFF in OS, Multithreading ON in plugin and DAW. If the authors of plugin wrote it this way, it will work perfectly.
Of course, multithreading in DAW may screw up some plugins optimized for single thread performance, but then you just split the voices between two instances running identical patch. Problem solved
I would definitely expect plugins to implement MT in 2025, but just like on the games market, software writers became lazy - they want you to buy the latest CPU and run a thermal plant in your room, even though good writing would make everything simple and efficient. This sucks big time
Other than that, it's likely to be counterproductive -- the overhead of threading will decrease the total amount of processing power available for audio rendering. Don't believe me? Ask Urs, who recommends turning it off in many situations these days. Or even the Diva manual itself:
It's worth noting that every DAW distributes plugin instances across multiple cores these days, unlike when Diva was released.
By the way, you brought up core parking. The multi-threading thing is a conceptual problem that affects every platform, including Macs. Core parking is a thing specific some AMD and Intel chipset models. If it's causing problems for you in your DAW, that's not really relevant.
The reason I'm mentioning and replying with this is that it's irrelevant to the topic of the Korg multi/poly native synth. Posting that this synth will suck if it doesn't have in-plugin multi-threading is not true and this whole tangent is a derail.
No way! especially I have much more synths than I need! It must be so special that no synth I have can match it in sound ability and quality, which I doubt.
