Bug 7607 - soft power on splash screen should be "Squeezebox" logotype
: soft power on splash screen should be "Squeezebox" logotype
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: unspecified
: Macintosh Other
: P3 normal (vote)
: ---
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-24 17:03 UTC by Blackketter Dean
Modified: 2008-12-15 11:58 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
squeezebox logo used in firmware (10.07 KB, application/octet-stream)
2008-06-15 18:52 UTC, Blackketter Dean
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2008-03-24 17:03:24 UTC
When you soft power on a boom, the splash screen should be the Squeezebox logotype, instead of the free your music screen, since the localized versions won't fit on screen.
Comment 1 Chris Owens 2008-05-14 09:19:20 UTC
Felix notes that this is actually a Squeezecenter change, since this is the message that happens turning on when connected to SC.  This should be tested against SN as well.
Comment 2 Michael Herger 2008-06-05 17:22:58 UTC
Felix/Dean - that logo is part of the firmware. Can I download it somewhere? Or could you upload a copy to this bug? Thanks!
Comment 3 Blackketter Dean 2008-06-15 18:52:35 UTC
Created attachment 3436 [details]
squeezebox logo used in firmware

Ah, yes, sorry.
Comment 4 Michael Herger 2008-06-16 06:48:16 UTC
change 20785 - added logo font with Squeezebox logo for Boom. 

Due to the small size of the display and it being 1-bit only this logo might need some tweaking. Please revise - thanks!
Comment 5 James Richardson 2008-07-25 13:34:27 UTC
Verified logo looks good with r19 & 7.2-22118
Comment 6 James Richardson 2008-12-15 11:58:22 UTC
This bug has been fixed in the latest release 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.