Well, _that_ ain't right, John! (Duh! :-) ) That dreadful amount of sluggishness suggests a severe system bottleneck somewhere, or something's just broken. I was using CS5 (circa 2010 version) prior to a recent CC upgrade to edit my 645Z .dng files (converted to layered TIFF by Lightroom) and responsiveness was always quite snappy. Nothing at all like what you are describing.
On paper your system sounds like it should be a speed demon. Have you tried profiling the system with any general purpose benchmarking apps to exercise the various pipes? Is your SSD scratch drive large enough to not fill up when working with the large layered files? Have you accidentally configured Ps to put any one of its scratch files onto a slow device? Ps will use all the file locations you mention to it, so you could remove them all and just give it one to work with. Have you enabled any advanced device features for a peripheral (eg the nVidia) which it actually cannot handle well? You might try turning off any special features like the GPU to see what effect that has. It sure shouldn't be acting like you're seeing, John. My sympathies; most frustrating, I know. On Wed, Apr 25, 2018 at 1:38 PM, John <sesso...@earthlink.net> wrote: > It's the entire program. I'm working on a K-1 .dng file. > > Example ... from the angle I was shooting, the pistol is not visible in the > original image. But the second pirate coming up behind the first to do him a > mischief was the whole theme of the image, so I needed to comp the pistol > in. > > I have other images where the pistol is visible, but the lighting is wrong > and the two pirates are too far apart. So I copied the pistol (with a lot of > transformation) onto a layer sandwiched between two copies of the base > image. Then I made a selection on the top layer to cut out a hole making the > pistol visible. > > I used the polygonal lasso tool to outline the pistol. I should have used > the pen tool, but the delay is so long it's completely unusable. > > I'd click a point & move the pointer a to click the next point ... wait and > wait and wait for Photoshop to show the selection line between the two > points and wait some more for the line to catch up with the pointer. > > Repeat that process for each successive point. There are over a hundred > points in the selection (which I saved as a path so I don't have to go > through that again). > > For reference "wait and wait and wait" is about how much time as it takes to > go into the kitchen, get a cup of coffee and walk back to the desk where I > do my Photoshop work. > > That much coffee would kill me, so I'm thinking about checking out Tolstoy's > "War and Peace" to read while I'm editing. If I'd had it for Monday night's > session, I'd be half way through by now. > > > > On 4/25/2018 08:35, Bruce Walker wrote: >> >> A very cinematic scene, John. >> >> Have you tinkered with the Performances settings in the Preferences >> menu? There are some good tutorial notes and videos in the Adobe help >> site (and elsewhere) that explain the effects of these. >> >> Which specific actions are slow, or is the entire app sluggish? I >> usually find it's one or two specific filters or activities that are >> really slow. >> >> >> >> On Wed, Apr 25, 2018 at 12:04 AM, John <sesso...@earthlink.net> wrote: >>> >>> The PPNC Eastern Guild Seminar offered an opportunity to shoot with >>> Pirate >>> reenactors. >>> >>> https://www.flickr.com/photos/jb_sessoms/41645196632/lightbox/ >>> >>> K-1, 77 Limited. The really grungy, dark look is intentional. Taken >>> inside >>> the "dungeon" at Fort Macon State Park, near where archeologists >>> recovered >>> Blackbeard's ship. >>> >>> >>> https://news.nationalgeographic.com/news/2011/08/110829-blackbeard-shipwreck-pirates-archaeology-science/ >>> >>> https://tinyurl.com/BB-the-Pirate >>> >>> I'm having trouble with Photoshop. It's just soooooooooooooo damn slow >>> and I >>> don't understand why. >>> >>> I've got a fast i7 processor, nVidia graphics processor, 24GB RAM and >>> Solid >>> State drives (with a separate one for Photoshop's scratch disk). >>> Photoshop >>> CS6 Extended 64-bit on Windows 7 64-bit. >>> >>> Photoshop should scream on this machine. Instead I'm ready to scream at >>> Photoshop. >>> >>> I am *NOT* installing Windoze10; I am *NOT* installing Lightroom; I am >>> *NOT* >>> installing CC! >>> >>> But I would welcome *helpful* suggestions. >>> > > > > -- > Science - Questions we may never find answers for. > Religion - Answers we must never question. > > -- > PDML Pentax-Discuss Mail List > PDML@pdml.net > http://pdml.net/mailman/listinfo/pdml_pdml.net > to UNSUBSCRIBE from the PDML, please visit the link directly above and > follow the directions. -- -bmw -- PDML Pentax-Discuss Mail List PDML@pdml.net http://pdml.net/mailman/listinfo/pdml_pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
