I manually changed the entry in the connect file to "plugin_dir = .\plugins" (don't know why that would be a difference) and restarted Firefly, and then I DID correctly see both the RSP and DAAP versions of the library being available for selection on my Soundbridge. Maybe the config file change didn't make the difference (I don't understand why it would), but if that isn't the reason the RSP DLL wasn't loaded earlier, maybe when Firefly does a full-scan startup (I had deleted the database to force a rescan) it doesn't do the plugin startup?
Nope, it should have worked like that. Strange, as mine was modified in the same way and worked okay.
I'll take another look and see if I can replicte that.
I've just had it happen again (this time with "plugin_dir = .\plugins", so that isn't a factor in when it does/doesn't happen - good!)
Anyway, it seems intermittent, but the twice it has happened to me, this is the scenario (running on Win XP SP2):
1. Stop Firefly service.
2. Delete songs.db
3. Start Firefly service (so that a full rescan and rebuild of songs.db is performed)
4. After rescan is finished, on the Soundbridge only the DAAP version of the Firefly-served library is visible, not also the RSP one.
NB: This is NOT always repeatable, and has only happened twice out of maybe 10 times I have done the sequence above, but it has ONLY happened on a restart which is also doing a full scan. Stopping/starting the Firefly service again when the problem happens has so far always made the RSP version of the library visible on the Soundbridge. NB: Maybe the full scan isn't a factor; it isn't reproduceable enough for me to be able to say for sure, but definitely sometimes after Firefly startup the RSP version of the library is _not_ being shown to the Soundbridge, whereas the DAAP version has been available every single time, no matter what.