This thread is for listing complaints about and bugs found in Photoshop CS. For the sake of brevity and clarity, please list each problem / gripe ONLY ONCE. If relevant, list your system specs and / or circumstances under which the problem occurs. Again, list each one ONLY ONCE. If your beef has been taken, shut up or get a new one. Don’t pile on with, "Me too," or add unhelpful grumblings. No doubt most of what gets listed here will already have been brought forth in other threads. The purpose of this one is to create a comprehensive list. Thank you for your cooperation.
Learn how to rescue details, remove flyaways, add volume, and enhance the definition of hair in any photo. We break down every tool and technique in Photoshop to get picture-perfect hair, every time.
This could be related to my using Avant Browser, but I’m posting it here in case someone else can corroborate it.
Selecting any option within Photoshop CS or Album 2 that opens a web link (Help, Registration, etc.) opens a malformed url with "http://%1%20" added at the beginning of the actual/correct url.
Is anyone else seeing this? Or should I check with Avant Browser?
Running Windows XP (all service packs and updates). 512MB RAM Sony VAIO PCG-GRX670 laptop 1600×1200 screen resolution Pentium 4, 2.0GHz
Ho – if you include the composite image (maximize compatibility), then the OS should show the preview. If it doesn’t, then it is a problem with the OS.
I’m using W2k SP4 and max compatibility doesn’t seem to matter one way or the other… I *have* tried it both ways. It may well be on my end, but I never saw it with PS6. In fact, I can take an image that’s giving me a black box (saved with CS), open and resave it in PS6 and my thumbnail is restored. Max compatibility is not checked in PS6 and never has been.
I agree with everything you said except this part, howard. Me toos can be useful to adobe in determining the extent of a problem or in telling if a problem is limited to only one user’s system.
Strangely enough, even though I had the double extention problem in ps7, that went away after a format and os reinstall then came back after about a month, (Chris, remember that thread?) I do NOT have that problem in CS … yet. 🙂
Sorry, Dave, it seemed like a good idea at the time. I was just looking for this to be a list of problems and bugs, not a discussion of same. However, I see that I was not thinking too clearly when I hatched that scheme. So, here’s my "me too":
I don’t get a double extension, I just (for example) get a JPEG file that says its a TIFF. Or, if the original file was a PSD, then I get some other file type (let’s use JPEG again) that has a PSD extension. Then, if you double click on the file, PS CS refuses to open it, saying that it is not a valid Photoshop document! If I edit the name of the file, replacing PSD with JPEG, all is well. This is a major pain in the butt.
Getting "Could not complete (whatever I am running) because disk is full." Dual 2.2, 1 Gig of Ram, 60% allocated to Photoshop. Primary Disk is 80% free and scratch is 90% free. Two 7200 RPM 30GB Drives. This is making no sense.
I also have problems opening web links and I am not using a filebrowser. Was unable to register using the link, I had to go to the Adobe website and register. Unable to open help files as well. Is there a fix for this?
Notebook: Windows xp, sp1 AMD athlon xp2400 1800 megahertz 768 mb of RAM 40 gig harddrive
I was asked to repost this here from another thread:
Problem with Magic Wand Tolerance in a Layer
After upgrading to CS, I’m having a problem with the magic wand when I use it in a layer. It seems to be ignoring the tolerance setting altogether. Here’s how I reproduce the problem:
Make a new file with a pure white background Make a new layer (Normal blending, 100% opacity, 100% fill) Make a small square selection Feather it by 1 pixel Fill with black Set the Magic Wand Tolerance to 1, anti-aliased to off, contiguous to on, and use all layers to off Click the Magic Wand in the solid black
The result is that it selects the entire black square along with the feathered edges, not just the pure black. Setting the tolerance to any number results in exactly the same selection. Selecting the transparent area of the layer also makes the same selection (inverted, of course). However, if I flatten the image, the tolerance works perfectly.
Additionally, if I select the entire layer contents by Ctrl-clicking the layer, the selection marquee is in a different place.
I’m mystified. Anyone know why the tolerance setting is being ignored? I’ve trashed preferences, rebooted, and it didn’t help. Running XPPro on a Dell, plenty of memory, plenty of space.
Sorry about that — what I had written down for the requirements was SP4 – but that was from over a week ago. Did they change that or did I tranfer info wrong?? Henry
In the RAW camera module for Fuji file types (RAF), there are three radio buttons. The two below the OK and Cancel buttons are the "Basic" and "Advanced" buttons. The text for these buttons is cut in the middle, and it appears that the font is wrapping over above itself (does that make sense?). The "Preview" button text does the same thing. I have: Windows XP Pro ATI Radeon 9700 Pro graphics card. Athlon XP 2700+ processor 1 GB memory -Joe Finnivan
What DPI (font) settings are you using for the video driver? (92 or 120) If you’re using 120, try setting it to 92. To check your setting, in XP, go to Display properties | Settings | Advanced.
I set my font to 96DPI, which is the "normal" size, and the problem went away on the PC running 1280×1024. The problem didn’t go away on the 1600×1200 PC I assume this is a legitimate "bug", since this should have been tested with different font sizes before release. I always run with the 120DPI fonts. Us old timers need a slightly bigger font size sometimes…
The issue appears to be specific, so far, to setting the DPI setting above 96 for some ATI drivers. You might want to try leaving your DPI at 96 but setting your Windows fonts to Large (from Display properties | Appearance) as an alternate solution. I’ve tried this on my system and it works but I haven’t had your issue with my ATI (Mobility Radeon) card so mileage may vary.
What card are you running on the system with the higher resolution?
The second system has an nVidia Quadro2 Pro with 64 MB of video memory. It’s not a serious problem, but it just indicates sloppy testing before shipping.
I think I just found another bug in the PSCS program…
I was working on a 67.2 mg file with 4 layers making it 211.7 mg. When I zoom out below 16.7% the items I have retouched out reappear on the screen as if it they hadn’t been retouched out. When I zoom to 16.7% or in closer the retouched items disappear and show as they have been removed. Turned this in to Scott Byer last night. After saving the file as a PSD everything is back to normal.
Using PS CS and PS 7.0.1 on same Win2k SP4 1.0 gHz machine w/1.5 gig ram and 60-80 gig of HD, system is always in good shape and defragged, virus free, drivers updated regularly, etc.
In a side by side comparison loading PS 7.0.1 is measurably quicker to load than PS CS with the same exact plugins in the plugin dir. Loading PS 7 is like grabbing a sip of coffee, lite a smoke and you’re ready to go. CS is more like waiting for the coffee plant to ripen and roasting the beans…one at a time. <BG>
Seriously though, does anyone have an idea on this? BTW, If I go back to a plain vanilla plugins directory the time to load decreases to a reasonable amount. Now granted I have a ton of plugins, but it was never a major problem in PS 7.
When an image loaded with the Camera Raw plug-in (at least from Canon CRW files), the EXIF data finds its way into the image in some non-standard way. If you save the image as JPEG and reload it, the EXIF data is still there. However, it is no longer visible in ThumbsPlus, and PBase, the gallery site, no longer deciphers it either. If I shoot a JPEG in the camera, and save an edited version, the EXIF data is saved in the correct format, and is still read by the other apps.
My only gripe is that my RAW files from my Olympus C5050z look awful, the contrast is really low and the colour is off. They look fine when I use iMatch to view and convert them but not in CS.
This has been discussed in the Photoshop CameraRaw plugin forum. From the thread "Photoshop CS RAW saved to JPG and EXIF data vanishes"
"EXIF data brought in from JPEG files will be rewritten to EXIF and XMP. EXIF data from CR files will only be rewritten as XMP. There are technical issues that currently prevent us from rewriting as a standard EXIF block."
———————
I’m guessing the neither ThumbsPlus nor PBase are XMP aware.
Neil – are they reall awful, or just different from how the Olympus software processes them (which is usually over contrasty and saturated)?
Also, have you come up with good ACR settings for your camera and set them as the default?
If they’re really awful, then we’ll need some sample files to examine. The ACR defaults may be different (designed for professionals), but they should be providing good quality.
Yes they are really awful, it takes way too much work to recover them. Like I say, when I use iMatch, my image management software the RAW files look great. In ACR the contrast is extremely low and the colour just isn’t what it should be.
I have tried my RAW images with the old ACR and they looked incredible, they almost popped right off the screen.
I can upload a couple of examples of you want to see what I mean, just let me know and I will provide a link.
The whole window does not appear. For example " when I use the conte crayon filter, where it says foreground level, I am unable to see the box with the numbers " I was using the book by Scott Kelby "PS CS down and dirty tricks" on page 40 it shows a window of the filter dialog box with a narrow dialog box, and the Little window is in the upper left corner and you can see the whole box. In my case the Little window is Large and on the left. The right side of the box stops at just about the middle of the " OK and Cancel " buttons. And I am unable to grab the corners or the sides to expand the window.
Magnetic lasso tool: problem removing fastening points.
Information from the Photoshop-Help: "To erase recently drawn segments and fastening points, press the Delete key until you’ve erased the fastening points for the desired segment."
In PS 7.0 the Delete key worked, but in CS nothing happens when I use the Delete key.
laura, try setting your screen res as high as it can go and see if you can grab the dialog. if not reset your prefrences per the faq.
toorman, if you’re using the numeric keypad, make sure your Num Lock isn’t on. I just tried and it works with both delete keys EXCEPT when the num lock key is on.
Chris – Could you please be more specific? I’ve searched and mostly find your messages making the same reference; a link to the actual thread would be most appreciated.
I am making headway in my own investigation, narrowing down the issues to some older plugins and twain but I’d like to view this win2k thread you speak of as well.
Knocking off some old plugins I didn’t use certainly helped a bit (as it would in PS7) but the real culprit here seems to be TWAIN. I only have two TWAIN drivers in my WINNT\TWAIN_32 dir and I tried removing them one at a time without any difference. If I remove the TWAIN plugin from the IMPORT-EXPORT however, the entire process speeds up dramatically. In fact adding back in some plugins doesn’t have as dramatic an effect as putting TWAIN back in.
Is there any info I can provide to you to assist in the investigation? As I really don’t scan directly into PS anyway for now I’m just going to remove it, but I figure this is something you guys would want to be aware of.
Thank you for your reply, but I’m not really sure what you mean. Forgive me I’m really new to photoshop. Well about a year anyway and I’m still learning. When you say to set the Res. higher do you mean the photo I’m trying to change or the screen itself? and "reset my preferences per the faq" Could you direct me to this faq. Sorry for being illiterate, but hopefully in the future I will overcome that.
No problem here you go laura, the first link is how to do the screen res thing to try to get the dialog back, the second is to reset the prefs. If the first doesn’t work, try the second:
Mathias Vejerslev "Dialog box is missing??" 10/29/02 1:06pm </cgi-bin/webx?50>
Mathias Vejerslev "How to delete/reset Photoshop preferences" 2/11/03 12:04pm </cgi-bin/webx?50>
I had my comp. res. 800 X 600 and that seems to not work very well for my adobe setup. I now have it at 1024 X 768 which shows the whole dialog box, but the fonts are pretty small now, not to mention the icons on the desktop. But hey at least I can see the whole box now!
the way I read it, large fonts from the "system fonts" were causing errors. Creating a custom "appearance" in the Control Panel -> Display -> Appearance is different from large "system" fonts.
Heck dave, try it and let us know! Adjust your appearance to make the font, say 18 point and see how it all displays!
Win XP Home, SP1+updates, ATI Rage 128 video. PSCS not yet activated, but no crack.
With several images open in PSCS, document and application windows maximised, status bar visible:
Hit TAB to hide palettes.
Using ctrl-TAB or ctrl-F6 to switch documents causes a blank, status bar sized area to appear at the bottom of the image. Selecting an image from the Window menu does not.
Hit TAB to bring back palettes.
Closing the top image causes the blank area to appear across the bottom of the next image, above over the status bar.
Anyone else getting this?
(Incidentally, any idea why I get a "Date out of range" when I try posting via Newsreader?)
I’ve had a problem with saving files in CS. Several times when I go to save an existing file under a new name or overwrite another file I get an error message about unable to complete task due to program error. Some times I’m able to save by choosing another output name, but most recently I couldn’t do anything to save the file.
I also had the same error message occur when I was doing a color range select. I’m running Win2K with the latest service packs..
I’ll try gh… i only have the option for normal large or extra large. i’ll set to large…
Dave, Can you not go into the display properties/appearance tab and modify each and every setting, such as horizontal and vertical spacing of icons? I can do this from the Items dropdown and if there is a font and font size associated with that particular item, you can modify it. I have my desktop set for 1027×768, but am not using the default 10 point font sizes, as they seem too small! Try using that feature and see how big you can make your text 😉
ps. i think you’ve just walked across the rice paper without leaving footprints grasshopper! <VBG> ooooh, you think I am ready to attempt to snatch the pebble???? 🙂
Occasionally, CS refuses to open Leaf RAW files, giving me the "not enough free RAM error." this can not be the case: as 1)I have 4gb RAM, and 2)this has happened when starting up CS completely fresh.
Bug seems to come and go, sometimes they open fine. I have set max RAM now to 89%, this has seemed to help for now. but I don’t know why I can’t use 100% (1777MB) since I have extra RAM anyway.
ellen, not sure about CS, but in the past the free ram error was generally related to scratch space, either PS’s directly (which you’ve addressed) or windows itself. make sure you have a swap file set up in windows and that it’s fairly large if you’re working on large files. make sure you have enough free contiguous (defragged) disk space on both the windows scratch drive and the ps scratch drive.
btw, with 4 gig of ram, you should be able to safely crank ps mem usage up to 100% as any app in windows only uses 2 gig anyway. the remaining 2 gig is more than enough for the os.
it can’t be a scratch isssue as I have an entirely separate drive for scratch. and yes, I have used PS7 @ 100% in the past.
interestingly, another guy just posted the EXACT same error message just now, this time with Canon 1ds RAW files entitled:
"Not enough memory message"
just like me, his RAW files opened fine the first time he used CS. but after he changed his max ram to 85%, they stopped opening.
I figured this out too, because the only thing I had changed was my max RAM preferences. for some reason, RAW files now open @ 89%, but not 90%! go figure.
could this be a bug affecting many different RAW formats?
Len: An updated driver would be a lovely idea – however, ATI released an XP verion in October ’01, or there’s the MS version included with XP (which seems more stable). Soon, I really will have to bite the bullet and decide on a new card. In the meantime it’s only a cosmetic issue, so as long as nothing worse happens I’ll live with it.
Could it be an inverse relationship? Could it be that the more RAM you have, the less you need to devote to PSCS? That is to say, if you get higher than say 1GB, maybe you need to put your RAM percentage less than 100% for optimal use?
Okay, okay, okay, on the face of it, it seems to make no sense, but it also seems to be what is occuring! 😉
OK, just tried with no video acceleration and the blank line is still there. However, I was wrong about the source; it is where the horizontal scroll bar would go if it was needed. My test was with some portrait-orientation images that didn’t span the screen, but with a landscape image (or with further zooming-in on my earlier images) a scroll bar appeared in the blank area. As I said in my original post, the area is filled with image if you swap using the Windows menu, it’s just ctrl-tab/ctrl-F6/closing an overlaying window that shows it so I think it is a real, if minor, PS bug.
Incidentally, the status bar is still inclined to go AWOL between sessions in PSCS.
what is your desktop resolution set to? PSCS needs to have it set to 1024×768. Perhaps the scroll bar is there, you just can’t see it because of the display resolution?
I don’t have PSCS, but I believe it’s optimized for 1024×768, higher resolutions should be fine. It’s the lower ones that cause the issues of not seeing all the dialog boxes (from what I understand).
Grass Hopper: it’s the other way round – under the circumstances I listed (keyboarding between windows or closing a window to reveal another beneath) PSCS is clearing space for a horizontal scroll bar even if it isn’t needed. (And I am at 1024 x 768, so it probably isn’t a resolution problem.) It’s a very minor niggle, but I hope (if it isn’t system specific) that it will be tidied up (mind you, Illustrator CS *still* starts full-screen but unmaximised, and that’s been pointed out for at least two verions, so I’m not holding my breath).
A little bug I’ve come across. I recently upgraded from 6 to CS and I’ve never seen this before.
When I save newly scanned files (4000 ppi from slides) with a few adjustment layers (usually levels, HSB) and a single image layer as background they are being saved at about twice the file size on disk as what they should be. Previously in 6, files were about 50-60Mb from the scan with little noticable increase in size from the adjustment layers. Now they are about 130Mb.
The cure: I go -Save As- and overwrite the file and it jumps back to normal size.
Yeah, ugh. What’s happening is that you are out of address space. On XP, applications can only address 2GB of address space. With Photoshop’s memory set to 100%, by the time Camera Raw gets around to try and allocate any memory, there isn’t any – address space, that is. You could still have 1GB free RAM and CR still wouldn’t be able to allocate any. It’s one of those nasty computer science-y things that users shouldn’t have to deal with, but…
"640kb is all the memory that anybody will ever need".
No Chris. I’m scanning at 8 bit and keeping them at 8 bit, directly into Photoshop using Nikon Scan and they are normal size after the scan. They swell up after I’ve applied the adjustment layers. I’ve noticed it since I first upgraded about 11 days ago. It doesn’t happen with every file but perhaps 1 in 2 or 3.
I’m getting strange text behavior in PSCS. Text doesn’t seem to be updating correctly as I type. I often have to switch out of text editing to see the changes I make.
Also when I opened a file created in v7.1 the text layers moved completely out of their positions.
I have had a similar problem with the text updating, although it does not happen every time I use Photoshop. My problem is the last letter I type is not viewable, until I type the next charecter. If I change tools, then all the text becomes visible. Like I said, it doesn’t happen every time I use photoshop and I haven’t had time to really stop and look at all my settings yet, (which I why I haven’t posted the problem yet).
Opening files is extremely slow when compaired to previous versions of PS. I have a P41.7Ghz machine with 512MB of RAM and over 200GB of combined HD storage so this should not be an issue. Adobe needs to address this problem.
Also when I opened a file created in v7.1 the text layers moved completely
out of their positions.<<
From the Photoshop CS Readme (Yes, it is on your HDD!)
Text Positioning
Due to a minor change in the way the Photoshop CS text engine renders certain text blocks, opening documents created in earlier versions of Photoshop may change the position of a text block. This specifically affects text blocks with hanging carriage returns, but may affect others as well.
Len, I saw this in the readme too, but I assumed the change would be minor positioning changes. The change is not minor and can be a really big deal if you have to totally redo a layout (especially for web work) you previously created.
"CS extreme(!) slow startup compared to PS7" Julian K "CS extreme(!) slow startup compared to PS7" 11/19/03 11:48am </cgi-bin/webx?13/1>
For me the issue with the forever loading pattern set ( ate startup as well as inside of CS) is a pretty serious issue, since I make heavy use of patterns in layer styles.
Is this with specific fonts or all fonts? Is the update appearing in square parts (normal)? What else is running on the machine, and what is the Photoshop memory percentage slider set to? Certain processes that are more common nowadays (IM software, MP3 players) really munch RAM and having Photoshop’s memory slider up too high in that case can really slow things down.
Actually, the change is minor, but in certain cases can be near enough an edge case for wrapping a word that the entire text block after that point re-wraps.
If that isn’t the case here, I’d be interested in getting the file to see what’s going on.
I have a complaint. Bring back the eye icon and add some color to that feathery white box! In my quick start menu cs looks deceptively like wordpad and I’m repeatedly starting wordpad, having to close it then going into CS. Especially since you’ve made the screen res requirement 1024×768!
Installed CS on Mac with no problems last week however received CS for Windows today and nothing but problems.
Using Windows XP Pro Removed Photoshop 7.01 using add/remove facility
De-activated Norton antivirus, shut down Zone Alarm Pro and installed CS. All went smoothly. Activated CS on line. Although no programmes running in background restarted PC.
Norton and Zone alarm have not caused any problems in the past with Photoshop 7.01.
Photoshop CS loads correctly but then CS displays the following Adobe generated message; ‘An error has been detected with a required application library and the product cannot continue. Please reinstall the application’. No error codes appear in this message.
I remove CS using add/remove programmes facility and restart in safe mode only to get the same message. Same problem occurs after 3rd attempt to install. I opted for activation by telephone on the third attempt.
Through trial an error it seems this message only appears if Zone Alarm Pro is running even though CS has full permissions.
Has anyone else experienced such problems? I have spent all afternoon researching the problem but other than waiting for a possible solution from Zone Alarms I have come up against a brick wall. Two phone calls to Adobe UK have not resolved an issue which is an enigma to them.
Hmm… my prefrences in CS seem to have reset themselves. Strange. Never happened before with any other version of PS back to 5.02. Keeping a hairy eyeball on it to see if it happens again…
Have you checked ZoneAlarm’s log to see it it blocked something without asking you about it? If not, on a fresh boot, clear the log, try to run CS. If it again acts up, recheck the log. If there is nothing there that is odd, I would think it isn’t ZoneAlarm.
Have you tried CS with the network cable unplugged with and without ZoneAlarm running? If so, was there a difference? I know, an odd question, but it might help a network expert or someone from Adobe figure it out.
If its any consolation I cannot open the help file either and it does not look like adobe are doing anything about it because they have had our money!!
I’m attempting to use Picture Package to print out CS images at 16 to 20 different images per page, as contact sheets. I drag each separate image onto a placeholder, select file name display options, then press OK. At this point, PS CS becomes hyperactive. It keeps on creating multiple versions of the picture package, seemingly in an endless loop. It can only be stopped with repeated strikes of the ESC key. At that point, dozens of picture packages may have been created but only a few remain as viable files on the screen. It is possible to delete most and retain the first created, which comes out as intended.
I’m using Windows XP, 1GB memory (650 mb allocated to PS), 2.53 GHz P4 processor. The files I was using to create the picture package were all 1600xd1200 JPEGs. 72 dpi was chosen as the output resolution, and each picture package size was just over 1 mb.
I just got the CS Premium set, and all appears great, except for this, which started tonight: When I try to open one particular .PSD file created recently, I get the "can’t complete your request due to a program error" message… Everything else seems fine, and I can open the same file in Image Ready, but can’t even hop over to PS from Image Ready with it…
Apparent bug in "Apply Image". When using 16 bit files in Apply Image Add mode, any time I offset less than zero the entire blended image drops to pure black. Can work around this by using subtract mode, but it would be nice to have it work correctly.
Droplet doesn’t work. Created an action to perform USM on images. Batch works, but when I create a droplet, it starts and does not bring up any images. Used the same settings as to source file, action, and destination file for batch and for droplet. One works and the other one doesn’t. It worked for PS7.
Intermittent shutdown of PSCS in XP SP1. CS appears to be swapping out to disk much more the 7.0 ever did. With single image opened with 512 memory CS takes an inordinate amout of time to shut down with an extreme amount of disk activity.
Something seems to have changed with the transparency in PNG files? They no longer work when inserted into Powerpoint XP. Instead of transparency you get black (PS7 still works fine)
Issue with File Browser and very large .pdf files.
If, when using the File Browser in CS, I click on a folder that contains a very large .pdf file (236 mb, containing several hundred high resolution images), File Browser and Photoshop lock up (FB is "getting metadata"). I have to use Task Manager to exit.
If I click on a folder that contains a smaller .pdf (120 mb, several hundred high resolution images), I can’t exit File Browser or do anything else in Photoshop (palette title bars and toolbar go white if you try), but it will unfreeze after about 5 minutes. The File Browser task bar says it is getting metadata, so presumably it takes a long time, but there is no escape until it is finished.
The larger file (236 mb) never seems to finish. I’ve tried waiting 20 minutes before using Task Manager to quit Photoshop. Until I remove that file from the folder, I can’t access any image files that are also in that folder. I am not clicking *on* the .pdf, I am simply opening the folder.
I searched for this one in this thread and didn’t see it, so forgive me if it’s already been posted:
Two or three times now I have opened a file, made an edit or two, hit save and been greeted with: Could not save E:\filename.psd because the file is already in use or was left open. Well, duh, of course it’s open, I OPENED IT! Now I want to SAVE IT! In each case, no other files were open. Just one file, a few edits, and CS can’t seem to grasp the concept that this is the original file and ALL I WANT TO DO IS SAVE THE DAMN THING! If I select a new folder and do a Save As (same file name), it works.
Sorry about all the shouting, but my frustration with CS is about to max out. All the more amazing when you consider that I’m using PS6 almost exclusively. If I were using CS full time, shots would have been fired by now.
That sounds exactly like the problem that the psicon.dll was causing. I’ve only seen it when it was associated with TIFs or JPGs but others have reported the problem with PSDs. Unchecking "generate thumbnails" in the properties tab seemed to fix it in PS6 and PS7. BTW, I had the same problem in Illustrator (caused by aiicon.dll) but it also went away when I unchecked "generate thumbnails" in the properties tab. And no, this does not affect the large thumbnail generation in Explorer, just the small icon in Icons view (for XP, I think it’s called something else in 2000)
Two or three times now I have opened a file, made an edit or two, hit save
and been greeted with: Could not save E:\filename.psd
this does not affect the large thumbnail generation in Explorer
I only wish I could get it to work. As discussed in another thread, some people, me for example, do not get good thumbnail generation in Explorer if the image aspect ratio is less than 1.25 (in landscape orientation). I really wouldn’t care if psicon.dll ever comes back if I could just get my thumbs to show reliably in Explorer.
EDIT: OK, I’m going to uninstall CS, clean out the registry, reinstall and hope for the best. I don’t expect it to make any difference, but there may be remnants somewhere from the failed reghack that are screwing things up.
Two or three times now I have opened a file, made an edit or two, hit save and been greeted with: Could not save E:\filename.psd because the file is already in use or was left open.
Ho, you’ve been saying you don’t have the problem others have had with psicon.dll so you want to use it… well, THAT’S been the problem all along. Now you know!
I never had it with PS6, dave, and I still don’t. Those same files open fine in PS6 and, after nearly four years, that error message has never appeared when using that version of the software. Adobe possibly changed something in version 7 and newer that caused it to malfunction with some systems. And as I just stated in my previous post here, IF the thumbs would show in Exporer as they are supposed to WITHOUT psicon.dll, I will not miss it nearly so much.
Derrick, I see a General tab with a little thumbnail and the Summary tab. Haven’t done the uninstall yet…
It’s not a ps version problem, per se, it’s a psicon.dll problem. And it’s only ever been intermittant. I’ve seen it maybe 2 or 3 times since version 7 and never in 6 (or since I’ve installed cs). Others would get it weekly.
Adobe possibly changed something in version 7 and newer that caused it to malfunction with some systems
Actually, the biggest change was the os change – for the most part. Most reports (IIRC) came from XP users with a smattering of 2k and 9x/me users.
IF the thumbs would show in Exporer as they are supposed to WITHOUT psicon.dll, I will not miss it nearly so much.
I hear ya. 🙂 Just trying to give a litte more info.
Ho, has PS6 always been on your machine and the thumbnails stopped working after the CS install? If that is the case then I don’t know what to tell you, although it certainly sounds like you are having psicon.dll difficulties, possibly from the reg hack
H/W: Athlon XP 1700 ASUS A7V266 1GB Memory ATI RADEON 9600 128 MB AGP 20" monitor at 1280X1024 WACOM Graphire 3 Microtek Scanmaster 3 SCSI WD 120 GB 8 MB buffer
S/W: W2K SP4 W/ security patches ATI most resent updated drivers Tested with Norton System Works 2003 installed and not installed Microtek ScanWizard
I have made two attempts to rebuild my image (re format hd)and have tested with and without System works 2003 installed. I have another system that has a different Video; nVIDIA GeForce FX5200 128 MB and it runs fine with System works 2003 running 1024X768.
Now the problem: I cannot get my Healing Brush and Clone stamp to work. It logs it in the history. If I do not alt-click it acts the same way as if i had. Meaning If I alt-click and get a cursor change then when i start using the tool nothing appears except in the history. I am using only 1 layer. If I go out and back in an do not alt click I never get a error msg. and it still acts the same as above.
PS. (unrelated item update)I had a previous problem with not getting remote disks to work but that was corrected once I brought down my network and cold started everything inclyuding the router tables.
An update. This may be in the WACOM SW. I tried useing the pen and it works then when I go back to the mouse it works. Also my mouse (system) does not work unless I use the pin first on these two tools. OK I disonnected the USB/WACOM Graphire 3 and shut down CS and brought it back up and the system mouse works. I will be contacting WACOM but it appears that this may be a clasic finger pointing contest. Does CS have a dev contract with WACOM?
From my experiment today with the PS6 and PS7 psicon.dll I’d say that you almost certainly have the PS6 psicon.dll controlling your thumbnail generation, which seems to cause the aspect ratio problem in CS files. It also could cause the saving problem and the extremely long time to generate the Open dialog image preview if "generate thumbnails" is checked and should be an easy fix (uncheck "generate thumbnails"), but if you don’t have access to the thumbnail image tab in properties I believe you can still manually do this by changing the "IconBits" in the CLSID registry from "1" to "0". I don’t know what Chris Cox meant by saying the OS should show the preview because it has to have some sort of shell extension to do this (at least for PSD’s) and the readme clearly states that without psicon.dll the preview will not show. Maybe he meant Macs work differently than Windows.
I only wish I could get it to work. As discussed in another thread, some
people, me for example, do not get good thumbnail generation in Explorer if the image aspect ratio is less than 1.25 (in landscape orientation). I really wouldn’t care if psicon.dll ever comes back if I could just get my thumbs to show reliably in Explorer.
Thanks for the detective work. I may try to find the v7 dll to experiment with. Chris was saying, if I understood correctly, that checking the Max Compatibility option (which makes PSDs visible to apps like ACDC) would enable Explorer to show the large thumbnails of PS files. I did not find this to be true when I first installed CS on XP, but I have decided that I really can’t use my system as a barometer of the capabilities of this newest version of Photoshop.
I would like to know if you have had other versions of Photoshop or Elements on this machine. Testing this with a Win2K box and CS with no previous versions of PS I was unable to get thumbnail previews in PSD’s, no matter what settings I chose.
Open Photoshop/Edit/Preferences/File Handling and in the ‘File Saving
Options’ also make sure ‘Image Previews’ is set to ‘Always Save’.
I did the test on my Win Xp Pro/P111 800 /512 Ram… Saved a normal psd file without this option selected, sure enought – no
preview in explorer…
with the option turned on, save the file, i have Thumnail Preview…
I have two machines here. One a clean install of CS with no other versions and another with 7.0. The machine with 7.0 has thumbnails, the one with only CS doesn’t even with save thumbnails selected.
My problem exists with CS but didn’t with 7.01. When using the healing brush, on rare occasions the program will freeze for 15-20 seconds, with the hard disk LED on the entire time. This occurs perhaps once per week and is not repeatable. I have only observed it when working in a selected area, but that may be coincidental.
I had a similar problem in my old system running Win98SE and v7.0.1, where activity of this type (healing brush, clone stamp, dodge, burn, etc.) would slow considerably when working in a selected area, regardless of the area’s size.
iclick, try turning down the memory allocation pct in cs. you may be starving the os and forcing it to do memory paging to disk. crank it down to about 40% and inch it up (~5% at a time) until you start to see the problem resurface. of course you’ll need to restart ps every time you change it.
When I’m running iTunes or any program which uses GTK+, CS will randomly crash, taking the whole system with it. I’m running up-to-date XP on a Compaq Presario 1720 US with a 1 ghz p3m, 512 mb or RAM, an 80 gig firewire hard drive and a mobility radeon.
Two issues I don’t think have been brought up here:
1. When opening random bmp or jpeg files that have not been saved via PS, attempts to enter text result in a small grey square cursor at the mouse click entry point but with what seems to be a minute – if invisible cursor ie: Not the expected "I" beam at all. Attempts to enter text thereafter do not result in any visible output. No error messages occur.
2. When opening random bmp, tiff or jpeg files, at times the background layer lists itself as "index" rather than "background" in the Layers pallete and no further actions are possible.
One way around both issues I’ve found, has been to create a new PS document and drag the offending document onto it. For some reason, text and other manipulations then work as normal.
I’ve come across these issues with files saved via Hemera and old bmp’s I’ve had on my system and created via screen capture or Paintshop Pro 8. Frustrating but as CS is so young I wonder if these are bugs? Running CS premium on a P4 2.8.
Adam, sounds like what you’d expect to happen if you were working on a gif (file is in indexed color mode). Next time it happens open image> mode and make sure it’s rgb 8 bit. (if that’s your prefrence.)
Alden, if you have xp and a crash is completely locking your system up to where it’s unresponsive (crtl-alt-del doesn’t work) or if the computer automatically reboots, you most likely have a hardware problem. XP (and win2k for that matter) is/are "process isolated" – meaning that an application cannot bring down the system. The only other possibility is bad bios or EXTREMELY buggy low level (sound/video/other system level) device driver. (Usually device drivers will blue screen in xp or 2k, but i’ve seen reboots off a creative labs driver.) Since you mention iTunes, maybe your sound driver is causing problems. Is it digially signed for XP? Either way, I’d try updating it first. Get it from the manufacturer, NOT from MS Windows Update. If the system still locks, look for a hardware error… and see this faq:
Mathias Vejerslev "Computer locks up, shuts down, or reboots while running Photoshop" 6/5/03 3:49pm </cgi-bin/webx?13/1>
Dave thanks for the reply. I haven’t since been able to replicate the "Index" issue but if it arises again I will check.
I’ve a bit more on the "Text" issue though.
When I open the bmp, the dimensions are showing as 1280 x 960 pixels and this is equating to 1300.48 x 975.36 cm (that’s strange in itself I think but I do get the same dimensions in Paint Shop Pro too).
Therefore when I go to apply text in PS I am actually getting an "I" beam afterall but it’s a really unintelligible one even at 100 points. The total text looks smaller than a "marching ant"!
If I create a new 1280 x 960 pixel doc and drop the original full-sized bmp straight onto it as a layer, problem solved. The 100 point text can then be applied as normal and shows up huge (and in fact, bigger than 100 point text if applied with PSP straight onto the original).
Therefore when I go to apply text in PS I am actually getting an "I" beam afterall but it’s a really unintelligible one even at 100 points. The total text looks smaller than a "marching ant"!
again check image mode to be sure you’re in rgb> 8 bit (or your prefrences). index mode images don’t support layers, hence any text will be rasterized and when you use the text tool, you’ll get ‘marching ants’ outline of the text you type.
if it’s not that, check image> image size, and make sure your resolution (ppi) is around 72 for screen work, or 300ish if the piece will be printed.
if that STILL doesn’t work, reset your prefrences per the faq topic:
Mathias Vejerslev "How to delete/reset Photoshop preferences" 2/11/03 12:04pm </cgi-bin/webx?50>
Dave you hit it on the head – resolution was 2.5 pixels per inch. Although PSP didn’t seem to mind, Photoshop seems a little more picky on these things BUT I think you’ve helped with an ancillary query I had re strange pixel totals whenever I changed the cm size of documents of this type! It was the resolution!
Back to the issue you’ve been helping with, I changed resolution to 72 pixels/inch (though I did receive a couple of "scratch disc full" errors along the way) and the Text tool now works fine.
for the scratch disk problem… how much free space do you have? do you have multiple scratch disks set up in prefrences? what’s your memory allocation set to? knock it down to about 50% and see if the problem goes away. inch it up say 5% at a time (restarting photoshop each time you do) to find a good balance of performace v. scratch size. chris cox (adobe engineer) said they needed to tweak some of the memory routines, so this might help you out.
dave, cut petrula some slack. Those of us with high screen resolutions and less than perfect eyesight don’t WANT to make the change because we CAN’T see the tiny little type that is foisted upon us when using small fonts.
In PS CS, I couldn’t open photoshop 7 files with complex styles applied. (You receive this warning : Could not complete your request because of a program error) I have deleted my preferences folder and then i could !!! I have try to change my preferences one by one (and then close-open PS CS and try to reopen the image) The error comes again when i change the cache level value.
Problem with two computers running CS: Saving a file (any extension) and checking "As a Copy" under "Save Options" will not save the file as a copy, but wants to overwrite the existing file. With PS7 I used this procedure routinely but can’t get it to work in CS.
In PS CS, I couldn’t open photoshop 7 files with complex styles applied. (You receive this warning : Could not complete your request because of a program error) I have deleted my preferences folder and then i could !!! I have try to change my preferences one by one (and then close-open PS CS and try to reopen the image) The error comes again when i change the cache level value.
* ****************************
and what was the cache level that wouldn’t work?
and the cache level that would work?
* ****************************
The default value is 4, if you change it, you have the bug (I have read some other people which can’t save with the value modified)
dave i have the same problem as alpha. i went to image/mode i am set on rgb/8bits. when i goto image size i am set at resolution: 72 pixel/inch. those 2 didn’t work for me so i did the reset, by doing ctrl+alt+shift…and i reset the settings…that didn’t work…it still looks like ants marching. 8\ you wouldn’t happen to know what else it could be?
danny, only think that reminds me of is maybe you’re in type mask mode instead of type mode. right click on the type tool and make sure type and not type mask is selected. if this isn’t it, please restate your full problem from the beginning. actually, it’s better to start a new thread, but since you’re already here, just remember that in the future! 🙂
when you say you did crtl-alt-shift, did you get a dialog box asking you if you want to reset photoshop’s settings? if not you didn’t reset the prefrenecs. you need to be really quick. took me like 5 tries when i was testing it for myself to make it work and get the dialog.
Did anybody experience problems (a bug?) with the ‘layer thumbnails’?
In PS 7.0.1, if I create a new adjustment layer I get different thumbnails in the ‘Layers Palette’ for the different adjustment functions.
But in PS CS, no matter which adjustment layer function (fill layer icons are ok)) I select, I always get a black & white symbol just like the Layers Palette icon for creating an adjustment layer.
Any ideas? It’s kind of annoying not to see which layer represents which function. My workaround right now is to put the function in the name and hover over the name or to just click on it and see which funtion pops up.
I have some more issue with PS CS (not 7.0.1) with my Wacom tablet (sometimes pressure-controlled opacity for brushes does not work, is ok after PS restart; USB mouse and tablet connected) and the file browser (sometimes ghost browser window after PS start, from previous session?), but I’m still trying to get a better idea why and when.
Adobe Photoshop Version: 8.0 (8.0×118) Operating System: Windows XP Pro Version: 5.1 Service Pack 1 System architecture: AMD CPU Family:6, Model:4, Stepping:2 with MMX, SSE Integer Processor speed: 1200 MHz Built-in memory: 1023 MB Free memory: 675 MB Memory available to Photoshop: 933 MB Memory used by Photoshop: 50 % Image cache levels: 4
1: My CS says i don`t have enoght memory in my computer. when im "saving for web" on images thats larger than ca:1024X768. When i checked the system, and i got 1,5Gb memory left!
2: THe Clipart in Windows stop working and gives the message "not enough space in the clipboard to copy the screenshot" When i clip out some IE apps to CS. But When i tur off CS this problem does noe happen anymore..
And i got a general problem whit the new SHITTY Filebrowser. Have u ever thought of 2 screens? ( maby for mac, but not for win) The filebrowser in 7 was perfect. Why did u destroy it? And it says (by adobe) that this filebrowser is supposed to be better for 2 screens? And u cant even take the browser out of the Cs window.. Stupid man.
1: My CS says i don`t have enoght memory in my computer. when im "saving for web" on images thats larger than ca:1024X768. When i checked the system, and i got 1,5Gb memory left!
what’s your memory percentage set to in ps prefrences. set it to about 50% and try again.
2: THe Clipart in Windows stop working and gives the message "not enough space in the clipboard to copy the screenshot" When i clip out some IE apps to CS. But When i tur off CS this problem does noe happen anymore..
there’s some reg file in the Goodies\Optional Plug-Ins\Photoshop Only\Optional Extensions folder on the cd called AlwaysImportClipbd_ON.reg and ClipboardSizeLimit_OFF.reg . this should allow you to copy large amts of data via the clipboard.
see the Registry Keys ReadMe.wri file in the same directory for details on these registry files.
as for the browser, 2 choices, set it to run overnight with background processing and check subdirectories with high quality previews, or turn off background processing and high quality thumbs in the prefrences. either way cs will run better when the browser finishes it’s processing. i agree that i don’t like the fact you can’t move the browser to monitor 2 without stretching the full ps app across both monitors.
This should certainly be an almost instant phenomenon?
What should be? The thumbnail processing? Nope. in my experience it’s fast if the files are fairly small, but can take quite a while per image if you work with a ton of large files. My stuff usually under 50 meg or so and they create high quality thumbs in seconds each, but i’ve got a couple that are several hundred meg and they seem to take a lot longer. 20 or 30 seconds each. multiply that if you have hundreds or thousands of files!
it takes much longer because the thumbnails is much higher quality than in 7 and is color accurate. i’m sure it does more than that, but that’s all i know about it.
so right after getting cs, after reading a couple of posts from people crying that the browser was slow, and the responses from the techs saying it’ll speed up once the processing is done, i let it run after setting it to process all files and subdirectories and it’s been fine ever since.
couple errors I have experienced with Photoshop CS are:
1.) Used to get an error when trying to save for web..would NEVER let me…ever..for the last few months/weeks..
I had PS 7 installed as well.maybe that was the problem…
anyways got a new computer P4 3.0Mhz/XP Pro
with out PS 7..no longer have that problem…
2.) Now whenever I try to save ANYTHING I work on in PS CS…I choose Save/Save As/Save for Web and it hangs for at least several minutes…then it lets me choose a directory to save it ..
How can I "speed" this up?..this is NOT very productive..and I doubt it has ANYTHING to do with my computer as it is NEW! I mean BRAND SPANKING NEW!
Any advice or other people who rectified this problem? Thanks
Moving around either in the File|Open dialog box or in File Browswer causes system hang. I am also experiencing hangs in the Save As dialog box too. This is happening on an XP machine with 1Gb of RAM. Scratch file is set up properly and memory is set to give 85% to CS.
This is happening on a machine that has fast IDE133 drives (RAID-1), is defragged each night and with little apps running in the background.
Hi Chris – thanks for the reply (who are you – with Adobe…you are I see…cool).
No, the OS doesn’t hang, just the Adobe process. It eventually works itself out. I suspect if I killed the process, things would sort out just fine. I might do that to confirm that it is, indeed, CS.
I’ll try that and turn down the memory. FYI, I also have unchecked the background f’n in File Browser and all other "things" which cause CPU use.
OK – then the hangs could be from something trying to create a preview for a very large image file, or it could be from a problem with the disk system.
Drew, what size files are in the folder where this is happening? Sounds like the File|Open delay caused when the system is trying to generate the preview to the File Browser cache for large files. If you let it generate the preview does the delay go away when you open the folder again?
Gents – I appreciate your hanging with me on this (and such prompt replies too!).
Okay, I think you both are onto something. It may be a good idea to give you a better sense of my enviro:
WinXP Home 1Gb or Ram P4 2 Ghz Raid Array (mirror) with two 200Gb Maxtor 7200 RPM DiamondMax Plus 9 ATA/133 drives w/8Mb buffer Promise TX2000 PCI RAID controller The drives are partitioned (NTFS) into a 4Gb Swap (F:temp), 70.5Gb (G:Data) and 115Gb (H:Photo; where all the images are stored) and I also have another 20Gb (C:System) Maxtor drive where all my apps are located. Virtual memory is at 1012-1500Mb and the swap file resides on the F:temp drive. CS is now set at 65% memory util and scratch is on G:, then H:, then C: At boot, my page file is just a tick under 300Mb.
I currently have 879 images totalling 74.3Gb of data on my H: drive. Not all of these have been cached and all the raw images are each at 100Mb (which is the majority of the 879, I think).
SO – do I need to cache all these images in CS’s Image Browser to improve performance? Also, in Windows Explorer (if I open it from the File|Open menu, let’s say), should I turn thumbnails view off (meaning, there seems to be some caching going on then too). The bottom line is that the drive pages alot during all this which appears to be most of the problem. Maybe it makes sense with all this data? Sometimes the CS process is at 99% or so CPU util, sometimes not. I did kill the process one time to check, which got the system back on track.
Again, I appreciate your sticking with me on this. I’ve been tinkering with PS for years but have only recently had the capacity to get serious with my slides so I’m eager to get things tuned just right.
Drew, I’d say you are going to have to let your machine cache all of those files (let the File Browser do this overnight seems the least obtrusive way). Unfortunately, the preview in the File|Open dialog is also coming from the File Browser cache so if the previews aren’t cached yet your system will appear to lock while it’s doing this on large files. I think this process needs to be rethought by Adobe, at least they should allow us to turn off the preview in the File|Open dialog (there are people who would never use the Browser and not know that this thing is happening). Chris, I don’t suppose you ever found out if we currently can turn off the preview?
Well, I’m currently caching images as we speak. I’m opening up each directory and allowing it to cache the thumbs. However, your reply is somewhat confusing as it relates to File Browser. Won’t I have to do the same thing with this (meaning opening each directory and letting it cache)? Are the cache files connected to one another or separate?
One idea is to utilize a process which caches thumbs when the system is idle OR at a scheduled interval. A good example of this is Executive Software’s Diskeeper defrag utlility. It even gives you the option to do degrags while the screensaver is running. Basically, they have found a good way to optimize idle time to get the job done. Something to consider.
If you check the file browser cache folder, you’ll see entries being written to it when you have the File|Open dialog generating previews, so I assume they use the same cache. I’d just open the File Browser, pick on your data drive and select File > Build cache for subfolders.
All of my chinese fonts cannot work in photoshop cs. There is no problem in the previous version of photoshop. It happens after I upgraded from photoshop 5.5 to photoshop cs. Only the windows default chinese font can work.
Derrick/Chris – wanted to let you know that all the thumbs are now cached in CS. I’ll dick around in it this w/e and get back to you on how it worked out.
I can tell you that the cache in CS is not integrated with thumb cache in XP. I am now going through the same process in Windows Explorer, just to be sure. The difficulty here is that XP does not include a batch cache process like CS does….meaning I have to do each directory independently. AAARGH!
I still vote for a user-configurable process allowing for background caching to occur in CS for File Browser. It should be easy to create a low-level process that optmizes PC idle time in this fashion.
That’s true, I was talking about the preview under the contents window in the File|Open dialog, not the thumbnail views inside the window, which is XP’s thumbnail cache. Does the File|Open dialog still lock up after caching the Browser?
I can tell you that the cache in CS is not integrated with thumb cache in
You should know by now that Adobe do not comment on any product until it is ready to ship (and I really wouldn’t expect any updates for Photoshop CS for another 6 months or so, minimum)
Okay Dave, step away from the keyboard. You can do it, its the first step towards recovery. Take two aspirins and get a good nights sleep (not that this is going to change anything, but you will feel better and probably even more impish).
As a permanently intermediate level hobbiest photographer I have been using Photoshop CS for a couple of months and have found a few defects and have a gripe.
My system is a Pentium 4 2.6C with hyperthreading turned on; Windows XP; 1 GB memory with 735 MB dedicated to Photoshop; 120 GB disc with 90 GB free.
Defects:
1. The dates for "created" and "modified" shown in the metadata window of the file browser are mostly incorrect. On images that I have just downloaded from my Canon G1 or scanned with a PhotoSmart S10, the reported dates range from years 1920 to 2037. The files themselves have the correct dates as reported by Windows Explorer, but the Photoshop browser reports them incorrectly.
2. Frequently I find that after using Photoshop a while small files ~18 MB which usually converts to ~219 MB in Photoshop(including Photoshop itself) will result in ~680 MB consumed. Even if I purge everything it still consumes this ~680 MB. If I close Photoshop and re-open it and reload the image the memory usage drops to the ~219 MB. Apparently some memory management problems exist.
3. I sometimes leave Photoshop minimized while browsing the Web with the Explorer browser. Often when I return to Photoshop the browser window and image windows will be repositioned so far up that I can’t grab the title bar and reposition them. It’s not hard to work around this, but the windows should remain where I left them.
4. When I scan images directly to disc files using the HP PhotoSmart S10 as .BMP or .TIF files and then try to view them with the Photoshop browser it often cannot produce thumbnails of them – most of the time failing with .BMP and less often failing with .TIF. If I load the image into Photoshop from the browser and resave it the thumbnail is produced.
Gripe:
The lack of thumbnails of PSD images for Windows Explorer and other Windows file viewers is baaad form. If it only affected non Photoshop stuff users might understand. But it affects Photoshop itself. If you use the Picture Package automation and want to select different images to print you have to select all but the first image using – you guessed it – a Windows dialog box which shows only the PSD generic icon. Baaad form!
Question: Is there any way to delete history from metadata? I started out with the recording turned on and later realized how much useless editing info I had gotten attached to some images.
1) The only time I’ve seen that is when the camera date was set wrong, or some other application included metadata with the wrong date.
2) No, that’s normal. Files are compressed – the IMAGE size in Photoshop does not include any compression. Photoshop allocates memory up to the limit that you assign in preferences, and then manages that memory until you quit. Releasing and reallocating the memory would really slow things down.
3) I don’t know.
Gripe: Sorry, but that is up to Microsoft. We tried to provide previews using their APIs, and encountered too many problems.
Chris, thanks for so prompt a response. I need to make myself clearer, and/or get a clearer explanation for some of these items.
1. The dates are definetly being reported wrong in file browser, and it is not a fault of camera date settings. Just one of hundreds of examples:
A file in which the camera exif data as displayed by Photoshop file browser shows a "Date time" of 2004-01-23 (the date of download), "Date Time Original" of 2003-09-18 (date picture taken).
In the same metadata display the File Properties shows for "Date Created" and "Date Modified" 9/19/1966.
Microsoft Explorer shows "Date Modified" as 1/23/2004 and "Date Picture taken" as 9/18/2003, which is the same as exif data.
Clearly the file has the correct date information and it is incorrectly, and apparently randomly, reported in the File Properties.
2. I do not understand how a file being loaded into an "empty" Photoshop resulting in memory usage of 680 MB one time and 219 MB another, in both cases out of a reserved memory space of 735 MB can be considered normal. In the case where 680 MB usage is reported, as soon as you do any modifications the memory usage goes up, quickly exceeding the 735 MB and resulting in disc swapping and slow processing. Purging "All" only goes back to 680 MB usage. If I then close Photoshop and restart it and reload the same file the memory usage is reported as 219 MB and I can modify extensively before usage exceeds the 735 MB reserved, and processing is fast. I only use the 219 and 680 as examples – other files of different sizes have shown the same problems with different memory usage amounts.
4. You didn’t comment.
Gripe:
It seems to me that if Adobe couldn’t get thumbnails into Windows it should have made it possible to select images from the browser – which actually makes more sense to me anyway.
On deleting the History in metadata – I opened the file, displayed File Info and selected History. After selecting all I tried the delete key, which did nothing, then I tried right click which only gave me one option, copy. It does not appear that there is any intended way for this to be deleted. Other suggestions?
I am not alone in this observation. It seems PS CS slows down after awhile, even after purging. It is almost like in the old days when PS used to leak or lose memory over a long period of time. Work around: Close PS every hour or so for max speed. Tried a whole bunch of other solutions. Really weird when you close all files and purge and the slowdown is still there! We are talking from screeming speed to medium speed. Almost like some cashe isn’t dumping somewhere. Problem goes away with a PS restart.
I typically open PS in 3 seconds. Open a 72 meg file in 3 seconds. Move around with filters, etc extremely rapidly. Gradually, as I work over a period of hours, things just get a little slower, and slower, and slower. Purge all. New image. Still much slower than very beginning. Of course, as I stated above, the simple workaround is to restart PS CS. But why???????
By the way, I have been with PS since day 1 so I ain’t a newbie. But I am not a computer super tech either! Also, tmp seems to be set correctly.
1) Then we’ll need example files that show the problem.
2) Because you’re comparing apples and oranges, and don’t have any understanding of how Photoshop’s memory management works.
4) Because I have no idea. I haven’t heard of anyone else with that problem, so my first guess would be a problem with your scanner software.
Steve – Photoshop has never had a major memory leak. It sounds like you could have a problem with the scratch disks. What version of Windows are you running? How are the scratch disks setup? How are they formatted (NTFS or FAT32)?
Well, I can go get a bunch of quotes for you from other photographers, but here is one from Zane Paxton "I think there is a "memory Leak" in CS, i.e. I notice that the available RAM slowly disappears until it is operating intolerably slowly. I have 1-1/2 Gb of total RAM (WIN XP) and it will start a session with maybe 950 Mb free RAM and then after an hour or so end up trying to operate with less than 300 Mb of RAM and it really starts to drag. (I can monitor this with my MEM Turbo Pro utility). Then I reboot. Kind of frustrating… I do a lot of RAW conversion and 16 bit editing."
This is the same thing that is happening to myself and others. Not sure what you mean about apples and oranges.
I am running XP (fully updated) on a Dell XPS, CPU 3.2, with a mirrored raid array of a pair of 120 SATA drives, 2 gigs or ram, and formatted as NTFS. As I run nothing but Photoshop and have tons of hard drive space (75% free) I chose not to partition (80 gigs of free space should be enough).
Lastly, I don’t use a scanner. My files are brought in from my Fuji S2 as raw files, converted to 16 bit tiff (Adobe 1998 RGB), tweaked a little, and changed to 8 bit tiff. They are either 35 or 70 meg files. As I do a lot of collage work I can have 4 or 5 images open untill I can drag and drop as layers. Then I close the images that I am not using. After I do this sort of heavyweight stuff for an hour or two Photoshop starts to slow down. So I save, restart PS, and I am back up to speed again – with the same identical file. PS doesn’t crash, it just gets slow. Does this help?
And Zane understands Photoshop’s memory management how? His description is normal, EXCEPT that it has nothing to do with slowing down and there is no need to reboot — he’s just hitting the scratch disk.
Again, you’re comparing comparing things that are unrelated (apples and oranges) and jumping to highly unlikely conclusions.
MemTurbo can’t tell you squat about Photoshop’s memory usage – just how much has been allocated (which is meaningless because Photoshop allocates up to the limit YOU set and then manages the memory itself).
We’ve looked for memory leaks in Photoshop (we test that with every release) and haven’t found any. Several versions ago I think there was a leak of 12 bytes every time you opened a certain dialog — but that’s about it (and that was the OS leaking).
Again, what you are describing sounds like you’re hitting the scratch disk (perfectly normal) and something is making the disk access slow.
At random times the levels dialog box will start repeatedly calling up the help document in explorer. Whenever the dialog box gets focus it seems to spawn the window repeatedly. It only seems to happen after I’ve been using PS CS for a couple of hours and the only way to get it to stop is close PS CS from the task manager and reboot. This is the fourth or fifth time this has happened in the last month. It’s very annoying as I now have about 30 copies of the help text up.
I am running windows XP home, up to date with patches, on a P4 2.4ghz Dell 8250 with 1gb ram.
At random times the levels dialog box will start repeatedly calling up the help document in explorer.
I have seen the same thing several times in Photoshop 7.01. Suddenly IExplore fires up the help file and when you close the window, a new window just pops up. The only way to get rid of it is to kill Photoshop and start it up again. I don’t have to reboot Windows.
Yes, I always CLOSE the file browser. Tried memory allocation from 90% to 60% to 40%. If I open PS CS (only) at 8:00 in the morning, open a file, and just let it SIT idle for 6 hours I can watch my memory gradually go down to the point of PS being unusable. Others on various forums have experienced the identical symptom. Of course if you start working with 200-300 meg files it will grind to a halt after only an hour. Of course all this is without using ANY filters. However, this last time (just to see) I did decide to use a filter on a 200 meg file after I hour of PS use. Not enough ram says the friendly message (I have 2 gig). So I purge and close the file and open a small 10 meg file and tried again. Not enough ram says the friendly message. OK. I close PS and reopen it. Open the 200 meg file and apply the filter – zip, done. That fast. This ain’t right. I, and others with the same identical problem, feel PS isn’t clearing some memory and has a ram leak – just like happened many years ago. Chris says PS has never leaked memory in past versions. Uh, I sure disagree. Anyway. Waiting for a computer guru to show up or for Adobe to admit there MIGHT be a problem. I will gladly take either one. I LOVE PS – I have been using it since it first hit the streets as v1.01. And before that Aldus Photo Styler that was purchased by Adobe in order (I imagine) to ease into the PC code. I guess I will try the phone. That almost always works.
If you’re not using it, and the filebrowser isn’t running, then Photoshop isn’t doing anything.
No, others have not experienced the same thing (or haven’t reported it). All that’s been reported are gross misunderstandings of how Photoshop’s memory management works. (usually from a failure to read the fine manual)
The filter not being able to allocate memory has nothing to do with Photoshop running out of memory (or having any possible leak). Photoshop isn’t running out of memory. The OS is running out of address space, and that prevents the filter from running. But Photoshop still has all the memory you told it to use.
OK, so it’s an OS problem. Never had this with 98SE and 7. Here is a quote from someone else having the same problem.
"I have been having the same problem with PS CS. Checking task manager after each open/close of an Image, the memory usage kept climbing. CS never released the memory back to the system.
It was recommended to me to try Ram Idle. (link below). I installed and ran Ram Idle and my memory leak is gone. CS is no longer hanging onto the ram used in open/close of Image files."
Hopefully this works for me. Perhaps I need to study the manual more for a fix. I tried once already. We shall see.
Steve – that IS NOT the same problem at all (you’re still comparing apples and oranges). Photoshop doesn’t release memory back to the system – that is entirely normal.
But it is NOT the same as sitting idle and the memory allocation growing – which you are reporting.
And he’s full of crap about PS not holding on to RAM after installing "RamIdle" – it’s part of the design of Photoshop (otherwise it would be a LOT slower) to manage it’s own memory and no third party hack is going to change that.
Whatever. Problem solved. PS now screams no matter how many files I open, close, or play with (Ram Idle worked). Just finished throwing around a 735 meg file while three other 70 meg files were open. Closed them and opened three more. No problem. Thanks for your instance that there was not a problem. I did go back and re-read the manual. This wasn’t discussed. All your talk about apples and oranges didn’t help a bit.
And yes, there are a bunch of people out there with the same problem. I just gave you quotes from two. How many quotes do you need to see that there MIGHT be a problem? OS, motherboard, or whatever.
Sorry for just being a dumb ‘ol photographer, and that the nuts & bolts of the RAM thing has taken a while to sink in, but I think I am finally getting a handle on it. Scott Byer’s description of PS’s memory management recently helped a lot.
I’m still getting stonewalled with the "out of RAM" stops, so if it is XP Pro that is running out of address space, what’s the cure? Bigger Page file allocation?( I’ve got heaps of sata raid 0 space) – or is it another one of those glorious MS "broken by design" features?
I’m also still intrigued as to why this seems to be hob-nailing some 2GB DC SDRAM users and not others, though.
My hardware checks out OK, and the fact that the problem exists with both PS 7 and 8 already had me thinking that there might be a Gates-ism at work here………..
I’ve tried to find reference to RAM handling in the "fine manual", but other than reference to scratch disks and not enough RAM, I can’t find anything specific. Page# or section you are referring to, please? Fred.
Sorry for just being a dumb ‘ol photographer, and that the nuts & bolts of the RAM thing has taken a while to sink in, but I think I am finally getting a handle on it. Scott Byer’s description of PS’s memory management recently helped a lot.
I’m still getting stonewalled with the "out of RAM" stops, so if it is XP Pro that is running out of address space, what’s the cure? Bigger Page file allocation?( I’ve got heaps of sata raid 0 space) – or is it another one of those glorious MS "broken by design" features?
I’m also still intrigued as to why this seems to be hob-nailing some 2GB DC SDRAM users and not others, though.
My hardware checks out OK, and the fact that the problem exists with both PS 7 and 8 already had me thinking that there might be a Gates-ism at work here………..
I’ve tried to find reference to RAM handling in the "fine manual", but other than reference to scratch disks and not enough RAM, I can’t find anything specific. Page# or section you are referring to, please?
Fred – reducing the memory allocated to Photoshop will help. But it can’t fix all cases – some plugins are just piggy about what they allocate and how they allocate it. We’re still trying to find a way to make everyone work happily together, but it’s not nearly as easy as it sounds.
It’s hitting people with 2Gig or more of RAM because the NT/XP address limit is 2 Gig per application.
I’ve never had much faith in M$. I’ve now identified the problem filters & actions I use, so I wind back the RAM allocation to 38% before using them and all works OK, though a bit slower than I’d imagined my machine should do.
In case anyone has misconstrued my complaints as being unhappy with PS, I feel obligated to state that this is not the case – I was just disappointed that the big bucks I’d spent on my new machine expressly to run PS well had seemed to come to nothing. CS is really an amazing piece of work. In my case, at least, it does everything quicker and better than 7 did.
I’m totally not surprised that my problem seems to be sourced with M$ and its "superior" software.
Chris, with regard to the problems I reported with file browser reporting incorrect "create" and "modified" dates in "File Properties", and also with its failure to produce thumbnails for bmp files I have tried an experiment with strange results.
I have Photoshop CS also on a laptop networked with my desktop, and almost identical settings and software on both. When I view the problem files on the desktop using the file browser on the laptop the correct dates are shown and the thumbnails are produced. If I copy the files to the laptop and view them there, everything is okay also.
It appears that something on the desktop is interferring with Photoshop. The only thing I can think of is that before buying CS I had run the tryout version of Photoshop 7.01. But it had long been uninstalled before I installed CS. Is there any possibility that something is left of 7.01 that is confusing CS? If so, how can I find and remove it. If not, any other ideas?
I would be happy to send examples of files if you tell me how, but my experiment indicates that the files are okay.
Chris, with regard to the problem with memory that I reported, I am seeing the same slowdown in performance as reported by Steve Bingham, but I only have 1G of memory with 735 MB reserved for PS. This is happening although the "scr" display may be showing something like 250/735, which implies plenty of available memory for PS to work. I did not mention this before because I thought my observation was an obvious indication of a problem.
For clarity, I will restate my observation and what I understand you to be saying about it:
If I do a fresh start of PS, open MYIMAGE, and the scr: display shows 219/735 it means (according to the manual) that PS uses 219 MB of memory to display the image and has up to 735 MB available to perform operations without using scratch discs.
After using PS for a while, doing whatever, then closing all images and purging everything I open MYIMAGE again. This time scr: display reports 680/735 MB. This means that now PS is using 680 MB to display the same image it only took 219 MB to display before. In only one or two operations we’re using scratch disc, and purging all gets it only back to 680/735.
This is what is often happening, and you said that this is normal. If so then you are saying that even if there are no open images in PS you cannot assume that PS has all the reserved memory (in this case 735 MB) available for working on the next opened image unless you exit PS and restart it.
Is this correct? I have a hard time believing PS is supposed to work this way. I used the tryout version of 7.01 and loved it. I don’t recall having any problems at all with speed using it.
I have been unable to extract anything like a useful explanation from anything you or others have said about this. Steve alluded to a "RAM idle" setting in XP which seemed to solve his problem, and mentioned a link, which I don’t see. You mentioned info in the manual, in which I, like others don’t see anything helpful. At this point, I’m not sure that the speed problems others are reporting are due to the same reasons as mine.
Jerry – PS 7 shouldn’t interfere in any way. But corrupt preferences are still possible, so try resetting the prefs. Other than that, I have no idea what could be messing up the date display.
The scratch numbers don’t relate to the particular image – they relate to the total scratch space used, and the RAM used (there is a different display for the memory used by each image). Yes, they will grow until the RAM hits the limit you set in preferences and then only the scratch will keep growing. Yes, you are ALWAYS using scratch disk space.
If you have no images open, then all that memory (scratch and RAM) is available for more images – it’s reserved, but not in use. (it sounds like you misread something)
RAM Idle is a red herring – it can’t help Photoshop in any way, only hurt or do nothing.
Yes, they will grow until the RAM hits the limit you set in preferences
and then only the scratch will keep growing.<<
Bingo! The penny just completely dropped, and I now fully understand just what’s been happening. Sorry to have been so stupid, and thanks for your patience, Chris.
I really don’t give a rat’s (whatever) how PS CS manages memory. I’m glad that you finally understand it, though, Fred. Myself, the numbers don’t concern me. What concerns me is that I can’t use PS CS to get my work done. It’s too slow.
OK, let’s say it’s my hardware. If so, somebody please tell me why a Win2K machine that runs PS7 beautifully runs PS8 horribly. I’ve reinstalled PS CS (three times! I’m on a first name basis with the activation womanoid!) I’ve created a new partition and done a fresh install of both Win2K and XP Pro on that partition, then installed PS CS. No joy. Is it the fault of my machine? I don’t think so, if PS7 runs on it just fine. Must I upgrade my hardware to run a new version of PS, even though my machine far exceeds minimum requirements??
I’ve been trying to "hold my tongue" but I’m seeing little reason to do so.
Nick – without having your machine in my hands, I don’t know. I’ve given you my guesses and you say that those are not the problem. Well, I don’t know what your problem is. But Photoshop itself is running fine for thousands of other users – so it is still most likely a problem specific to your machine. You shouldn’t have to upgrade your hardware, but you are going to have to do some investigative work to tell us why it is slow on your system and not on other systems.
Chris, I think you should stop defending PSCS with such passion. Also, stop making up excuses (and lots of BS) about how everything is so dandy with the program. It really is slow (on Windows)…just admit it. You remind me of a father, who at the last parent-teacher’s meeting, refused to acknowledge that his son was a troublemaker (even though 3 teachers and 1 principle insisted). Just curious…..on what computer and OS are YOU mainly running PSCS?
What computer(s) does Chris run, well he either wears sun glasses and grits his teeth behind some and has to chase the rest of them all over the place.
Tony – I’m not making any excuses. I’m just telling you the truth.
No, it really isn’t that slow – for most users. I’d like to find out why it is slow for a few users – but we can’t reproduce the problem yet, and we’re not going to be able to until we get ahold of those machines or the users help us figure out what is different about their systems. We can’t just wave a magic wand and make all your troubles go away.
I run CS on 5 different machines in my office: 3 Macintosh, 2 Windows. But because I do the hardware work, I tend to have the fastest machines. So periodically I do sanity checks on slower machines in our testing lab (or my home machine, a whopping 500 Mhz PIII).
Maybe the fineprint should read: WHEN UPGRADING TO PSCS FROM VER. 7.0, YOU SHOULD ALSO UPGRADE YOUR SYSTEM. Just curious (again)…..Are MAC users complaining about PSCS’s speed?
I know that I have griped a lot about some Adobe company actions but I have to say that their software program, Photoshop CS, is working wonderfully here. No "bugs", crashes or extra requests for "reactivation".
The system is just an "plain Jane", out of the box 2.4 gHz Gateway,with the memory brought up to 1 gig, running XP Home. Well loaded with applications but I try to keep it "very clean".
I suspect that 90% of the problems that people report here and are having with CS are due to something unique to their system and not due to any defect or limitation in Photoshop.
My suggestion is to really examine your setup before you blame Photoshop.
Not on all Windows machines – no speed problems with CS compared to 7.0.1 at all here.
XP Pro SP1, P4 3.0, 2GB DC DDR SDRAM. I had RAM issues (but this was for both 7 & 8 equally), which I now understand not to be PS’s fault, but my not understanding the relationship between PS & the OS & 2GB RAM, and work-aroundable (if that’s a word) to a degree with a bit of forward planning.
CS ran equally as fast as 7.0.1 on my old XP Pro SP1, P111 1.0, 1.5GB SDRAM machine – i.e what was slow on CS was as slow on 7.0.1.
Of course, it was all a lot slower on that machine.
I would like to support the observation about the PS Browser reporting wrong dates in Metadata File Properties, in particular the "Date Created" field, which is however reported correctly in the camera EXIF date for "Original" and "Digitised". This is with files direct from the camera (whose settings I have checked) or from other sources.
You shouldn’t have to upgrade your hardware, but you are going to have to do some investigative work to tell us why it is slow on your system and not on other systems.
Believe me, I’ve tried everything that you or anyone else has suggested. I’m willing to accept that it may be something hardware-related, but I doubt that it is unique to my machine, judging from the fact that this thread alone has nearly 250 posts.
I’ve posted my system specs before, but will do so again if necessary.
Here’s another situation that was pointed out to me by another user on a different forum: Both he and I use a set of actions called PhotoKit Sharpener, developed by Bruce Fraser, Jeff Schewe and company. For me, these sharpening actions run much slower on PS8 than on PS7, but that’s old news. The new wrinkle is that the degree of slowness is dependent on what zoom setting is set in PS8. For instance, when viewing a file at 25%, the Capture Sharpener action takes 25 seconds to run. When viewed at 50%, the same action takes 42 seconds to run on the same file. This is not the case when running the same action on the same file in PS7. The action runs in 14 seconds, regardless of zoom setting. Any thoughts? Video card is Matrox G450, latest drivers, dual monitors.
I have a similar setup to you Jerry and so far there are no major slow downs or other problems. Having the File Browser open when working does slow down moving the image windows around but that is solved by closing the browser. I am probably not taxing the program though like some people who are having problems.
wrote in message
I know that I have griped a lot about some Adobe company actions but I
have to say that their software program, Photoshop CS, is working wonderfully here. No "bugs", crashes or extra requests for "reactivation".
The system is just an "plain Jane", out of the box 2.4 gHz Gateway,with
the memory brought up to 1 gig, running XP Home. Well loaded with applications but I try to keep it "very clean".
I suspect that 90% of the problems that people report here and are having
with CS are due to something unique to their system and not due to any defect or limitation in Photoshop.
My suggestion is to really examine your setup before you blame Photoshop.
In my case these PK Sharpener actions Nick mentioned were working fine in both PS7 and CS (~13 sec/6-megapixel/ 8-bit file) until I increased system RAM from 1GB to 2GB. All of the sudden things slowed down, PK Sharpener 20 sec on the same file @50% zoom.
This is where I noticed that zooming out to 25% (or smaller) speeds things up considerably. This certainly isnt the case in PS7.
I also noticed general slowdown is PS CS since 1GB stick of RAM was added (PS7 is unaffected and very happy with it). This is especially evident with screen redraw during Curves, Levels adjustments. There is bit of hesitation in CS where in PS7 transition is smooth and instant.
BTW: PS memory allocation makes no difference, times are exactly the same at 30, 50, 60, 75 or 90%.
Other than added RAM and Page file size (increased to 3070/3070MB) nothing has changed on the system.
I still did all the usual troubleshooting steps: disabled all nonessential background processes, network etc. No joy.
Video Cards: Matrox G400 (primary display), G200 PCI (secondary display).
Here is the rest of the system (if anybody cares)
Adobe Photoshop Version: 8.0 (8.0×118) Operating System: Windows 2000 Version: 5.0 Service Pack 4 System architecture: AMD CPU Family:6, Model:6, Stepping:2 with MMX, SSE Integer, SSE FP Processor speed: 1333 MHz Built-in memory: 2047 MB Free memory: 1830 MB Memory available to Photoshop: 1778 MB Memory used by Photoshop: 75 % Image cache levels: 4 Use image cache for histograms: No Serial number: PAID FOR with Ctrl key working Application folder: C:\Program Files\Adobe\Photoshop CS\ Temporary file path: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ Photoshop scratch has async I/O enabled Scratch volume(s): F:\, 19.5G, 5.95G free H:\, 35.5G, 20.6G free G:\, 19.5G, 8.13G free I:\, 8.54G, 7.10G free Primary Plug-ins folder: C:\Program Files\Adobe\Photoshop CS\Plug-Ins\ Additional Plug-ins folder: not set Installed plug-ins: xxx
I may be off track – but then again, maybe not……..
Seems that your trouble stems from a third-party plugin, the video re-draw and their interaction with CS and the 2GB of RAM.
My old machine had a similar video card setup to yours – Matrox Marvel G400 & G200 PCI secondary (and Nick mentions he has a G450). At the time of purchase the Marvel G400 was about their most expensive card, yet Matrox dropped the baby when XP was released – they never wrote drivers to support the full function of the card, but only supplied drivers (with XP) that supported a limited display mode. Their driver page still lists the Marvel G400 XP driver as "none planned".
That said, I always had trouble with Matrox software, but I never realized how bad it was until the new computer which, given the preceding, I made sure would have nothing labelled Matrox in it. So I have a dual-head setup using an Asus V9520 8x AGP card (Nvidia 5200 chipset) running Nvidia drivers which runs absolutely flawlwessly, and shows up how truly badly the Matrox setup performed.
I’ve re-installed 7.0.1 to run the following on my machine in comparison with exactly the same thing on CS, same pref settings etc (RAM allocation @ 50%, 4 cache levels, same scratch disk setup), using Nik Sharpener Pro as the third party sharpening plug-in.
Ran the following 3 times each. File: 215MB RGB 8-bit. Nik Sharpener Pro 1.0e using "Inkjet" at default settings:
a). zoom @ 50% – 7.0.1 = 58 secs, CS = 60 secs
b). zoom @12.5% – 7.0.1 = 58 secs, CS = 60 secs
Given that consistent result, and my inherent distrust of Matrox, I’d suggest you might look towards your video cards/drivers as being a likely source of the problem. Maybe CS taxes them more than 7.0.1 in combination with them perhaps not liking the 2GB RAM setup. If Matrox couldn’t supply drivers for my Marvel 400 to suit XP, maybe their software or the G200/400/450 series can’t handle what CS throws at them. Even with the latest drivers.
I used Nik Sharpener Pro here as this was the 3rd-party plug-in that first tripped up my 2GB DC DDR SDRAM P4 3.0 machine and led me on my flawed crusade against PS and its RAM handling, so I figure it is as intensive as the sharpener you used.
Not being a technophobe I may be well off the mark, so I stand to be corrected, but my experience with Matrox was not a happy one.
Nick – that could be related to the cache level you have set (and you’ve said it’s at 4), or the histogram palette or info palette. Try hiding those two palettes and see what happens.
Seems that your trouble stems from a third-party plugin, the video re-draw and their interaction with CS and the 2GB of RAM.
Anything is possible I suppose.
I’d suggest you might look towards your video cards/drivers as being a likely source of the problem. Maybe CS taxes them more than 7.0.1 in combination with them perhaps not liking the 2GB RAM setup.
Matrox Millennium G400 max has been a workhorse more than able to handle anything PS had ever thrown at it including CS. Matrox drivers have always been very stable for me.
I find it hard to believe that adding more RAM to the system could suddenly cause video card and/or drivers to misbehave. Furthermore how could this account for slower execution of bunch of actions? After all PK Sharpener plug-in is nothing more than set of actions executing standard PS commands.
Anyhow Ill revert to previous video driver version (latest certified) as opposed to the latest and (maybe not) the greatest just to be sure. Not holding my breath this will cure anything though.
OTOH if there is possible problem with PS CS/ Dual CPU/ 2GB RAM/ Win 2000 and some other specific hardware/ software combo Im open to any suggestions.
that could be related to the cache level you have set (and you’ve said it’s at 4), or the histogram palette or info palette. Try hiding those two palettes and see what happens.
Closing Histogram (and info) palettes does indeed speed up PK Sharpener but closing them and zooming out to 25% speeds it up even more.
So there is still significant difference in speed depending on zoom % of the image.
So there is still significant difference in speed depending on zoom % of the image.
Which is why I headed down the path I did – there was absolutely NO difference in the speed of the sharpening on my computer between the different zoom levels. That’s why I smelt video card probs – but, as always, I am probably wrong.
I don’t think going back to the earlier driver will help, either. Matrox enjoys a far better reputation than it deserves – the "latest" driver for your card is 29 August ’03, after all. A lot’s happened since then, including CS.
I tried Chris’ suggestion on my computer, and it made absolutely no difference to speed whatever, make of that what you will.
Having finally got a handle on the 2GB RAM thing and the OS addressing etc (put together Chris’ comments in this thread, along with Scott Byer’s explanation below, and you may see what I mean), I reckon just about anything’s possible regarding misbehaving……. a lot of software is still catching up. Note the last sentence:
Tuning Photoshop:
Open Windows Task Manager. Go to the Performance tab. The number to watch is in the Physical Memory section, "Available".
Start Photoshop and start working. That Available number will decrease and, after a while, will often stabilize out.
Is it below 15000 (15MB)? Your Photoshop memory percentage is set too high. Lower it and try again. Is it above 50000 (50MB)? If you really have been doing things you normally do, including running a filter and you still have more than 50MB free, you’re probably leaving a little performance on the table (but not as much as you think!). Consider increasing Photoshop’s memory percentage slightly.
If you *really* want to get technical about it, bring up Performance Monitor and set it up to track a few things (free memory, disk activity, memory paging rates).
What you are trying to avoid is having the OS page out Photoshop’s memory. We don’t lock down Photoshop’s memory because that causes many, many more problems than it solves. But when Photoshop has allocated a lot of memory, some of it looks to the OS as "not busy" and will get paged out if RAM gets low. If Photoshop’s scratch and the OS paging file are on the same physical disk, this is doubly bad.
If all you want is the fastest performance on your machine, this is all you need to know. Scratch size, tile size, all red herrings and they generally don’t affect performance how you think they will.
I don’t think going back to the earlier driver will help, either.
I didnt think so either and it didnt.
Matrox enjoys a far better reputation than it deserves
I think youre wrong there
the "latest" driver for your card is 29 August ’03, after all. A lot’s happened since then, including CS.
The drivers were good long before then and didnt really need updating.
You are missing the point completely. From the previous posts I take you are running XP. NO?
I run Windows 2000. If Adobe cant make PS CS run on W2K they need to drop this OS and face the con$equence$. Im fine with that but I need to know up front before I make my decision to purchase the product.
If they claim it does work on W2K I expect it to work.
I shouldnt need to change perfectly good hardware that by far exceeds minimum system requirements.
Yes, I agree, everything should work as claimed. And on my computer, it does. That’s why I reckon there is something else amiss. I can see no reason why it would run OK on XP and not on 2K.
I’m just pointing out that the "obvious" cause (CS, in this case) may not necessarily be the culprit – in my case it turned out that XP was involved in a way I’d not even thought of.
I am intrigued, however, as to the effect that Chris’ suggestion had on your computer where it had absolutely no effect on mine. As we both have CS in common, you’d think that there may be another player involved, or that Chris is on to something that the rest of us are oblivious to.
As CS offers increased 16/32-bit support and 300,000 pixel width vs 30,000 in 7.0.1 amongst other things, standards that almost no third party stuff commonly recognizes (yet), I’m not surprised that there may be problems with other software.
I’m not trying to be difficult, more like I am interested as to the cause of your problem so that I can further my own understanding of the way things work, if nothing else.
One thing for sure – there will be a solution eventually. Please post it if you find it independently for the benefit of the rest of us.
Chris, I just ran a series of tests, trying your suggestions. In all cases, memory allocation to PS CS is 50%.
First, changing the cache levels from 4 to 6 made no discernible difference. Changing cache to 2 slowed things down. Other than that, my results are similar to Andrew’s. In my case, closing the Info and Histogram pallettes made CS run the PK Capture Sharpener action 20-25% faster. And, like Andrew, mine runs faster as I go to smaller zoom settings. To give you an idea, here are the times (with Histo and Info Pallettes closed):
50% – 30 sec. 25% – 20 sec. 6.5% – 15 sec. 2% – 13 sec.
I’m not using a stop watch, just the second hand on my watch. But the general trend is easy to see.
I would add that closing the Histo and Info pallettes made no difference in the speed for opening a NEF file with ACR2. That takes 14 seconds in PS CS, as opposed to 3 seconds in PS 7 with ACR1.
Moving over to my XP Pro machine (which has an nVidia card as opposed to Matrox), I noted pretty much the same behavior, ie., PS CS runs the same action faster at smaller zoom settings, and faster still if the Info and Histo Pallettes are closed. The XP machine, however, is much faster at opening a NEF file – 4 seconds as opposed to the 14 seconds on Win2K machine.
I hope that tells you something, and will look forward to your thoughts.
Nick, how much memory is there on the XP/nVidia machine; what processor does it use? did you try to install the nVidia card in the 2K computer (even if it is also affected by the zoom %) What is the size of the layer thumbnails in CS? did you try to set it to none to check the speed?
Andrew, are you using dual processor Athlons?
Chris/Scott, what controls the redraw of the layer thumbnail, navigator, and histogram, Photoshop or the display drivers? (I remember that some people had blacked out histogram palette due to bad videocard drivers)
Pierre, the XP machine is a P4 1.7GHz, 1 GB RAM. I had the layer thumbs set for small. Changed them to "None" and it made no difference in speed, still seeing the different times based on zoom settings.
I haven’t tried installing the nVidia card in the Win2K machine, yet.
I don’t think it’s a fair comparison. The Win2K box is 1.3GHz Athlon with 1.5GB RAM, while the XP box is a 1.7GHz P4 with 1GB RAM. Apples and oranges. Also, the XP box is a garden variety Dell, while the Win2K box was custom-built specifically to run PS. But overall, the XP box runs the same action on the same file a little slower.
FWIW, the guy that built the Win2K machine (a couple of years ago) included bench test results with the computer. At that time, the Athlon was considerably faster than a comparable P4.
Nick, I did just point out the fact, Nick, in fact, I use AMD’s as well, so it is not just a bashing of that brand… I tried to see what are the common points that you and andrew seem to have to try to find the "faulty" hardware in your machine, or at least the one that is not PSCS friendly…
or that Chris is on to something that the rest of us are oblivious to.
This is very much what I hope for.
I’m not trying to be difficult, more like I am interested as to the cause of your problem so that I can further my own understanding of the way things work
I know you mean well. 🙂
Look I wish the fix was as easy as buying another video card. Given the circumstances though I think it would be premature for me to do so.
All that changed on my system was RAM (going from 1GB to 2GB). I dont see how this could invalidate my video card/drivers configuration.
I somehow think likely culprit is 2.
2 CPU/ 2GB/ W2K
I hope Adobe folks can pin it down and come up with a fix.
Andrew, have you tried turning down the hardware acceleration on your card? If it performs better w/HW Accel. off, the problem is likely in the drivers.
Dave, I just re-ran some of the tests with hardware acceleration turned off. It shaved a few seconds off of all of the times that I’d recorded with acceleration all the way up, so you might be right about it being driver related. But, I’m still seeing the same differences in times relating to different zoom levels and having the info and histogram pallette turned off.
have you tried turning down the hardware acceleration on your card?
YES!
Its very, very, very unlikely my video drivers could suddenly become a problem.
They worked fine with PS7 and CS with 1GB of RAM. Everything is still fine in PS7 with 2GB of RAM.
How can adding 1 stick of RAM corrupt video drivers? I dont know why you keep hanging on to this video drivers idea. I dont see connection here at all.
Ive tried three versions of video drivers for my card. They all work fine.
I wish I had another suitable video card near me so I could swap it and put this idea to rest or be proven wrong.
I dont know why you keep hanging on to this video drivers idea.
Because it’s a very valid issue and one that has caused many other people headaches in the past. Additionally, it’s one of the easiest things to check for.
It was one of the first things I checked. As I mentioned in my original post I went thru all the usual trouble shooting steps. And yes my power cord is plugged in before anybody asks. <g>
What I’m wondering is if anybody on the Beta team was using a Matrox card with Win2K? It would seem likely that they were, since Matrox has been recommended here since PS4. It would also seem likely that if there were problems with Matrox drivers that we would have heard about it.
Like I said earlier, turning off hardware acceleration with my Matrox G450 shaved a few seconds off of my test times, but not significant. I still see a considerable speed difference when turning off the Histogram and Info pallettes, and when going to a smaller zoom setting when running the PK Sharpener action, both with the Matrox and nVidia cards.
Scott, Chris Cox had asked me about NTFS earlier, and I answered him the same.
Chris, you suggested that I shut off the Histogram and Info Pallettes, which I did. Is this a known issue? Do you have any idea why we’re seeing PS CS performance vary, based on zoom settings?
Chris, these tests were run on the same file (17.2MB, 8 bit, flat TIFF) using the same PhotoKit Sharpener action (Digital Low-Res sharpen, medium edges).
The two machines are:
Win2K, 1.5GB RAM, 60% memory allocation to PS CS, Matrox G450 Dual Head 32MB RAM.
XP Pro, 1 GB RAM, 60% memory allocation to PS CS, NVIDIA GeForce2MX Single Head 64MB RAM.
I did a Purge>All after each timing, before resetting zoom ratio.
If there’s anything you would like me to do differently, let me know and I’ll be happy to do it. If you’d like, please feel free to email me: nick at yhti.net.
You said earlier that your machine ran the test file in the same time regardless of zoom in PS7, so the following may be of interest:
I set up the same test on my computer, downloaded PhotoKit and let loose on a 17.2MB 8-bit flat tiff file at your settings in CS with the following results:
At 50% zoom, the image became bigger than the 19" display, from then on the times are longer, but don’t increase with further zoom.
Closing the info & histogram boxes shortened the 12 secs results to 10 secs, but the larger zooms stayed at 17 secs.
As a comparison, I sized an image I have a custom action set for (multi-selections, Nik Sharpener Pro Inkjet sharpen step, a diffuse glow filter and several image colour and curves adjustments, two layers) to 17.2MB, and it ran consistent 16 second times regardless of zoom.
Make of this what you will – I just hope it can help steer the minds at Adobe down a path that I now just totally cannot even guess at.
Thanks, Fred. I neglected to mention that the Histogram and Info Pallettes were closed for all of my testing. I had already determined that they slowed things down generally in some earlier testing, so I don’t use them at all unless necessary.
The fact that Nik Sharpener has consistent timing is normal: as far as I know, it doesn’t use the standard photoshop filters to process the images. I like to see the team work here!!!
That’s why I included my actions test – there appears to be some part of the PhotKit actions set (and I’ve tried it with a couple of other filter settings with the same result) that causes my machine (or CS) to slow once the image zoom is larger than the display area. That it doesn’t continue to slow up to that point and as I continue to increase zoom after that point is where it differs from Nick and Andrew’s results.
And that it does slow at that point is where it differs from my own custom action test.
If I get time today I’ll reinstall PS7 and see if that behaves differently on my machine with the PK Sharpener test (just to round the results out).
I can’t believe someone made a conscious decision to change a standard keyboard command sequence (File, save_As F,A) and substitute something completely non-standard (F, V)! It’s been driving me nuts hourly since upgrading to CS! Change anything you want in your command sequence, but leave those that are established standards that you have supported in the past alone!
loren, i posted that a couple of months ago and was told that it would be fixed. hopefully. dosn’t hurt to bring it up once in a while though. drives me crazy too.
ah, here it is…
dave milbut "accelerator keys" 12/8/03 9:23am </cgi-bin/webx?13/2>
and here’s the one with adobe’s response (stephanie):
dave milbut "Why flaunt convention????" 12/18/03 3:04pm </cgi-bin/webx?13/11>
had the same problem on Feb 12. could it be a "Lincoln" bug- (had to reactivate photoshop cs for absolutely no reason- cause nothing was changed at all). doesn’t seem like a coincidence. wrote in message
A clock reset (beyond a certain limit), or a registry problem could
When opening older Photoshop files in CS I got the message "Could not complete your request due to a program error."
As stated ealier in this thread the solution is:
Open this menu: Edit>Preferences>Memory & Image Cache
The problem with CS is that any more cache levels, or any less, and it generates that error. The correct number needs to be 4. (It’s the system default)
Nick, it’s a very specific set of things that trigger the issue having to do with Layer Effects and patterns. For the most part you can run with your cache level set higher. It’s just something to remember if you do ever run into the issue of not being able to open a file.
what u mean for my version of photoshop.. like downloaded it for windows and everything.. what do u mean specifically, like is these different versions (options) to choose from besides linux and windows?
sounds like an error with the trial software. vbox is what’s used to time limit it. once hosed, there’s usually nothing to do but reformat if you want to use the trial again… that said, i don’t think vbox is included in the shipping version. are you sure you dl’d the right file?
then what i said about the trial version above probably stands. it’s very finiky and if it something in the trialware fails or times out, the only workaround is to reformat the drive.
My trial version dies when I try to "View/Proof Setup/Custom" on a 500 MByte tiff image. The image is a 4"x5"colour slide with 24bit scanned at 3200 dpi with an Epson 4870 scanner (which I can recommend for the quality). I got XP and 1GB of RAM, screen is 1600×1200, 2nd monitor is 1024×768. No message why it crashes, no offer to send a report to Microsoft.
1. Don’t drag and drop outside of the Adobe file browser. You can do it but after several pics you will spontaneiously abort out of CS.
2. I had my DPI set to 120 instead of the normal value. The very first license screen on the install was broken so I could not agree to the license. I changed the setting back to 96 DPI and the install proceded normally.
Dave (Milbut), you asked about my settings in the thread about "extremely slow opening files in PSCS." I’m posting this here because slow opening of files (other than ACR2.1 NEF conversions) is not a problem that I’m seeing, and I didn’t want to give that impression. I’ve posted them before, but here they are again, just in case.
I’ve removed PS 8 plugins from the list. The machine has two IBM 7200rpm drives, one is 20GB, the other is 60GB (partitioned). Also has an external firewire 120GB drive.
Operating System: Windows 2000 Version: 5.0 Service Pack 4 System architecture: AMD CPU Family:6, Model:4, Stepping:4 with MMX, SSE Integer Processor speed: 1327 MHz Built-in memory: 1535 MB Free memory: 1251 MB Memory available to Photoshop: 1402 MB Memory used by Photoshop: 60 % Image cache levels: 4 Use image cache for histograms: No Application folder: C:\Program Files\Adobe\Photoshop CS\ Temporary file path: C:\DOCUME~1\NICKDE~1\LOCALS~1\Temp\ Photoshop scratch has async I/O enabled Scratch volume(s): (In reverse order, meaning primary scratch is L:\, and that partition is used only for PS scratch) C:\, 19.2G, 12.1G free D:\, 19.2G, 5.23G free G:\, 111.8G, 46.3G free L:\, 38.1G, 37.9G free Primary Plug-ins folder: C:\Program Files\Adobe\Photoshop CS\Plug-Ins\ Additional Plug-ins folder: not set Installed plug-ins: ADM 2.84pe69a 02.06.17-00:03:36h ASDStrm 1.02×7 02.02.15-01:45:06h Lensdoc 1, 1, 0, 1 Lensdoc 1, 1, 0, 1 Nikon NEF 2, 2, 0, 3000 Nikon Tiff YCbCr 2, 1, 0, 3000 PhotoKit 1, 2, 1, 0 PhotoKit Capture Sharpener 1, 1, 0, 0 PhotoKit Creative Sharpener 1, 1, 0, 0 PhotoKit Output Sharpener 1, 1, 0, 0 Installed TWAIN devices: Launch PolaColor Insight EPSON TWAIN 5
File Browser settings: Do not process larger than 200 MB, Display 10 most recently used, Custom Thumb size 256px, Do not allow Bkgrd Proc., HQ Previews checked (although I have tried turning this off), Do not render vector files, Do not parse XMP data. I have allowed FB to run overnight (several times).
I have tried allocating memory to PS from 20% – 90%. I have tried creating a new partition with a clean OS install and just PS CS on it (did this once with Win2K and again with XP Pro). All drives are defragged daily with Diskeeper. Windows paging file is set at 2X RAM (3000MB) and is currently set to my C: (boot) drive, although I’ve tried moving it to other drives.
You made the point that PS 8 is "a different program with more features and heftier system requirements" Agreed, but I (like others having problems) far exceed those listed requirements. Where I have to disagree is with your statement that expecting PS8 to run as well as PS7 on the same machine (with system specs that far exceed requirements) is a "BS argument." To me, it seems quite logical to expect that, and I do.
Crop tool issue. Don’t know if it’s really a bug or just a workplace restyling, but I carefully checked options and preferences, and I couldn’t find an answer. I’m on a beginner level in PS.
I’ve used PS7 for a couple of years. I need often to make high precision croppings of image edges, sometimes only two or three pixels wide. My usual workflow is to maximize the image window, rulers on, zoom very deep into the image, make a "full image" crop selection bound from top left corner down to bottom right, then scroll to the edges one by one and adjust the bounding box. In PS7, I could grab the bounding box in ANY point, and the cursor showed as the usual two-arrow resize cursor. Now, with PSCS, I can grab the bounding box only in the corners and in the middle point. On any other position, the cursor is a single black arrow, which does not allow me to move the crop selection edges. Of course, dealing with very large images (i.e. 6400×3200 px), and doing this work lot of times a day, it’s becoming time consuming. Any tip? I love new PSCS "Color replacement" tool and "Shadow/Highlight" correction, and I really don’t want to switch back to 7. Thank you in advance Andrea
OK, on my machine solid "tail-less" arrow appears under these circumstances (go further into the ruler and the arrow gets a tail and acts like it wants to create a guide), click/drag with this "tail-less" arrow and the bonding border gets dragged in. Once in the field, the two-headed arrow appears as normal when the bonding border is clicked again.
Since the small crop adjustment double-arrows only seem to disappear when the edges of the bounding box *exactly* coincide with the edges of the window, maybe the best solution is to leave a one-pixel gap when you first create the crop box. Since you’re zoomed in pretty deeply, this should be easy to do. (I’m assuming you’re creating the crop box by clicking at the top left and dragging to the bottom right, and not using some shorthand way of selecting the whole image that I don’t know about.)
Not an ideal solution, but it seems workable, as long as you’re careful not to move the crop edge exactly to or beyond the window edge. If that happens you can always just click in the crop box itself to move the edge back inside, but of course that will affect the other edges too.
(Though I have to say, it seems as though you can drag the crop edges from anywhere along their length as long as the edge itself is visible. I’m hard pressed to see how this could have been different on 7.0, but I don’t have installed anymore.)
I first thought this was a problem in Photoshop Album, but realize now it’s a bug in PS CS. Here’s the scenario. I take a portrait orientation photo with my Canon 300D. The fact that it’s portrait (i.e. rotated by -90 degrees compared to a landscape pic) is recorded in the IFD0 block of the EXIF data (which Adobe calls the TIFF data in File Info/Advanced).
On loading the image, PS reads the rotation and orients it correctly by doing a rotate by -90 degrees. It also sets the orientation flag to "normal", which is correct. BUT… instead of replacing the original orientation tag in the EXIF data, it appends a new one, so you have both the old "-90" entry and a new "normal" entry. In fact, it duplicates several EXIF tags on saving.
If you then save the image, and reload it, it looks correct because now the image itself is portrait mode (i.e. 2:3 aspect ratio) and PS reads the second of the two orientation tags.
Unfortunately, other programs, like PS Album, just read the first of the orientation tags (and why not?) which is the original "rotate -90" one, and act on that, causing it to rotate an already rotated file.
There’s a workaround, which is to go into File Info and delete the old orientation entry in the TIFF section, but without scripting (and I have no idea if it can be scripted) this is not practical if you have hundreds of photos.
Thanks Chris. On the workaround front, someone on the PSA forum suggested recording an action, and it does seem to work… just record the deletion of the Orientation tag followed by a OK in the file info dialog . This deletes the first version of the tag in the case where there are duplicate tags (even though it’s the *second* tag whose value is displayed in the UI, hmmmm…), and lets PSA see the modified second (now only) one.
In more weird Photoshop behavior, though… say you do this for an image whose (only) orientation tag has the value 8 (lower left). Delete the tag from the TIFF info, click OK in the File Info dialog, then re-open it the dialog. It looks as though the tag has been restored with the original value, 8. BUT… Save the image itself then re-open File Info, and you see that the tag was indeed deleted, and has been recreated with the default value of 1 (upper left).
Thanks to Fred and Peter. Peter wrote: "Since the small crop adjustment double-arrows only seem to disappear when the edges of the bounding box *exactly* coincide with the edges of the window, maybe the best solution is to leave a one-pixel gap when you first create the crop box" … I found this to be a nice workaround, it’s easy to familiarize with, and I did a lot of work today this way. Thanks again. Andrea.
I don’t see this problem mentioned anywhere else, but it’s beginning to seriously detract from my work. What happens is that say 70% of the time when I start CS, the flash/logo screen appears, the CS workspace loads and the the Browser appears to attempt to open. I get the Browser frame, but inside the frame all I see is part of that flash/logo screen. And, if another app or screen was up on my desktop at the time I started PS, part of that displays in there, too.
The Browser will not allow navigating to a folder and cannot be closed. I have to use the menu to start another Browser, close it and re-start Photoshop. This happens both when I left the Browser open when I last exited PS and sometimes even after I have made darn certain I closed the Browser before exiting.
Other times, the Browser opens in a usable manner, but in full-screen mode although I either minimized or closed the Browser at last exit.
At first it seemed that this only happened the first time I started PS after booting the machine, and then only if something else was already up on the desktop. But, alas, an afternoon spent trying to consistently reproduce the problem was a bust. My scientific conclusion is that it does it when it feels like it. But I sure wish it wouldn’t.
System is W2K, SP4, AMD 2800+, 1.5 g RAM, 4 80 gig maxtor harddrives, Matrox G550… Photoshop has it’s own swap drive (38g) and 66% of memory allocated. Installed and activated Photoshop CS on 19 Feb.
A clean system with only ZoneAlarm Pro and Symantec NAV running, broadband internet connection. Antivirus def. up to date and am sure no viruses, worms, etc. are present. This machine (ABIT-nF7S motherboard)is new this year, and I’ve seen no problems with system errors. Periodic inspection of the system log files with event viewer show no recorded problems, either.
This morning I got an error that I hadn’t seen before. I had been working on a folder of tif files (about 110 files, 3.6 gig worth, 16-bit tifs), mostly from within Filebrowser, previewing some, opening some by double-clicking to look at further in Photoshop. Deleting some. All developed from Canon RAW files, some with ACR 2.1, some with PhaseOne DSLR, but all had been worked on in Photoshop CS.
A dialog appeared that my "configuration file is invalid/missing, uninstall and reinstall CS" or something to that effect. I dismissed Photoshop and reopened it and was able to proceed without seeing the error. My name and serial number were in the about box, so I assume this was a transitory error, but it was really worrisome. It would appear to have been a problem with the interaction between CS and the Filebrowser and/or perhaps Adobelsmcv.exe?
You’re totally correct. I saw this problem crop up and went "poor guy" and next day whap!!!!!!!!! same thing but not able to repro. Had to wait the proverbial XXX seconds so that PSCS decides it’s time to let me work and then as yourself clicked the browser button and it sorted itself out.
I work on PS ALL day and the evening comes I have to start-up again ‘cos re-draw and all pre-sets die a death. Sometimes I get a white screen for about 1.5 minutes before anything happens. Today my prefs got trashed and the message my memory and scratches were set to the same volume. Well I saw that when I bought it. I don’t expect to see it in 3 months time but there you go.
No!! PSCS really does need a revamp but nobody wants to own up that his department has screwed. It seems there’s more than passing the buck. The buck can’t even get passed by PS let alone loaded to work on LOL!
Steve, get over it as they all say, there’ll be a fix for the fix for the fix for the …………….. LOL!
Here’s a File Browser bug, not criitcal but disconcerting. I mentioned it in an earlier post when I first discovered the Edit History was missing from an image, while the History in File Info was intact. I couldn’t figure out what had happened with the file.
I later discovered that wasn’t the only file with Edit History not showing, or only partially showing. The instances I looked at were duplicates, and in some instances, the duplicated files showed the Edit History and the originals didn’t, in some cases it was missing in all the copies of the file, and in some cases it was the original which kept the information intact.
I sent one file that showed no Edit History to me to a tech friend who managed to view some of the Edit History, but it kept disappearing. The XML looked to be fine to him, so he thought it might be a problem with the File Browser itself. When he changed the size of the pane that holds Edit History, he sometimes got it all back.
I’ve since replicated this on a great number of files. Why some will show up fine at a given pane width, while their duplicate will show nothing until I widen the pane, appearing the same as when there IS no Edit History with an image, I don’t know. But I can make any file lose the ability to indicate there is an Edit History log simply by narrowing the pane to about halfway into the text, then clicking on another file to see its History. Widening brings it all back, at least so far on my machine, but it does have to be as wide, at least, as the last letter of the widest line.
Under "automate" then "web photo gallery", in p.s. cs i am unable to resize the "large images" under "options" above "450 pixels". this is the same setting level that i get if i select "large" instead of "custom". In p.s.7 i was able to select large custom size photos, say 800. this would resize my images to 800 x 600.
so the "bug" the custom won’t go over 450 pixels like the large setting.
hope you can fix this. i am usually taking large image size photos, above 1meg each and then i need to email or post a copy of them. i don’t really need to make web pages but this works good for batch resizing images.
As reported elsware, my ‘Save As’ isn’t fully functional. When I ‘save as’ a different extension (TIFF to PSD, in my case), I simply get a message asking if I would like to replace the existing TIFF file. If I do so, I still have a TIFF file. Of course the work-around is ridiculously easy (type in ‘.psd’) but I thought if this were a bug, bringing it to your attention would be worthwhile. By the way, I find the functionality of CS (vs PS 6) to be perfectly astounding…as an artist, the difference its made to my final product is greatly appreciated.
A minor complaint to keep the complaints department in business seeing as Grass Hopper is doing his best to keep this thread alive and well.
I imagine this is an oversight rather than intended behaviour. In the old days of PS6 (I haven’t got 7 to compare) Layers and Hue/Saturation dialog boxes (adjustments and adjustment layers) would default to a number field so you could type in the numbers and tab to the next field without having to move the mouse and find the dialog box to enter a field. Now there is no active field, the default is the OK button and the tab order means you have to hit tab several times to get to a number field. I know it’s minor but I would love to see it changed back.
I think it’s important to keep this thread up near the top so that all "bug" complaints can be kept in one place. It’s a heck of a lot easier to find them if they exist in one thread!
In my case (XP Pro on an Athlon XP 1700+) CS ALWAYS produces this problem:
I open a 48-bit TIFF, add adjustment layers (levels, curves, hue/saturation) and save as PSD. WHATEVER the settings for "Optimize Compatibility", I always get a full-res composite, and thus double file size.
Some workarounds were suggested on these forums. None work. When using a 24-bit image, everything is fine.
Any ideas? I would like to have manageable file sizes…
and that’s exactly where it came from! I was learning web design from a "Master" and he dubbed me, the student, Grasshopper. The name has stuck since then 🙂 I *still* can’t get that pebble …
I’m not a stupid beginner crying for help. I *do* get a full-res composite. The 48-bit TIFF is 58 Megs. When saving the PSD, CS says "generating full-res composite", and file size goes to 107 Megs or something. If I don’t use any layers, it stays at 57 Megs.
This is regardless of the compatibility setting, whether on, off or ask. When asked, regardless of whether I leave it checked or not.
Thanks for pointing me to the other treads, Mick. But the workarounds (resaving, having PS ask for the compatibility) don’t work for me WHEN using 48-bit files. Anybody have an alternative?
Learn how to optimize Photoshop for maximum speed, troubleshoot common issues, and keep your projects organized so that you can work faster than ever before!
Related Discussion Topics
Nice and short text about related topics in discussion sections
