Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Bill Av

macrumors 6502
Original poster
Oct 21, 2006
285
207
I know this is not a solution, but I have joined Apple one and it seems that if you have Apple Music the problem goes away and everything works.

All my NON Apple Music that I had that did not work previously, are now working!
Interesting to know. I wonder if you lose that functionality if you leave the service. Does joining Apple Music do that "upgrade" thing where it takes over your personal music library and replaces your files with higher bit rate files? I'm not interested in that
 

hammie14

macrumors regular
Mar 18, 2010
247
145
UK
Interesting to know. I wonder if you lose that functionality if you leave the service. Does joining Apple Music do that "upgrade" thing where it takes over your personal music library and replaces your files with higher bit rate files? I'm not interested in that

If you look back at my posts you will say I posted saying that the bug was fixed. It was in fact that I had a trial of Apple Music which I canceled.

The songs continued to work even when canceled, BUT if you then restore your phone and re sync your library then it seams to go back to being screwed!

I am going to keep the Apple one service as I will be saving money, I know its not for everyone but seems like the problem is solved for me. I have reporting the bug to apple and supplier information but they don't seem to act on it!
 

throw19

macrumors newbie
Feb 23, 2020
8
1
Does this problem affect all Apple Watch users who try to play their own music?

I just reset both Apple Watch and iPhone, and the set them up as new devices, but the problem persists.
 
  • Sad
Reactions: Zanton68

throw19

macrumors newbie
Feb 23, 2020
8
1
I tried the method of changing the Album ID of m4a files and it worked for the first album, but it didn't work afterwards and then the first album failed also, not sure why.
 

Zanton68

macrumors 6502
Sep 24, 2012
315
219
UK
Hi! Anyone with latest iOS 14 and WatchOS 7 Betas to check if this problem persists?

Thanks a lot!

Yep. Still persists. Apple standard response, wipe everthing, restore etc etc etc. They are a multi billion dollar company. I think they should fix it.
 

throw19

macrumors newbie
Feb 23, 2020
8
1
I tried the method of changing the Album ID of m4a files and it worked for the first album, but it didn't work afterwards and then the first album failed also, not sure why.
I found out why this didn't work. The Kid3 tagger program was actually converting the field "Album ID" (as typed) into "plID" (as stored). If the actual field was just "Album ID" then it'd fail. So the better method is to Add a "plID" field directly and enter an album ID value, and then it would work.

Current observations:
- album covers of the added m4a files don't work on my Apple Watch, even though they're visible on iPhone
- this is an INSANE method when dealing with more than a few albums. Unfortunately, this is the only way I've so far been able to get playback to work in more than a year. To get my full library to work, I'd need to:
* make an m4a copy for all my music (huge wasted space)
* find another command line tool like the aforementioned forked version of AtomicParsley (which is no longer available), or develop such a tool myself
* write my own script to automate the process for all my files. I didn't know consumers need to be actual programmers in order to do something as complex as playing a song on an Apple device.

Opinion: Apple Watch is currently an insanely bad solution for my needs -- by far the most unfriendly music playback tool I have ever encountered, considering how much work is needed compared to probably every mp3 player in history. The number of steps required to achieve the intended function is absurd considering the totally basic nature of the function. And, seeing that such a problem remains unfixed after a year, it is not irrational to assume that it may never be fixed, especially if the company has an incentive to ignore the bug so that more consumers may be encouraged to buy their music subscription service; that's assuming the company did not plan all this on purpose in the first place.

I would likely never buy another Apple Watch or recommend it to anyone unless this is fixed.
 
  • Like
Reactions: boazf

masterjorn

macrumors newbie
Jan 25, 2020
4
1
CA, United States
Add me to the list 😭

it sucks because I got the watch specifically so I could more easily change music while driving. And when it didn’t work (while I was driving btw...) I was a bit miffed, glad I’m not the only one experiencing this though. It sucks even more knowing this issue originated a year ago, and is still happening on my 3 week old Apple Watch SE 😥.

Running iOS 14.1 on an iPhone 8 Plus, and watchOS 7.0.2 on an Apple Watch SE, if that helps.
 

Bill Av

macrumors 6502
Original poster
Oct 21, 2006
285
207
Despite what I wrote in an earlier post, I bought an Apple Watch Series 6. I had a reason for it other than "I need the latest gizmo". I had zero expectations that it would fix any of my AW issues. But anyway, yeah, it didn't fix any of my issues, including the music control problem. Just figured I'd let everyone know.
 
  • Like
Reactions: Zanton68

