| Author | Thread |
|
|
09/02/2009 07:24:56 AM · #1 |
So I made a gigantic panorama in CS4, and my system seems to be physically unable to convert to a JPEG.
The file is a bit over 600mb, and neither CS4 or Capture NX are able to convert it. I currently have the maximum amount of RAM able to be used by a 32 bit OS and a Core 2 Duo 2.4ghz CPU w/ Nvidia Quadro FX 570M 256mb GPU. Is there another program I might have luck with or is this just a hardware limit with my machine? I have no problems loading and manipulating it or saving as TIFF, only as JPEG.
Thanks |
|
|
|
09/02/2009 07:42:10 AM · #2 |
Originally posted by spiritualspatula:
So I made a gigantic panorama in CS4, and my system seems to be physically unable to convert to a JPEG.
The file is a bit over 600mb, and neither CS4 or Capture NX are able to convert it. I currently have the maximum amount of RAM able to be used by a 32 bit OS and a Core 2 Duo 2.4ghz CPU w/ Nvidia Quadro FX 570M 256mb GPU. Is there another program I might have luck with or is this just a hardware limit with my machine? I have no problems loading and manipulating it or saving as TIFF, only as JPEG.
Thanks |
if you have acess to linux system, you can use convert command of imagemagick if it is installed. Another way is if there is a way to share it put it online i could do it for you. I have a monster with 40gb ram. Your file is not even infant for what i usually do with it. |
|
|
|
09/02/2009 07:53:31 AM · #3 |
| Just a thought, is it an 8 bit image? don't think standard JPEGs support 16 bit files (or so I thought). |
|
|
|
09/02/2009 08:19:28 AM · #4 |
Originally posted by Ecce Signum:
Just a thought, is it an 8 bit image? don't think standard JPEGs support 16 bit files (or so I thought). |
No, they don't, but that's automatically done when doing batch conversions (which is how I discovered this problem). My other files were 16 bit and converted fine. Ironically, the file in question is actually 8 bit though...
Originally posted by zxaar:
if you have acess to linux system, you can use convert command of imagemagick if it is installed. Another way is if there is a way to share it put it online i could do it for you. I have a monster with 40gb ram. Your file is not even infant for what i usually do with it.
|
No access to linux system. Thanks a lot for the offer. It isn't a big deal to me really, but it seemed odd and I figured somebody here would know.
Your system sounds like a beast. What are the rest of the specs? |
|
|
|
09/02/2009 09:02:13 AM · #5 |
Originally posted by spiritualspatula:
Originally posted by Ecce Signum:
Just a thought, is it an 8 bit image? don't think standard JPEGs support 16 bit files (or so I thought). |
No, they don't, but that's automatically done when doing batch conversions (which is how I discovered this problem). My other files were 16 bit and converted fine. Ironically, the file in question is actually 8 bit though...
Originally posted by zxaar:
if you have acess to linux system, you can use convert command of imagemagick if it is installed. Another way is if there is a way to share it put it online i could do it for you. I have a monster with 40gb ram. Your file is not even infant for what i usually do with it.
|
No access to linux system. Thanks a lot for the offer. It isn't a big deal to me really, but it seemed odd and I figured somebody here would know.
Your system sounds like a beast. What are the rest of the specs? |
my machine is actually for doing moderate calculations. It is a 64bit amd machine with total ram of 40gb. (it is normal for me to do read-write with file as small as 10gbs :-D ).
it has gimp loaded too so if it is read into gimp i could convert that way.
in case you do it regularly i will see if there is any possiblity to write computer program to do it for you without eating up much of memory. (i think it shall be possible if i try a bit).
Message edited by author 2009-09-02 09:02:46. |
|
|
|
09/02/2009 09:50:59 AM · #6 |
| What is the dimension (in pixels) of the longest side? I can't find a reference to whether there is a hard-coded limit for JPEG images at the moment, but it's remotely possible you've exceeded it. |
|
|
|
09/02/2009 09:23:32 PM · #7 |
Well, I figured I might as well try to convert with GIMP and that had zero problems and did it exceptionally fast. So I guess the question is why CS4 and Capture NX both refused and failed but GIMP did it effortlessly...
Any guesses? |
|
|
|
09/02/2009 10:25:27 PM · #8 |
Originally posted by spiritualspatula:
Well, I figured I might as well try to convert with GIMP and that had zero problems and did it exceptionally fast. So I guess the question is why CS4 and Capture NX both refused and failed but GIMP did it effortlessly...
Any guesses? |
There are many things possible. But the root cause of your problems is
- memory management.
There are two possibilities.
1. Large memory allocation.
Computer programs need to allocate memory to run. Now usually memory is allocated as continuous chunk. For large data many times it is not possible to get continuous chunk of space. This results in failure.
This is exacerbated by the fact that some of the programs allocate lot of unnecessary data anticipating that user would do certain things. For example in your case you needed to convert but program did not know this and thus try to allocate memory fully rather than not loading few module.
A good program will have a better memory managers. The programs i have written work with much much larger memory sizes and they never fail. Becuase i have good memory manager program.
2. Small memory.
You will ask why this is problem.
Modern programs work with lot of dynamic data structures like tree etc etc. Since they are dynamic in nature allocating small chunks for a large number of chunks could create failure. I can simulate this for even a relatively moderate tree structure.
Gimp it seems does not allocate memory until you ask it to do something that requires that allocation. Which is correct thing to do.
Message edited by author 2009-09-02 22:25:48. |
|
|
|
09/02/2009 10:53:43 PM · #9 |
| I addition to the memory issues noted, it could also possibly be a hard drive space shortage. I don't know about the CS versions of Photoshop, but the older versions wanted up to five times the "scratch disk" space as the file size for temporary storage. When possible, you want to assign the primary PS scratch disk to an empty partition, or at least a different drive than that which contains the application and OS files. |
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 12/25/2025 06:23:41 PM EST.
