Subsonic Forum

Hello there...

Long time user, first time poster. Loving everything about everything that is Subsonic.

I have a tiny problem. I recently reinstalled and reconfigured the Subsonic server and Android phone client. The problem is, with certain tracks, I get the following error on Android:

"Error playing "Crazier". Prepare failed.: status=0x1 (IOException)"

I have seen this error before, but rarely. Now it happens with one track on almost every album I have. These tracks ALWAYS give this error, even if they are deleted, and then redownloaded. Oddly, they work fine through the web interface. The problem is definitely with the Android client player.

From Subsonic.log:

Code: Select all

[2011-03-05 16:38:18,452] DEBUG TranscodeInputStream - Starting transcoder: [c:\subsonic\transcode\lame] [-S] [-h] [--resample] [44.1] [-b] [160] [--tt] [Crazier] [--ta] [Gary Numan] [--tl] [2003 - Hybrid Disc 1] [g:\Music\Gary Numan\2003 - Hybrid Disc 1\03 Crazier.mp3] [-]
[2011-03-05 16:38:18,514] DEBUG InputStreamReaderThread - (c:\subsonic\transcode\lame) hip: bitstream problem, resyncing skipping 3770 bytes...
[2011-03-05 16:38:18,514] DEBUG InputStreamReaderThread - (c:\subsonic\transcode\lame) hip: bitstream problem, resyncing skipping 6168 bytes...
[2011-03-05 16:38:18,514] DEBUG InputStreamReaderThread - (c:\subsonic\transcode\lame) hip: bitstream problem, resyncing skipping 1864 bytes...
[2011-03-05 16:38:18,514] DEBUG InputStreamReaderThread - (c:\subsonic\transcode\lame) hip: bitstream problem, resyncing skipping 12742 bytes...
[2011-03-05 16:38:18,514] DEBUG InputStreamReaderThread - (c:\subsonic\transcode\lame) hip: bitstream problem, resyncing skipping 462 bytes...

Any help would be GREATLY appreciated!

Will this file succeed w/o transcoding?

Thanks for pointing me in the right direction....

I seem to have made some headway by disabling the 160 kbps bitrate limit in the Android client menu, and instead enabling this option via the Players tab of the Subsonic web client. Forcing the Android Player to 160kbps on the server end, instead of the client end SEEMS to have remedied this problem. I will post an update if I notice it again.

Thanks for the help!

Good news! Thanks for reporting back!