Beta has been out for a few days now. Has anyone actually tried the Music app and seen any difference in performance?
I specifically turned off Sync because of this. A good chunk of my music is from other sources ("Included digital download" are my 3 favourite wrods), a good chunk of my music is not on iTunes, and I LOATHE having to do EVERYTHING on my phone when it comes to creating playlists.Did they ever fix that issue where if you quit Apple Music it deletes not only all your Apple Music downloads but a bunch of your purchased music and songs ripped from CDs as well?
original post said:The move will lead to significant improvements to the performance and experience of using the Music app, but no significant UI or interface changes.
It does have lossless. It just looks like it’s from 1995.
That's literally what they have done. It's all native now.The problem with the Music app is that it is essentially two apps in one.
The old iTunes app and then bundled in, essentially a browser that renders AppleMusic.com.
They really should make a decision, are they going to go full browser like Spotify or are they going to full native like iTunes used to be. The half-way house is the problem.
Oh you really really REALLY don't want to be using iTunes on Windows. I run iTunes on Monterey, but I stick to the web interface on Windows.When I move to a new version of macOS on my Mac, I'll be moving my iTunes environment to a Windows machine.
Oh my god yes
I’m reasonably satisfied with Apple Music as a service but using it on macOS is just painful with the disguised webviews constantly messing up
Hopefully they will also make the navigation less counter intuitive
This guys found a way to bring iTunes up to Big Sur, might work for Monterey as well, but I did not tested itIn other words, same awful interface, but with the ability to push crappy recommendations and thinly disguised ads for Apple "services" faster than ever!
You say that like that's a bad thing. 🤣
Even if it's not the most "elegant" interface, iTunes made a lot of sense for people who like to manage their own music and podcasts. I've kept my home mac on Mojave specifically to avoid Apple's newer media apps, but I do need to move to a newer OS for other reasons. When I move to a new version of macOS on my Mac, I'll be moving my iTunes environment to a Windows machine.
Works perfectly on Monterey, but not for Apple Silicon unfortunatelyThis guys found a way to bring iTunes up to Big Sur, might work for Monterey as well, but I did not tested it
![]()
GitHub - cormiertyshawn895/Retroactive: Retroactive has been discontinued. You should transition from Retroactive to supported apps such as Music, iTunes for Windows, iMazing, Photos, Darktable, Lightroom Classic, and DaVinci Resolve.
Retroactive has been discontinued. You should transition from Retroactive to supported apps such as Music, iTunes for Windows, iMazing, Photos, Darktable, Lightroom Classic, and DaVinci Resolve. - ...github.com
Out of curiosity, what would you change?In other words, same awful interface
SwiftUI is not ready for prime time. And I’m not sure if It ever will be. Using it is a huge paradigm shift. The documentation for it is abysmal, and designing the whole UI in code, rather than visually with Interface Builder like you do with Appkit is a huge step backwards.My thoughts exactly. SwiftUI would be a much better choice and would allow Apple to share significant portions of the code between platforms.
It is a paradigm shift, yes, but in a good direction. And you can still build your interfaces visually using the Canvas. SwiftUI just simplifies development and state handling dramatically.SwiftUI is not ready for prime time. And I’m not sure if It ever will be. Using it is a huge paradigm shift. The documentation for it is abysmal, and designing the whole UI in code, rather than visually with Interface Builder like you do with Appkit is a huge step backwards.
And It doesn’t really make it much easier when writing cross-platform code. Too many things don’t work the same. Too many gotchas.
I’m not sure what apple are thinking TBH
Unlikely. They'll want to have as broad backward support as they can to keep subscribers. Also, while I know nothing about JET, if it's a web technology there would be nothing in the code that would require the new architecture or be handled inherently better by it.Wonder if it’s for M1 boxes only.
I would bet money that it's at least not backward compatible in the initial release.I hope scripting is still supported and backwards compatible.. there are many apps and plugins that rely on iTunes automation.
Yep - latest release isn't any better. Maybe they are waiting for the next OS in June? HD660s awesome headphones BTW...still waiting lol got my hd660s ready with amp dac at hand can’t wait
Sorry to awaken an old thread!SwiftUI is not ready for prime time. And I’m not sure if It ever will be. Using it is a huge paradigm shift. The documentation for it is abysmal, and designing the whole UI in code, rather than visually with Interface Builder like you do with Appkit is a huge step backwards.
And It doesn’t really make it much easier when writing cross-platform code. Too many things don’t work the same. Too many gotchas.
I’m not sure what apple are thinking TBH
It's a native rendering of the Apple Music backend. Anything AM related that was rendered as a webview before is now much more responsive.Well we still don't have that native app...
It's a native rendering of the Apple Music backend. Anything AM related that was rendered as a webview before is now much more responsive.