Bug 7964 - Alarm: volume jump on power off
: Alarm: volume jump on power off
Status: RESOLVED DUPLICATE of bug 4289
Product: SB Boom
Classification: Unclassified
Component: Audio
: unspecified
: All All
: -- minor (vote)
: 7.3
Assigned To: Felix Mueller
http://forums.slimdevices.com/showthr...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-24 07:51 UTC by Mark Lanctot
Modified: 2009-09-08 09:21 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Lanctot 2008-04-24 07:51:29 UTC
If I turn Boom off very shortly after the alarm is triggered, the volume increases for a fraction of a second as Boom went into the off state.

I have the fade alarms in option checked and the fade-in probably didn't complete before I hit the power button, so maybe this was the fade-in being canceled and the playback going to the chosen volume (50) before the player went into the off state. I can't say I heard this on an SB2 used as an alarm though, and it's not that I reached the power button quicker, I was almost as quick with the SB2 remote.

SqueezeCenter Version: 7.2 - 19104 @ Thu Apr 24 00:20:08 PDT 2008 - Debian - EN - utf8
Perl Version: 5.8.8 x86_64-linux-gnu-thread-multi
MySQL Version: 5.0.45-Debian_1ubuntu3.3
Platform Architecture: x86_64-linux

Boom firmware 4.
Comment 1 Blackketter Dean 2008-05-02 12:41:02 UTC
Another case where a client-side fade would make things better, I think.
Comment 2 Mark Lanctot 2008-06-05 10:24:39 UTC
Just something additional I've noticed over the last little while (all with the latest nightly builds) - the volume not only jumps, it seems that the track pauses as Boom goes into the "off" state, then the track resumes at higher volume for about 1/4 of a second.

The display does something bizarre as well before displaying the "off" screensaver (flashes the Now Playing screen or something, I can't remember and it's very fast).
Comment 3 Chris Owens 2008-06-05 16:34:42 UTC
related to bug 4289 ?
Comment 4 Mark Lanctot 2008-06-06 06:34:39 UTC
Yes, this seems to be the same as bug 4289.  You can mark this as a duplicate.
Comment 5 Felix Mueller 2008-07-25 01:24:00 UTC
This won't make it into 7.2
Comment 6 Blackketter Dean 2008-07-25 06:41:14 UTC

*** This bug has been marked as a duplicate of bug 4289 ***