Jump to content

Performance Meter - thread (core) processes


Recommended Posts

Okay, I'm not someone who knows the innermost workings of a computer (so this may not even be possible).

How many of you have had a session stop because ONE damned thread is maxing out, while a bunch of others have lots of room to go?  I know it happens to me.

If possible, processing should distribute the load so if one thread/core is getting maxed it, part of the load of that process could be assigned to one of the ones that isn't doing much. 

IF it's nice but not possible, how about this:

Click and hold on the offending thread/core in the Performance Meter and have a little popup telling you exactly WHAT the offending process (ie plugin name) is so you don't have to guess.  

  • Like 2

Logic Pro 10.7.4 - OS 12.4 - Mac Studio - M1 MAX - 64 GB RAM - Apogee Symphony Desktop
API Lunchbox 500-6B - API 512C pre - AMS Neve 1073LB pre - Genelec 8331A SAM monitors & 7360A sub

Link to comment
Share on other sites

If a software instrument track is selected and you see the one core shoot up, you have your culprit.

That's the way Logic is designed on software instruments being in live mode when selected.

  • Like 2

Logic Pro 9 Master Pro and X certified - ProTools 10 & 11 Certified Operator
2 x 3.06 Intel Six-Core 24 GB RAM, Logic 10.5.1, 10.14.6., UA Apollo - 2012 i7 MBP 16 GB Logic 10.6.3, 10.15.7
Contact me for Logic help (Teamviewer, Zoom, Skype) - http://www.ultimatestudiosinc.com

Link to comment
Share on other sites

Yes.  Good to know and I’m aware of that clue.  Still doesn’t completely solve the issue. I’ve had plenty of thread overloads with an empty audio track selected and the queue at 1024. Just thinking it would be great to not have to go on a fishing expedition trying to find the problem.  

Logic Pro 10.7.4 - OS 12.4 - Mac Studio - M1 MAX - 64 GB RAM - Apogee Symphony Desktop
API Lunchbox 500-6B - API 512C pre - AMS Neve 1073LB pre - Genelec 8331A SAM monitors & 7360A sub

Link to comment
Share on other sites

19 minutes ago, songseeds said:

I’ve had plenty of thread overloads with an empty audio track selected and the queue at 1024.

In case you didn't know already, make sure that no input is selected at the top of that track's channel strip. 

14 hours ago, songseeds said:

Click and hold on the offending thread/core in the Performance Meter and have a little popup telling you exactly WHAT the offending process (ie plugin name) is so you don't have to guess.  

That would be a nice feature indeed. 

  • Like 1

My new Logic Pro Book is out!

Link to comment
Share on other sites

Didn’t know about deselecting an input on the empty audio track. Thanks David. 

  • Like 1

Logic Pro 10.7.4 - OS 12.4 - Mac Studio - M1 MAX - 64 GB RAM - Apogee Symphony Desktop
API Lunchbox 500-6B - API 512C pre - AMS Neve 1073LB pre - Genelec 8331A SAM monitors & 7360A sub

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...