Mike Chaney's Tech Corner
August 03, 2020, 05:31:34 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Feb 2013: Qimage Ultimate Challenges... have fun and explore features!
 
   Home   Help Search Login Register  

Professional Photo Printing for Windows
Print with
Qimage and see what you've been missing!
Pages: [1] 2
  Print  
Author Topic: v2012.200 issues/comments  (Read 13498 times)
admin
Administrator
Forum Superhero
*****
Posts: 3108



View Profile Email
« on: September 23, 2011, 08:38:11 PM »

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

v2012.200    09/23/11

Priority: Low

v2012.200 is the most significant update to Qimage Ultimate since its initial release in July 2010:

  • All new build: Complete code review/rewrite includes bug fixes, new memory manager, new device drivers, etc.
  • Color management: Color management engine updated to latest LCMS 2.2.
  • TIFF support: Expanded file compatibility supports TIFFs in all flavors: with alpha channels, "per channel" pixel order, Mac byte order, etc.
  • IPTC support: All new IPTC support includes bug fixes and allows for multi-language metadata.
  • Printers: Brand new (saved) printer setup format for maximum printer and OS compatibility.  Note: newly saved printer setups/jobs (from v2012.200+) cannot be opened by old/prior versions.
  • Speed: New device drivers enable faster and smoother screen operations and smoother operation of dialogs and controls.
  • Future: New Unicode code base allows for future multi-platform/multi-language development: 64 bit version already being explored for possible release later in 2012.

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



View Profile WWW
« Reply #1 on: September 23, 2011, 08:56:06 PM »

Quote
Speed: New device drivers enable faster and smoother screen operations and smoother operation of dialogs and controls.
That's the first thing I noticed, a significant reduction for Full Screen, Image Editor, Comparator and Page Editor HQ  views to appear.
Thanks,
Terry
Logged
msadat
Newbie
*
Posts: 28


View Profile
« Reply #2 on: September 26, 2011, 05:41:01 PM »

i have a problem with this version and acdsee. i use to be able to send images from acdsee to qimage but since this release it does not work.
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3196



View Profile WWW
« Reply #3 on: September 26, 2011, 05:53:28 PM »

Quote
i use to be able to send images from acdsee to Qimage but since this release it does not work.
Seeing this I just checked Send To and Open With from Windows Explorer.
If QU is NOT open they work fine but if QU is already running then the image(s) selected in Explorer do not open in QU.
I'm this worked ok with v2012-104 because I checked it to help a friend with another problem just last week.
Perhaps someone else can check this out too.
Terry
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3196



View Profile WWW
« Reply #4 on: September 26, 2011, 10:51:05 PM »

Quote
If QU is NOT open they work fine but if QU is already running then the image(s) selected in Explorer do not open in QU.
v2012-201 has fixed this so I would think acdsee should be ok too.
Terry
Logged
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #5 on: September 27, 2011, 06:48:32 AM »

Mike,

The "200" update works fine in Win7 64bit working in VirtualBox on my Mac. Although rebuilding very large TIFF thumbnails initially took ages.

I also have QIU installed on my Win XP Pro 32 bits as a backup. Again "200" works fine but it is unable to rebuild thumbnails of TIFFs larger than about 9,000 (maybe 10K) pixels wide, nor display the images. The thumbnails display "Image Read Error" in red.

I'm referring to the same set of TIFFs as successfully "rebuilt" using QIU on Win 7 64bit.

Is there some size limit operating within the new QIU routines, on Win XP?

The same issue occurs on "201".

Thanks

Peter
« Last Edit: September 27, 2011, 06:53:17 AM by pshrutpark » Logged

admin
Administrator
Forum Superhero
*****
Posts: 3108



View Profile Email
« Reply #6 on: September 27, 2011, 12:23:45 PM »

The size is limited only by your computer and OS: if Windows doesn't have the memory to give, it can't load the file.  Hold the shift key while you choose "Analyze Current Settings" from the Help menu.  QU will show you how much memory Windows has available.  You might be one of the people with an XP setup that is very low on memory.  Keep in mind that when building thumbs, four thumbs are built at once which means if you are low on memory and only have 500MB available, don't expect to be able to build a folder of 500MB TIFF's without a problem if you have hyper thumbing turned on.  If you are running on a "marginal" system, you might want to turn off hyper thumbing as it won't use nearly as much memory with it turned off.

Mike
« Last Edit: September 27, 2011, 12:26:19 PM by Mike Chaney » Logged
jeffjessee
Jr. Member
**
Posts: 76