Bill Av

macrumors 6502
Original poster
Oct 21, 2006
285
207
Anyone found a fix for this yet ? 🤔
Not me. My work around even has a problem. Asking Siri (through my EarPods) to play an album causes her to say “Apple Music is having a problem” every time. But then the album starts.
 
  • Like
Reactions: Zanton68

boazf

macrumors newbie
Jan 14, 2021
3
0
Apple's engineers are obviously never going to figure this out so I'll give you the actual problem and its solution.

Your AAC files contain MPEG-4 audio metadata which tells your playback software how they should be grouped. These tags live inside the moov.udta.meta.ilst namespace. While the Music apps on the Mac/iPhone/iPad all group by album artist + album name (aART + @ alb), which is a sensible solution, the Apple Watch developers (in their infinite wisdom) apparently decided to make their version of the app group by plID, which is a unique numeric ID that Apple uses to identify the album in the Apple Music (iTunes) store.

You know, because Apple is the only place in the world to purchase music and every album ever made is available from Apple and why would you even think about buying your music from anyone else but Apple?

Of course, this means that the Apple Watch will only correctly play files that have the plID tag. This is why the files that you buy from Apple work, but any files you download from other vendors, or from CDs you've ripped yourself, won't work.

Fortunately, there is a solution to defeat Apple's anti-competitiveness, but it will take some work on your part. You need to create a unique plID for every album in your collection, and use a tool to update your files to set that value on each of your music files. I use a modified version of AtomicParsley (command line tool) for this so I can script the updates, because doing this with a graphical tool for thousands of files in my music collection would be ridiculous.

You run the command like this:

$ AtomicParsley yourfile.m4a --plID 123456789

You can also list all of the current tags on your file by running this command:

$ AtomicParsley yourfile.m4a -t

Every track in a particular album should have the same plID, and every album should have a different plID. Unfortunately, if you use a different plID than the one Apple uses in their store, then the "View Album" feature won't work because it doesn't know where to go to. You can get the plID by copying the large number out of the Apple Music URL, for example for this album
the plID should be 201281514.

Try this on one of your albums, then add that album to the Music app on your Mac and sync it to your iPhone, and see if your Apple watch is able to play it back.
Dave, thank you very much. This is the most helpful post that I find in this thread. I tried your approach and I find it almost accurate. It is possible that since the time that you posted this iPhone/watch was/were modified. I found that plID cannot just be any random number, it should be a valid ID from apple music. Not necessarily the one that is assigned to the specific album, just any existing ID of any album. And the ID must be different for each album. What I also noticed is that you may assign plID just to the first track of each album. This possibly indicates that internally iPhone duplicates lpID to all other tracks while syncing the album. But this is only a guess. However somehow it works when assigning lpId to only the first track.

I used ATL (Audio Tools Library) instead of modifying AtomicParsley. You can find it here: GitHub

I hope that Apple will eventually fix this. I'm surprised that this bug already exist for so long. Perhaps this is a feature intended to force us to use apple music? If this is so, I'm done with Apple. Enough is enough.
 

davehensley

macrumors newbie
Jun 28, 2020
4
6
I hope that Apple will eventually fix this. I'm surprised that this bug already exist for so long. Perhaps this is a feature intended to force us to use apple music? If this is so, I'm done with Apple. Enough is enough.
Yeah, they will never fix it because they *want* this behavior. Many of us have reported it via Apple's (generally useless) bug reporting tool. My report has been sitting in Apple's queue for many months, with no response from them. And it's still "broken" (as intended) on watchOS 7.3 of course.
 

Bill Av

macrumors 6502
Original poster
Oct 21, 2006
285
207
Anybody beta testing iOS 15 with any news on this bug? I assume that it’s still there.
 

ZipZapRap

macrumors regular
Jun 1, 2011
159
1
Add me to the list of people this is broken for. Just got my new Watch today (first ever, Series 6) and absolutely gutted this doesn’t work. I want to choose my music when I’m out for a run but apparently can’t.

what a joke. Get your act together, Apple. The solution isn’t for me to sign up to your subscription service. I don’t spend more money on a service when the initial experience is inferior; I don’t spend money to fix a problem that should work
 

verdeel

macrumors newbie
Jan 2, 2020
1
0
Dave, thank you very much. This is the most helpful post that I find in this thread. I tried your approach and I find it almost accurate. It is possible that since the time that you posted this iPhone/watch was/were modified. I found that plID cannot just be any random number, it should be a valid ID from apple music. Not necessarily the one that is assigned to the specific album, just any existing ID of any album. And the ID must be different for each album. What I also noticed is that you may assign plID just to the first track of each album. This possibly indicates that internally iPhone duplicates lpID to all other tracks while syncing the album. But this is only a guess. However somehow it works when assigning lpId to only the first track.

