I just tried the SqueezeNetwork for the first time (having just received my replacement SqueezeBox2 with a working headphone socket).
Here's some initial ramblings... 1. I found it easy to connect to the SqueezeNetwork (SN) and configure. 2. How does the PIN get generated? Is this id allocated from SN the first time a unique SB2 connects? 3. The SB2 feels a lot slower to navigate through menus when connected to the SN. Does each remote control action perform a round-trip visit to the server across the internet? 4. I selected a radio station to play, and for the first few seconds it played fine. After that it was really choppy. I tried a few stations, but all exhibited the same stuttery sound. I checked my PC's network traffic, which was utilising 0% transmit and receive, so the SB2 could use all bandwidth. 5. Whilst connected to the SN, I looked at my slimserver UI, and my player was no longer listed. Is it not possible to connect/disconnect to/from the SN from the slimserver? I was kind of expecting my local slimserver to override the SN on demand, such that when my local server is not present, it can fall back to the SN, but when the slimserver is available, it could switch back to it. 6. I couldn't set an alarm time of 7:15am. It doesn't like 10's of minutes - I could set the time for 7:05 or 7:01. Still, with my timekeeping, this is perhaps not a bad thing ;) 7. As an idea, it would be nice to have some kind of scheduling facility - set a time, a short message and a sound effect using the SqueezeNetwork website, and the SqueezeBox2 would play this sound effect and scroll the message onto the display. I could then send reminders to home from work. Perhaps the slimserver could periodically connect to the SN to get any updates to scheduled reminders, so it would work even when the SB2 is connected to the local server. Phil _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
