Bug 8521 - Music is interrupted by update message, "Updating DSP..."
: Music is interrupted by update message, "Updating DSP..."
Status: CLOSED FIXED
Product: SB Boom
Classification: Unclassified
Component: Audio
: 12
: PC Other
: P1 normal (vote)
: 7.2
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-20 13:52 UTC by Dan Evans
Modified: 2008-12-15 12:39 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2008-06-20 13:52:05 UTC
Periodically while listening to music on PQP2 Boom w/ fw 12, the music stops and when I look at the display it reads, "Updating DSP..."

Is this expected?  I'm guessing not.
Comment 1 Mark Miksis 2008-06-20 14:30:18 UTC
http://forums.slimdevices.com/showthread.php?t=49034 explains when and why this happens.
Comment 2 Caleb Crome 2008-06-20 16:27:51 UTC
You should not see that 'updating DSP' message any more.  Delete any 'default.i2c' files in server/Plugin/ABTester/StandardImages, and/or delete any user plugins of ABTester.


However, I'll leave this bug open, so to keep track of it.  I think the right fix would be to allocate some DRAM, store the image there during download, then push it to the DSP quickly.

-Caleb
Comment 3 James Richardson 2008-06-30 16:17:29 UTC
Jim C. wants this fixed before shipping!!!
Comment 4 Dan Evans 2008-07-07 16:44:21 UTC
I continue to see this message.  Using firmware 17.
Comment 5 KDF 2008-07-07 18:54:40 UTC
and are folks who still see this deleting the default.i2c files per comment 2?
Comment 6 Dan Evans 2008-07-08 08:43:22 UTC
Actually no, I'm uninstalling and deleting the entire server install, then doing a clean install of a new nightly... which I imagine has the same effect.

Currently running SC 21546 from July 7.
Comment 7 Caleb Crome 2008-07-26 14:31:32 UTC
This isn't really a problem with the 'Updating DSP', it's more a problem that there is a drop and then a reconnect, and when there is a reconnect that should not cause a audio dropout, the DSP still reloads. 

How can we tell the difference between a benign dropout and a severe one?  I don't understand why, sometimes when there is a reconnect, the music continues from where it left off, and other times, it goes to the beginning of the song.

I don't think this one belongs to me -- perhaps Felix, Sean, or soembody on the server side would know better.
Comment 8 Chris Owens 2008-07-28 10:38:32 UTC
Caleb, this needs to really get resolved this week.

Erland, Andy says that we're going to take out ABtester for now.  You can still release it as a plugin or post about it on the developer group to talk about its future.
Comment 9 Caleb Crome 2008-07-28 10:43:45 UTC
I don't think this one belongs to me.  The 'updating DSP' message is just a symptom of some other disconnect-reconnect.  Who should take it?

The 'updating DSP' won't happen, since we're not releasing a default.i2c image, so this particular symptom isn't a problem.  The deeper problem is the disconnect-reconnect that people are seeing. 
Comment 10 Caleb Crome 2008-07-28 13:18:59 UTC
I'll say it again. :-)  This one doesn't belong to me -- it has to do with disconnects. Perhaps felix, or sean.  
Comment 11 Caleb Crome 2008-07-31 13:53:15 UTC
I suspect that this is related to the congestion/memory problem that felix fixed.  We should see if these disconnect-reconnects still happen.
Comment 12 Chris Owens 2008-08-04 09:18:24 UTC
With abtester gone this bug should not exist.

Andy to mark this as 'invalid' (or 'fixed') after that work is done.
Comment 13 Andy Grundman 2008-08-04 09:22:51 UTC
Removed ABTester in change 22352.  It can now become a 3rd party plugin.
Comment 14 James Richardson 2008-10-10 14:33:43 UTC
Verified fixed in

SqueezeCenter 7.2.1-23472
Boom r33
Comment 15 James Richardson 2008-12-15 12:39:16 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

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