Notifications
Clear all
Topic starter
January 12, 2021 1:35 pm
John always mentions in YT-videos that Unify spreads CPU-load to different cores/threads.
As performance of Unify inside Logic is not that great on my MacBook Pro 15” 2019 i9 occasionally, I checked Logics CPU-performance-meter.
I have one instance of Unify on one track and noticed that it always shows only ONE core working regardless of how many layers in Unify.
MacBook Pro 15” 2019 i9
Unify 1.2.1
Logic X 10.5.1 OSX 10.14.6
“Audio > Devices > Processing Threads”-preference is set to “Automatic”
Would love to see John having Logics CPU-meter open in a (coming) YT-video …
Do I get something wrong ? Can someone explain please ?
Thanks & best regards
Rob
January 12, 2021 2:05 pm
Logic's CPU meter only shows Logic's use of each CPU core. To see what's happening on all cores, use MacOS Activity Monitor. When Unify recruits additional cores to run hosted plug-ins, Logic doesn't see that.
Unify's "CPU Meters" have their own subtleties: see https://pluginguru.net/unify/manual/doku.php?id=cpu-meters. Think of them more like the tachometer in a sports car; they're there to show you how close you are to the "red line" beyond which you will hear audio glitching.
Please explain in a bit more detail what you mean by "performance of Unify inside Logic is not that great":
- What sample rate and buffer size are you using in Logic? These have enormous effect on performance.
- Not that great compared to what?
- What patches are you running?
- Is the performance spectacularly better running the same patches in Unify stand-alone?
