Notifications
Clear all

Unify's multi-core magic

3 Posts
2 Users
1 Reactions
505 Views
Robert.P
(@robert-p)
Reputable Member
Joined: 4 years ago
Posts: 293
Topic starter  

Hi, I was playing with Surge XT recently (I tried some of it's CPU intensive patches) and this is what I discovered:

  • Normally, Surge XT uses a single core on my system (VST3 in Studio One/Bitwig and CLAP in Bitwig)

however,

  • when I use it inside Unify, the processing is spread across all of my CPU cores

I'm not sure why it works better with Unify, magic?


   
Quote
Robert.P
(@robert-p)
Reputable Member
Joined: 4 years ago
Posts: 293
Topic starter  

Multi-core graph:


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4500
 

I'm afraid I can't offer a simple answer. Multi-core performance is challenging to measure and understand, and is both OS- and CPU-dependent. I'm happy to know that Surge XT is working well for you in Unify.

All plug-ins use one thread (the "audio thread") for audio rendering, and another (the "message thread") for everything else. Unify sets up a pool of additional "worker" threads, one per layer, and defers audio-rendering tasks to them. In some cases (your included, apparently), this can result in better overall CPU utilization, even if only one INST layer is used.


   
Robert.P reacted
ReplyQuote
Share: