@prupert wrote:
Hopefully I wont make so much of a tit of myself with my second post.
Nobody else seems to worry, plus you’ve not done too bad. 🙂
I guess you can’t use one instance of Firefly to provide multiple libraries (even though I would only ever be accessing one library at a time).
Not really, although that’s something I might like to pursue at some point.
Whilst I can figure out setting up the config files, I think, I am not too sure how I would need to edit the S60mt-daapd file to launch the four instances, as I don’t really know Linux that well.
mostly that’s just an exercise in cut and paste. The lines look something like:
mt-daapd -c /opt/etc/mt-daapd/mt-daapd.conf
You’d just add another one like:
mt-daapd -c /opt/etc/mt-daapd/mt-daapd-library2.conf
etc.
I’m running the latest version of Unslung on my NSLU2.
Also, will the NSLU2 take a real hit running multiple instances of Firefly, is there a recommended limit to the number that I run? And is there an alternative way of having multiple libraries, if you only ever plan on accessing one library at a time?
I know there are people running to libraries, so at least that much runs fine.
That’s really the only way I can think of to address your issue.
I imagine one elegant solution to all this, would be to set up static playlists, that are limited to 1000 songs each (and then arranged by genre or whatever) and then only serve information about these playlists, not the whole library. Thus, is it possible to configure Firefly so that when a client connects, it doesn’t provide details of the whole library, but just of the individual playlists, thus the memory problem wouldn’t occur for WiFiTunes? Or is this something that can only be configured on the client device side?
Cheers for any views.
Kind of a pain to maintain, though. I may have some playlist functionality here soon (plalists of top “n” items, for example, as well as “order by random”, so you can pick 1000 random items from a playlist or something).
But I think most of the owrk needs to be done on the client side.
— Ron