Mike Chaney's Tech Corner
December 23, 2024, 07:08:13 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Qimage registration expired? New lifetime licenses are only $59.99!
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: v2010.103 issues/comments  (Read 15734 times)
admin
Administrator
Forum Superhero
*****
Posts: 4229



Email
« on: August 03, 2010, 07:33:11 PM »

http://www.ddisoftware.com/qimage-u

v2010.103     08/03/10     

Priority: Med     

v2010.103 includes the following:

  • Raw thumbnail building: New dual stage thumbnail builder builds raw thumbnails much faster.  Start working with your raws and create print jobs right away while Qimage Ultimate builds its raw cache invisibly in the background!
  • Build thumbs/cache for entire folder trees: Simply browse to a folder and click "Thumb Builder" from the top menu and select "Build all thumbs/cache" and Qimage Ultimate will build thumbs/cache for all images in the current folder and all subfolders.  This is a great way to start a thumb/cache build to ensure you don't have to wait when navigating to new folders.  Progress of the build is shown above the thumbnails and you can even navigate away from the thumb/cache building to another folder or even close Qimage Ultimate if you don't want to wait for the build to finish.  To resume building the tree of thumbs/cache, just open the saved album "Thumb Build" with the date/time you started the build.  Qimage Ultimate will pick up right where it left off, and will continue down the tree until it is finished!
  • Thumb/cache management: Added new options under "Utilities", "Manage Thumbs and Raw Cache" to help users manage the files that are thumbed or cached by Qimage Ultimate.
  • Fixes: Fixed some minor bugs and occasional error messages.
   

Mike
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3251



WWW
« Reply #1 on: August 03, 2010, 10:55:39 PM »

Mike,
Well done & thank you; what a great improvement, especially for those like me still using an old P4 PC.  Cool
I can now see new raw images in a folder very quickly and get on with refining as required. I have the impression that background cache building stops while I do this, is this correct?
It's even better on my modest Core 2 Duo laptop.

I've also tried the background building of a whole group of folders, it makes the old CPU work hard but I left the PC to get on with it for a while and when I came back just stopped it. Re-start from the album is easy too.
Terry
Logged
atodzia
Full Member
***
Posts: 121


« Reply #2 on: August 04, 2010, 12:22:37 AM »

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
Logged
Fred A
Forum Superhero
*****
Posts: 5644



WWW Email
« Reply #3 on: August 04, 2010, 08:57:25 AM »

Mike,
Well done & thank you; what a great improvement, especially for those like me still using an old P4 PC.  Cool
I can now see new raw images in a folder very quickly and get on with refining as required. I have the impression that background cache building stops while I do this, is this correct?
It's even better on my modest Core 2 Duo laptop.

I've also tried the background building of a whole group of folders, it makes the old CPU work hard but I left the PC to get on with it for a while and when I came back just stopped it. Re-start from the album is easy too.
Terry

Now, This is slick!
What an improvement!!
I have complete control over which folders get cached if I don't want some old images cached, they don't need to be.
The building of the thumbs is really fast now.

Love it.
Fred
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3251



WWW
« Reply #4 on: August 04, 2010, 08:59:40 AM »

Quote
and basically stops me from using the computer for much else until it is done
You can use Qimage, as cache building seems to stop when you do, and that's on an old P4 machine. Otherwise, stop caching, you choose the priority.
Terry
Logged
atodzia
Full Member
***
Posts: 121


« Reply #5 on: August 04, 2010, 12:50:08 PM »

When I migrate Qimage data to another hard drive using the menu utility the RawCache folder does not migrate.

Andy
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4229



Email
« Reply #6 on: August 04, 2010, 01:31:45 PM »

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
« Last Edit: August 04, 2010, 01:36:29 PM by Mike Chaney » Logged
atodzia
Full Member
***
Posts: 121


« Reply #7 on: August 04, 2010, 01:38:55 PM »

You just jogged my memory. A few months ago when I was having a problem with my Epson driver and trying to figure it out I set the processing priority on Qimage in Task Manager to High. I just set it to Normal and will see if that helps with being able to do other things when the Raw Cache is being built. The Epson driver issue was resolved and not related to processing priority.

Andy
Logged
atodzia
Full Member
***
Posts: 121


« Reply #8 on: August 04, 2010, 01:41:59 PM »

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

Does that mean I can create a RawCache folder on my D drive and Qimage will use it if it is there?
Andy
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4229



Email
« Reply #9 on: August 04, 2010, 02:56:30 PM »

Does that mean I can create a RawCache folder on my D drive and Qimage will use it if it is there?
Andy

No.  Instead, use v2010.104 and use the "Migrate" function to migrate the application data to your D drive and answer "Yes" that you want to use the new location when it is done.  Then yes, it will use the D: drive for both thumbs and raw cache.

Mike
Logged
atodzia
Full Member
***
Posts: 121


« Reply #10 on: August 05, 2010, 02:04:50 AM »

Thanks. That works. Also the CPU hogging is fixed now that I set the priority for Qimage to be normal again.

Andy
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Security updates 2022 by ddisoftware, Inc.