Bug 15508 - Content on SD card always requires retry
: Content on SD card always requires retry
Status: RESOLVED DUPLICATE of bug 15540
Product: SB Touch
Classification: Unclassified
Component: TinySC
: unspecified
: PC Windows XP
: P1 normal (vote)
: 7.5.0
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-01-20 09:27 UTC by Ryan
Modified: 2010-02-18 09:40 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan 2010-01-20 09:27:53 UTC
When I plug in and SD card with some content tiny SC starts up but requires a retry before the content is actually available. Sometimes it requires 2 retrys.
Comment 1 Andy Grundman 2010-01-20 09:32:38 UTC
The server takes a while to start, are you waiting long enough?
Comment 2 Ryan 2010-02-06 21:24:48 UTC
Could be I didn't wait long enough but if it is so long there should be some sort of indication of readiness. 

When the card is inserted you get the important notice with SB server status and eject SD card options. You can also press the back button. I selected the SB server status and waited until discovering files indicated complete.

When I then went to my music there was a message that I need to change library and it still took a second try before the content came up.
Comment 3 Andy Grundman 2010-02-09 18:35:47 UTC
This should be fixed, the initial rescan was blocking startup of the server.  
The server does still take about 25-30 seconds to start though.
Comment 4 Ryan 2010-02-16 11:03:05 UTC
So this is better as once it is done scanning the SD card you can select my music successfully the first time. If you do not choose to enter the Squeezebox Server Status and wait.  It still frequently takes two or more tries to  complete the scan and connect the SD card. Couldn't starting squeezebox server (tinySC) be confirmed complete before requesting the user to retry.
Comment 5 Andy Grundman 2010-02-18 09:40:54 UTC

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