Close the file browser.
Otherwise it’ll keep working until it gets the higher quality preview (not huge ones like the "high quality preview" option) calculated. The initial thumbnails are just tiny icons, not previews.
Any chance you could respond to the question I asked?
The question is about continuing to process thumbnails, not the HQ preview.
Any chance you could respond to the question I asked?
any chance you can read the response? CLOSING THE BROWSER will stop it from processing thumbnails of ANY quality.
if you want, and what many of us have done, is set high quality previews on, set background processing on, set scan sub folders on and point it at the root of a drive, then go to sleep for the night and let it run. when you get up it’ll be done. no more processing except when adding new files.
Dave, I have done as you suggested in posting #3 and have been using CS for some time in this fashion. I have noticed that if I access a folder which I haven’t looked at in some time the browser starts going through its cache update for that folder, like creating previews, etc.
I thought once this had been done it was permanent. Should it be doing this? I never, intentionally at least, delete a cache.
I am using XP Home edition, 1 GB memory at 70%, a Pentium 2.6 with hyperthreading (with the updated dual processor patch) and a single disc drive with >80 GB free space. Settings in CS are default for cache and most others.
I thought once this had been done it was permanent.
it is. it’s probably not completely done. do yourself a favor and let it run over night. it did my family pix folder (several gig) in one night. now there’s never a delay.
I am using XP Home edition, 1 GB memory at 70%, a Pentium 2.6 with hyperthreading
very similar to mine. 2.8c hyperthreading 1 gig pc3200 ram, 400mhz fsb. let it go and do it’s thing. you’ll be much happier. 🙂
if you want, and what many of us have done, is set high quality previews on, set background processing on, set scan sub folders on and point it at the root of a drive, then go to sleep for the night and let it run. when you get up it’ll be done. no more processing except when adding new files.
I Have never had to do this for Photoshop 7 I get the previews fast and and start working and when I move the mouse the browser closes all by it self.
The bright spark at Adobe who designed the CS browser must have woke up with his head screwed on backwards.
Why should I run my computer the whole night to work effiently what sort of logic is that.
I Have never had to do this for Photoshop 7
it’s a new beast. high quality and color managed. that didn’t exist in 7.
Why should I run my computer the whole night to work effiently what sort of logic is that.
ok mister spock. have it your way. there’s klingons off the starboard bow, you know.
"it’s a new beast. high quality and color managed. that didn’t exist in 7. "
Photoshop is supposed to be tailored for the professional by supposed professionals. Colour managed previews and high quality Unnecessary bloat ware and highly inefficient.
excuse me
What is the definition of "browsing" – The action performed when one browses "browse" -To look ,as through files and directories on a computer.
It is very much like the classic movies in the past the content and acting was good and the special effects well not good as far as realism but that was not so important , the story line and good acting was.
The trend now is wow special effects and poor story lines and acting as if the special effect are the important factor in a film.
I live in the real world and have to work as quickly as possible and efficiently to meet my deadlines.
Isn’t that idea of updates and new versions "improvement and efficiency or is it wow special effects bloat ware.
Who the hell needs colour corrected thumbnails or previews
Man I have 140 gigs of hi rez image files across 2 drives shifting data and archiving
I regularly backup my C drive and don’t need to backup hundreds of megs of cache files esp when the files are archived to cd
At least with Photoshop 7 it was the case of getting in and out and start working. Now with CS run your computer overnight to solve the problem excuse me what planet did you say you live on. That is not logical at all just plan stupidity on behave of Adobe. Someone in development lost a few screws in the case of the CS file browser.
" Close the file browser. " well now that is real clever. If Adobe knew the problem exsisted why did they change the tabbed and auto closing function as in Photoshop 7.
I would greatly appeciate an CS update to have the option to change the browsers function back to the way photoshop 7 does it.
"why did they change the tabbed and auto closing function as in Photoshop 7"
Hold down your Alt key when double-clicking on an image to open it. That will close the File Browser.
As for color-managed previews, that’s not as important to me personally, but I’ve come to depend on the high-quality previews. By dragging the panes of the preview window, I can see a high-quality preview almost as large as it will open on screen. Very handy for seeing exactly what I’m gonna see when it opens.
"Different strokes", of course, but I for one appreciate the new capabilities of the FB.
Hold down your Alt key when double-clicking on an image to open it. That will close the File Browser.
An Extra Unnecessary step in the name of imporvement. not logical at all
dude, no one here said it was logical or even that they liked it. we’re simply trying to help. bitching at other users like us who are trying to give answers to questions just makes you sound like an ass. we’ve given you advice on what we’ve done to make it better. if you don’t like the way the browser works, go to the feature request section and make a nice long soul edifying rant there. better yet call adobe, i’m sure they’ll be glad to listen to you.
I note that the ones who rabbit on about being "professional" are usually the ones who are least likely to be so, both in demeanour and fact.
I’m not bitching at any particular user if you would read carefully and between the lines but at Adobes 1 step forward and two step back approach to improvement in the case of CS.
I don’t want a new feature in the browser but the damn thing fixed instead of having to resort to extreme work arounds sugguested here.
It would be very assuring to know if Adobe is reading the posts in the forum and informing us in the forum that they are working on fixes.
Referencing postings 3,4 and 5 with regard to caches being re-updated unnecessarily.
I did a little troubleshooting and found that I have two folders, call them A and B, which seemed to re-create their cache almost every time they are accessed. Then I noticed that this only happened if I accessed folder B after viewing folder A and letting its cache completely update, or vice-versa. Viewing any other folder does not seem to cause this to happen when I come back and look at either A or B.
The first of these folders contains a mixture of camera raw files and jpegs that had been first downloaded into my laptop and viewed with PSCS on it, then transferred to my desktop where I’m seeing the problem. The camera was a Canon Digital Rebel.
The second folder contains only 18 images from the 75 in the first folder which were processed in PSCS on my desktop and saved as jpegs.
All the files in the second folder have different names than in the first folder.
It seems as though viewing one of these folders resets a flag telling the other that its cache is missing or not up to date. The fact that they contain some of the same images seems suspicious.
I did try purging the caches of both, but it did not help.
This is annoying, but not life threatening for me. I thought the information might help you Adobe folks figure out some of the bugs in the browser.
Jerry,
If you change the contents of a folder or even simply change a file within that folder then FB will update the cache. Generally small changes update almost instantly, but larger files (i.e. over 200MB) can slow things down. Since you appear to be moving back and forth between systems then FB will need to update the full cache for the relevant folder (even if nothing has changed). Simply renaming, copying or even moving a folder on the same hard-drive will result in FB rebuilding the cache. That is how FB was designed. That is how likely remain.
For the most part the delays can be overcome by simply Exporting the Cache (an option under the FB File Menu). Once you build a cache for a given folder you need to choose FB File>Export Cache (the folder MUST be highlighted/selected) and this will ensure that a version of the cache file will be written INTO that folder. Have a read through the following thread for more info:
<
http://www.adobeforums.com/cgi-bin/webx?128@@.3bb477c1>
Ian
Ian, the experiment I did involved no changes. I was simply selecting a folder to view, watching it complete the cache update, viewing the second folder, of the A, B pair referenced in posting #15, and then viewing the first folder again – which updated its cache again. If I view the second folder again, it updates its cache also. I opened no images or moved any files in the interim. The browser seems happy to do this as often as I try it.
Note that it appears to be only with these two folders, but I am suspicious that it happens intermittently with others as well.
