vrobin;275543 Wrote: > > re-calculate: > ============= > Solution 1: store the computed hash in the file tags, recalculate > become necessary only if the tag has been wiped > Solution 2: store in a table hash and file url (file://), recalculate > on "force update" or file not found/file not in db > SqueezeCenter development team would never allow SqueezeCenter to write anything to the music files, so I think solution 2 is the one that would work.
I wonder how SHA1/MD5 calculation would affect the scanning times, especially scanning times on NAS boxes with a slow processor and little memory. Does anyone have an idea if this would be a problem ? Since the SqueezeCenter database is cleared on a full rescan this means that all 50000 FLAC/MP3 files in a library would need to be calculated again during a full rescan. -- erland Erland Isaksson 'My homepage' (http://erland.homeip.net) 'My download page' (http://erland.homeip.net/download) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library and Database Query plugins' (http://wiki.erland.homeip.net/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=43851 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
