Possible transcode / playback error?

Issue description:

Experiencing issues with playback of WMA files where the song will stop playing and skip to the next track partway through (variable exactly when - sometimes it’ll refuse to load the song altogether, sometimes when it’s ~90% finished). MP3 and OGG files don’t appear to be impacted. The issue has only started recently (last couple of days).

The uploaded log captures the issue. Before I captured the log, I did a full restart of my local Navidrome server, my phone, and cleared the Symfonium app cache to rule out (I hope) any of that weirdness.

Forcing transcoding on the Navidrome end seems to avoid the issue, since WMA gets converted to OGG before it hits Symfonium. I’ll probably leave that setting on for now and see how it goes, but I wanted to give you the log in case it’s an app error and not a my-server-is-just-wonk error :slight_smile:

Logs:

Upload description: azuredragon113.log / Log containing errors that I believe are linked to local transcoding from WMA (unsure if it’s related to my Navidrome server or to the app so I will let you be the judge of that :slight_smile: )

Additional information:

 
My phone does occasionally lose connection with my Navidrome server. I tried to capture a time when that wasn’t happening (and I did set a playback cache, which tends to help). With cache enabled and playing MP3 or OGG files, I rarely notice the network drops
 

Reproduction steps:

 

  • Start playback from track mix
  • Playback hits a WMA file
  • Song playback halts partway through and skip to next track
  • If the next track is WMA, repeat
     

Media provider:

Subsonic

Screenshots:

     

Probably a duplicate of Music stops and skips while using Android Auto

But in the logs there’s many errors because the server name is not resolvable.

This does sound exactly like my issue. And it seems like my attempts to solve my network issues have a ways to go yet :sweat_smile: Thanks for the response! For now I’ll make sure WMA files are transcoded on the server end, since that seems to avoid the issue so far.