@platypus That will cause PL6 to rediscover the directory all over again, not something you want to do if it has 11,960 images in it!! The swirling “render” icon doesn’t stop the product working providing it hasn’t actually encountered “the problem”!
My tests reported above, after moving the cache to NVME, were all undertaken in one session and all worked perfectly, unless I was living in an alternative universe!? I didn’t understand that at the time and after last nights testing definitely do not understand them!
Firstly for those that like to treat their images as unstructured “blobs” with no subdirectory structure then the best of luck! This is XnviewMP discovering the images on a USB3 SSD for the first time (it also builds a database)
and this is PL6 re-discovering them (and encountering the “problem”) last night, one of many tests all of which failed!!
A repeat just now actually completed the re-discovery from NVME (with the database now on SATA SSD) and the counter reached “11960 images” in 03:44.63 minutes and I refrained from any scrolling through images until the counter showed 11960!.
But the ‘rendering’ needs to take place as the display is scrolled and I then encountered the following (please note that there are some thumbnails being displayed in amongst the “chaos”!
All the tests I reported in the post above had no scrolling from an impatient operator (me) until the counter reached 11960!
During my test last night I scrolled down the images while the discovery or re-discovery was in progress and every test failed regardless of the location of the database which was cleared before every new discovery test. Discovering from HDD is just a nightmare but from NVME was just over 19 minutes and from USB3 connected SSD was just over 23 minutes.
So I have no magic bullet other than using XnviewMP to break large numbers of images into smaller batches and passing them to PL6 and making them into projects in an attempt to keep the numbers relatively small but I would only attempt that on up to 1,000 images breaking into 3 batches and only if it was important to process those images!! This is using another piece of software to navigate and PL6 to process the images (as a “workaround” until the fix arrives)!
Once PL6 “breaks” then, as I found last night, all further attempts to process even small directories failed to display the thumbnails correctly, but I have successfully used PL6 to process such images, i.e. navigating “blind” does not stop the main image from being presented and processed (hence navigating externally and then processing in PL6).
For reference:-
My drive configuration during the tests was C:, E:\ are SATA SSD drives, F:\ is my main HDD, H:\ is the NVME drive (fitted to a card rather than to the motherboard to keep all SATA ports fully active) and I:\ is the USB3 SSD.
I only moved the database for some tests from H:\ (NVME) to E:\ (SATA SSD), the Cache remained on H:\ (NVME) throughout and the images were confined to either H:\ or I:\ no tests were done last night with the images on F:\ (life it too short)!