I have a mt-daapd server installed at my Asus wl500 working fine. I can use the daap protocol for iTunes and GetItTogether without any problems. It should be noted that both programs do autodiscovery regarding locating the server. The server is hosted on my internal lan at 192.168.1.1 which is also what i can see it be discovered as. However, neither the fireflyclient application or applet is able to locate the server. What do i do?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right about the 404 error. I tried to change the config file but it seems as this is'nt supported either by my mt-daapd installation. I should perhaps stress that the firefly media server is installed on my router and not a pc. This narrows the posibilities regarding supported protocols as not all versions of firefly are ported to the the asus wl 500. What i hoped for in the fireflyclient programme, was a java based open source client project that supported Apple's DAAP protocol and had a more up-to-date GUI than GetItTogether.
I don't see it as a posibility for me to make the server RSP aware. I rather hope for client to be DAAP compatible like eg. GetItTogether. Lastly, it would be nice to add support for the AirPort Express by porting the JustePort project from http://nanocr.eu/software/justeport/ into fireflyclient. Thereby it would be fully on line with iTunes, but have the portabilty that iTunes does not. If it is not of any interest of this project to incorporate the DAAP protocol, i might start on doing this myself on a fourthcoming rainy summerday
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay - i think i more or less found out myself by debugging me through fireflyclient. Correct me if i am wrong, by fireflyclient connects through the rsp protocol not the daap protocol? And as mt-daapd for the asus wl500 does not support the rsp protocol it won't work. Correct?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firefly client uses RSP protocol by default to communicate with the mt-daapd server. To work, the RSP plugin has to be well installed on the server. You can check that on the server status page http://localhost:3689/index.html You must have the rsp plugin listed. Another method to check if it is installed is to get the following url in your browser: http://localhost:3689/rsp/info which must return an xml response (I think this is this url which causes the 404 error).
For the first versions of the software, Firefly Client used XML-DAAP protocol (an XMLized version of DAAP supported by mt-daapd), but it has migrated to RSP mainly for performance reasons. You can still switch to the XML-DAAP mode with worse performances (I tried to maintain it but I don't ensure that it is not buggy!). To do so, you have to manually edit your firefly config file ($HOME/.firefly-client/config.xml - You can see the value of $HOME in the About Box of Firefly Client) and replace RSP by XML-DAAP.
Anyway, the best solution is to make the server RSP aware. All the softwares you tested use pure DAAP protocol which explain that they work without raising any issue.
Hope this can help...
-- caribou
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a mt-daapd server installed at my Asus wl500 working fine. I can use the daap protocol for iTunes and GetItTogether without any problems. It should be noted that both programs do autodiscovery regarding locating the server. The server is hosted on my internal lan at 192.168.1.1 which is also what i can see it be discovered as. However, neither the fireflyclient application or applet is able to locate the server. What do i do?
You are right about the 404 error. I tried to change the config file but it seems as this is'nt supported either by my mt-daapd installation. I should perhaps stress that the firefly media server is installed on my router and not a pc. This narrows the posibilities regarding supported protocols as not all versions of firefly are ported to the the asus wl 500. What i hoped for in the fireflyclient programme, was a java based open source client project that supported Apple's DAAP protocol and had a more up-to-date GUI than GetItTogether.
I don't see it as a posibility for me to make the server RSP aware. I rather hope for client to be DAAP compatible like eg. GetItTogether. Lastly, it would be nice to add support for the AirPort Express by porting the JustePort project from http://nanocr.eu/software/justeport/ into fireflyclient. Thereby it would be fully on line with iTunes, but have the portabilty that iTunes does not. If it is not of any interest of this project to incorporate the DAAP protocol, i might start on doing this myself on a fourthcoming rainy summerday
Okay - i think i more or less found out myself by debugging me through fireflyclient. Correct me if i am wrong, by fireflyclient connects through the rsp protocol not the daap protocol? And as mt-daapd for the asus wl500 does not support the rsp protocol it won't work. Correct?
Well you're right, but it could work though. Here is a post I had done on the firefly media server forum :
http://forums.fireflymediaserver.org/viewtopic.php?p=20120#p20363
Here is the interesting part below :
Firefly client uses RSP protocol by default to communicate with the mt-daapd server. To work, the RSP plugin has to be well installed on the server. You can check that on the server status page http://localhost:3689/index.html You must have the rsp plugin listed. Another method to check if it is installed is to get the following url in your browser: http://localhost:3689/rsp/info which must return an xml response (I think this is this url which causes the 404 error).
For the first versions of the software, Firefly Client used XML-DAAP protocol (an XMLized version of DAAP supported by mt-daapd), but it has migrated to RSP mainly for performance reasons. You can still switch to the XML-DAAP mode with worse performances (I tried to maintain it but I don't ensure that it is not buggy!). To do so, you have to manually edit your firefly config file ($HOME/.firefly-client/config.xml - You can see the value of $HOME in the About Box of Firefly Client) and replace RSP by XML-DAAP.
Anyway, the best solution is to make the server RSP aware. All the softwares you tested use pure DAAP protocol which explain that they work without raising any issue.
Hope this can help...
-- caribou