DPChallenge: A Digital Photography Contest You are not logged in. (log in or register) 
 

DPChallenge Forums >> Tips, Tricks, and Q&A >> Too Stupid to NOT Clog Up Memory with PhotoShop!
Pages:  
Showing posts 1 - 25 of 45, (reverse)
AuthorThread
 02/06/2007 11:49:38 AM · #1
Hi!

I have CS2 and I'm too stupid to figure out what to do when the Camera RAW Save Status box comes up and says "Not Enough Memory".

What have I done????

How do I fix it????

I hate being this inept!

HELP!!!!
 02/06/2007 11:52:21 AM · #2
How much RAM do you have?

How much of it have you allocated to Photoshop?

What is the size of your virtual memory?

How big is your scratch disk? Is it full?
 02/06/2007 11:53:39 AM · #3
Originally posted by NikonJeb:
Hi!

I have CS2 and I'm too stupid to figure out what to do when the Camera RAW Save Status box comes up and says "Not Enough Memory".

What have I done????

How do I fix it????

I hate being this inept!

HELP!!!!


Not sure what your running into exactly but a 9 MegaByte RAW, when opened into photoshop resids in memory as a bitmap. All images are covnerted to a bitmpa internally during editing and then are recompressed into whatever format u save them into.

A 9MB RAW image could potentially be a 40 Meg Bitmap. A 50 Meg PNG can be a 1.66 GB Bitmap.

I dunno how big the raw ur working with is but i cant imagine it would have any memory issues lol.
 02/06/2007 12:01:50 PM · #4
Originally posted by cpanaioti:
How much RAM do you have?


512

Originally posted by cpanaioti:
How much of it have you allocated to Photoshop?


How do I ascertain that?

Originally posted by cpanaioti:
What is the size of your virtual memory?


I do not know what that means.

I was serious when I said inept.

Originally posted by cpanaioti:
How big is your scratch disk? Is it full?


You're going to have your hands full with me......fairly tech ID10T

I *will* follow orders, though!

Message edited by author 2007-02-06 12:03:00.
 02/06/2007 12:07:15 PM · #5
Originally posted by rainmotorsports:
Originally posted by NikonJeb:
Hi!

I have CS2 and I'm too stupid to figure out what to do when the Camera RAW Save Status box comes up and says "Not Enough Memory".

What have I done????

How do I fix it????

I hate being this inept!

HELP!!!!


Not sure what your running into exactly but a 9 MegaByte RAW, when opened into photoshop resids in memory as a bitmap. All images are covnerted to a bitmpa internally during editing and then are recompressed into whatever format u save them into.

A 9MB RAW image could potentially be a 40 Meg Bitmap. A 50 Meg PNG can be a 1.66 GB Bitmap.

I dunno how big the raw ur working with is but i cant imagine it would have any memory issues lol.


Okay.....XP home, I have 58.2 available from an 80 on my local disc C, 2.93 Ghz, 493 RAM Celeron.....that's about the extent of what I know.

Most of the RAW files that come out of my Nikon end up 4.0 to 6.0 when I'm done, save and convert.

Message edited by author 2007-02-06 12:08:14.
 02/06/2007 12:10:54 PM · #6
CS2 is not happy with 512MB's of RAM... seriously. One of the best ways to sped it up is to add more RAM.

Secondly it likes to have a second hard drive as a scratch disk (one separate from Window's Virtual Memory).

My system is set up where all my documents are on a second drive, which is also my Photoshop scratch disk.
 02/06/2007 12:12:48 PM · #7
Colette's questions are useful ones...
I will assume you are using XP

How much RAM do you have? Start button, settings, control panel, system. You should see the amount of your RAM on the General Tab of your System Properties. Hopefully you have at LEAST 512MB. 1GB should work well.

How much of it have you allocated to Photoshop? This question is for MAC people.

What is the size of your virtual memory? tart button, settings, control panel, system. Click the Advanced Tab. Under performance, click the settings button. Then click the Advanced tab. Under virtual memory, see what it says for total paging file size for all drives. If you have more than one HD in your computer, you should click the change button, then select your secondary HD (highlight the one that is not C:),then below select the "System managed size" radio button and finally click the Set button. Note that people might want to argue this point, but if you don't know what you are doing you should definitely let the system manage your virtual memory.

How big is your scratch disk? Is it full? In Photoshop click Edit-preferences-plug-ins and scratch disks. Next to first you will see "Startup". Under second and third and fourth you can select other hard drives. If you have to drives for example, you would select it under second.

Note: performance is a HUGE multi-variate issue - to complicated for a thread... I just wanted to make clear what was already posted...
 02/06/2007 12:14:31 PM · #8
With XP and 1/2GB RAM, running Photoshop will be a bit taxed, especially if your machine has been running a while, you have the web up & running, other applications running like Media Player, etc.
Best suggestion without being there, is when you want to do some RAW editing, or dealing with large files in PS/multiple layers, etc, best if done on a freshly-booted machine, with nothing else running.
 02/06/2007 12:14:59 PM · #9
Originally posted by santaspores:

How much of it have you allocated to Photoshop? This question is for MAC people.



And only for Mac people NOT running OS X (OS 9 or ealier). We haven't allocated memory for a looooooooong time.
 02/06/2007 12:18:02 PM · #10
Jackson,

You system is a poor performer I am afraid. You can run CS2 successfully with your specs, but would need a computer-pal to come to your house and do some tweaking. Best bet though, is to buy more RAM and a second HD. Not much $$ will be needed. Ask your computer pal to check your motherboard and find cheap ram and a second HD for you. Offer him $20 for the help if he is a college student.

And what Brad said is good advice. May not be enough but is your best bet to try on your own.

Message edited by author 2007-02-06 12:19:24.
 02/06/2007 12:23:59 PM · #11
Another question:

Is your disk fragmented? You may need to run the defrag process.
 02/06/2007 12:30:54 PM · #12
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).
 02/06/2007 12:31:06 PM · #13
Originally posted by santaspores:
Jackson,

You system is a poor performer I am afraid. You can run CS2 successfully with your specs, but would need a computer-pal to come to your house and do some tweaking. Best bet though, is to buy more RAM and a second HD. Not much $$ will be needed. Ask your computer pal to check your motherboard and find cheap ram and a second HD for you. Offer him $20 for the help if he is a college student.

And what Brad said is good advice. May not be enough but is your best bet to try on your own.


Okay....I have noticed that it seems to work when I first fire it off.

Do the RAW files I have stored in My Pictures create any problem?

This has only started happening in the last week and I've had CS2 since November.

I noticed that at first, when I didn't have pictures in folders, it took forever for Bridge, then PS to open.

That went away once I put all my loose pics in folders.

Now I have a bunch of folders and quite a few RAW pics in them.

Is that possibly my problem?

Where can I put my picture file that they aren't always in Bridge every time I open it?

Or aren't they in there if I only have one folder open at a time?

02/06/2007 12:31:50 PM · #14
Originally posted by cpanaioti:
Another question:

Is your disk fragmented? You may need to run the defrag process.


Did that within the past week.
 02/06/2007 12:33:04 PM · #15
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).


Let me check, 'cause that may be an issue.....it seems to happen on pics I'm cropping.

I'll try one without cropping.
 02/06/2007 12:34:09 PM · #16
Originally posted by fotomann_forever:
CS2 is not happy with 512MB's of RAM... seriously. One of the best ways to sped it up is to add more RAM.

Secondly it likes to have a second hard drive as a scratch disk (one separate from Window's Virtual Memory).

My system is set up where all my documents are on a second drive, which is also my Photoshop scratch disk.


I have 1GB of DDR and Photoshop/XP still allocates 95% of the image to virtual memory and not ram. Then again i typically work with images that uncompressed fill 1 to 1.6 GB of memory.
 02/06/2007 12:34:12 PM · #17
David,

I was going to mention that mem allocation was outdated but didn't want to offend... but then again I didn't mean to suggest that mac users needed to resort to that. You are completely right of course.
 02/06/2007 12:36:57 PM · #18
Pedro wins the "Why is Jeb Stupid " prize.

I just went to a RAW file in the same folder and converted it without cropping, it went WHOOSH! whizzing by on its way back to the folder.

So....what is it that I'm f*cking up when I crop?

How fix, dude?????

And how much is this costing me a minute?

Will you take a third party check drawn on a bank in Beruit?
 02/06/2007 12:38:10 PM · #19
Hey are u running Camera Raw 3.6 and have Photoshop 9.0.2 update installed?
 02/06/2007 12:40:40 PM · #20
Originally posted by NikonJeb:
Originally posted by santaspores:
...
And what Brad said is good advice. May not be enough but is your best bet to try on your own.


Okay....I have noticed that it seems to work when I first fire it off.
...

I noticed that at first, when I didn't have pictures in folders, it took forever for Bridge, then PS to open.

That went away once I put all my loose pics in folders.

Now I have a bunch of folders and quite a few RAW pics in them.

Is that possibly my problem?

Agreed that BradP's advice is solid.

I'd further recommend you do not run the Bridge at all. It has its memory requirements that is getting in your way and taking precious resources.

Open images directly from CS2.
 02/06/2007 12:41:02 PM · #21
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?

How do I check what I'm cropping on the RAW screen?

I have trouble with the way that the crop thingie works in my RAW processor.....it does that corner thing only.....I can;t figure out how to bring in the side alone.

It kinda makes me nuts 'cause I feel like I have to wait 'til I convert to jpeg to do any fine cropping I want to.

I seem to lose effect of the vignetting that way, too.

I don't know how to vignette in regular non-RAW processing in PS.
 02/06/2007 12:46:29 PM · #22
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.
 02/06/2007 12:49:37 PM · #23
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.
 02/06/2007 12:50:12 PM · #24
Originally posted by santaspores:
David,

I was going to mention that mem allocation was outdated but didn't want to offend... but then again I didn't mean to suggest that mac users needed to resort to that. You are completely right of course.


PLEASE do not worry about offending me with what may seem to be stupidly obvious.

Assume I know nothing and you probably won't be far off the mark.

This past weekend was the first real crash I ever had in about 14 years of having computers, but I figure it's only been like that 'cause I'm so scared of f*cking up that I rarely tax the unit.

I try not to do things I don't have some instruction on how to use.

Needless to say, this CS2 and its accompanying abilities has me about whimpering.....8>)
 02/06/2007 12:54:20 PM · #25
Originally posted by NikonJeb:
I have trouble with the way that the crop thingie works in my RAW processor.....it does that corner thing only.....I can;t figure out how to bring in the side alone.

It kinda makes me nuts 'cause I feel like I have to wait 'til I convert to jpeg to do any fine cropping I want to.

I seem to lose effect of the vignetting that way, too.

I don't know how to vignette in regular non-RAW processing in PS.


IMO you should never crop out of the RAW processor, and you should definitely be converting to TIFF or .psd, not JPG. You want one straight-from-RAW conversion to be completely unedited, and then you work on copies of that. The way I do it is start with RAW, set my WB, and exposure adjustments in RAW, then create a 16-bit TIFF file from that. The 16-bit TIFF is my base image for further work. I open it in CS2 proper, save as a .psd, and do my sharpening, contrast, color saturation etc. on the .psd document; plus, of course, whatever other adjustments I make along the way. I end up with a multi-layered .psd document, which only becomes a JPG after it is resized, "output sharpened", and flattened, at which point I use save for web to create my 640-pixel JPG.

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

R.

Message edited by author 2007-02-06 12:55:43.
Pages:  
Current Server Time: 08/31/2025 01:25:22 AM

Please log in or register to post to the forums.


Home - Challenges - Community - League - Photos - Cameras - Lenses - Learn - Help - Terms of Use - Privacy - Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 08/31/2025 01:25:22 AM EDT.