ADLondon Posted January 26 Author Share Posted January 26 10 hours ago, fisherking said: am suggesting you have NONE of those apps open on startup, so all processing power and memory is devoted to logic. and yes, resetting the nvram is 'zapping the pram'. google for your particular mac (and the smc reset). a safe boot's a good place to start; hold down the shift key on startup; will take longer than usual; keep holding the key, you'll get to the login screen and should say 'safe boot' in red (upper right menubar). sign in, reboot normally (safe boot is a good basic diagnostic; clears user cache, etc) Ok, thanks. Will start with those then. Frankly, I can't say I hold much hope though, as unless it's a shed load of coincidences, I've had issues from day one when it was new.... Quote Link to comment Share on other sites More sharing options...
ADLondon Posted January 26 Author Share Posted January 26 15 hours ago, fisherking said: am suggesting you have NONE of those apps open on startup, so all processing power and memory is devoted to logic. and yes, resetting the nvram is 'zapping the pram'. google for your particular mac (and the smc reset). a safe boot's a good place to start; hold down the shift key on startup; will take longer than usual; keep holding the key, you'll get to the login screen and should say 'safe boot' in red (upper right menubar). sign in, reboot normally (safe boot is a good basic diagnostic; clears user cache, etc) Ah ok. Doing the 'nothing else open' thing today. Will do the resets either later, tomorrow or over the weekend.. What am I supposed to do after the safe boot? Just shut down and re-open as normal? Quote Link to comment Share on other sites More sharing options...
fisherking Posted January 26 Share Posted January 26 34 minutes ago, ADLondon said: What am I supposed to do after the safe boot? Just shut down and re-open as normal? once you sign in and are back at the Finder, you can restart once more, normally. and (hopefully) life gets better, a logical assumption... 😉 1 Quote Link to comment Share on other sites More sharing options...
ADLondon Posted January 26 Author Share Posted January 26 1 hour ago, fisherking said: once you sign in and are back at the Finder, you can restart once more, normally. and (hopefully) life gets better, a logical assumption... 😉 Haha. Ok, cheers. And thanks again to you (all). 🤞 Quote Link to comment Share on other sites More sharing options...
ADLondon Posted January 27 Author Share Posted January 27 Argggh! If I had the money, I would throw this Mac and the drive out of the window and start again! So now, I plugged in a 2nd screen (which I've done before) - but now, the hard drive just keeps voluntarily ejecting itself!! It did this when I first had it, and I kept trying different positions, leads and finally it seemed to stabilise, but god forbid I should slightly move the machine or the hard drive, or sneeze near it or anything! It's my main hard drive where I save ALL my music/work projects and am DESPERATELY trying to Time Machine back it up before it corrupts anything. (It did have a hissy fit yesterday and freeze) but it won't let me because it keeps ejecting when only partly done. I'm struggling to a) know what to do and b) keep my fecking sanity here! I know - Call Apple! I hope they are prepared to spend all day on the phone now, because I've been making a list!!!! 😩🔫 1 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted January 27 Share Posted January 27 Does the hard drive ejects itself when you're touching it or moving it? Or while it's not moving at all? I've noticed that one of my external SSDs is pretty capricious to even the slightest movement, and I better not touch it or move it while working with it. Otherwise one thing you can consider is to spend $100 in an external SSD, do a fresh install of the latest macOS/Logic Pro combination your Mac supports, and start rebuilding a new system that way, carefully monitoring the behavior as you install new apps/plug-ins. A lengthy procedure, but that may help figure out what's going on. Quote Link to comment Share on other sites More sharing options...
ADLondon Posted January 27 Author Share Posted January 27 I did move it slightly when I plugged the screen in, but it's ejecting when just sitting there now - no movement. It is a 2TB Samsung SSD drive that cost me £220 in Nov 2021. The drive is connected by a short USB 3 cable. It has a SATA port too, but I stopped using that when it kept disconnecting in the first place. Oh god, lengthy? The very thought is making me want to run away and never be found. Mind you, right now, I'm not sure how much more I can take anyway. 😭 Quote Link to comment Share on other sites More sharing options...
ADLondon Posted January 27 Author Share Posted January 27 Actually it's not a Samsung (I was reading the invoice) It's an OWC Mercury Elite Pro Mini!! Hmmm Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted January 27 Share Posted January 27 Ah. Mine is a Samsung (T7). I was starting to wonder if it had something to do with the Samsung! 🙂 Quote Link to comment Share on other sites More sharing options...
polanoid Posted January 27 Share Posted January 27 (edited) I think I found it. Most probably a bug in Logic (quite funny to think how this bug has made it into Logic at all). Logic seems to mix the data of all sub lanes (at least in your example project) that share the same color. So, if I delete all automation on the "Dale 1" track except for e.g. the two orange ones (which are "Compressor Release" and "Enveloper Release Gain" it will look like this when you show all automation sub lanes but like this when I hide the sub lanes If all sub lanes have different colours (unfortunately you can not manually assign these), the issue doesn't occur anymore. Weird one. I suggest reporting it to Apple (and attach your example project, I have not managed to recreate this in a clean new project yet). Edited January 27 by polanoid 2 Quote Link to comment Share on other sites More sharing options...
polanoid Posted January 27 Share Posted January 27 BTW to repair (and, actually, clean up a lot) your project, use the "Mix -> Delete Automation -> Delete redundant automation points". There's tons of automation nodes that just have exactly the same value as the previous ones. These unnecessarily increase your project's CPU load. 1 Quote Link to comment Share on other sites More sharing options...
polanoid Posted January 27 Share Posted January 27 (edited) 46 minutes ago, polanoid said: Logic seems to mix the data of all sub lanes (at least in your example project) that share the same color. Narrowed it down a bit more: It's not the color of the automation curve, it's the fader number that has to be the same to make this issue happen. You can easily verify this in your example project when you open the automation event list for the Dale 1 track (Cmd-Ctrl-E): The Enveloper Release Gain and the Compressor Release both have Fader Number 3, only the channel (which determines which plug-in slot receives the automation) differs - 6 and 4, respectively. This makes this bug at least a bit less weird to me 😉 . Attaching a very small example project which shows the issue as well (I just used two instances of the same plug-in to make it easier). Just toggle the automation sub lanes on and off and see what happens different plug-in, same fader number.logicx.zip Edited January 27 by polanoid 2 Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted January 28 Share Posted January 28 11 hours ago, polanoid said: I think I found it. Wow, that's fascinating. Thanks a lot for posting this! 🙂 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.