I have searched here and elsewhere on the internet but found little help for my problem (only one thread here (2009/01/22) and it didn't mention anything I hadn't tried). So if I missed a thread, my appologies.
I am trying to stitch a 24 image pano together and I keep getting "The application ran out of virtual memory. Please close some windows to free memory". The thing is that PS is the only app I have open! This is definitely the largest pano I have ever tried.
I have 4GB of RAM, two internal hard drives with the app on one drive (C) and the scratch disk on the other physical drive (G; this drive has 115GB free). Preferences -> performance tells me that I have 1707MB of available RAM (I'm guessing that CS3 PS can only access 2GB), and I have tried giving it from 70% all the way up to 90% (1536MB). Control Panel -> Advanced -> Performance -> Advanced, Virtual Memory paging file for C is max of 5120MB while G on the other physical drive has an additional max of 7168MB. But total paging file size on all drives is currently only 4603MB! I saw something on the web that said to disable Version Cue, which I did but it didn't help.
I tried to merge all 24 pictures, but it didn't work. I rebooted and tried 12 at one time, with the idea of flattening the layers and saving it, doing the same with the other 12 and then merging the two resultant pictures. But I got the same error with 12 pictures, so I rebooted and tried 4 and got the same error again!
The files are 11MB to 15MB, with most being 12 to 13. The source files are Canon CR2. I ran Task Manager with Virtual Memory Sizes column added. What I saw was 1.66GB of real memory used along with 1.64GB of virtual. So while real memory is being well utilized, my virtual memory is not. The Doc Size was 57.7MB for each and the Scratch Disk value was 151.5M/1.5G. Efficiency was 100%. Is this a problem with Photoshop CS3? Almost forgot to mention; version is 10.0.1.
If I merge two pictures, flatten, merge another two pictures, flatten and then attempt to merge the resultant two pictures and so on, am I going to run into the same VM problem, just a little later in the work flow?
Any suggestions? BTW, I have seen some suggestions to reduce the source file sizes, but then what is the point of shooting multiple images? Might as well just shoot one high res image and go with that.