Connects to server but will not stream about daap-client HOT 30 OPEN

It looks like it is unable to download the song.  Do you see a yellow progress 
in the back of the seek bar?  If you could, can you send me a log?

Did the newest release (0.9) fix this for you?

I am having the same (or similar) problem - connects to mt_daap server, 
downloads library, lets me select song, but when I press the play button it 
shows green for a fraction of a second and then greys out again and no music 
plays.

Did the older version work for you?

I haven't tried the older version - the latest one is the only one I've 
installed but I can change it out and see what happens.

As an update to my earlier message though I did manage to get a couple of songs 
to play (I tried maybe 50 altogether, selected at random from the whole library 
of about 10,000 songs).  I couldn't see what it was that was special about 
these that made them work but they did play OK while none of the others would 
play at all as per my original message.

I've had other complaints about this.  I haven't been able to discern a 
difference in the files to cause such a bug.  Could you try a song that doesn't 
work many times to see if it will randomly play or is it only certain songs 
will work?

Sure, I'll see if there is any pattern I can discern.  At the moment I would
say that it's a very small percentage of songs that will play but they did
play OK each time I selected them although I didn't explore this
exhaustively.

I did wonder if there was an issue with the server but it seems to be fine
with a bunch of other client devices including a mac mini, macbooks, linux
(Ubuntu) pcs and Windows (xp) PCs that I have tried it with.  I haven't
tried it with any other handhelds or phones though as I only have access to
one Android device (running v2.1 of the OS).

I doubt it is the server.  I didn't get any reports of problems until this 
newest update.  There is something wrong with our client.  Sometimes it just 
will have an error trying to play a stream.  I'm not sure why this error pops 
up and under which circumstances.  My G2 hasn't had this issue, for instance, 
if I were to connect to your phone, I'd never have this problem.  This is what 
makes this bug so elusive:  It depends on the phone.  Thanks for investigating 
for me. :-D

I have the same issue with most songs not playing but some will. 90% won't then 
one album 7 out of 10 songs play, another album all will play, but most won't 
and I see "write error: broken pipe" in firefly logs. I see no difference in 
files that will or won't. Have checked permissions and rebuilt database file 
with no luck. Running android 2.0 on rooted Pandigital Novel. 

Similar behavior to the original report on Samsung Galaxy S (Android 2.1) with 
the latest revision from the Market.

The client connects to mt-daapd, lists all the songs, goes to the playback 
screen when a song is selected but playback doesn't start - the "Play" button 
immediately gets depressed after clicking it.

Works fine on 0.8.5.1.

Seeing the same behavior on a Samsung Epic (Galaxy S) running Froyo with 
version 0.9.1 of the DAAP player.  The DAAP server is a NAS running 
freenas/firefly, sharing only MP3s.  I can also say that the older version of 
the app, 0.8.5.1, works albeit known bugs.

What is interesting in my case is that all the songs I have purchased through 
Amazon MP3 seem to be streaming just fine.  I tried to re-encode the rest of my 
music collection to match my Amazon files (LAME 3.97, -V0 with id3v1 and v2 
tags) and have not been successful.

I'm very interested in seeing this come to fruition, so I'd like to offer up my 
phone to help debug.  If you have a special debug build with verbose logging, 
I'd be happy to be a guinea pig. :)

Thank you very much for your enthusiasm and support.  I will e-mail you with 
development packages and if you could e-mail me the logs.  That'd be nice.  I'm 
sorry for the delay.  My brother and I (the developers) are both in our last 
semester at our university and have been busy; so, it may be a little slow 
until we have time.  Please have patience.  Thanks again!

I see the same problem on my Galaxy Tab, but not on my HTC Desire. 
On the Tab, I am able to connect to the server and browse the library, but I 
see the same behaviour 
Running against the same mt-daapd instance. In the mt-daapd logs I see this 
line after it says it starts streaming: Error writing to client socket: 
Connection reset by peer.

The version on both my HTC Desire and the Tab is .9.2.

@Thomas
It seems that some phones aren't streaming certain types of files.  Do you know 
if your files are variable bitrate encoding or not?

Same behavior here on Cruz Reader.  Exact same mp3 file plays successfully via 
wifi file explorer, but not via daap-client v0.9.1

Same problem here. Can browse but cannot always play. Maybe I can play 1 song 
out of 20 or 30. If the song starts playing, it plays ok.
It does not seem to be related to particular songs, as all songs sometimes play 
and sometimes fail.

