Bug 13904 – Add limiting to speakers to prevent shutdown

Bug 13904 - Add limiting to speakers to prevent shutdown

Summary:

Add limiting to speakers to prevent shutdown

Status:	CLOSED FIXED

Product:	SB Radio
Classification:	Unclassified
Component:	Audio
Version:	Include FW version in comment
Platform:	PC Other

Importance:	P1 critical (vote)
Target Milestone:	7.4.0
Assigned To:	Caleb Crome

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-08 09:24 UTC by Caleb Crome
Modified:	2009-10-05 14:27 UTC (History)
CC List:	4 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Caleb Crome 2009-09-08 09:24:50 UTC

Add limiting to prevent > 18 Watts power consumption.

Comment 1 Caleb Crome 2009-09-09 10:00:34 UTC

Created sinewave generator & tested limits.

Comment 2 SVN Bot 2009-09-09 10:01:23 UTC

 == Auto-comment from SVN commit #6378 to the player repo by ccrome ==
 == https://svn.slimdevices.com/player?view=revision&revision=6378 ==

Bug #13904.  Added sinewave generator.  18 Watt limit is 18500.

Comment 3 SVN Bot 2009-09-09 11:22:58 UTC

 == Auto-comment from SVN commit #6381 to the player repo by ccrome ==
 == https://svn.slimdevices.com/player?view=revision&revision=6381 ==

Fixed #13904.  Added limiter to DSP code so it should not shut down anymore.

Comment 4 James Richardson 2009-10-05 14:27:24 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.