emanuel_froes Posted March 22 Author Share Posted March 22 On 3/2/2023 at 4:44 PM, analogika said: Production always on the internal drive, whenever possible. If external, SSD only. Mechanical hard drives SUCK for music production. They are slow, any vibration or physical irritation KILLS what terrible performance they have (vibration will cause the mechanical read/write head to lose track and force it to re-read on the next rotation, or even lock up the drive entirely for a few hundred milliseconds as the heads are parked away from the platters to avoid mechanical damage). Use mechanical hard drives ONLY for archival and backup purposes. As for external SSDs: I have five or six Samsung T5/T7 drives that I've been quite happy with. I think the SanDisk portables are comparable. I will book mark your answer forever, mechanical hard drives SUCK! haha now i fear to have bought mac studio for a problem that was actually extern... Quote Link to comment Share on other sites More sharing options...
mattrixx Posted March 23 Share Posted March 23 Hi there, I am also a Mac Studio user. I fear the issue you are seeing is perhaps not actually related to drive speed. I've been speaking with Apple support for sometime now about a problem related to Core Audio and the way it works with the Apple silicon Macs. For example, one way to invoke the problem, is as easy as firing off some alert sounds from system settings. Even if you have all notification sounds turned off. You cannot completely turn it, or at least the trigger for it off. So , for example, you are playing Logic and you have the Finder as the front most app and you fire off an error by doing something wrong in Finder, this will trigger an error notification in Core Audio. Logic might stutter, or throw an error such as you are seeing. Pro Tools is even less tolerant and almost always throw an error when an Apple alert fires off. You can re-nice (using CPU Setter, or the Terminal) Logic or ProTools to -20 to give it greater priority, but does not completely solve the issue. BTW this is mattrixx (long time forum member), using a different browser, as this forum goes all weird in Safari for me and I cannot make posts normally with it. 1 Quote Link to comment Share on other sites More sharing options...
mattrixx Posted March 23 Share Posted March 23 Apologies, just re-read back through page 1. This is a different issue. Quote Link to comment Share on other sites More sharing options...
emanuel_froes Posted March 23 Author Share Posted March 23 (edited) 15 hours ago, mattrixx said: Hi there, I am also a Mac Studio user. I fear the issue you are seeing is perhaps not actually related to drive speed. I've been speaking with Apple support for sometime now about a problem related to Core Audio and the way it works with the Apple silicon Macs. For example, one way to invoke the problem, is as easy as firing off some alert sounds from system settings. Even if you have all notification sounds turned off. You cannot completely turn it, or at least the trigger for it off. So , for example, you are playing Logic and you have the Finder as the front most app and you fire off an error by doing something wrong in Finder, this will trigger an error notification in Core Audio. Logic might stutter, or throw an error such as you are seeing. Pro Tools is even less tolerant and almost always throw an error when an Apple alert fires off. You can re-nice (using CPU Setter, or the Terminal) Logic or ProTools to -20 to give it greater priority, but does not completely solve the issue. BTW this is mattrixx (long time forum member), using a different browser, as this forum goes all weird in Safari for me and I cannot make posts normally with it. this looks like a real bug to be reported to Apple? I would also like to know if the is a bug report list. I have other suspicions, like my display 2 not activating after sleep. I have to connect disconnect the cable and then starts. My "background sounds" also does not work anymore . Stream DEck is totally black for weeks now, after me starting it in tnhe wrong usb cable (weird). But i did not check these things yet, i dont have time to research each issue, really. This is why tech problems suck ; ) But regarding Logic, people are welcome to tell the mac studio stories here. WHen i get system overload message doing some basic simple music in Logic i do like with a woman rejecting me: i don´t take it so seriously anymore and move on lol Edited March 23 by emanuel_froes Quote Link to comment Share on other sites More sharing options...
analogika Posted March 23 Share Posted March 23 I notice from your Activity Monitor (Aktivitätsanzeige) that Logic is running in Rosetta (Intel mode). Is there a reason why you've set it to open in Rosetta? Quote Link to comment Share on other sites More sharing options...
emanuel_froes Posted March 23 Author Share Posted March 23 1 hour ago, analogika said: I notice from your Activity Monitor (Aktivitätsanzeige) that Logic is running in Rosetta (Intel mode). Is there a reason why you've set it to open in Rosetta? because this is the advice, untill all companies are updated to m1, and because I had issues running native Quote Link to comment Share on other sites More sharing options...
analogika Posted March 23 Share Posted March 23 55 minutes ago, emanuel_froes said: because this is the advice, untill all companies are updated to m1, and because I had issues running native Huh. Still, though? M1 has been out for 2 1/2 years… 44 out of 46 of my software vendors are at least officially compatible with Rosetta, 35 of those are native. The only ones I've had any issues with, running Logic native, have been Waldorf and Plugin Alliance plug-ins, but those have to do with Ventura, not Apple Silicon. I do make sure that all my plug-ins are up-to-date as far as possible, though — and I maintain a comprehensive list of all my software vendors with links to compatibility statements, updaters, and checkmarks for official certification. Quote Link to comment Share on other sites More sharing options...
emanuel_froes Posted March 28 Author Share Posted March 28 On 3/23/2023 at 8:43 PM, analogika said: Huh. Still, though? M1 has been out for 2 1/2 years… 44 out of 46 of my software vendors are at least officially compatible with Rosetta, 35 of those are native. The only ones I've had any issues with, running Logic native, have been Waldorf and Plugin Alliance plug-ins, but those have to do with Ventura, not Apple Silicon. I do make sure that all my plug-ins are up-to-date as far as possible, though — and I maintain a comprehensive list of all my software vendors with links to compatibility statements, updaters, and checkmarks for official certification. i will try again without roseta. 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.