Twitter | Search | |
🆆il 🆂hipley, his arms wide
It’s almost impressive how inefficient the Music app and AirPlay are on the latest macOS. This is on a top-of-the-line 2019 MacBook Pro 16”. I don’t...I kinda don’t know how you could even make something this slow. Is it logging every packet?
Reply Retweet Like More
🆆il 🆂hipley, his arms wide Dec 11
Replying to @wilshipley
I used to run NeXTstep back in 1988 and it could handle outputting 2 channels of 16-bit audio at 48 KHz no problem. Didn’t take up very much of the 68040’s single 40 MHz core, and new machines have 2.3 GHz cores. So, you know audio today is only 1000x as inefficient or so.
Reply Retweet Like
🆆il 🆂hipley, his arms wide Dec 11
Replying to @wilshipley
Ok when I brought Music to front and hid it, it suddenly stopped burning CPU - now they’re at 2.8% and 1.0%. Crazy. This is feedback issue FB7490500 for my Apple tweeps.
Reply Retweet Like
Daniel Fox Dec 11
Replying to @wilshipley
I’ve done packet logging and it doesn’t take this much CPU power.
Reply Retweet Like
🆆il 🆂hipley, his arms wide Dec 11
Replying to @danudey
I have no idea what was triggering it but it decided to heal itself after I showed/hid the app. Luckily I got a sample from before so maybe Apple will figure it out. It seemed to be spamming itself with (spurious) volume changes notifications.
Reply Retweet Like
Hannes Oud Dec 12
Replying to @wilshipley
Does it trigger the fans on the 16“ if one or two cores are doing this kund of constant work?
Reply Retweet Like
🆆il 🆂hipley, his arms wide Dec 12
Replying to @hannesoid
Nope.
Reply Retweet Like
Costantino Pistagna Dec 12
Replying to @wilshipley
agree, also occurring on mbpro 15”
Reply Retweet Like