Player: v0.92 Sony Ericsson X10 mini (Android 2.1)
Tried always over wan, both through 3G and Wifi.
Servers tried (in the same machine): mt-daapd (last version), forked daapd 
v0.12 and 0.13
The servers work fine with the daap client in Songbird

It seems to be related to http connection as suggests the following 
forked-daapd debug log:

httpd: Found query string
[2011-03-15 12:43:22]     daap: DAAP request: 
/databases/1/items/3.mp3?session-id=100
[2011-03-15 12:43:22]       db: Running query 'SELECT * FROM files WHERE id = 
3;'
[2011-03-15 12:43:22]    xcode: Determining transcoding status for codectype 
mpeg
[2011-03-15 12:43:22]    xcode: User-Agent: PVPlayer E10i CORE/7.507.1.1 
OpenCORE/2.05 (Linux;Android2.1-update1)
[2011-03-15 12:43:22]    xcode: Could not identify client, using default 
codectype set
[2011-03-15 12:43:22]    xcode: Codectype supported by client, no transcoding 
needed
[2011-03-15 12:43:22]    httpd: Preparing to stream 
/home/jaime/Musica/ACDC/ACDC - [1992] Live/ACDC - Live - 03. Back In Black.mp3
[2011-03-15 12:43:22]    httpd: Kicking off streaming for 
/home/jaime/Musica/ACDC/ACDC - [1992] Live/ACDC - Live - 03. Back In Black.mp3
[2011-03-15 12:43:22]    httpd: Read 65536 bytes; streaming file id 3
[2011-03-15 12:43:22]    httpd: Connection failed; stopping streaming of file 
ID 3

[deleted comment]

To everyone listening on this issue, can you investigate whether or not only 
variable bitrate files are unable to stream or can you not play static bitrate 
files as well?  My phone can play all files; so, I know it is a problem with 
the phone's streamer that comes installed.

 Is anyone able to tell me how to find out if the bitrate is variable or static. I think the problem is about the cd ripper, because all files I am able to play were not ripped by myself

I'm having the problem on my Samsung Galaxy GT-I5500M. My DAAP server is a 
FreeNAS box. I've tested on LAN and over internet, both resulting in the same 
behaviour (generally described above). One key difference is that the specific 
files that work always work. Those that don't work never work. I used the lame 
encoder to encode a wav into fixed and variable bitrate mp3's, each in mono, 
stereo, and joint stereo. They all worked. What else should I try?

I have tried with moore files than before, and here are some results:

All files encoded with LAME 3.98r VBR V4 fail to play, I have tried lots (most 
of my music!!).
Most CBR mp3s play, but I have found one that doesn't. I can email it to you if 
you want
Not all VBR files fail, I have a VBR file encoded with LAME3.87 (beta 1) that 
plays OK. Unfortunately I have not more VBR files encoded with that encoder to 
test if all play OK

Tell me if you need more testing, or if you want me to test a particular file.

I had this issue on my samsung ace.Yesterday I upgraded to gingerbread and now 
it works!

[deleted comment]

I got the same problem with my Samsung Galaxy S.

I even experienced that some songs are played partly! So daap-client is playing 
the song and suddenly skipping to the next one.

Also some songs from the same album are played and some not — so I guess it 
can't have to do with the encoding!

It doesn't seem to matter through which server I'm playing.

I hosted the same music files with mt-daap and rhythmbox, and it's the same 
songs that daap-client can play or not.

So, I just tried with two files out of which one is not played by daap-client.

Both got the following encoding:
MPEG 1.0 layer III, 192 kbit/s, 44100 Hz stereo

Same issue on a Samsung Galaxy Tab.

I'm having the same issue. However, I wasn't able to find any file that works 
for me. i'm using a Motorola Miilestone 2 phone, Android  2.2 and DAAP Client 
0.9.5.1

[deleted comment]

I've got an Orange San Fran (ZTE-Blade) on 2.2 and latest DAAP Client 
(downloaded 1 hour ago) - all seems to work well streaming to it from my main 
Ubuntu 10.04 server. However I also have just put mt-daapd on a friend's slow 
Eee Netbook running Ubuntu server 11.04 and consistently get a broken pipe 
streaming to the Android, nothing plays. However there is no problem connecting 
the same server to Banshee on this Ubuntu 11.04 desktop machine. So I wonder if 
it is some timing/latency problem. The new server is quite slow, is there any 
timing negotiation re the pipe?

working on a Sony Xperia Sola 2.3.x, not working similar to above on ainol 
advanced 7 with ICS