Mike Chaney's Tech Corner
April 19, 2024, 03:30:12 PM *
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 Search Login Register  

Professional Photo Printing Software for Windows
Print with
Qimage and see what you've been missing!
Pages: [1]
  Print  
Author Topic: Maximum file size?  (Read 5961 times)
gchappel
Newbie
*
Posts: 39


View Profile
« on: December 09, 2018, 02:41:45 PM »

I tried the search function here with no results, I hope I am not asking a question that has been handled here before.
I have used Qimage for years.
I am starting to print large- really large.  40x60" routine.  40x100" not unusual.
On my largest files, I get an " Image Read Error."  If I take the same file and downsize it Qimage builds the thumbnail and can print, so it is not the file itself.  It is the size.
I would like to stay in the Qimage environment. 
As an example one pano is 12633 x  19043.  688MB.  Gives me an Image Read Error
Any idea of how I should handle these very large files?
Thanks
Gary
Logged
Fred A
Forum Superhero
*****
Posts: 5644



View Profile WWW Email
« Reply #1 on: December 09, 2018, 03:42:21 PM »

Quote
Personal Message (Offline)
   
   
Maximum file size?
« on: Today at 09:41:45 AM »
   Reply with quoteQuote Modify messageModify Remove messageRemove Split TopicSplit Topic
I tried the search function here with no results, I hope I am not asking a question that has been handled here before.
I have used Qimage for years.
I am starting to print large- really large.  40x60" routine.  40x100" not unusual.
On my largest files, I get an " Image Read Error."  If I take the same file and downsize it Qimage builds the thumbnail and can print, so it is not the file itself.  It is the size.
I would like to stay in the Qimage environment.
As an example one pano is 12633 x  19043.  688MB.  Gives me an Image Read Error
Any idea of how I should handle these very large files?
Thanks
Gary

Gary,
I just built a file to your specs....722MB
Works fine.
So it seems as if we should look at your system. Which windows? 32 bit or 64 bit? How much RAM available?
What other programs are running at the time along with QU?
If my memory serves...... I think around 1.2 gigabytes was the max size.
Do a HELP ANALYZE while holding the shift key
See screen snap
Win 10- 64 bit with 16.0 gigs of RAM


Fred

Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #2 on: December 09, 2018, 06:15:55 PM »

Thanks for the reply
win 10 pro
64bit OS
32GB ram
i7-8700K
One year old build
Logged
Fred A
Forum Superhero
*****
Posts: 5644



View Profile WWW Email
« Reply #3 on: December 09, 2018, 06:25:52 PM »

Quote
Thanks for the reply
win 10 pro
64bit OS
32GB ram
i7-8700K
One year old build

What about something else with heavy RAM usage running?
What numbers do you get when you click HELP, and then click ANALYZE with Shift key down?
Otherwise I am stumped. Will have to pass it on to Mike.
I assume the pano was stitched. What software stitched it?
Fred
Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #4 on: December 09, 2018, 10:53:55 PM »

Pano stitched with photoshop as a tiff.
Other large files enlarged with topaz Gigapixel
Nothing else ram intensive running- and the image read error is permanent- it does not "correct" over time.
Information:
Start 2145MB
Addl: 909MB
Now: 2145MB

I do not need to see the thumbnail at all.
On these images I do not use any of the qimage tools. 
I just need to assign a page size, an image size, set sharpening and print
Thanks
Gary
Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #5 on: December 09, 2018, 11:07:35 PM »

Oops- I just realized I am using v2018.115
I did not upgrade, as I only use qimage to print and did not use any of the new features.
If an upgrade will solve my issue I will be more than glad to do it.
Thanks again
Gary
Logged
Fred A
Forum Superhero
*****
Posts: 5644



View Profile WWW Email
« Reply #6 on: December 10, 2018, 10:15:53 AM »

Quote
Oops- I just realized I am using v2018.115
I did not upgrade, as I only use qimage to print and did not use any of the new features.
If an upgrade will solve my issue I will be more than glad to do it.
Thanks again
Gary
.


Just poking around, I found this


    2018.126 includes improved memory management which enables printing of larger (higher resolution) images.
Always good to stay current Might as well get 2019

Fred
Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #7 on: December 10, 2018, 12:35:05 PM »

Well I upgraded, but no change.
I still have the image read error messages.
Still glad I upgraded, great program.
Gary
Logged
Fred A
Forum Superhero
*****
Posts: 5644



View Profile WWW Email
« Reply #8 on: December 10, 2018, 12:44:50 PM »

Quote
Well I upgraded, but no change.
I still have the image read error messages.
Still glad I upgraded, great program.
Gary

Gary,
I alerted Mike. Give him some time to get to this.
Fred
PS Any way I could download the file from you or you sending ut to me via WE TRANSFER?"   My email is wathree.ssz@verizon.net
« Last Edit: December 10, 2018, 12:47:05 PM by Fred A » Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #9 on: December 10, 2018, 01:47:53 PM »

Success!!
I think the upgrade actually fixed the issue.  I was choosing a file to send you.  I did nothing to the file except rename it.  I resaved the file and when qimage built the new thumbnail it was fine.
I tried that with 5 other files- all worked fine.  I think I just need to force the updated qimage to rebuild the thumbnails. 
Even if I have to do it manually one at a time, no big deal.  I only have 15-20 image files large enough to be causing an issue.
Thanks for walking me through this.
Qimage comes through again.  Great program
Gary
Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #10 on: December 10, 2018, 02:21:59 PM »

Quick associated question- as I have more of these large files than I thought.
Is there a way to force qimage to build new thumbnails?
Thanks again
Gary
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #11 on: December 10, 2018, 03:04:03 PM »

Yes.  You can rebuild thumbs one folder at a time: click "View", "Rebuild Thumbs/Cache".  I noticed you said you are enlarging with Gigapixel first.  You should try just letting Qimage do the enlargements by just letting Qimage print the originals at 40x60 (or whatever size).  Compare the output to the Gigapixel files and if you don't see a difference, you can eliminate the extra time and disk space of using Gigapixel.  Gigapixel will really only show a difference in extreme cases.  I don't know the resolution of your originals so maybe printing at 40x60 is extreme for you depending on the camera/resolution used, but it might be good to do a test print with Qimage (without Gigapixel) to compare anyway.

Regards,
Mike
Logged
gchappel
Newbie
*
Posts: 39


View Profile
« Reply #12 on: December 10, 2018, 05:20:30 PM »

Thanks for the quick reply.
I have never compared large printed files.  I need to do that. 
My native resolution at 40x60 is 130ppi.
I use gigapixel because I tried it once on a file and was amazed at how good it looked blown up- so I just use it.
I do need to step back and let qimage handle this once.
Qimage has never let me down before, will give it a try next time I print that big.
Will let you know
Thanks again
Gary
Logged
admin
Administrator
Forum Superhero
*****
Posts: 4120



View Profile Email
« Reply #13 on: December 10, 2018, 05:57:37 PM »

Starting at 130 PPI, the results will likely be pretty close.  Keep in mind that Gigapixel adds some extra sharpening so to compare, you might want to increase the sharpness a bit on Qimage's Printers and Settings tab.  You could potentially create smaller test strips (crops) at the same original PPI to test it.

Regards,
Mike
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.