Failed to parse error

[bpa]

The software is typical open source: developed by a bunch of geeks with little or no top down design and no thought for useability. .

The LMS is not really open source. The bulk of it was developed by Slimdevices (although in the first few years, I believe there were significant contributions from a few dedicated users) and now Logitech. When new strategic feature or support for new hardware are being developed they are usually hidden until ready for beta. The "open source" is the release s/w and users are free to change it for themselves only and also offer patches for bugs. The patches are applied mainly by Logitech staff.

Over the years many users have made similar remarks about shortcoming in UI, design, modularity etc - however it is Logitech s/w and their staff devleoping and maintaining it and have over the last few years tidied it up a bit. However the staff are also sometimes directed by corporate strategy to develop features that become dead ends such as DLNA support.

Many plugin and user are frustrated by LMS but there is little point in complaining as it will not be rewritten.

This is a user to user forum and not a Logitech one - users try to help users. So if you could be more specific about the problems you are encountering perhaps suggestions and workaround can be offered.

[aubuti]

Not GUI, just UI. IOW the user experience is not simple, intuitive or helpful especially on the LST (LMS & MySB are a bit better I must admit).

The software is typical open source: developed by a bunch of geeks with little or no top down design and no thought for useability. as a couple of forum members said, if you're not a programmer buy a SONOS. Luckily, I was once a programmer, system designer and IT developer so know my way around a bit. I'd still like a fully working, perfect, user interface on the unit per my Roberts Stream 83i, though.

Logitech have missed out here and that's a shame because the sonics, even in basic configuration using mp3s, are excellent.

I know, that's why I said UI, not GUI. For example, the Touch's infrared remote interface only GUI under a very generous definition of graphical. It still stands that there are many ways of interfacing with the SB system, whether it is system setup or actually using it. I'm at a loss to understand what it is you are trying to do with your Touch that requires a background in programming, systems design and IT development.