PDA

View Full Version : acdsee 4.0


oops
3rd of October 2001 (Wed), 20:07
Finally a plug-in for RAW format. I tried to open a small file containing 25 RAW pics and twenty minutes later it was 20% done. Meanwhile my system was "locked up" waiting on my new program to execute.

I decided it would take as long as I took growing up (and I'm really old) to finish and had to do a Ctrl-Alt-Del to stop this whole nonsense.

Ah. Got my computer back so I could send this post. Is this normal? Anybody else have a "warm fuzzy" over the AcdSee treatment of RAW data? If not, I will need to hide my RAW pics in files I never access with AcdSee.

gandini
3rd of October 2001 (Wed), 21:53
oops wrote:
Finally a plug-in for RAW format. I tried to open a small file containing 25 RAW pics and twenty minutes later it was 20% done. Meanwhile my system was "locked up" waiting on my new program to execute.

I decided it would take as long as I took growing up (and I'm really old) to finish and had to do a Ctrl-Alt-Del to stop this whole nonsense.

Ah. Got my computer back so I could send this post. Is this normal? Anybody else have a "warm fuzzy" over the AcdSee treatment of RAW data? If not, I will need to hide my RAW pics in files I never access with AcdSee.

I had heard about this on dpreview, but your experience seems to be extreme!
I think I will stick with BreezeBrowser and keep ACDSee to view and sort/file the TIFFs I convert using BB.
By the way, BB is extremely fast at converting RAW to TIF.
Without doubt, the *fastest* way to get an image into PhotoShop from the camera is: Remove MD from G1, insert into MicroTech USB reader, copy file to harddrive using explorer, open file using BB, convert to TIF, and then open in PS. I'd say that took less than 1.5 minutes, whether for 1 or 5 files.

cheers

Don Ellis
5th of October 2001 (Fri), 00:21
oops wrote:
Anybody else have a "warm fuzzy" over the AcdSee treatment of RAW data? If not, I will need to hide my RAW pics in files I never access with AcdSee.

I had the same interminable problem. Here's the "solution":

1. Go to a file manager program.

2. Shft-Right Click on a CRW file.

3. Associate it with the Canon RAW File Converter.

4. Open ACDSee.

5. It will ask if you know that CRW is associated with another program, and do you want to keep it that way. Uncheck the box and click OK.

5. Now, when you press Enter on a CRW file, the Canon RAW File Converter will appear and you can work with that program.

And that's why I put "solution" in quote marks. It's more of a work-around.

ACDSee 4.0 definitely needs some work. I've supported them from the beginning but this version was kicked out the door too soon. One feature that I liked in the previous versions was the ability to hit Home, Enter and back out of a directory where you could use arrow keys to go to the next directory you wanted. That's now gone and you have to use the mouse with the Folder Tree to select another directory. I wrote to ACDSee and they said there was little chance of bringing this feature back.

The other thing that 4.0 does is overwrite your 3.1 version. Fortunately, I still have 2.43 installed and I find myself using it more and more.

Good luck.

Don

P.S. The best solution to your problem is BreezeBrowser at www.breezesys.com.

oops
5th of October 2001 (Fri), 08:20
I had forgotten about the file association option, thanks. I don't think it will help if I click to open a file in the ACDSee directory tree that happens to contain CRW images, though. ACDSee will still try to display the thumbs for these images on the right and this takes forever.

I suspect (knowing little about the technical issues) that ACDSee is processing each CRW file as it prepares to display all of the thumbs in a given folder rather than using the embedded .jpg or even the G1 .thm that may be present. This means a fast full screen display of the .crw when you are finally able to double click the ACDSee thumb for larger viewing, but makes selecting a file with .crw content a nightmare waiting on the thumbs to load.

I'm with you. I still have a 3.1 cd so that version will go back in and I have BreezeBrowzer 1.1. Between the two I was getting along just fine.

Don Ellis
5th of October 2001 (Fri), 19:02
oops wrote:
I had forgotten about the file association option, thanks. I don't think it will help if I click to open a file in the ACDSee directory tree that happens to contain CRW images, though. ACDSee will still try to display the thumbs for these images on the right and this takes forever.


Hmm...I don't have this problem with 4.0. When I go to a directory with both CRW and THM files, only the THM files display as thumbnails and they do it very quickly.

The problem with ACDSee 3.1 for me is the batch conversion from whatever format to JPG produces files with uppercase extensions -- which I then have to go into ZTree and fix.

oops
5th of October 2001 (Fri), 20:32
You know what, Don, I posted without even trying your suggestion and relied on my past experience.

I will try this tonight and post my apology sometime this weekend.

Damn; just when I thought I was good!:D

oops
7th of October 2001 (Sun), 09:32
I associated my .crw file extensions with BreezeBrowser and verified they had the BB icon showing in Explorer. When I opened ACDSee it warned that .crw was no longer associated with ACDSee. I unchecked the box and continued.

It still tried to load the .crw when I went to my folder containing RAW files. I closed and restarted ACDSee; no luck. I restarted my computer; no luck. I checked Tools>File Associations in ACDSee and the .crw box was still un-checked.

I went to Program Files>ACDSee>Plugins, found the .crw plugin, and disabled it by renaming it's .apl extension to something else. That did the trick. No more RAW loads. Also, as a bonus, ACDSee will now load the .thm for the RAW files in any given folder so I know the folder contains them and what they are.

I can now play with 4.0 a bit to see if the other bells and whistles are worth saving before going back to 3.1.