.


View Profile Email
« Reply #7 on: September 27, 2011, 01:24:53 PM »

Mike-

Since most new PC's now seem to have quad processors, and using that hardware has really speeded up thumb building, any chance you could use quad processing in other areas of QU? I'm thinking especially of converting files for the web, and any converting files in general. Those still take a long time.

Thanks,
Jeff Jessee
Logged
hongu123
Newbie
*
Posts: 28


View Profile
« Reply #8 on: September 27, 2011, 03:43:38 PM »

Hi similar problem I now get read errors on lots of tiffs (large ones) that was ok in previous versions. I did shift analize settings and get 2000/1830/1465 Is this low? I have 16gb of ram installed is QU only able to use 2gb?
Thanks Phill
Logged
hongu123
Newbie
*
Posts: 28


View Profile
« Reply #9 on: September 27, 2011, 03:49:10 PM »

OK an update! Just installed 201 and its fine now.  Wink
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3196



View Profile WWW
« Reply #10 on: September 27, 2011, 04:17:13 PM »

Hi Phill,
Quote
I have 16gb of ram installed is QU only able to use 2gb?
It is really what Windows is allowing Qimage to use. The final figure of shift analize settings is the one that matters and depends on your operating system. W7 is much better than XP.
Terry
Logged
Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3196



View Profile WWW
« Reply #11 on: September 27, 2011, 04:24:54 PM »

Hi Jeff,
Quote
any chance you could use quad processing in other areas of QU? I'm thinking especially of converting files for the web, and any converting files in general. Those still take a long time.
I've always assumed that if Quad core processing is enabled in QU, then it applies to all QU processing.
Certainly, since I acquired a quad PC nearly a year ago, all processing is much faster and with v2012-2xx, conversions to tiff are almost instantaneous. Jpegs are a little longer due to the compression process, I suppose.
Terry
Logged
admin
Administrator
Forum Superhero
*****
Posts: 3108



View Profile Email
« Reply #12 on: September 27, 2011, 05:04:05 PM »

Hi Jeff,
Quote
any chance you could use quad processing in other areas of QU? I'm thinking especially of converting files for the web, and any converting files in general. Those still take a long time.
I've always assumed that if Quad core processing is enabled in QU, then it applies to all QU processing.
Certainly, since I acquired a quad PC nearly a year ago, all processing is much faster and with v2012-2xx, conversions to tiff are almost instantaneous. Jpegs are a little longer due to the compression process, I suppose.
Terry

Dual/quad core only applies to thumbnail/raw-cache building and printing.  That's why there are two specific listings under "Hyper Processing": one for thumbs and one for printing.  Image conversions are single core.  Multi-core image conversions may come at a later date but I have no immediate plans for that due to the potential complexity (and memory requirements) when converting from the queue.  You can have potentially very large images in the queue, images with very complex filters, and even the same image repeated in the queue multiple times.  Doing that multi-threaded can easily overwhelm the most well equipped machine without a lot of clever (complex) programming and lots of bug testing.

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



View Profile WWW
« Reply #13 on: September 27, 2011, 05:06:55 PM »

Quote
Dual/quad core only applies to thumbnail/raw-cache building and printing.
Thanks for the clarification.
Terry
Logged
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #14 on: September 27, 2011, 07:12:50 PM »

The size is limited only by your computer and OS: if Windows doesn't have the memory to give, it can't load the file.  Hold the shift key while you choose "Analyze Current Settings" from the Help menu.  QU will show you how much memory Windows has available.  You might be one of the people with an XP setup that is very low on memory.  Keep in mind that when building thumbs, four thumbs are built at once which means if you are low on memory and only have 500MB available, don't expect to be able to build a folder of 500MB TIFF's without a problem if you have hyper thumbing turned on.  If you are running on a "marginal" system, you might want to turn off hyper thumbing as it won't use nearly as much memory with it turned off.

Mike

Thanks Mike.

I omitted to point out that the same set of TIFFs did not cause any thumbnail nor display problems on QIU v2011, running on Windows XP 32bit.

On the Win XP Pro PC changing the Thumbnail build to single core made no difference.

I have since found out that most, if not all, of the large TIFF panoramas even if they have correctly generated thumbnails can not be displayed using SPACE nor double-click. Get a red "Image Read Error" on the screen.

Peter


  
« Last Edit: September 27, 2011, 07:34:12 PM by pshrutpark » Logged

Pages: [1] 2
  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!