![]() ![]() I see your point and it is certainly valid, I'm just not sure if it is something that IKM can do anything about. Even the ST4 standalone app seems CPU bound with more than 2 or 3 instrument parts, so this is not just a DAW or plug-in issue. ![]() I have tested ST4 on Ableton Live 10, Studio One 4 Pro, and others. It is excessive, and this is not typical with other multi-timbral plug-ins. The CPU loading within a single ST4 plug-in instance needs to be reduced. I understand this, which was actually my whole point.Īllow me re-phrase the statement. It is within Logic Pro X anyway, as all the DAW sees is 'plugin/bunch of data to be processed' irrespective of what the plugin actually is. Unfortunately, this single-core loading is going to be down to the DAW AFAIK. So it gets very CPU hungry very quickly as it is dependent on the clock speed of a single core. It seems that when ST4 is used as a plugin, all of the instrument parts in a single instance of ST4 are channeled through a single CPU core/thread. Zzz00m wrote:So now it would be nice if they focused on CPU optimization. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |