![]() ![]() ![]() The 11 unsigned apps are audio plugins – not the issue – this problem predates them and persisted before I finally got them installed end of last month. I've cleared library/cache, launch daemons, unfamiliar and familiar startup items that I haven't used in a few months, etc. I've run several Safe Mode restarts but will be doing another after this post, in addition to an SMC reset. Also, always starting an edit with a new empty project file (rather than 'Save As' of a previous project) in Audition has been a godsend. Moving all pro-audio related files to a fast external M2 drive and basically clearing out iCloud has been a huge help. (Can time machine really not travel back to a previous OS?!?) I've got whatever PTSD happens after a dozen failed 'restore from time machine backup' attempt. If there's a way to simply weed out the bad now that I'm down >100 hours and a few weeks behind on work I'm dying to know. Is this because in Migration Assistant I restored user data? If you advise against that, how do I retain useful user data while not restoring any 'problematic' aspects? Or is that a lost cause? Must start from scratch and omit user data (please say no!). Now that they're close to former speed and glory, I'm still seeing an occasional 100% CPU for finder or quicklook. I've done a 'clean' reinstall, restored from backup (not applications), upgraded from Catalina to Monterey, and cleaned out all superfluous apps, launch items, and daemons.įinally had a breakthrough with one major issue of not being able to use 2 popular DAWs (Adobe Audition and Ableton Live 11). Playback of short sequences of edited WAV audio clips in widely-used DAW apps grinding to a halt, dropped frames, hanging for >10 s after I hit the play button– whereas it previously played almost instantaneously. Fans go berserk kernel stuff obviously related to the turbo CPU and 10 cores running at full bore. Very high CPU loads for simple native processes, like 50-100% for Finder, quicklook, WindowServer, kernel_task, >1,300% for 'mds' or Spotlight/indexing-related processes, etc. Or, let me down easy–I'll take 'unplanned' neglect-based phenomena, entropy, schmutz, dust, hardware malfunction, or a physical bug. I'm not a conspiracy theorist, but please help convince me it's not planned obsolescence, LOL. Secondarily, are you running a similar machine that is about as fast as it was when you got it? What OS? Are you by any chance also able to run Adobe Creative Cloud apps and/or Ableton Live or a similar pro DAW? How do you do it, pray tell?! Main Request: How do I quash this sabotage-like activity and get my system back up to speed? The rest offers more granular detail, but is summarized in the EtreCheck Report above. Is this a normal fate for the fastest iMac from three years ago? Main culprits: >1000% CPU-hogging Apple native processes that never used so much load before. Can you solve this paradox: 2020,2 iMac (3 years old) with the fastest CPU, max RAM, and fastest internal SSD available in 2020 yet, it ground to a near-halt last month. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |