Too Stupid to NOT Clog Up Memory with PhotoShop!

Nikon AF-S DX Zoom-Nikkor 18-70mm f/3.5-4.5G IF-ED

02/06/2007 12:55:37 PM · #26

Originally posted by kirbic:

With an image open in the converter window, right-click in the image area. Here you can change the options. Click on "Normal" at the top and you should be all set.

That fixed it!

Thank you soooooooooo much!

It does both the side cropping that I want it to and saves the cropped image.

So.....am I stupid and inept, or what?.....8>)

It constantly amazes me how these tiny little things that I do not know and have to learn can foul me up so badly.

I want to take courses to learn basic stuff, but I don't know enough to figure out what to go after.

Suggestions?

Shecoya

Nikon D70s

02/06/2007 12:57:57 PM · #27

lmfao... OKAY you know what.. YOU JUST MADE MY DAY NikonJeb...

in the not so distant past.. (couple of weeks ago actually) Pedro got a distressed call from me.. in a panic.. You see he built my computer and hooked me up with everything needed to pursue this photography stuff. I have huge memory on my computer but I was getting scratch discs full.. no memory etc.. everytime I would edit. Figured I needed YET another computer..

Well P comes over to rescue me, ran a bunch of stuff on the computer etc.. everything looked great.. should be no problem. Then I show him some pictures and try editing stuff so he can give me tips..

LIGHTS FLASHED.. alarms went off.. bells rang.. as soon as I cropped an image he started laughing.. Much to my dismay I might add.. *then he very politely and with a lot of kindness, pointed out *inches* Erm.. yeah. was a lesson hard learned but very effective.*

I'm just sooooooooooooo happy to have someone else in the world who had to learn the same lesson ;)

Smiles..

GeneralE

Canon PowerShot S3 IS

Canon 12x IS USM (S3 IS built-in Lens) -- 36-432mm (35mm EQ)

02/06/2007 12:59:53 PM · #28

Originally posted by NikonJeb:

Originally posted by Pedro:
might be a silly question, but had you used the crop tool on the image when you got the message? more than a few times I've seen people intending to crop to 640pixels, and they inadvertently have the units as inches instead...so they end up creating a file that's a brazillion googlibytes (which is really really big).

Umm....isn't that when you're sizing an image as opposed to cropping?

If you have the units set to inches you are upsizing at the same time ... an image which is 640 inches would be considerably larger (640 x 300 ppi = 192,000 pixels!).

Even is you don't do this, PS can "stall" when you crop because it keeps several "versions" of your image in the scratch-disk area, which is what allows you to "undo" many of your editing changes. As I recall, PS recommends that your scratch disk have available about five times the space of the largest (uncompressed) image you open, so a 40MB file should have at least 200MB of free space to play with.

But really, in this case, more RAM is probably your most (cost-)effective solution; 512 is probably barely enough to run the OS effectively, meaning PS may be loading mainly into virtual memory.

Brad

Olympus OM-D E-M1

Olympus 40-150mm f/2.8 PRO M.Zuiko

02/06/2007 01:03:21 PM · #29

I *cough* did just that a couple weeks ago *cough* and was all over my hardware *cough* trying to find the problem.

I failed to realize there was a dork involved - the dude in the mirror.

02/06/2007 01:04:18 PM · #30

Originally posted by Bear_Music:

IMO you should never crop out of the RAW processor...

Actually, I don't necessarily agree. The crop tool in ACR actually has much more flexibility than the very limited version in Photoshop itself. For instance, it's easy to constrain to a ratio without worrying about PS outsmarting itself and messing with the pixel size. FWIW, when cropping in Photoshop, I always use the rectangular marquee tool instead of the crop tool, because of the horrid limitations of the crop tool. It's one thing I can't believe they didn't fix in CS3, though there's still hope since it's still in Beta.
Your RAW file is your "negative" and there's no reason not to crop in conversion, if you know what your intent is. I *do* feel that it can be beneficial to crop near the end of workflow if you don't have a set idea of what the crop should be.

Nikon AF-S DX Zoom-Nikkor 18-55mm f/3.5-5.6G VR

02/06/2007 01:14:38 PM · #31

Originally posted by Bear_Music:

Originally posted by NikonJeb:
I don't know how to vignette in regular non-RAW processing in PS.

In CS2, your vignette tool is in filters/distortions/lens correction.
R.

Thanks!

I've wanted that for some time now.

Is that considered something that can be done in Basic, or not?

RainMotorsports

Nikon D60

02/06/2007 01:15:40 PM · #32

Originally posted by NikonJeb:

Originally posted by rainmotorsports:
Hey are u running Camera Raw 3.6 and have Photoshop 9.0.2 update installed?

I believe so, how do I check for sure?

As I said, I got it in November and I did the 72 MB worth of updates at that time when I installed it.

That took ALL night on my dialup.

All night heh should have taken all year.

02/06/2007 01:22:30 PM · #33

Originally posted by BradP:

I *cough* did just that a couple weeks ago *cough* and was all over my hardware *cough* trying to find the problem.

I failed to realize there was a dork involved - the dude in the mirror.

I found out many years ago that most computer problems are PBKS.

I've never forgotten that.

It almost always turns out to be that way when I have a problem.

Tamron SP AF 28-75mm f/2.8 XR Di for Canon

02/06/2007 01:25:27 PM · #34

Originally posted by NikonJeb:

Originally posted by Bear_Music:

Originally posted by NikonJeb:
I don't know how to vignette in regular non-RAW processing in PS.

In CS2, your vignette tool is in filters/distortions/lens correction.
R.

Thanks!

I've wanted that for some time now.

Is that considered something that can be done in Basic, or not?

Only in Advanced or Expert.

Bernard_Marx

Canon EOS-40D

02/06/2007 01:29:15 PM · #35

Hey - I am happy all ended so well! You should offer to send Pedro a pizza or something (though I imagine a thanks would suffice for him).

Do follow the don't open bridge (or anything else) advice for faster performance though.

Do follow the get some more ram and a 2nd hard drive advice.

Pedro

Nikon D200

Nikon AF Zoom-Nikkor 70-200mm f/2.8 VR DG IF-ED

02/06/2007 01:49:18 PM · #36

Sorry I wasn't here to follow up in time - glad Fritz got you sorted out.

...and to echo him (yet again) I also tend to crop in Adobe RAW converter as it doesn't do any upsizing, and it lets me get the exact same crop each time if I want to throw on some more layers or body parts after I've messed with the working copy. If i don't crop in RAW, I use the square marquee tool in 'constrain aspect ratio' mode and then image-->crop, then upsize afterwards.

and seriously don't feel bad - how do you think I got to know about the problem in the first place? ;)

02/06/2007 01:50:45 PM · #37

Originally posted by santaspores:

Okay....I will, but how do I get a pic up in CS2 without opening Bridge?

How big of a hard drive do I need and are we talking an external that hooks in through USB and ends up being drive F or something?

Can I probably take the 256 RAM card out of an old box I have and just add it into this one?

Or should I just not screw around and go get 512 more?

Sony 24-70mm F4 Vario-Tessar T* FE OSS

02/06/2007 02:01:09 PM · #38

Originally posted by NikonJeb:

Okay....I will, but how do I get a pic up in CS2 without opening Bridge?

You'll need to be able to see the thumbnails, so you'd have to have the Windows RAW thumbnailer installed. Then you just browse to the photo and double-click it. It should open in the RAW converter.

Originally posted by NikonJeb:

How big of a hard drive do I need and are we talking an external that hooks in through USB and ends up being drive F or something?

yoiu could do either an external or internal. Unless you've got Firewire, I'd recommend an internal. These days, even 200GB drives are pretty cheap. Take the number of pics you shoot in a year, multiply by the RAW file size, then estimate how many edited pics you keep and their average size. Now you've got your *current* annual space needs. Buy for at least twice, preferably 3 times that.

Originally posted by NikonJeb:

Can I probably take the 256 RAM card out of an old box I have and just add it into this one? Or should I just not screw around and go get 512 more?

Probably not. RAM specifications change. You'll need to get what's compatible with your current box. If you already have both "banks" used, you may have to replace your current memory as opposed to augmenting it. This is something you may want your local computer geek to look at.

Bear_Music

Samsung Galaxy S24 Ultra

02/06/2007 02:20:35 PM · #39

Originally posted by kirbic:

Originally posted by Bear_Music:
IMO you should never crop out of the RAW processor...

Actually, I don't necessarily agree. The crop tool in ACR actually has much more flexibility than the very limited version in Photoshop itself. For instance, it's easy to constrain to a ratio without worrying about PS outsmarting itself and messing with the pixel size. FWIW, when cropping in Photoshop, I always use the rectangular marquee tool instead of the crop tool, because of the horrid limitations of the crop tool. It's one thing I can't believe they didn't fix in CS3, though there's still hope since it's still in Beta.

Your RAW file is your "negative" and there's no reason not to crop in conversion, if you know what your intent is. I *do* feel that it can be beneficial to crop near the end of workflow if you don't have a set idea of what the crop should be.

I'd agree with that if I was absitively, posolutely 100% sure where I was gonna go with the cropping. But to me there's nothing more annoying than to do a lot of work on a cropped image and then realize, after the fact, that I'd have preferred it in a different, less extreme crop.

So what I do is take a 16-bit TIFF to CS2 and then work on the image as a whole at least 90% of the time, then do my cropping (usually with the marquee tool, like you do) at or near the end of the work flow, then save-as "-crop". Maybe it's just me, but that seems more efficient to my way of thinking.

R.

Sony 24-70mm F4 Vario-Tessar T* FE OSS

02/06/2007 02:20:49 PM · #40

Thank you all MOST egregiously!!!!

I am going to a job interview.....I've been unemployed since the week before Thanksgiving....wish me luck and I'll talk to y'all later.

This place ROCKS!!!!!

Bear_Music

Samsung Galaxy S24 Ultra

02/06/2007 02:24:51 PM · #41

Good luck, job-seeker-jeb!

R.

Pedro

Nikon D200

Nikon AF Zoom-Nikkor 70-200mm f/2.8 VR DG IF-ED

02/06/2007 03:28:12 PM · #42

Originally posted by Bear_Music:

That makes some sense to me, particularly if you're doing a lot of edits to the working copy. Since cropping in Adobe RAW Converter doesn't actually affect the original I've never worried about that much. I dunno if it's just because I'm getting more efficient (pfft - I mean lazy) but I'm finding I do most of my editing (exposure/shadows/sharpness/contrast/etc) in the RAW converter now, so even if I want to change my crop after the fact I can do it and save the rest of my edits.

But for those ones that I do a lot of work in PS after the conversion it makes good sense to save the crop until afterwards :)

02/06/2007 04:07:52 PM · #43

With CS3, there's a solution that, while a little clunky, is the best of both worlds...

- Convert from RAW, don't crop
- Edit to heart's content
- Save and close
- File>Open As, select file and select "Camera RAW" from the "Open As" drop-down.
- File will open in ACR, and you can use the full-featured crop tool included in ACR. :-)

The only thing that the ACR crop tool does not allow is changing the opacity and color of the applied overlay on the cropped portion of the image. I wish I could change this, but I'll live with it to get a full range of cropping choices.