Bug 1694 - Need scanning feedback on home page of web interface
: Need scanning feedback on home page of web interface
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: unspecified
: Macintosh MacOS X 10
: P2 normal (vote)
: ---
Assigned To: KDF
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-19 15:11 UTC by Bill
Modified: 2011-03-16 04:18 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
refresh home every 5 mins during scan, and show a warning message (2.93 KB, patch)
2005-06-30 19:31 UTC, KDF
Details | Diff
add strings this time (3.59 KB, patch)
2005-06-30 19:34 UTC, KDF
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Bill 2005-06-19 15:11:32 UTC
Running SlimServer 6.0.2, Mac OS 10.3.8, Powerbook G4 titanium

Hey guys, how long did it take slimserver to process the entire database for your iTunes library? (mine 
is ~1400 songs, 9.5 gb) I've let the 'perl' process chug away for already 1 hour (saturating my CPU to 
max the whole time) and decided to terminate it as my laptop was getting quite hot.

Wouldn't it be better if the database be created during the installation process instead of the first times 
while you're using the server?  (there's no system feedback so I haven't the slightest clue if 'perl' is 
actually doing anything useful here)  Btw, in creating the database, does SlimServer pick up from when I 
last terminated it or does it start over from the beginning everytime?

I just want to be able to use SlimServer while returning my computer's CPU to normal, cool levels.

Thanks for your help,

-Bill
Comment 1 KDF 2005-06-19 15:37:51 UTC
this is a bug tracker.  Is this a bug report or a support question?
support questions can be directed to the forums
(http://forums.slimdevices.com/), or support@slimdevices.com.  for certain, this
has nothign to do with lists.slimdevices.com or email as a bug. That gives me
the impression that this was in fact intended to be sent to the lists, instead
of here.
Comment 2 Vidur Apparao 2005-06-30 13:49:57 UTC
I don't have a definitive answer to how long a scan will take with your size of
library, but your experience suggests that, at the very least, we have a
feedback problem.

The home page of the web interface should display a message while SlimServer is
scanning. It will also have to refresh itself (probably with not too small an
interval) until the scan is done.

Changed the subject line and targetted the bug.
Comment 3 KDF 2005-06-30 16:19:54 UTC
Web/Pages.pm, Line 659:
	if (Slim::Music::Import::stillScanning()) {
		$params->{'warn'} = 1;
	}

HTML/Default/home.html, insert at line 16:
[% IF warn %]<p><b>[% "NOTE" | string %]</b> [% "SCAN_WARNING" | string %] [% END %]

This doesn't do any refresh, but that could be a simple javascript ripped from
status_header and only included if [% warn %] is defined. You can re-assign to
me if you want me to take care of that.

Comment 4 Dan Sully 2005-06-30 17:35:10 UTC
Consider it done! :)

Though I think a different warning should be used - something along the lines of: SlimServer is scanning 
your music library - this may take a while.
Comment 5 KDF 2005-06-30 19:31:36 UTC
Created attachment 586 [details]
refresh home every 5 mins during scan, and show a warning message

Uses a javascript refresh timer during scan to refresh the home page and show a
warning.  So as not to add any extra overhead, I've moved the warn parameter
setting into addLibraryStats so that browsedb and home can both share the same
call to stillScanning()
Comment 6 KDF 2005-06-30 19:33:22 UTC
Dan or Vidur,

When you have time can either of you please check this over to make sure that a
5 minute refresh seems like the right kind of pace, and that the new string is
worded acceptably.
Comment 7 KDF 2005-06-30 19:34:42 UTC
Created attachment 587 [details]
add strings this time

forgot the strings in the first patch
Comment 8 Dan Sully 2005-06-30 21:20:40 UTC
Looks ok.

The bodyscript should be conditional on the WARN though.

We don't want to refresh all the time.
Comment 9 KDF 2005-06-30 21:31:43 UTC
committed at change 3587
Comment 10 Chris Owens 2008-03-11 11:28:21 UTC
This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!