OK Erland First Pass: Sonos/SB3/Touch.
I will assume that the target market for this will tend to a multiplayer installation. First time purchases buy into the concept, then expand. The investment in multi-room audio will assume a significant interest in music, therefore a reasonably large collection of audio files for a family unit. There are two prime customer groups. The distribution/recommenders and the end users themselves. Addressing the Distribution/Recommenders: 1) The installation process needs cleaning up. As with Pippin's comments, the current product line would probably be hopeless without the help of forum members. Key issues are a more user based installer, that tries to pre-empt through discovery and by asking questions about where and what users want. Location of music files, local WiFi, Menus, auto-network capacity testing etc. In support of this an installation manual needs to be created, multi-level from step by step getting started through to what to do now. ( a bit like a dummies guide to Squeeze). This need very comprehensive indexing. And, no the cop out Wiki is not the place. 2) There should be an easier log file creation and diagnosis. Users/installers should not have to enable specific debugging modes. Just tick some key simple english boxes. The resultant log files should also be post processed to highlight key areas (debug information as currently presented requires far two much technical knowledge) or call support, with an automatically created pre-structured email containing all technical debug data. Similarly support should be able to provide pre-structured debug settings request for users / installers. Now the users: In a multi-room, multi-user scenario, there are several issues arising. Some of these have been covered many times in forum comments. 1) Library database creation; 1a) First the existing library database should be archived automatically, probably weekly with ability to return to an old copy by choice. Roll-back to what worked. 1b) Option to have library scan interactive. This to allow user intervention on decisions based on multiple tagging, or tagging errors. These decision choices also to be kept and logged with option to re-use as input for further scans. 1c) Ability to split library into user partitions. People are different, ability to categorize for spouse and family members and should make user selection of playlists somewhat easier. 1d) Ability to split library into music groups(sort of high level genre, Well almost. Classical, Jazz etc.) 1e) Ability to rip and add easily. Yes it can be done. Why can't we just rip to a music to be added folder? 1f) Recognition of a library structure independent of tagging constraints that supports classical music - Composer, Artist, Piece. 2) What to play: 2a) The current selection Artist Composer Album etc is reasonably OK. Add the multi user view, segment by music type as appropriate. 2b) Some form of random play, with mood, seed track within limits is essential to the Squeeze experience. Track counts need to kept to avoid repeats. Music IP helps, but it is for geeks, installation etc. is just too hard. iTunes Genius is too simplistic. This could be the real killerfor music lovers - if more people could get it to work. 2c) Party Mode. Essential for users to be able to queue tracks Jukebox style, without any ability to wipe playlist 3) Where to play 3a) The synchronisation interface is dreadful. Some form of zoning etc is required. iPeng has simplified it a little for my household. 3b) Ther should be a fully supported firewalled remote player facility, for office - holiday - on the move use. Probably should have an iPhone App like the Touch. 4) The server 4a) I believe Logitech need to make available a server as an appliance. This needs to cover large collections, and multi-users, so although the Touch maybe OK for start ups, a higher powered Touch is required - maybe audio-less and display-less. 4b) Server and Player power modes. the whole sleep and WOL issue is over complex for users. IPeng manages to look for the server, if not available, it sends a WOL. Seems obvious - why don't the players do it. Rant coming: if I press on for a player it sends a WOL to server, server then sets player to previous known state, usually off. A power on that achieves off, very user friendly. I personally believe that GHarris plug in should be incorporated. All users with time need server sleep modes, never mind global warming it's the electricity bill. 4c) For long term success in this market, I believe Logitech should License to the HiFi product streaming community. They will probably not address the transporter market. But users with a prime and expensive HiFi component still need multiple room devices like the Touch, Radio etc. to cover the less hallowed listening areas. 5) Plug in Apps Logitech undoubtedly have limited resource pools. In order to maximise creativity and acceptance they need a development community, as per Apple. A defined development approach, optional revenue generating. This to address the weather, time, football score, download new music, add radio program, control the curtains etc. This needs a dedicated resource pool, for support, documentation and some form of indexing with user reviews/comments. Dave -- DaveWr ------------------------------------------------------------------------ DaveWr's Profile: http://forums.slimdevices.com/member.php?userid=9331 View this thread: http://forums.slimdevices.com/showthread.php?t=72512 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
