Notifications
Clear all

Apple Silicon performance issues

10 Posts
3 Users
0 Reactions
270 Views
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4453
Topic starter  

As part of the Unify v1.8.2 public beta, we're seeking feedback on any performance issues users may be experiencing on Apple Silicon Macs, most particularly the Mac Studio.


   
Quote
 JonG
(@jong)
New Member
Joined: 2 years ago
Posts: 4
 

Hi

I’ve just installed on a new Mac Studio 64 GB RAM and a 2 TB drive… finally got all the plugs recognized, but am having audio dropout problems. It seems to be over driving the CPU. No other plug is having this problem. Wonder if anyone else is having this problem 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4453
Topic starter  

@jong

Thanks for bringing this here. This sounds like the same problem another Studio user has described, and as far as I can tell, it seems to be specific to the Studio models. I have four questions for you:

  1. Which version of Unify are you using?
  2. Does this happen in the Unify stand-alone app, or the plug-in, or both?
    • If it occurs in the plug-in, what DAW/host are you using, and what plug-in format for Unify (AU, VST, VST3, AAX)?
    • If in the stand-alone app, what type of audio interface are you using, and what are your settings (buffer size, sample rate)?
  3. Do you get audio glitching all the time, or only when using certain plug-ins? If so, which ones?
  4. What's happening with Unify's CPU meters? (Please attach a screenshot if you can.)

   
ReplyQuote
 JonG
(@jong)
New Member
Joined: 2 years ago
Posts: 4
 

thanks Shane!  Unify v 1.8. in Logic 10.7 ... cutting out on many different patches and seemingly now.. not doing it on the standalone version


   
ReplyQuote
 JonG
(@jong)
New Member
Joined: 2 years ago
Posts: 4
 

my buffer size is either 128 or 256.. so far what I've tried... sample rate 24 removed link the CPU meters I have to admit.. not sure how to see them in Unify


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4453
Topic starter  

@jong

To show CPU meters, click on the concentric-circles icon at the very bottom center of the GUI and choose "Toggle CPU meters".

To show CPU meters always, go to Settings and scroll down to where it says "Show by default" near the bottom, check "CPU meters". Note you'll need to restart Unify before the change will take effect.

The forum software seems to have removed a link from your post. You can try simply copy/pasting the link address right into the text (don't use the insert/edit link icon at all), or better yet, include whatever content you want as an attachment. You can attach images and text files directly, but just about any other kind of file(s) needs to be zipped first.

Unify v1.8 is Intel-only, so Logic will run the Unify AU in bridged mode. I've heard lots of stories of plug-ins not working well that way. You might consider trying our public beta version available at https://www.ilio.com/dl-unify. Make a save copy of the Unify.component file in /Library/Audio/Plug-Ins/Components first, before installing the beta, so you can revert to v1.8 easily.


   
ReplyQuote
 JonG
(@jong)
New Member
Joined: 2 years ago
Posts: 4
 

It seems to be hitting the Threads pretty hard... when Unify is off.. 20-25% .. when on 75% about to install the Beta


   
ReplyQuote
(@stevemoxi)
Active Member
Joined: 3 years ago
Posts: 5
 

I am also experiencing a single core spike and random dropouts in native and Rosetta mode... especially with Kontakt inside Unify.  It only hits one core. Other cores appear normal.

Another issue: Kontakt and Native instrument plugins do not load in Logic M1 mode (non-Rosetta).  All plugins are latest versions from NI.

System

Mac Studio

M1 Ultra

Memory 64G 

macOS Monterey 12.5.1

Logic Pro 10.7.4 native & Rosetta 2

Steve moXi


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4453
Topic starter  
Posted by: @stevemoxi

I am also experiencing a single core spike and random dropouts in native and Rosetta mode... especially with Kontakt inside Unify.  It only hits one core. Other cores appear normal.

Kontakt is single-threaded, so unless you have multiple instances, the CPU hit will only be on one core. The spiking is still the main issue I hear about on Mac Studio. It's interesting that you say it happens both in native and Rosetta mode. Is any automation active in Logic when the spikes appear?

Another issue: Kontakt and Native instrument plugins do not load in Logic M1 mode (non-Rosetta).  All plugins are latest versions from NI.

I'm working on a solution to that. Apple built native/Rosetta bridging into MacOS for Audio Unit plug-ins, but not for VST/VST3.


   
ReplyQuote
(@stevemoxi)
Active Member
Joined: 3 years ago
Posts: 5
 

@getdunne No automations active.  Kontakt does not spike the core when on separate Logic track, only inside Unify.  I tried 4 instances of Kontakt inside Unify: only 1 core utilized.  I will do additional testing for more insights.  Thank you Shane- you're the best!


   
ReplyQuote
Share: