Bug in Android Subsonic App

[sierramtngoat]

Hey, not sure where to post a bug, but I figure an op will forward this to whomever.

Subsonic server version:
Version 4.7 (build 3106) – September 12, 2012
Server jetty-6.1.x, java 1.6.0_31, Windows 7 (18.4 MB / 34.6 MB)

Android version:
2.3.4 running on Motorola Droid2

Subsonic App version:
not sure, I got it from the Google on 10/24/2012, if you can tell me how to get the app version off my Droid2, I'll give it to you.

Behavior:
With the server transcoding non-mp3's with the settings 'ffmpeg -i %s -ab %bk -v 0 -f mp3 -', the stream comes to my phone w/o error, however, depending on the App 'network settings' the stream will come at an illogical bit-rate. With these settings:
max bitrate - wi-fi = 320
max bitrate - mobile = unlimited
wi-fi streaming only = off
The stream will be saved to the cache at the expected 320KBs; I'm using wi-fi.

With max bitrate - wi-fi = unlimited
The stream will be saved to that cache at < 160Kbs? (file=4.8MB); this should be 320KBs (~10.9MB)

I also tried turning the 'wi-fi streaming only' option on and that seemed to trick the sever into delivering a 320KB stream, but this wasn't always the case for me; non-deterministic?

My issue I suppose is why when the max bit-rate is set to unlimited, the size of the file is cut in half? Why would the wi-fi only option even matter, considering my files are only accessible via wi-fi?

I like this product immensely; my collection is now everywhere in my home and on my mobile.

-Andrew

[BKKKPewsey]

"Unlimited" IMHO is mis-named as it defaults to the ffmpeg default transcode bitrate of 128k.
Set the bitrate to the value reqd eg 320K - it won't "upscale" so that will deliver the best available.