I am now running firmware 23 and build 2178 on the remote. This has been the worst build for me yet. I have the SBC wired to my home router. I am connecting the remote to the SBC adhoc. After updating the remote this morning, I had my PC on. I reset the SBC and then factory reset the remote. The remote found the SBC and I chose a wired connection. It completed successfully and I could access the music on my PC and listen to internet radio. Life was good. I turned off the SBC with the remote and placed the remote in the cradle and went to work. I came home tonight and decided to listen to some music during dinner. I spent the entire dinner trying to connect the remote to the SBC via adhoc connection. This included about 4 factory resets and 4 trips to the SBC to reset it (8 feet away). It would find the controller fine but would error out saying it could not connect wirelessly. Note to developers - you say to hold the SBC button until it blinks red. After a few seconds it blinks red slowly and then if you keep holding for another 3 or so seconds, it starts blinking red quickly. Is there a difference between these two modes? If so, you need to clarify for users or this could be causing problems. I always hold the button until I see a fast blink.
The only difference between my unsuccessful attempts at trying to connect this evening compared to this morning was that my PC was on this morning. Tonight during dinner, when I just wanted to listen to Internet radio, the PC (where the MP3's live) was off. That shouldn't matter for initial connection/setup - right??? So I went upstairs and turned on my PC. Reset remote, reset SBC. Still would not connect. Then I decided to try connecting to my wireless network. I was able to successfully connect. The only problem with this setup is I often run into delays of up to 30 seconds when I change the volume. Is adhoc mode now broken? What should I try to make it work again? Note to developers, PMs, marketing, and Slim executives. I have been working as a Product Manager in high tech companies for almost 15 years (Intel, Xircom, and a slew of telephony start-ups). I have been involved in numerous 3rd party software betas (Win95-XP) and hardware betas. I'm even in charge of running beta programs. The Squeezebox Duet is by far the most unstable product I have ever used in my entire life. It reminds me of several Alpha stage devices. It is very disappointing to see such an immature product released. In fact, it is perhaps very telling about the state of affairs at Logitech/Slim Devices. I cannot see any respectable product development team releasing such a bug-ridden product. Was there pressure by upper management to get this thing out the door before the end of the quarter to make the numbers? The Duet has sooo much going for it. It is just a shame that you had to release this thing in the state that is in. -- davidmac27 ------------------------------------------------------------------------ davidmac27's Profile: http://forums.slimdevices.com/member.php?userid=11117 View this thread: http://forums.slimdevices.com/showthread.php?t=45031 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
