With latest server version - 1.18.2.2029-36236cc4c and Android Beta app version 7.25.0.13736, it is back to square 1. Direct Play works as expected on home network. On Cellular, 1st song plays Direct Play and rest transcoded.
We’ve been talking about THAT bug for a few months… The issue with transcoding when local is what was being discussed here. Two different but similar issues.
Client: Beta version of Android client 7.25.0.13736.
Server: 1.18.2.2029
Played a FLAC album remotely via cellular data starting from track 1 starting 11/15 at 11:07 am.
First song direct plays and the following 3 display Transcoding / quality -1.
Logs attached for result of playing tracks 1-4 with sweet fades and volume leveling on. Playback started at 11:07. First song transition at 11:11. From looking at these logs it seems that the problem may strictly be cosmetic, meaning the player is displaying -1/transcoding but the file is actually direct playing?
If a Dev could just review this and verify that this issue is just cosmetic (wrong bitrate display) we may be able to close this issue. My logs posted above. Dashboard says direct play while I’m playing remotely. So not sure?
I wonder if the phone hardware is the limiting factor here. I have some MP3s on my server at 256 kbps bit rate. It also is transcoded to 128 kbps with the message the bit maximum was exceeded, same as the uncompressed files I have. This make me think it is a limitation of the phone hardware I am using.
I am convinced this has nothing to do with limitation on the phone.
On external wifi and home network, the phone plays in expected original resolution (flac in my case). Even on cellular the phone plays first song in expected original resolution (flac in my case).