Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 16
  1. #1

    Why not integrate SlimServer & SqueezeNetwork menus?

    I am glad to see that these two menus will be made more consistent in 7.0. But why not integrate them fully into a single menu? In particular, have a single "Internet Radio" menu and a single "Favorites" list (right now each is different depending on whether you're connected to SlimServer or SqueezeNetwork). Perhaps the player could automatically login to SqueezeNetwork when powered on -- but even if that's not possible for some reason, the UI could be unified and the player could login when the user chose a command that required it.

    I think consistent menus, while improving usability a bit, is much less helpful than having a single menu that's always accessible. The system essentially operates in 2 modes now, local and network, which is more complex than necessary.

    (Sorry if this has already been discussed... I couldn't find it when I searched.)
    Last edited by bruce; 2007-07-20 at 18:24. Reason: clarify

  2. #2
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,460

    Why not integrate SlimServer & SqueezeNetworkmenus?

    > I am glad to see that these two menus will be made more consistent in
    > 7.0. But why not integrate them fully into a single menu?


    SQN services (Pandora, Rhapsody & Cie.) will be integrated in SlimServer's
    menu.

    > I think consistent menus, while improving usability a bit, is much less
    > helpful than having a single menu that's always accessible.


    The problem would be that SQN would have to talk to your slimserver to get
    your music collection. This wouldn't add to system's performance...

    > essentially operates in 2 modes now, local and network, which is more
    > complex than necessary.


    That's exactly the goal for SS7: have the user set up its system and don't
    make him go forth and back. From the user's POV there will be one menu
    offering all the features of the local slimserver _and_ SQN. Only in case
    you shut down your slimserver you'll have a reduced selection, as your
    local music won't be available.

    > (Sorry if this has already been discussed... I couldn't find it when I
    > searched.)


    You just didn't fully understand the announcement ;-)

    Michael

  3. #3
    Thanks Michael, that sounds great. I assume that there will be a single Favorites list, accessible from anywhere, containing SlimServer and SqueezeNetwork items?

  4. #4
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,460

    Why not integrate SlimServer & SqueezeNetworkmenus?

    > Thanks Michael, that sounds great. I assume that there will be a single
    > Favorites list, accessible from anywhere, containing SlimServer and
    > SqueezeNetwork items?


    The new Favorites plugin is still work in progress. There's already a
    framework to synchronize some settings. We'll have to see whether
    Favorites can make use of this or some similar mechanism. Thanks for the
    hint.

    Michael


  5. #5
    By any chance, is there a detailed spec for this feature that I could look at? (And if so, would comments be welcome?)

  6. #6
    Watcher of the Windows build
    Join Date
    Mar 2006
    Location
    NYC
    Posts
    1,260
    Quote Originally Posted by Michael Herger View Post
    That's exactly the goal for SS7: have the user set up its system and don't make him go forth and back. From the user's POV there will be one menu offering all the features of the local slimserver _and_ SQN. Only in case you shut down your slimserver you'll have a reduced selection, as your local music won't be available.
    Maybe I'm missing something very obvious, but why is this swtiching from SS to SQN not a function of the SB firmware? I can see the need for configuring this feature from the SS, but not for it to reside completely in the SS. Of course I'm assuming that the SB has an internal clock and some intelligence. The integrated menu options would appear if both the SS and SB have a heart beat. This could be reflected with two tiny icons in the interface of the SB. If the SB fails to connect to either one after trying for specified period of time, then one gets the SS or SB menu with its corresponding tiny icon. If both fail then flash a warning for a short period of time and then go the blank screen. Of course one should be able to configure this switching (from the SS and SB) to be automatic or manual allowing one to set the specific time intervals and to connect by default to the SS or the SQN... or to both. I don't know... but the SS should not be requirement. What if I want to take my SB to a friend's house and want to connect to the SQN? Again, as I said, I'm probably missing something. Could this something be related to the fact that the SB firmware does not support fully qualified domain names?

  7. #7
    NOT a Slim Devices Employee kdf's Avatar
    Join Date
    Apr 2005
    Posts
    9,493

    Why not integrate SlimServer & SqueezeNetworkmenus?

    On 21-Jul-07, at 11:01 AM, tamanaco wrote:

    >
    > Michael Herger;216050 Wrote:
    >>
    >> That's exactly the goal for SS7: have the user set up its system and
    >> don't make him go forth and back. From the user's POV there will be
    >> one
    >> menu offering all the features of the local slimserver _and_ SQN. Only
    >> in case you shut down your slimserver you'll have a reduced selection,
    >> as your local music won't be available.
    >>

    >
    > Maybe I'm missing something very obvious, but why is this swtiching
    > from SS to SQN not a function of the SB firmware?


    There is a manual choice operation in the firmware, but some users
    didn't react kindly to having to hold left button to get back into
    firmware setup in order to get to SQN. The controls now exist in
    firmware with redundant software hooks to enable switching from SS. If
    a user were to want automated switching based on time, then a plugin
    could work very well for this. The firmware, however, has limited
    space reserved for things like audio decoding. There is no "clock"
    aside from the basic digital tick that drives synchronous controllers.

    -kdf


  8. #8
    Watcher of the Windows build
    Join Date
    Mar 2006
    Location
    NYC
    Posts
    1,260
    Quote Originally Posted by kdf View Post
    There is a manual choice operation in the firmware, but some users
    didn't react kindly to having to hold left button to get back into
    firmware setup in order to get to SQN. The controls now exist in
    firmware with redundant software hooks to enable switching from SS. If
    a user were to want automated switching based on time, then a plugin
    could work very well for this. The firmware, however, has limited
    space reserved for things like audio decoding. There is no "clock"
    aside from the basic digital tick that drives synchronous controllers.

    -kdf
    Thanks kdf... Another dumb question... I guess I have to assume that for the plugin solution to work the plugin would have to be hosted in both the SS and the SQN... Right? I have not seen many plugins added to the SQN. Btw, just out of curiosity... is there a clock in the Transporter?

  9. #9
    NOT a Slim Devices Employee kdf's Avatar
    Join Date
    Apr 2005
    Posts
    9,493

    Why not integrate SlimServer & SqueezeNetworkmenus?

    On 21-Jul-07, at 12:44 PM, tamanaco wrote:

    >
    > kdf;216195 Wrote:
    >> There is a manual choice operation in the firmware, but some users
    >> didn't react kindly to having to hold left button to get back into
    >> firmware setup in order to get to SQN. The controls now exist in
    >> firmware with redundant software hooks to enable switching from SS.
    >> If
    >>
    >> a user were to want automated switching based on time, then a plugin
    >> could work very well for this. The firmware, however, has limited
    >> space reserved for things like audio decoding. There is no "clock"
    >> aside from the basic digital tick that drives synchronous controllers.
    >>
    >> -kdf

    >
    > Thanks kdf... Another dumb question... I guess I have to assume that
    > for the plugin solution to work the plugin would have to be hosted in
    > both the SS and the SQN... Right?


    Well, no. No plugins on SQN. However, perhaps it could be something
    of an end run if a "special" playlist were added
    that could be used by the alarm clock to cause a switch. However, there
    are things under consideration like settings allow the player to
    switch to SQN automatically if the local SS is lost and vice versa.
    Something like that could be along in the future. It is a work in
    progress, but most likely that progress will come from SS/SQN.

    >


    > Btw, just out of curiosity... is there a clock in the
    > Transporter?
    >

    No clock. That aspect of Transporter is the same as SB3. Even the
    second display is done by an added feature of SlimServer/SQN

    -kdf


  10. #10
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,460

    Why not integrate SlimServer & SqueezeNetworkmenus?

    > Thanks Michael, that sounds great. I assume that there will be a single
    > Favorites list, accessible from anywhere, containing SlimServer and
    > SqueezeNetwork items?


    That's the plan, yes.

    --

    Michael

    -----------------------------------------------------------------
    http://www.herger.net/SlimCD - your SlimServer on a CD
    http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •