songseeds

Just noticed my signature was incorrect - I'm running Monterey natively (no Rosetta) and having the problem. VERIFIED. Just restarted USING Rosetta with Logic and the problem disappears. des99 got it right.

Been a Logic user forever so this workflow change is tripping me up. I often rearrange the plugins on a track. NOW when you move the plugin, it opens and displays it. NEVER done that before. I just want to move it, not open it up. So I end up having to click the close button on EACH plugin window to close them. Is this change hard wired or is there NOW some setting that defines this behavior so I can go back to normal?

If you're wondering what the real world increase in performance is, I've got news. I upgraded from a Mac mini Intel i7 6-core to the Mac Studio M1 MAX. When purchasing I upgraded the Mac Studio RAM to 64GB and the storage to 1T. After installing in my studio I brought up a project I had been mixing with the Mac Mini into Logic on the Studio to do more work. Because I still have a few plugins that aren't yet Apple silicon ready, I'm running Logic under Rosetta. Here's some details of the project: The song has 36 tracks. There’s: 4 software instruments (Logic Vintage B3, Logic Studio Strings), UVI Workstation, Sonic Academy ANA 2 (5 instantiations) 31 FabFilter Q3 EQs 1 FabFilter L2 limiter (with 4X oversampling set) 8 Sonnox Limiters 1 Waves Reel ADT (a processor heavy plugin) 2 iZotope de-essers 2 Apogee Clearmountain reverbs 2 Soundtoys reverbs 1 Logic Space Designer reverb 2 Soundtoys micro shift 1 Soundtoys phase mistress 1 Soundtoys Devil-Loc 5 FabFilters Saturn 2 4 Slate Virtual Tape Machines 2 Waves CLA-2 compressors 12 Slate FET compressors 2 Slate VCA compressors 2 Slate Distressor compressors 1 Slate custom EQ 1 Slate buss compressor 1 D16 delay I initially had the queue set to 1024 (which I often do for mix down). Just for kicks I thought I'd lower it to 512 and see if my Performance Meter started showing increased load. It did NOT. So I lowered it to 256. No change. 128. Same. OK, now I'm starting to freak. Surely I'll see some increase in thread load at 64 but NO. OK, taking it ALL THE WAY now to 32. AND STILL NO CHANGE IN THE THREAD LOAD!!!!!!! This project would barely play on the mini with a queue at 256 and would occasionally stop at 512 just to give you some perspective. Here's a screen shot of the project running and you can see how low the thread load is with the queue at 32. So, if you're thinking about getting a Studio I can say with first hand experience that for me, it definitely was well worth making the change. I can't wait until all the software companies are running on silicon. The Mac Studio is awesome.

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

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.

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.

Ah, I see. When I change the Preferences from Automatic to 10, 10 bars display in the Performance Meter. So they should have changed the Performance Meter so it doesn't say "Processing Threads." Thanks des99

New Mac Studio user here. Traded in my 2018 Mac mini 6-core. I'm a bit confused by the Performance Meter display and the Audio settings in Preferences. The Mac mini was 6 core, so the Performance Meter would show me 12 bars (the core threads). The Mac Studio is 10 core BUT the Performance only shows 8 bars. Shouldn't I see 20 bars? ALSO The Processing Threads setting in Preferences/Audio/Devices shows me a choice of 10 cores but then in parenthesis shows (8 High Performance Cores). Anyone have any idea what's up with this?

As triplets suggested way back when, to bounce using AAC instead of mp3. I made this change and never had the problem again.

Over the years my mix down workflow has been to open Automation and (in Play mode) manipulate the curves while listening to set the volume. I'm talking Track-based Automation - I never use Region-based Automation. So, I play the track and manually move the curve and listen to the volume change until it's where I want it. At some point I noticed and began using a volume automation subtrack available in the Automation Parameter pop-up menu called Relative as a means of automating a volume gain or reduction across an entire track without messing with regular Volume automation settings. Very useful. However I began noticing that if I go into a track that has both Volume and a Relative Volume subtrack there is a problem. For instance, if I play the track and move the regular Volume automation curve, I hear no change in volume until I hit Stop and Play again. So I can't manipulate the regular Volume and hear the results in real time! I did a bunch of troubleshooting and discovered that tracks that do NOT have a Relative Volume subtrack work just fine. Play the track, move the automation curve, hear the change in real time as you move the curve. I also discovered that if I select a track that has both regular Volume and a Relative Volume subtrack and MUTE the Relative Volume subtrack, manipulating the regular Volume automation curve works fine - UNMUTE the subtrack and the problem returns. So, is this a bug?

You're a sharp one Mr. N. Indeed there IS a marker that ends at the point. I did not have the marker track displayed. So, I gather the dimmed ruler lines are there to let you know a marker exists when the marker track is hidden because I see that when I DO display the marker track, all the ruler lines are the same. Mystery solved. Thank you David.

I see this behavior once in awhile and I'm wondering if anyone knows what it indicates? Some of the ruler lines are barely visible and some are much MORE visible. In looking at my project I don't really see it corresponding to anything. Any wisdom out there?

Yeah I just got bit in the butt with this one. Moved everything to the new drive (named the same as the old) but Logic just can't do it. If I open the drive relocate dialog box in Logic it shows that there IS Library content there but provides no way to simply tell Logic to use IT. It DOES seem ridiculous that you have to download the whole Library all over again even though it's SITTING RIGHT THERE on the drive ! ! ! ! Shouldn't a relocate from one external hard drive to another external hard drive be an available choice or is there too much rocket science involved?

Here it is 3 years later and this little glitch just popped up on me COMPLETELY out of nowhere. I have no idea what the cause of this is (which DOES worry me somewhat). At any rate thanks to Mandubien for posting the fix. Saved me time and trouble.

FOLLOW UP: After restarting Logic I'm now getting it to work. Not the first time I've had odd things suddenly disappear after a restart. Worth a try if you're having problems.