I used ATL (Audio Tools Library) instead of modifying AtomicParsley. You can find it here: GitHub

I hope that Apple will eventually fix this. I'm surprised that this bug already exist for so long. Perhaps this is a feature intended to force us to use apple music? If this is so, I'm done with Apple. Enough is enough.
ATL is a library, is there a program that is ready made that uses this library? I don't know enough (yet) of .Net to write my own simple program to use this.
 

Kelchwid

macrumors newbie
Sep 23, 2021
2
0
Le bout du monde...
Still persists in iOS 15 + watchOS 8 🤬
Yes it persist on IoS15 and watchos8 … and I don’t want using Apple Music service for the moment.

I have making some reset an I see ten or eleven device on health..
I don't want to erase because I have activities that I want to keep.... Besides, the loading of the exercises is very slow…
The gps is still not accurate on the exercise application, I lose a lot of meters…
Every topic was discussed with Apple and I never got a solution.
All of these since installation of the iOS13 beta may be?!?
All these problems must come from iCloud because my son recovers my old watch and phone and he has no problem… I’m jealous ! 🙈
 

boazf

macrumors newbie
Jan 14, 2021
3
0
I don't believe my eyes and ears, this was resolved. I'm using IOS 15.0.2 + WatchOS 8.0.1. I can play any track or album from my iPhone music library by selecting it from the music app on my watch. Also albums that I ripped and uploaded to my iPhone. I definitely couldn't do it before.
Sorry, this was an incorrect message. Apparently, this is working for me because I recently activated my apple music subscription. I cracked because they started to support lossless music. I will probably discontinue this subscription and will remain with my Tidal subscription which I like better. So I will surely hit this problem again.
 
Last edited:

slowpoke

macrumors regular
Oct 13, 2007
131
81
Bellona
Just got my first Apple Watch and immediately ran into this bug and oh my god this very fundamental feature has been broken for two years????? Oh my god.
 

boazf

macrumors newbie
Jan 14, 2021
3
0
Just got my first Apple Watch and immediately ran into this bug and oh my god this very fundamental feature has been broken for two years????? Oh my god.
From Apple perspective this is not broken. This is how it meant to be. They want us to buy Apple music subscription. If you have this subscription, everything works.
 

slowpoke

macrumors regular
Oct 13, 2007
131
81
Bellona
The least they could do is be honest about it being an (arbitrarily) subscription-gated feature.

Also, I happened to buy a pair of beats headphones that came with an Apple Music trial today, and I decided to activate it to see if it fixed the issue like that other poster suggested it would... nope, still just as broken as before.
 

Bill Av

macrumors 6502
Original poster
Oct 21, 2006
285
207
It looks like MP3Tag can now edit an MP4 file's plID tag in version 3.07 or later (they call it ITUNESALBUMID apparently). I haven't tried it, but this might be useful for those who wanted to download the now-deleted AtomicParsley fork. https://www.mp3tag.de/en/download.html
I picked it up on the Mac App Store. I bought an album, tagged it and transferred it to my iPhone. I was able to initiate playback from my watch, so it seems to work. I did a few more albums that I had in my Music library, but they didn't sync over. I expected this, as changing metadata doesn't cause a file to transfer over when you next sync - you've got to remove it from the phone first.

Anyway, I'll play with it over the next few days and decide what I'm going to do. Adding the Album ID to 2500 albums would be time consuming. There's no menu item to directly add this metadata (if there was, I could have made a keyboard shortcut to quickly access it), so just getting to the AlbumID entry requires a few steps for each album.

I see in the preferences that you can add any field to the tag panel. That simplifies it a ton.

Update

It’s been a few days and I think I can safely say that this works. I can control music that I’ve added AlbumID to. However, you can’t just edit the metadata while the files are in your library; you have to import the files into Music/iTunes after the metadata has been added. No surprise, but adding AlbumID does nothing if the track is an MP3; it’s got to be an AAC. You can add AlbumID to ALAC files, but I don’t think the info carries over if you use iTunes to convert it to AAC.

For music that isn’t available in the store, you can seemingly use another album’s ID without an issue - it won’t change the album title or track names. One caveat: you may get different album artwork if you don’t have artwork embedded in the files. I would say that you shouldn’t use an AlbumID of something that you may get in the future.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.