mherger wrote: > Now there's a twist to this which can have a massive influence on the > artwork.db file cache: applications or plugins can register their own > sizes to be pre-cached. Eg. iPeng does this. Therefore the size of your > > cache file depends on your use of 3rd party tools, too. You can find > those additional sizes in Settings/Advanced/Performance. > > > some of the sizes aren't precached, if the same original images are > > being handled later, you'd think GDresizer wouldn't have a problem > with > > them. > > That's true.
What about embedded images in tracks? Do each of them get precached during a scan? If so, they'd greatly increase the size of artwork.db (as well as greatly increasing scan times). If not, I would think the potential for a malformed embedded image to unexpectedly blow up GDResizer during normal use would be high. ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=101516 _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
