Closed GoogleCodeExporter closed 8 years ago
If I had to guess it is one of two things...
1. The HTTP call timing out retrieving that much data.
2. Your Android device throwing an "Out Of Memory" exception.
3. An internal error in Forked-Daapd with so much data.
I test using MonkeyTunes DACP Server and I have 100,000 tracks, 6100 albums,
and 1700 artists and TunesRemote+ works fine for me on a Dell Streak and Google
Nexus One.
Original comment by mellowaredev
on 17 Oct 2011 at 12:49
OK. Do you have any idea how I could test/verify this?
Original comment by baril...@gmail.com
on 17 Oct 2011 at 3:14
From the Forked-Daapd side ,does it log? Maybe look for an error in the log?
Another way would be to have the app running in the Android Emulator? You
might also be able to use this tool to debug its a desktop tool and it might
have the same issues.
TunesRemote SE: http://code.google.com/p/tunesremote-se/
Original comment by mellowaredev
on 17 Oct 2011 at 9:22
Here is a log from Android: http://pastebin.com/w85bvaeU
And here is a log from Forked-Daapd: http://pastebin.com/hPJ4tWK2
Any idea?
I also tried with Android App "Remote for iTunes" and official Apple iPodTouch
app "Remote" but I'm not even able to pair with Forked-Daapd so I can not tell
if they would have same problem. As for TunesRemote SE on my Mac desktop, it
will not show a pairing code so I tried with 0000, but same result as with the
two other app, pairing does not occur. Only TunesRemote+ which does not ask for
pairing code will connect to Forked-Daapd (at least in my tests), but as I
cannot choose music, it is useless at the moment.
Original comment by baril...@gmail.com
on 17 Oct 2011 at 8:35
I hate to say it but since it won't pair with Remote for iTunes or
TunesRemoteSE it sounds like forked-daapd is in worse shape than I thought not
handling Bonjour and DACP properly. So I really hate to chase any of these
ghosts without more forked-daapd knowlegde.
Original comment by mellowaredev
on 17 Oct 2011 at 8:44
Original comment by mellowaredev
on 6 Nov 2011 at 4:01
Is anyone still maintaining the Forked-Daapd codebase? I have been getting
tickets reported here but TR+ definitely uses standard iTunes DACP queries and
my thinking is the forked-daapd codebase has not been modified in a long time.
Original comment by mellowaredev
on 6 Nov 2011 at 4:03
Yes, Forked-Daapd is still maintained. In fact it is actively maintained (but
mainly by one man).
You should not confuse mt-daapd (firefly) and Forked-Daapd which the later is a
fork and complete rewrite of the former.
blog: http://blog.technologeek.org/category/hacks/forked-daapd
git tree: git://git.debian.org/users/jblache/forked-daapd.git
Original comment by baril...@gmail.com
on 6 Nov 2011 at 5:55
OK great. I would definitely notify him of these issues as there is something
in the Forked-Daapd code that is not compliant with the DACP spec. Maybe he
can debug it.
Original comment by mellowaredev
on 7 Nov 2011 at 1:28
Have these issues been reported to the Forked-DAAPD developer? I have not
seen any progress on these.
Original comment by mellowaredev
on 24 Dec 2011 at 2:15
I suggest opening an issue with Forked-DAAPD here:
https://github.com/jasonmc/forked-daapd/issues
Original comment by mellowaredev
on 12 Jan 2012 at 1:04
Closing as invalid as this is a Forked-DAAPD issue.
Original comment by mellowaredev
on 18 Jan 2012 at 11:38
Original issue reported on code.google.com by
baril...@gmail.com
on 16 Oct 2011 at 6:23