>>>>> Dan Sully <[EMAIL PROTECTED]> writes: > It is cataloging and indexing your music. A number of join tables are built, > and checks to create unique albums, etc.
OK, but don't you agree 5 minutes on a nearly 3 GHz CPU is a preposterous number of cycles to spend indexing 8246 tracks from 641 albums and 414 artists? This is a puny amount of data. Is there any easy way to turn off the SQL side of the scanning to confirm that reading the tags is reasonably fast and that all this time really is consumed by the SQL? thanks, greg _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
