Is Bug Sur already out as a public beta? Or was it just iOS/iPadOs/tvOS so far for public? I am on the developer betas, but I’m unsure if Big Sur is on that public beta list. Genuinely asking for a friend.
Is Bug Sur already out as a public beta? Or was it just iOS/iPadOs/tvOS so far for public? I am on the developer betas, but I’m unsure if Big Sur is on that public beta list. Genuinely asking for a friend.
@odd you know... Bug Sur has been pretty stable. I’m still convinced that they could release this tomorrow and it would beat Catalina out the water.
@vincent OK, that sounds great then 😃👍 Personally I can’t justify forking over more💰💰to Apple right now, so I’ll have to be on Catalina and High Sierra respectively for the moment. Maybe if I win the lottery, there will be something with Apple Silicon 🤑
@vincent Am I the only one without issues with Catalina ? Other than the annoying bit with Photos.app, which I believe is not Catalina-only, I have no problems whatsoever with it. Old Air too...
@maique it’s gotten better for sure, but is riddled with paper cuts since the beginning... and those cuts add up.
@jemostrom @davidrmunson Glad I’m not the only one happy with it. I’ve seen so many people unhappy with it on social media I was starting to believe I was somehow lucky to have it working (almost) flawlessly.
@maique I had a pretty annoying issue with the Music app where it used 100% CPU all the time. I was able to fix it by making a new music library. Other than that, everything has been good.
@tgray My Photos.app is always running like crazy, most times at over 100%, it’s awful.
Left Music for Spotify a while ago, so that one is not a problem I have at the moment. Glad you fixed it, would love to apply your tip to the photo library, not sure how that would work... maybe some investigating is in order.
@maique The music thing was some bug with album art lookup (I think). I have a lot of local ripped music. I ended up exporting my library as an XML file and reimporting it as a new library. No one else on the internet seemed to be having the same problem as me, so it's not common.
@maique @tgray - How long has Photos.app's processes been pegging your CPU? Is it because you imported a large set of photos into it? You know what I'm dealing with
@cdevroe Photos has been going on like this forever. The same processes as you mention. Finding faces, I believe. There are close to 90000 photos there now, I’m always importing “large” sets, that’s what I do for a living, and now, with the baby, it’s getting even worse 😂
@tgray I do take a lot of photos with the iPhone, and edit another huge amount on the iPhone, from the cameras. The library has been growing for years now, and I can’t seem to find a way to fix it. I want to clean it up a bit, but also can’t find a way to delete the photos. Trying to go through duplicates and bad ones on this scale is close to impossible.
@maique I'm operating at well above 100,000 photos and videos in my Library. Photos for Mac seems to perform just fine for the size of the Library that I have, it is the facial recognition part that seems to take a very, very long time. Otherwise, no speed complaints.
@cdevroe I could try that, yes. I really don’t use Photos on the laptop, there is no point in having it on the internal SSD.
@cdevroe And you have no issues with Faces when the library is on external disks ? It just does nothing when they’re not connected ? Is that it ? That would be enough for me.
@tgray I have recently had my fans spin up on a relatively idle machine with iTunes running, but not playing. Looking at the process list, it was a process that appeared to be doing something with album artwork or metadata. So maybe you're not the only one.
@maique I can open Photos when the drives are not connected. I can browse the photos, search the library, tag things, etc. It is using the thumbnails it creates. By leaving the files on external drive, my library file is “only” 41GB. If I need an original file, I mount the drives
@mcg So there was some discussion in the Apple forums about AMPArtworkAgent going nuts (like it did for me), but none of the solutions suggested worked. I also slaw some specific things mentioned in the Console that I never saw mentioned elsewhere, leading me to believe it was possibly a unique issue. I say search those forums for AMPArtworkAgent - if that is what is pegging your CPU - and they the suggestions. If those don't work, here is what I did.