I don't quite understand the improvements besides building the Raw cache faster. It still uses 100% of the 4 cores on my 3.7GHz PC and basically stops me from using the computer for much else until it is done. It would be helpful if in preferences you put a user changeable entry for percent of CPU usage dedicated to Qimage so you could use the computer for other things while it is building the thumbs and raw cache.
Andy
Two things on that. First, that's already there: go to "Edit", "Preferences", "Hyper Processing", "Hyper Thumbing" and change it to dual. Then it will only use 2 of your 4 CPU's, although I'm not sure why anyone would want to do that since if you have 4 CPU's, why not use all of them? Second, the background processes are already set to lower priority so when they are running on my quad core system using all 4 CPU's, I can still do other things without any problem. It does take a second or two longer to
open another app but once that app is open and in the foreground, it runs nicely because it will gain priority on one CPU since the Qimage processes are lower priority.
When I migrate Qimage data to another hard drive using the menu utility the RawCache folder does not migrate.
Andy
That's intentional. I didn't want to automatically migrate the raw cache because if it is a new system, it is very possible that the same (raw image) files don't exist on that system or may exist in different folders. That would cause the much larger raw cache to be copied to a new system and potentially cause all of the cached files to be "orphans". I didn't worry about that too much with thumbs because they are very small but I didn't want to migrate the raw cache automatically since that cache is much larger. I figured if people really know that their raws will be under an identical directory structure on the new system, that folder could be done manually. Perhaps in a future version, I can offer the choice though along with an explanation.
Mike