Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 5 of 5
  1. #1
    Guest

    Squeezebox alarm

    Thanks for the speedy response.

    I think a simple note on the web interface would be sufficient. As I
    said, now that I know it goes up to 100, it's really not an issue (just
    wanted to find out if there's a reasoning behind it all).

    Keep up the good work - planning on getting my 3rd unit in the summer.

    kdf <slim-mail (AT) deane-freeman (DOT) com> wrote on 26.02.2004, 00:14:48:
    > Quoting aynsley (AT) vicandaynsley (DOT) com:
    >
    > >
    > > Sorry, didn't mean to sound abrupt. Just an observation really.
    > >
    > > I guess it could be a feature request, but it's not a problem now that I
    > > know it works like that.
    > >
    > > Aynsley
    > >

    >
    > ok
    > Web Interface: 11, is a joke. Spinal Tap reference, but still fairly obvious
    > what max and min is. Other skins show things linek 1-10 or a graphic scale.
    >
    > Player Interface: Its a 40 character display, so makes sense to handle it as
    > 0-40. Again, pretty clear what is max and min.
    >
    > Alarm: Using the remote, is also 40, but web interface allows a value from
    > 0-maxVolume (a server hardcoded value)
    >
    > Server: in the background, the volume is always handled as 0-100, or in fact can
    > be negative for mute (stores the previous volume that way)
    >
    > So, one problem is clearly that while the alarm input on the web interface is
    > the most direct correlation, its confusing because of all the other cases of
    > obfuscation.
    >
    > Having fallen victim to this hole in user information, what would you think to
    > be the best way to have prevented that from happening:
    >
    > 1) Alarm setting in web interface, having a note saying max 100.
    >
    > 2) Alarm setting assuming all users understand 0-40 is range and process the
    > value accordingly. Bit of extra code needed, and still probably need a not to
    > say 0-40
    >
    > 3) Have the player report 0-100 (clearly sitll in 40 steps). This gets a little
    > odd as every step woudl be 2.5, or would step by 2 then 3 alternately.
    >
    > Is there another way to do this that you would like to see?
    >
    > cheers,
    > kdf
    >
    > 4)
    >

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

    Squeezebox alarm

    Quoting aynsley (AT) vicandaynsley (DOT) com:

    >
    > Thanks for the speedy response.
    >
    > I think a simple note on the web interface would be sufficient. As I
    > said, now that I know it goes up to 100, it's really not an issue (just
    > wanted to find out if there's a reasoning behind it all).
    >
    > Keep up the good work - planning on getting my 3rd unit in the summer.


    Reasoning really was just me being lazy. I contributed the little section for
    the alarm clock web setting. I never use it, but it was requested, so thought
    I'd help. Simplest thing is just to take the raw value from the prefs file,
    which is referenced 0-100. I couldn't think of a logical pattern to follow
    given the other two ways volume is handled. You were the first to say anything,
    so you get to be the ideaperson! I know, exciting but a heavy burden

    Teh note should have been there, but I'd love to hear any ideas how it could be
    done so that there is some consistency. A graphics bar didn't seem to really
    fit there. In the meantime, I'll sumbit a patch to make a note on the valid range.

    Thanks!
    kdf

  3. #3
    Neal Tucker
    Guest

    Squeezebox alarm

    How about allowing users to keep the notion that the volume goes
    from 0 to 40, and then add "%" on any UI which displays it as a
    0 to 100 scale? Minimal code change.

    No proposed solution for the 0-11 joke, but then again, I don't
    exactly see it as a problem. You can't demand to know the units
    on a scale that goes from 0 to 11. It just *isn't done*. :-)

    -Neal

    aynsley (AT) vicandaynsley (DOT) com says:
    >
    > Thanks for the speedy response.
    >
    > I think a simple note on the web interface would be sufficient. As I
    > said, now that I know it goes up to 100, it's really not an issue (just
    > wanted to find out if there's a reasoning behind it all).

  4. #4
    Pat Farrell
    Guest

    Squeezebox alarm

    At 08:05 PM 2/25/2004, fauxfrenchdeux wrote:
    >Why not take a more technical approach? Most digital
    >devices use max level as 0db and use negative db
    >values for the amount of attenuation applied.


    I say thumbs down to this. Even in the audio engineering communities,
    made broader by things like Apple's GarageBand, too many folks have
    no idea what a dB is. The best you could do is 0dBfs, meaning full scale.
    dB is only meaningful relative. Relative to what, is the critical question.

    Of course, in the spirit of skins, you could have a skin with labeling
    in dB or any other obscure technical approach.

    All IMHO, 'natch.

    Pat

  5. #5
    Roy M. Silvernail
    Guest

    Squeezebox alarm

    On Wed, 2004-02-25 at 18:47, Neal Tucker wrote:

    > No proposed solution for the 0-11 joke


    No, no, no. 11 *is* the solution!

    I mean, it's... one louder than 10, i'nit?
    --
    Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
    "How much blacker can it be? None! None more black!" - David St. Hubbins
    SpamAssassin->procmail->/dev/null->bliss
    http://www.rant-central.com

Posting Permissions

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