As long as I can continue to play my audio files with it (not streaming), I'm fine with whatever changes to bring to it.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Bringing Native Apple Music Experience to Music App for macOS
- Thread starter MacRumors
- Start date
- Sort by reaction score
It's awful, but still largely functional. However, it really needs the lossless support from Apple Music integrated in.
The issue is that it won't download the lossless files from Apple Music. It only downloads/streams the 256kbps AAC. Yes, it supports various output, and playing a number of formats. However, that's not what i'm talking about.
Oh. Well that's stupid. There are a LOT of things that need to be fixed with the Windows version. They really need to prioritize their Windows apps. There are probably a lot more iPhone users with Windows than iPhone users with Macs.
I kinda wish they'd also fix GPS directions while listening to audiobooks on your phone in your car. Listening to music is fine. When Maps gives directions, it lowers the music volume, says the direction like "In 1 mile, turn left on Washington Street," and resumes the music. When listening to audiobooks, the GPS directions get cut off like "In 1 mile, tur-" and resumes the audiobook. Really awful!
It seems obvious to me that this has been coming for a long time. They've been carving out parts of the old iTunes experience into other apps, deprecating features from it, and slowly rebuilding the interface elements used by iTunes/Music in new apps and platforms for years. It sounds like they finally feel confident that they have enough and the pieces are in place to tackle the remaining tech debt and try to stand it all up as something new. As much as everyone likes to be a critic about iTunes, it's a 20-year-old code base that has continued to evolve and keep moving forward. I don't envy the teams responsible for it, but this is going to be the culmination of a lot of work and I commend them for it.
I'm sure the first release will piss off a lot of people because their obscure favorite feature will be missing, but personally, I can't wait to jump on this MVP.
I'm sure the first release will piss off a lot of people because their obscure favorite feature will be missing, but personally, I can't wait to jump on this MVP.
Last edited:
It would be nice if it could handle local stored music better than it currently does, whether bought on iTunes or Bandcamp, etc. It's annoying when I play a song I own and it tries to get me to subscribe. Also harder to keep track of what stuff you own versus what was in your Apple Music library when you were a subscriber, weird there's no 'Local' (purchased) tab without having to dive into the iTunes Store tab.
I wonder how many lines of code Music is? The article says it's going from one framework to Appkit, so I'm sure that that isn't a small undertaking. Plus, it has to integrate with a lot of things like the online Music library, the Finder so users can sync their music to iPhones, etc. So going to an entirely new codebase while also making everything else work this is no small undertaking. However, Apple definitely has the resources to do this, so it shouldn't take this long to do.
You can add a column (I think it's called "Kind," but not sure) in your songs library. It would have "Purchased/Protected AAC" if it's bought from the iTunes Store, and then whatever format if you imported from a CD or something (eg AAC, AIFF, ALAC, MP3)
GOOD!
iTunes was [mostly] great in the earlier days when it was powered by WebObjects. Then they moved to HTML and the experience was degraded from a performance and fluidity standpoint.
The launch of the Music app came with some relief that the experience might be better, but it hasn't been. Yes, it works well enough, but is slower than it should be. Definitely been minor improvements over time, but a radical rebuild to address that issue is awesome. Glad that Apple recognizes the need for this. They need to restore the original (earlier) iTunes experience that didn't feel like a slow-loading website.
iTunes was [mostly] great in the earlier days when it was powered by WebObjects. Then they moved to HTML and the experience was degraded from a performance and fluidity standpoint.
The launch of the Music app came with some relief that the experience might be better, but it hasn't been. Yes, it works well enough, but is slower than it should be. Definitely been minor improvements over time, but a radical rebuild to address that issue is awesome. Glad that Apple recognizes the need for this. They need to restore the original (earlier) iTunes experience that didn't feel like a slow-loading website.
Haven't launched that horrible excuse for an app since I switched to Spotify more than a year ago. It's almost like Apple purposefully tried to lose customers, Doubt I'll go back.
I'll reserve judgement until it ships, but recent history tells us that an app rewrite is for apple an opportunity to remove features and replace them with bugs.
I still think that Apple should upgrade all (or as many as possible) of its frameworks/libraries in macOS, iPadOS, iPhoneOS, etc. to Swift, and then rebuild all its first party apps to use said frameworks. It's embarrassing how little Apple uses its own tech.
F-I-N-A-L-L-Y.
I've always hated Apple Music on the Mac because, come on, it's clear that it's just a website.
It's slow.
It's buggy.
It lacks life and energy.
I always have to double click twice for a song to play.
Clicking on things to dig through also doesn't work well.
And the search box is completely broken in Monterey.
I've always hated Apple Music on the Mac because, come on, it's clear that it's just a website.
It's slow.
It's buggy.
It lacks life and energy.
I always have to double click twice for a song to play.
Clicking on things to dig through also doesn't work well.
And the search box is completely broken in Monterey.
If the Music app is being rebuilt in AppKit and
Why rebuild the Apple TV app using JET rather than AppKit?
The main thing it needs is more caching. There's no need for Music.app to go to servers again when I hit "back". Just show what was there before; I doubt a new album or song was released in the last 30 seconds.
Well, this thread has been more than sufficient to dissuade me from upgrading from Mojave. I almost thought I might, this time. I have about 250GB of local music, meticulously catalogued, nor do I use Apple Music, so I see no advantage in “upgrading” my experience in this area.