1. A knowledge base article or readme is going to do nothing in the situation where, as in this case, one's significant other triggers the firmware update as requested by the device. The issue is that there is no messaging telling the user to update the client software beforehand.
2. Yes, having a pre-amp before the amp would be a good idea, for safety and for sound quality. Luckily, my amp has both clipping and thermal protection and my speakers can handle more power than was thrown at them. Good ideas aside, full volume on the device for a good percentage of your users is going to be a iffy proposition. 3. If the issue truely was a client software, device firmware mismatch, which makes no sense because I wasn't connected to the client while the firmware was updated, then couldn't there be a hash value that the device compared in the firmware and desktop client software, with a mismatch giving the user a warning or message of some sort? If the above isn't the issue, then I guess I don't understand the considerations and issues that triggerd this change or bug. Other than the above, I really like the new firmware and how I can browse my local and Rhapsody libraries without having to connect individually. -dhh -- dhh ------------------------------------------------------------------------ dhh's Profile: http://forums.slimdevices.com/member.php?userid=19041 View this thread: http://forums.slimdevices.com/showthread.php?t=50398 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
