Generally speaking, Photoshop places a very heavy load on your computer system when you do a Photomerge.
If your system isn't up to the stress, or if you have it misconfigured - e.g., the Photoshop RAM limit is too high and it starves the OS for RAM, or if your hard drive fills (scratch files can be huge during Photomerge) - then you might see a lock-up.
Are you seeing it actually crash (i.e., with a message), or just become unresponsive? If the latter, have you left it alone for a long time?
Thanks for the reply. It doesn't actually crash, but after about 10 minutes I give up when the cursor is still not moving. Now it is getting hung up and not moving on "align selected layers based on contents". I then go to Task Manager and it tells me PS is no longer responding and I need to shut it down through this as I can't shut it down through the PS window. I have 50 GB scratch disk and 12 GB RAM which I think should be more than enough.
Any other ideas. Again, it works fine with CS^ & CS5.
I don't know how big your pano is, but I've seen Photoshop use over 200 GB of scratch and a lot more than 12 GB RAM to do a pano.
Rather than assume it's not responding, go into the Task Manager and look in the Processes view to see if Photoshop.exe seems active, i.e., RAM allocations are changing, I/Os are happening, etc.
How big are your files, and how many of them are there?
Can you make it work with a couple of small overlapping images?
Just as a reminder, this strange behavior does not occur when I open the files directly into PS CC and use photomerge. It only occurs when I bring them into PS from LR with Edit in/merge to panorama in PS. And again, it down not occur in CS5 or CS6.
I am trying to merge 5 files that are about 80 MB each when it doesn't work. If I make the files smaller, say 300 KB each, it works. But I don't think 5 files of 80 MB each should overload my system.
When I go into Task Manager as you suggested and look in the Process view, Photoshope.exe does seem to be active, though it says not responding in the Application view. If it helps you, the memory usage is 1,075,556 KB
Chances are good that it's using a lot more resources than you think it should, but I can't say for sure.
Is it the 32 or 64 bit Photoshop that's running? That will matter in how much RAM it can use and how heavily it will use your swap file.
Also, when it seems to stall, look at your free disk space on your scratch drive and see if perhaps it's gotten short.
I am runnign Window 7 64 bit.
How do I look at the free disk space on my scratch drive when it stalls. I can Right lcik on my scratch disk file and go to properties and it tells me it has 45 GB avaialble and 5 GB used, but that's the same as when I'm not running PS, so I don't think that's how to do it. So how can I answer your question?
Just looking at Computer should show you an overview of scratch usage. There's no magic.
I suggest that if you're not seeing more than 5 GB used, then Photoshop has chosen to use another drive for scratch. For all drives other than the system drive, Photoshop will put files in the root folder of the drive of the form Photoshop Tempnnn...n where nnn...n is a number. You should see these files created when Photoshop is run by looking at the folder in Explorer.
I really appreciate your sticking with me and trying to solve this issue
for me and explain what's going on. Unfortunately, you're getting a little
over my head in my knowledge and understanding of computers.
I've double and triple checked my PS preferences and I have the correct
drive selected for my scratch disk.
I'm just having trouble understanding " Photoshop will put files in the
root folder of the drive of the form Photoshop Tempnnn...n where nnn...n
is a number. You should see these files created when Photoshop is run by
looking at the folder in Explorer.
We may be going beyond the time you're able to put into helping me, and if
so, I understand, but any other thoughts would be appreciated. I suppose
the work around is just to open them directly into PS and use photomerge
I am getting the same behavior from PS CC, if I select my images in bridge and use the photomerge option from there PS hangs on the blending, they align as quick as they should but blending is painfully slow. I do a lot of pano's, mostly with a TSE lens so photoshop should have no problems stitching as there is no paralax. Photoshop CS6 used to just chew through it.
The process does complete eventually, like i said it just hanges for a long time, once it kicks back into action is proceeds at a pace that I would expect. After the align layers based on content is complete and the blending layers .... starts the progress bars fills to about 1/5 then hangs........ 4/5 minutes later (worst case) then its zipp.. off she goes again. Its almost as is Photoshop has cought narcolepsy and has a spell half way through.
I use a hex core CPU and have 64ig of ram and allocate PS 40gig, I use a standalone (PS only) 120gig SSD as the primary scratch then a 64gig SSD as the secondary scratch, after that its the system drive. Monitoring the scratch during the blend the temp files get up around 5gig, the application is "not responding" in the task manager.
I cant believe its lack of resources, my PC was built for photoshop.. I also feel confident its not my system by the way it handles surface blur on large area 16bit images, I can run a 30 pixel radius @ threshold of say 20-30 in approx 1-2min which I think is very fast.
The panos I am attempted are also really quite small, three files from a 5DII, a laptop could handle that!.
Does it matter that I load the cr2 files into photomerge?, although I am sure it never used to so why would that matter now.
Like also mentioned above If i load the files into photoshop as layers then run photomerge (auto align layers) it completes the process in about 15-20 seconds.
I am happy to use the workaround of loading the files into PS, not looking for a solution but rather thought I would post FYI
Look in the Task Manager when it's running... Is it 32 or 64 bit. If the former, you know what's wrong. Is it possible you're running the 32 bit Bridge?
I do panos directly from .cr2 files myself, and select them via the dialog I get in 64 bit Photoshop when I choose File - Automate - Photomerge.
I am definetly running 64bit editions for both apps.
When I run the process through file>automate>photomerge I get the same hang as if running it from bridge.
Its very confusing, in the applications photoshop is "not responding" though in the processes I can see that its active, the usage is changing albiet only a few bytes at a time. In the performance the CPU usage is around 7-10% but with some obvious spikes intially in all six cores, and the memory is about 8gig (13%), another reason why I dont think its a resource issue.
Its the blend process, the aligning is just fine. I can use auto align layers and then do a manual blend, but if I auto align the layers and then auto blend panorama I get the same behaviour. At first I thought it might be because I was trying to blend merged bracketted images that had some motion in them and photoshop was having trouble blending but its the same with single images with no motion blur in them at all.
Like I mentioned earlier I use mostly shots from a TSE so they are distortion free so manualy stitching is basically just as fast, I still like to use the automated feature though as it does such a good job. I dont think I would like to be stitching multiple images with paralax with this problem, it would be very frustrating.
I too am still having this problem.
When I start in LR5.2/edit/merge to panorama which open pscc 64 bit, it
If I start in LR/edit all 3 files from LR into PSCC 64 bit and go to
file/automate/photomerge/open files/ it takes forever
But when I start in LR and edit all 3 files in PS CS6 and then go to
photomerge, it works fine.
It seems like it has to be a PSCC problem. Because it works fine in CS6.
I am also running into this. My system has plenty of resources, and Photoshop CC is setup properly with plenty of memory and scratch disk space, but when I try even a small 2 picture panorma from lightroom 5, photoshop CC stops on aligning the images. I can cancel the action fine, and nothing is frozen but the pano never completes. Photoshop CS6 does not have this issue.
Nope, at least not a bug that's easily reproduced by everyone.
I have a set of 25 raw files that I have set Camera Raw to open to 6144 x 4096 pixels @ 16 bits/channel. I use this set for benchmarking Photoshop.
I have benchmarked stitching these together into a 344 megapixel result since Photoshop CS5. My best time with Photoshop CS6, starting by selecting all the .cr2 files, was 6 minutes 26 seconds. Photoshop CS5 turns in a time of 6 minutes 35 seconds.
I just did them in 6 minutes 15 seconds with Photoshop CC 14.1.2. There are certainly some parts of the process that are single-threaded, but I see no new problem here. Photoshop CC is faster than ever.
My advice is to look for causes that might have something to do with your specific system or setup (e.g., scratch drive assignment, or memory limits).
yes i think its fair to say its not a global bug affecting all users but it is apparantly quite wide spread, just like the sampling issue with the healing brushes and clone tool. That has not affected everyone but has many and has only since the release of CC.
In almost all case though all was good in CS6 and earlier, if it is indeed a system or resource issue, why now, why not with CS6 and earlier. My biggest regret so far with CC is that I unistalled CS6 before installing CC, now I have no easy recource as I cant reobtain CS6 through the cloud which i would do in a heartbeat if given the chance.
"My advice is to look for causes that might have something to do with your specific system or setup (e.g., scratch drive assignment, or memory limits" If you read earlier posts this has been discussed and unlikely the cause, my settings are identicle to that of what they were in CS6 where all worked just fine.
now I have no easy recource as I cant reobtain CS6 through the cloud which i would do in a heartbeat if given the chance.
I just downloaded and installed a copy of Photoshop CS6 from the cloud the day before yesterday.
In my case, I went to Adobe.com, drilled down through the various Product links, then found a "Log in to Creative Cloud" link (it was on this page, specifically).
Once I logged in, I saw a screen full of product icons, including [Ps]. Next to it was a [Download] button, which I pressed.
That took me to this page: https://creative.adobe.com/products/photoshop
Note the little version selector at the left side, just under "In this version". It's set to [ Photoshop CC v ], but the little arrow at the right means you can pull it down and change it to Photoshop CS6.
Have you tried restoring Photoshop's preferences and restart both Photoshop and Lightroom?
It hangs when aligning and blending, depends how small images is. I also got monitoring of every system resources on a seperate LCD and noticed strange things. CPU only use 10%, GPU 0% and i got 12 GB free RAM, and even then PS CC hangs. This screenshot is after 30minutes of waiting on 10 images from 5D Mark III raws. Also happends if I use jpeg, but thats not a option. I got plenty of hardware power.
i7 3690x 5GHz watercooled, 16 GB g.skill ripjawz, gtx 580 amp2+, 4 velociraptors in raid5 and pci-e ssd.
Im also pretty sure this didn't happend with PS CS6 x64, but I removed that when I got PS CC x64.
Im using x64 os and x64 applications only.
CPU: 11% might indicate it's still working on something in one or more cores, though at 30 minutes it's getting awfully long. I take it the progress bar stops moving?
I suggest that 16 GB of RAM is not enough to be stitching 10 5D images in Photoshop. It should be enough for practically anything but Photoshop is not miserly with RAM when it comes to stitching panoramas. I've seen it use more than that when stitching sets of 25 MP images. It's possible there is part of the Photomerge that is incapable of using Photoshop's virtual memory system. I have yet to have a Photomerge fail or stall with 48 GB of RAM.
If you have a single SSD on a SATA III connection you'll only ever be able to sustain 500 MB/second I/O, by the way. That's because of the SATA speed.
Just out of curiosity, and kind of a shot in the dark... Does the behavior change if you lower your History states in the Performance preferences (e.g., to 10)?
If it can be at all helpful, here's a sequence of what happens in order, and how long each step takes, in the case where it completes successfully. Note that the overall operation to stitch 12 raw files opened to 6144 x 4096 x 16 bits/channel took a hair over 3 minutes to complete, and used 18 GB of RAM and 30 GB of scratch space,.
Selecting the files:
Hitting the [OK] button at exactly 10:20:00:
First thing we see in Photoshop at 5 seconds is the first image being opened:
At 47 seconds all images are opened and aligning begins:
At 1:46 Blending commences on the wider canvas:
At 2:45 into the process, it's creating layer masks.
At 2:57 it's creating a seamless composition:
At just over 3 minutes, it's done. Note especially that RAM usage has risen to 18.3 GB total.
Note also that 30 GB of scratch space was allocated. This was a fresh run of Photoshop.
Since I have a trial version of CC installed I though I would give it a try. My machine is capable of handling Photoshop CC. When I retired some 10 years ago I treated myself to a trip to New Zealand. I took a series of 13 portrait oriented images there to be stitched. Taken on top of the mount 360 around. Oly e-20 5Mpixel camera so 65Mpixel in all. Photoshop CC Photomerge had no problem stitching the images. Here is a screen capture.
Image on to the Photomerge layered stitched. Middle image stitch was done using different software. Bottom image a copy of the Photomerge image flattened and offset wrapped to match the order on the center stitch. Photomerge started it looks like stitching the first image in the middle of the panorama and wrapping around looking at the image layer names and the position they have been put in the stitched image. The stitch was quite fast and did not use much processor power.
You can set Camera Raw to open images at a higher pixel count if you want to test with larger images. Mine, as mentioned, were opened at 6144 x 4096 x 16 bits/channel, so as to stress Photoshop similarly to epos85. I suspect if you use larger images with a higher bit depth you'll see the resource usage go up as well.
And yes, I do see the stitch seams as well at zoomed-out resolutions. That's understandable as Adobe only includes a few pixels overlap in the masks, and zoomed-out resolutions average more pixels together.
Somewhere here I have a set of images that go around 360 degrees. I think I'll find them and experiment.
How long did your system take to stitch that pano? And how long if you stitch images the size I described? I'd be lying if I said I didn't crave a couple of E5 Xeons.
Yeah, but under 5% is PS only. I got a few more applications running in the background. None of them affects photoshop. It actually took >1.5 hr in total the last sequence with 15 images, 45minutes with 10images. It didn't move at all for quite a while. Sometimes PS will crash before it finish without making a errorlog.
There are no problem with RAW and 25Mpix. As I mentioned, I've tried this with PS CS6 and that worked like a charm before. I didn't remember this earlier, but I made a pano of 50 RAWs in PS CS6 without taking over 1 hr. This slowness happends with small and large jpegs\raw's in different degrees. Can't compare to CS6 in speed, so they must have changed something in photomerge after CS6.
My SSD is PCI-e and is the worlds fastest consumer based SSD from OCZ with 1-2GBs link. I got the bench somewhere if you doubt I know SATA3 got 500MB/s, you should read more about PCI-e disks because theyre awesome. http://ocz.com/consumer/revodrive-3-x2-pcie-ssd .. Im actually thinking of running that in raid, if its possible. I doubt the north bridge is faster than 3GBs though.
I'll try it and post the results I'll also going to install PS CS6 again and retry with same group of files.
Btw, excuse my rusty English.. Im from Norway.
At 00:35 GMT+1 choose "merge to pano in PS" in Lightroom. At 00:40 GMT+1 it was finished! 15x 25Mpix Canon raw files, same that took me 1.5 hrs to finish earlier. Guess what.. Cache levels was set to 2 (recommended by PS, not default).
Still, I had no difference in GPU/CPU/RAM usage. ~12% CPU, 0% GPU, approx 7GB RAM and low disk spin. There must be a bug somewhere, just gotta be when you can't see any difference in resource usage when changing those settings. I've tried higher value than 4 (default) but not getting any faster. Setting cache levels to 3 from 4 is like 1/2-1 hr in difference, setting it to 2 is 1.5 hr difference from 4.
Downside is that PS say: Set Cache Levels to 2 or higher for optimum GPU performance. Might notice other problems when retouching now.
History states to default didn't make any difference.
PS CS6 x64 with identical performance settings like when I had problems in PS CC, had no problems at all. Finished in ~5 minutes. It also startet faster and loaded images faster, same procedure. Ive also tried deleting adobe settings file and setting cache level to 2 in PS CC but its still slow.
Someone who can write better English should post a bugreport to Adobe about this. I hope you guys try this and post your results in PS CC. Try setting cache levels to 2 from 4 (or from you cache level to 4) and see the difference. Looks like 4 is the magic number for me if im doing panos. What do you get in time difference, and what gpu/cpu/os do you have?
I stand corrected; I had momentarily forgotten about the RevoDrives. I have a RAID array of OCZ SSDs and know a good bit about about SSD storage, actually. Sorry about the momentary lapse, and to have doubted you. I chose to go the PCIe SATA III controller with traditional disks route myself. I get 1.6 gigabytes/second throughput, though I suspect I may have more total storage than you do (2 TB). If I remember correctly, the RevoDrive actually IS a RAID subsystem under the covers.
Cache Levels should have little to do with how things like pano stitching will work, and more to do with how responsive your display will be. In an oversimplification, you're basically telling Photoshop how many pre-downsized images to create so that when you zoom out the data will already be ready for display at that size, with only minimal additional sizing.
If your Cache Levels setting is greatly affecting your performance, it's possible your GPU driver (aka Windows display driver) isn't playing well with Photoshop. I didn't think to suggest updating your driver before. Go to the web site of the maker of your video card and see if they have an update. Usually the latest is the best.
Glad you're seeing better perforemance now!
No problem, Its not a standard disk. Even I forget that.
Nice, only 1 TB here I know, but would have been nice to tried PCI-e Raid if that exists
Yeah, its strange. Well, im currently running latest nvidia driver, have tried with older driver also but no difference. Looks like my 2nd workstation have this problem too, so I doubt its only a hardware issue. Im not the only one with issues in photomerge either, I suggest people having problem change their cache levels and retry. People who don't have this problem, no matter OS or GPU/CPU should also try. It might be a nvidia or software issue. Adobe's applications isn't exactly known to lack bugs.
With you MAC(?), what happends when you set your cache levels from 4 to 2? If youre using 2, then try 4. Im just interested to solve this issue since it might be more than just my workstations. (There is a reason for this thread I guess) I hope Adobe read this.
Yeah, but will it solve the issue in total? I don't know yet. I probably gonna notice other performance issues when retouching or stuff like that.
No Mac here; I have a PC workstation (Dell Precision T5500) running Windows 7 x64.
For what it's worth I have always kept my 64 bit Photoshop set to Cache Levels 4, but I just tried 2 and the same stitch as above...
Just as you did, I saw it stall right at the beginning of "Align Selected Layers Base On Content". It doesn't look to be completely stopped, just INCREDIBLY slowed down, since a little green finally did show in the progress bar. But I didn't wait past 9 minutes for a resolution.
Looks like a bona fide bug, triggered by the lower Cache Levels setting.
I've submitted a bug report to the developers (though chances are they've seen this thread already).
Good job isolating the trigger condition! I'll have to remember to mention Cache Levels if others report similar problems here on the forum with stitching or layer alignment functions.
Just for fun, I ran Cache Levels up to 6 to see what it would do with the same stitching job. It came out to 2 minutes, 44 seconds - a sizeable reduction in time vs. my 3 minutes even before. So I can only suggest trying 6 yourself.
I can imagine that maybe the folks who programmed this feature used the downsized images available behind the scenes when Cache Levels is set to a higher number to facilitate quick, rough alignment.
Thanks for trying out mate. Just proves more there is an issue with cache levels.
It slows completly down, and in some cases PS will quit and not give any errors in errorlog. If you now try with PS CS6 (if you have it), there will be no problem -no matter what cache level setting you use. Thanks for submitting the bugreport. How is your retouching now then? You might get poor performance in other areas, at least when using cache level 6. Im completly noob about these setting and don't know what they do. I just know computers in general and try to isolate problems as you said. So thanks for the coop on this one
I actually have to admit something.. I had this bug earlier and submittet it to a thread on this site, but forgot it since I rarly use photomerge:
Chris Cox said he couldn't reproduce then. I find that strange since we have tried on several workstations (3x in this house) and could reproduce easily. You should check and maybe reply to that thread too. Its been a while since I posted there, but I got no reply form him. Don't know if they forgot or still trying to isolate the problem. You and other people who read this thread could click on "I have this problem too", if that speeds things up. Although ,im pretty sure they will read about it again since you submitted a bug report.
I'll try cache level 6 right away. Would have been nice to see what other things will change when we increase that number. Im afraid we loose performance in other sections now. Yeah, agree. I assume they think 10 small images will replicate 10 raw files, and thats not the case every time.
Just keep this tread warm. I'll report back on the cache level 6 results soon as possible. Gonna try some retouching, panos and focus bracketing stiching.
That's interesting that you should say Photoshop CS6 is faster, because I've noticed just the opposite.
For all things Photoshop CC 14.x has mostly been equally fast, if not a little faster - on my system. I've run specific benchmarks to determine this, including several of my own devising. Plus I still have the old versions of Photoshop installed, and can compare them directly. For me Photoshop CC has been the most responsive version yet. But of course we all use Photoshop a little differently from one another.
One notable exception, where Photoshop CC does seem (and measure to be) a bit slower is in painting operations with very large brushes.
Just as an example, here are some benchmark results where I've found Photoshop CC faster, from my logs... I hope this comes out readable...
Photoshop test file operations: CS6 x64 CC x64
Drag 1,736,577 KB PSCS6_large_test_file.psb to unopened Ps: 21.6 seconds 20.8 seconds
Save compressed test file as CompressedSave.psb: 20.4 seconds 20.2 seconds
Drag white dots layer around at 12.5% zoom: 4 FPS 10+ FPS
Drag black dots layer around at 12.5% zoom: 3 FPS 6 FPS
Drag white dots layer around at 100% zoom: 3.3 FPS 5 FPS
Drag black dots layer around at 100% zoom: 2.5 FPS 3.5 FPS
Flatten image: 13.8 seconds 13.8 seconds
Stroke Black soft 1000 pixel brush across top layer diagonally: 1.2 seconds 1.2 seconds
Stroke Black soft 5000 pixel brush across top layer diagonally: 6.4 seconds 12.0 seconds
Drag to Photoshop, time to open in Camera Raw 7.2 RC: 3.0 seconds 2.0 seconds
[Open Image], time to open as 6144 x 4096 16 bits/channel: 7.4 seconds 3.2 seconds
Fractal Sharpen, Med Sharp Low ISO: 1:44 1:20
Double click 64 bit Ps CS6: 3.2 2.8
Double click 32 bit Ps CS6: 4.4 4.6
http://clubofone.com/speedtest/: 13.0 seconds 11.0 seconds
CS5 x64: 14.8 seconds
CS4 x64: 16.0 seconds
Panorama Stitch of 25 6144 x 4096 raw files @ 16 bits/channel:
344 MP result: 6:46 6:15