[BUG] - .flac 1625 kbps track is not played

[wazolab]

Describe the bug

My .flac 1625 kbps track isn't played at all. But I can play it on my Navidrome server. Other .flac let's say 817 kbps are played nicely.

Expected behavior

I would expect .flac 1625 kbps to work on Tempo app unless not compatible somehow ?

To Reproduce

Environment

• Android device: Xiaomi Redmi Note 5
• Android OS version: Android 9
• App version: 3.6.0

Logs or Screenshots

[CappielloAntonio]

Yes, high bitrate should not be an issue. To demonstrate this, I tried to play a track with a bitrate of 1762kbps and everything went smoothly. Are you sure the file isn't the problem? Is the server logging anything meaningful?

Could you possibly log the error or, as a last resort, pass me the audio track?

[wazolab]

Here is the log when I'm trying to play from Tempo App (which doesn't work):

Feb 19 10:33:55INFO[48307] Streaming file artist=Vald bitRate=0 cached=false format=raw originalBitRate=1625 originalFormat=flac requestId=a0ad86d6-7d39-44ca-a886-10e4822f4d91/XqhMj4bJnq-005115 title=FORFAIT transcoding=false user=**** username=****

Here is the log when I play the same song from Navidrome UI:

Feb 19 10:36:23INFO[48456] Now Playing artist=Vald player="NavidromeUI [Chrome/Linux]" requestId=a0ad86d6-7d39-44ca-a886-10e4822f4d91/XqhMj4bJnq-005144 title=FORFAIT user=**** username=****
Feb 19 10:36:23INFO[48456] Streaming file artist=Vald bitRate=0 cached=false format=raw originalBitRate=1625 originalFormat=flac requestId=a0ad86d6-7d39-44ca-a886-10e4822f4d91/XqhMj4bJnq-005145 title=FORFAIT transcoding=false user=**** username=****

For info the whole album isn't working on Tempo App, but does work on Navidrome Web UI ... I could send you a track file if you want ? Maybe here: https://www.sharedrop.io/rooms/d245aeac-b575-417c-8c8e-89c1d4b6a932

[CappielloAntonio]

For info the whole album isn't working on Tempo App, but does work on Navidrome Web UI ... I could send you a track file if you want ? Maybe here: https://www.sharedrop.io/rooms/d245aeac-b575-417c-8c8e-89c1d4b6a932

Yes please. Even a single track.

[wazolab]

For info the whole album isn't working on Tempo App, but does work on Navidrome Web UI ... I could send you a track file if you want ? Maybe here: https://www.sharedrop.io/rooms/d245aeac-b575-417c-8c8e-89c1d4b6a932

Yes please. Even a single track.

as soon as you connect to P2P link I'll drop the file then

[CappielloAntonio]

Ook, I'm an Enthusiastic Penguin

[wazolab]

Ook, I'm an Enthusiastic Penguin

Sorry I was out for a while, waiting in the room as Charming Sheep

[CappielloAntonio]

Hi Charming Sheep, I'm Sincere Monkey

[CappielloAntonio]

Okay, now I can run some tests.

[CappielloAntonio]

Really strange, I can play the song without any problem. I can stop, jump from one point to another, go forward and backward. If you want, and you're free to say no, we can try directly with your server. You can create me a test user, and give me limited access for a few minutes, just long enough to debug the problem.

[CappielloAntonio]

Okay, thanks so much! You can now delete the message and message history with your credentials. As soon as I can I will test on your server.

[CappielloAntonio]

I actually did a quick test with the affected songs. As you can also see from the logs, the song is from the same album, and on my device it seems to run without any problems.

Now I don't know if I should blame the server or the device. Is there any way to try the app on a device other than yours?

[wazolab]

Ok, then it might come from my phone ... I will try with another phone and let you know :) Thanks a lot for your time !

[CappielloAntonio]

This section on Media3 library's troubleshooting page may be related to your problem. They talk about video, but the problem could also extend to high bitrate audio files.

[wazolab]

If I constraint Navidrome with transcoding OPUS - 128kps and set the same in Tempo (maybe it's useless as the server decides what to share with the client), it WORKS ! Then it looks like a device limitation.

[CappielloAntonio]

It makes sense, after excluding apps and servers the problem had to be elsewhere. I'm closing this issue then, feel free to reopen it should there be any other problems related to it.