View Issue Details

IDProjectCategoryView StatusLast Update
0021729MMAPlaybackpublic2025-10-13 10:58
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status resolvedResolutionreopened 
PlatformAndroidOS-OS Version14
Product Version2.1.0 
Target Version2.1.1Fixed in Version2.1.1 
Summary0021729: ?WMA? playback not working (missing codec error - regression 2.1)
DescriptionThe user at ticket 13516 / 13519 (contains saved log) is experiencing the missing codec error after having upgraded to build 1268.

I'm unable to replicate, but logs have been provided:
PQWD14IHK6
K99MR1FMKL

EDIT: It turns out that this is because the tracks in question were WMA, which MMA does not yet support.
Additional InformationAlso reported at 13688 (this user experienced the issue on a OnePlus device and has enabled auto-conversion to work around the issue).
TagsNo tags attached.
Fixed in build1282

Relationships

related to 0021035 closedmartin M4A (ALAC) support 
related to 0021806 newmartin Playback stops partway through a track 

Activities

martin

2025-08-14 07:39

developer   ~0079331

The user attempts to play WMA tracks. They've never been supported natively on Android. Therefore, the toast message and skipping to the next track are correct behaviors in this case.

rusty

2025-09-26 14:56

administrator   ~0079632

Last edited: 2025-10-01 15:26

This issue is still being reported by numerous users (unclear whether it's limited to WMA):

Play Store:
Andrew S - "Often it just jumps from track to track without playing anything. Sometimes it looks like it's playing but no sound comes out. The last time I tried to use it I picked a song from one album and every single time I tried to play it, it just jumped to a completely different song on another album. It's not the music library. I can play the same songs perfectly with other players"

Rune O - S23 Ultra - "Used to work, but now stops all the tme. Totally unusable"

Drizzle - Galaxy A50 - "Knocking off another star for the missing codec error that was supposedly fixed."

GQUSAZH5VA - Android 16/Motorola

Ticket 13854 (D. Furtney) - Switching to Native doesn't solve the problem
Ticket 13878 (W. Kiely)
Ticket 13773 (Cap) - Switching to Native solved the problem.
Ticket 13911 (Mike) - Switching to Native did not solve the problem. Issue occurs with WMA and some MP3. Debug SS5Q8ZP8D5

https://www.mediamonkey.com/forum/viewtopic.php?t=108561

rusty

2025-10-09 16:17

administrator   ~0079768

Last edited: 2025-10-09 16:36

Ticket 0014002 indicates that: the following MP3 podcasts fail with codec errors in MM and play in other apps:
Star Wars Book Club (https://audioboom.com/channels/5106290.rss)
Chilluminati (https://audioboom.com/channels/5031584.rss)

I was able to replicate the missing codec problem on a Pixel 7 with both of these podcasts (using the 5 most recent episodes of each).

martin

2025-10-09 17:44

developer   ~0079769

Last edited: 2025-10-09 21:22

Finally, the MP3 format, not WMA.
I was able to replicate it with these tracks, too.
So I've fixed it into build 2.1.1.1282

EDIT (by Rusty): the problem occured when TLEN from ID3, was empty (incorrectly).

rusty

2025-10-09 21:29

administrator   ~0079770

As to the remaining issue of lost WMA support on devices that include a WMA codec, would it make sense to 'Solve' this by issuing a different error for such tracks? e.g.
a) Automatically switch to 'Native'
OR
b) display an error:
"<format> tracks are unsupported with the current Playback engine."
"Try switching Options > Playback engine to 'Native'."

martin

2025-10-13 10:58

developer   ~0079791

Yes.
If only the Exo player fails, then "Playback engine: native" toast message appears. (I wanted to use existing text)
If both players fail, the MMA skips to the next track, and "Skipping tracks (missing codec)" toast message appears.

Fixed in build 2.1.1.1282