You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, using daap v .9.6 on HTC Wildfire.
connecting to Ubuntu Server 10.04, running firefly/mt-daapd version svn-1696,
described in package as v 0.9~r1696.dfsg-15build1
I got daap-client to work fine over wifi, and was trying it out with the
phone's wifi turned off. It was very jerky; it would play, pause, play, pause.
This led me to look at the config file for mt-daapd. There are settings in
there for transcoding mp3s and oggs to wav files "on-the-fly".
I changed the config to include a line
never_transcode = ogg,mp3
This means that oggs and mp3s are not converted to wav files, but provided
instead as ogg or mp3.
With this setting in force, I have tried to play ogg files and daap-client does
nothing, the progress bar stays at 0% and no sound comes out. mt-daapd log
file attached.
I recall that I had some problems playing MP3 files as well, but I cannot
confirm this now.
This problem means that I can't play my ogg files except over wifi and I have a
lot of ogg files!
In your blog you say that "should stream every file type supported by your
phone as I just use the media player of the phone progrmattically."
http://chris-miceli.blogspot.com/2010/05/daap-android-client-updates.html?showCo
mment=1303656223889#c7225757632660243092
I know that my phone can play ogg files, but it can't do it though daap-client.
Perhaps there is some sort of error when you call the media player
progarmattically?
I suspect this is related to bugs issue 34 and issue 53 as lots of the symptoms
are similar.
HTH.
Original issue reported on code.google.com by [email protected] on 14 Sep 2011 at 12:03
With a new phone running Android 4.04, this app version 0.97, the problem goes
away, i.e. can play files that are in Ogg format without them needing to be
transcoded. However the problem still exists on my old phone with app version
0.97, android version 2.2.1
Original issue reported on code.google.com by
[email protected]
on 14 Sep 2011 at 12:03Attachments:
The text was updated successfully, but these errors were encountered: