OK, onto the next issue that i am having integrating Sonos and Subsonic together. Last night, i had Subsonic index my full media library, i set up all the folders in Subsonic and scheduled a full media build at 3 a.m. This morning, i checked it and the process looked liked it "might" have completed successfully. I have torrents in a folder alphabetically by artist. So, i have a folder of live concerts entitled: "Torrents - A-G". When i went to that folder and started scanning, i saw what i was expecting. However, as i scrolled down for awhile, suddenly my screen started to fail to update. I was thinking that maybe the screen just had to catch up, because i was scrolling somewhat quickly. So, i stopped scrolling for a moment, in order to let the display catch up (i have gotten that behavior in Sonos too). I was playing some music at that moment, and the music stopped playing. In short, it appears that the Subsonic service on my PC crashed. I got the following error in Sonos:
"Unable to browse music - there was a problem connecting to Subsonic".
When i try and reload the Subsonic admin page in my browser (using Firefox), it doesn't connect and says "Waiting for localhost" and this never really ends, i never get connected to Subsonic. I don't know yet if this was a one-time thing or not, but i have two questions for the forum:
1. What is the best way (and fastest way) to restart the Subsonic service?
2. Are there memory settings that i can change somewhere to possibly clear up this issue?
thanx for any practical advice offered! I have Sonos running on a PC which is running Windows 7 and i was accessing the Subsonic service thru the Sonos interface on an iPad at the time of failure.
cheers!