Quote:
Originally Posted by
Pete Kaine
➡️
The Kontakt multi-thread setting is designed as a stand-alone setting, otherwise when it's run within a DAW, it's up to the DAW package to manage the threading on its behalf. This is why it should be disabled in the DAW and enabled in standalone mode.
That was made very clear to us by a major DAW developer that running the previous earlier gen VI tests that used Multipart instances of Kontakt, and MP on, was not preferred on the more current engines .
Thing is, that was the default method for many high end users for years, without issue, but the shift in thread management complicated things.
Quote:
Clocks are not comparable between architectures as it's not allowing for the "IPC" figure ("instructions per clock"). You can have a 10GHz chip but it's only doing 5 instructions per clock cycle, then a chip running at 1GHz and doing 10,000 instructions per cycle is going to obliterate it.
Also it needs to be mentioned that these DAW systems do not ever run at the Base Clock , ACT ( All Core Turbo ) would be the better metric. Then we have the situation where the serial process is also load spread across multiple cores in various DAW's, and it gets even muddier.
