33 Layers... - DPChallenge Forums

Canon EF-S 17-55mm f/2.8 IS USM

10/12/2012 07:49:49 AM · #1

So, last night I worked on my Pet Rock entry for roughly 6 hours. It had 33 layers of multiple scenes stitched together by hand; I really liked what I had. I started at 5:00 PM and had roughly a half hour to 40 minutes tops, left of work. I was going to squeek it in just before midnight...things were going great! I was happy. Although the file was huge...too big actually, and as I swiped my select tool over the image...yup...Photoshop locked up...then closed! Did I periodically save the file...naw, why should I?!
Now to say I was angry would be an understatement. Anyone on my block probably heard me drop the F bomb. I think what really got me was that...I'm an I.T. Guy. Been fixing computers for a living for over 20 years. I know better!
So...In a rage I deleted the small hour of a file that I did back up and went to bed..and that is why there are only 31 entries in that challenge and not 32...

bobonacus

Canon EOS-7D

10/12/2012 08:13:56 AM · #2

Oh no, that's gutting :(((((

1st thing I do when installing photoshop, reassign Ctrl + S to save and I constantly press that regardless of what application I am in

Mike

Canon EOS-5D Mark II

Tamron SP 24-70mm f/2.8 Di VC USD Canon Mount

10/12/2012 08:18:20 AM · #3

been there, i though i screwed mine up after i merged my layers, but i did do a save and was able to just close without saving, lost a little bit, but it wasnt bad.

at work on work on a cad platform (microstation) it saves after every design change, every single one. its great but it also spoils me from remembering to save often in things like excel and word and photoshop.

it would be nice if Photoshop did an auto save, lightromm auto saves changes, why cant photoshop?

Denielle

Canon EOS-7D Mark II

Canon EF-S 18-135mm f/3.5-5.6 IS

10/12/2012 08:21:40 AM · #4

ouch!
that sucks.

I don't usually save during editing... occasionally if I do a MASSIVE edit, I will save throughout...

I'm sorry. that really sucks!

gyaban

Canon EOS-1D X

Canon EF 24-70mm f/2.8L USM

10/12/2012 08:30:23 AM · #5

That really hurts. It happened to me too recently, when playing with unstable plugins, and fortunately CS6 implements the 'background/autosave' feature. I was dubious at first, but now I must say it's very useful!

jomari

Nikon D7000

Nikon AF-S DX 18-105 f/3.5-5.6 ED VR

10/12/2012 08:30:46 AM · #6

Commiserations, that really does suck and I've been there numerous times (not 33 layers though). Saving just often doesn't occur to me when I'm happily working on something, although from past experience it should. I find that using the erase tool is one of the most risky practices for making PS crash.

vawendy

Sony Alpha 1

Sony FE 200-600mm f/5.6-6.3 G OSS

10/12/2012 10:50:28 AM · #7

Originally posted by gyaban:

Agreed -- I would upgrade to photoshop 6 simply because of this. Since upgrading, it's already saved me about 10 times (I forget to save...)

Unfortunately, many times it does the autosave AFTER I resized the image to 800 pixels, so I have a small version, but not the large version. But it's better than nothing!!

gyaban

Canon EOS-1D X

Canon EF 24-70mm f/2.8L USM

10/12/2012 11:01:29 AM · #8

Originally posted by vawendy:

Unfortunately, many times it does the autosave AFTER I resized the image to 800 pixels, so I have a small version, but not the large version. But it's better than nothing!!

That's precisely why I never resize my main file. I first create a flattened copy of the whole thing in a new layer (ctrl+shift+alt+E) then copy this layer to a new file, which I resize.

kirbic

Canon EOS R5

Canon RF 24-70 f2.8 L IS

10/12/2012 11:02:36 AM · #9

Originally posted by mike_311:

...lightromm auto saves changes, why cant photoshop?

The answer is, because *all* of Lr's changes are non-destructive, whereas by its nature, Ps changes may be destructive. The implication of this is that Lr can save changes simply by saving a very small sidecar file. Ps has to save the entire file, which can be hundreds of MB, or even into the GB in size.
Now, to Wendy's point, even that's not a cure-all. If you make destructive changes such as resizing that you want to back out, you're out of luck if Ps has auto-saved since the change and you've closed and re-opened the file (or recovered from an app crash). The answer would be auto-save with versioning, but holy cats would that take up space! It does seem like some form of this could be implemented, however, given the massive size of hard disks. Good management of the number of versions, the time to retain them and the maximum space allowed could make it very workable.

Denielle

Canon EOS-7D Mark II

Canon EF-S 18-135mm f/3.5-5.6 IS

10/12/2012 11:03:18 AM · #10

Originally posted by gyaban:

Originally posted by vawendy:
Unfortunately, many times it does the autosave AFTER I resized the image to 800 pixels, so I have a small version, but not the large version. But it's better than nothing!!

That's precisely why I never resize my main file. I first create a flattened copy of the whole thing in a new layer (ctrl+shift+alt+E) then copy this layer to a new file, which I resize.

I save my main image, then do a "save as" then resize and save it again.

vawendy

Sony Alpha 1

Sony FE 200-600mm f/5.6-6.3 G OSS

10/12/2012 11:11:35 AM · #11

Originally posted by gyaban:

Hmmmm.... awesome idea! Though I have the terrible habit of working on the resized file. (what if I try this? Hmmm... maybe I should do this... and then realize it's all on the resized and I don't bother going back and doing the same to the original.

I'll have to try your option -- maybe that will force me to stop working on the resized.

vawendy

Sony Alpha 1

Sony FE 200-600mm f/5.6-6.3 G OSS

10/12/2012 11:12:28 AM · #12

Originally posted by kirbic:

Originally posted by mike_311:
...lightromm auto saves changes, why cant photoshop?

The answer is, because *all* of Lr's changes are non-destructive, whereas by its nature, Ps changes may be destructive. The implication of this is that Lr can save changes simply by saving a very small sidecar file. Ps has to save the entire file, which can be hundreds of MB, or even into the GB in size.
Now, to Wendy's point, even that's not a cure-all. If you make destructive changes such as resizing that you want to back out, you're out of luck if Ps has auto-saved since the change and you've closed and re-opened the file (or recovered from an app crash). The answer would be auto-save with versioning, but holy cats would that take up space! It does seem like some form of this could be implemented, however, given the massive size of hard disks. Good management of the number of versions, the time to retain them and the maximum space allowed could make it very workable.

I like that PS6 isn't auto-save changes, but that it has the recoverable file when a crash happens. It's exactly what I need.

10/12/2012 11:59:28 AM · #13

Originally posted by gyaban:

That is a great idea!! I actually wouldn't want an auto update becuase of the resize...but that is now my new way! :-) Thanks!

I'm still bummed this morning. I really liked the picture, and not sure if I will work on it again. Well, at least I have pictures that I may be able to use in some of the other challenges...by the way..I was trying out the Brenizer method, so my canvas was HUGE! I did the whole thing by hand becuase I didn't like the results of automate feature. It was the stitching that took so long...

10/12/2012 12:00:11 PM · #14

Originally posted by vawendy:

Originally posted by kirbic:

Originally posted by mike_311:
...lightromm auto saves changes, why cant photoshop?

The answer is, because *all* of Lr's changes are non-destructive, whereas by its nature, Ps changes may be destructive. The implication of this is that Lr can save changes simply by saving a very small sidecar file. Ps has to save the entire file, which can be hundreds of MB, or even into the GB in size.
Now, to Wendy's point, even that's not a cure-all. If you make destructive changes such as resizing that you want to back out, you're out of luck if Ps has auto-saved since the change and you've closed and re-opened the file (or recovered from an app crash). The answer would be auto-save with versioning, but holy cats would that take up space! It does seem like some form of this could be implemented, however, given the massive size of hard disks. Good management of the number of versions, the time to retain them and the maximum space allowed could make it very workable.

I like that PS6 isn't auto-save changes, but that it has the recoverable file when a crash happens. It's exactly what I need.

I wish I had that! :-)