ACR Problem

I'm using ACR 8.1, Photoshop CS6. After making all adjustments to a RAW file, I open the Workflow Options dialog box to resize the photo, but no alternative sizes are available in the drop down menu, only the default size (in this case, 16.1 MB for a Nikon NEF). Any ideas?

Click on the Resize to Fit button of the Image Sizing box and click on the arrows at the end of the button to bring up a pop-up menu where you can choose the parameters, then type in the desired values in the fields below that button (which are covered by the pop-up menu inn the screen shot):
Wouldn't hurt to read the Help files and other documentation or watch video tuts on Adobe TV to find out what's new.

Similar Messages

Any way of finding out how Apple will solve the Aperture / ACR problem?

Has anyone out there gotten any comments from Apple support or other people "in the know" about how Apple is going to solve the Aperture / ACR problem, and any potential time frame?
Of course, Apple is going to work on problems with its own RAW conversion; that goes without saying. But does anyone have any knowledge of whether Apple is going to open up the ability for Apple to send RAW, unconverted images to Photoshop, so that ACR can handle them?
I think knowing this now is pretty crucial. I am willing to live with the pain Aperture is going to impose on my workflow, in exchange for the file organization benefits it provides, IF I know that I'll be able to use Aperture with ACR soon (near term). But if Apple is going to just tinker with the RAW converter, and not attempt to send RAW files to ACR, then as someone else posted in another topic, this could be a long wait, and other companies have taken years to hone their RAW converters.
This is kind of my last-ditch effort to keep Aperture around, and build my workflow around it. If I know that within a month or two at the most, I'll be able to be using ACR directly when editing new versions, then I'll absorb the pain until then. But if I am looking at waiting six months for it (several man years), or riding out the process of Apple trying to get their own converter fixed, then as much as I don't want to, Aperture is going to get returned or hit eBay.
Does anyone have any idea on this? I've held up my projects for the past week trying to reorganize my workflow to work with Aperture, and I've got to pound the gavel, make a decision, and pursue a direction. Knowing what direction Apple is going to take with this makes all the difference in the world in what I do.
Thanks in advance for any info you can pass on.
Brad
Powerbook G4-1.33GHz-17" / Powermac G4-1.4GHz Mac OS X (10.4.2) PB: 1GB RAM, Radeon 9600-64MB / PM: 1.25GB RAM, Radeon 9000Pro-128MB

This "Open External Editor from Master NEF", versus open from a dynamicaly created version is, I have decided, crucial.
I am getting less clumsy with the interface, but I simply can not get all white balance, and noise reduction done on my best available light shots.
ACR in CS2, and a subsequent "Neat Image" scrubbing is excellent for this.
The automatic association within a stack, of the resulting flattened file would be a big difference. I agree a formal statement from Apple would make me more inclined to really commit to Aperture for all my work.
Going one step further, it would be nice to keep the layers on the round-trip Master file, even if you would work with a dynamicaly created version of the returned "master" within a stack. It would occupy more disk space, but would do so only for those images where the user has made a quality decision.
Michael
Powermac G5 dual 2GHZ, 2.5GB - 2x20in Mac OS X (10.3.4)

Full screen ACR problem

I open the ACR window on my primary monitor, but as soon as I push the fullscreen button at the top of the ACR window, the ACR window goes fullscreen AND goes to my secondary monitor! I have nview (nvidia) deactivated for Photoshop, so that can`t be interfering, I guess.
Any solutions?
Stefan

This probably isn't the right place to make this comment, but I'm going to do it anyway. I have upgraded to CS3, and generally speaking I like it. Camera Raw has a lot of nice new features, and Photoshop itself has some good improvements. Generally speaking, everything works reasonably well on my antiquated (1.6 GHz processor, 1 GB RAM) system.
However, it seems that every time a new version is released the whole program is becoming more clunky. Bridge sometimes will not update previews, and sometimes won't even start without rebooting my computer. Sometimes Camera Raw will take and process my JPEG and tiff images, and sometimes it won't. If this was still the beta version I would understand having problems like this. I used the beta hoping that some of the issues I was encountering would go away. Some did and some didn't. The problems might get fixed sometime, but historically most (not all, but most) fixes don't show up until the next release. Upgrades are costly. It seems to me that a released new version should perform without problems. I purchased Photoshop version 4, 6, 7, and am now on my third release on the CS series. The early versions did not seem to have a lot of problems. In fact, up to version 7, I didn't even worry about the one patch that was released for some of them because I wasn't having any problems with the programs.
I appreciate all the efforts Adobe goes to trying to provide new features and improvements to old ones. But upgrading isn't solving the irritations that I am constantly faced with. I'm glad I have CS3. I use it exclusively, even though I have not yet removed CS2. However, in light of the frustrations I'm still facing, it is highly unlikely that I will ever bother to upgrade again. I'm able to accomplish what I need with what I have now. Maybe it's my old computer causing the problems. But it doesn't seem likely that upgrading again next time would be of any value. I feel like the upgrades are mostly paying for the attempt to fix problems that seem to be ongoing.

D200 white balance presets problem or ACR problem?

Last night I was playing around with my D200 and an SB800. The scene was just a sofa with a Gretag-Macbeth 24 Patch Color Checker. The object was to see what results I got with the SB800 with the D200 set to the various preset White balance values. (I should point out that the lighting was mixed, but that is not relevant to the results I see.)
I set the D200 to each of the preset white balance values and then opened the NEF file in ACR. The preset temperature (from the D200 Manual) and the temperature/tint values reported as "As shot' by ACR are shown in the table below.
D200 ACR 'as shot'
preset temperature/tint
tungsten 3000 2950 / 0
fluorescent 4200 3950 / +31
daylight 5200 4950 / -3
flash 5400 6150 / -9
cloudy 6000 5550 / -7
shade 8000 7100 / +3
First of all I don't care if the temperature reported by ACR agrees with the preset temperature quoted by Nikon. What puzzles me is the discontinuity in the values reported by ACR when going from 'flash' to 'cloudy'. Is this a problem with ACR or with the Nikon preset values for these two settings?

>First of all I don't care if the temperature reported by ACR agrees with the preset temperature quoted by Nikon. What puzzles me is the discontinuity in the values reported by ACR when going from 'flash' to 'cloudy'. Is this a problem with ACR or with the Nikon preset values for these two settings?
Bob,
A full answer to your question would require a response by Thomas Knoll or some other ACR expert with knowledge of how Nikon records the white balance and the algorithm used to apply the white balance. However, I can bring up a few points which may shed some light on the matter.
One should first consider what white balance information Nikon cameras write to the NEF file. The following table refers to the D70 and similar Nikon cameras before encryption of the WB.
http://www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
The settings of daylight, flash, tungsten, etc are written as descriptive strings, not actual degrees Kelvin. Nikon considers daylight to be 5200K, but Thom Hogan writes that this value often produces a blue result and 5400K might be better.
The bias value refers to fine tuning between the above descriptive settings, approximately 100 Mired per increment. Finally, the red and blue coefficients are recorded (green would be redundant). Some raw converters such as DCRaw use these coefficients for the "as set" white balance. There is nothing corresponding to the ACR tint, which adjusts in the magenta green axis, whereas the color temperature slider adjusts in the yellow-blue axis. The degrees Kelvin figure specifies the white balance only for a black body radiator.
Thus there several ways to interpret the WB data. Mr. Knoll has written previously that ACR attempts to produce a neutral white balance appearance rather than the WB numbers. An interesting experiment would be to determine which converter (ACR or Nikon Capture) gives a more neutral white balance on your color checker with the above settings.
Bill
http://www.adobeforums.com/cgi-bin/webx/.3bbc87b2/0

Bridge or ACR problem?

Hi, few days ago I started to have a problem with either Bridge or ACR. I open a raw file in ACR and save it as jpg with no settings changed, when I open the jpg (through ACR) it would increase the contrast to +23, change the the shadows and curves always to the same amount. So it is as if whatever I do, upon closing/saving the file it applies same correction wich is visible in the Bridge preview. I have reinstalled the CS6, updated ACR not luck. Its driving my mad, please help!

Heres a visual sample of what happens when converting raw without changing anything. Very veird, please help!

ACR problems with elements 11

I'm new to the forums so not quite sure how to begin, but here goes.
Recently bought and loaded PSE11. Everything loaded fine except for Camera Raw. No evidence that ACR ever loaded. Went to update and it downloaded and updated to 7.4 (so it said), however when go to “help”, “about plug-ins” it’s not there (also when try to open a Nikon NEF from an old D200 it won’t even show in the files list). Uninstalled and reinstalled, updated raw again and still not there. Here’s my system info from "help".
Have elements 10 with acr and it works fine but need newer version for my newer camera.
Thanks!
Adobe Photoshop Elements Version: 11.0 (11.0 (20120830.r.32025)) x32
Operating System: Windows XP 32-bit
Version: 5.1 Service Pack 3
System architecture: AMD CPU Family:6, Model:10, Stepping:0 with MMX, SSE Integer, SSE FP
Physical processor count: 1
Processor speed: 2199 MHz
Built-in memory: 1983 MB
Free memory: 1514 MB
Memory available to Photoshop Elements: 1542 MB
Memory used by Photoshop Elements: 86 %
Image tile size: 132K
Image cache levels: 6
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 768, right: 1024
Video Card Number: 1
Video Card: VIA/S3G UniChrome IGP
Driver Version: 6.14.10.0194-16.94.42.03
Driver Date: 20041208040858.000000-000
Video Card Driver: vtdisp.dll
Video Mode: 1024 x 768 x 4294967296 colors
Video Card Caption: VIA/S3G UniChrome IGP
Video Card Memory: 64 MB
Application folder: C:\Program Files\Adobe\Photoshop Elements 11\
Temporary file path: C:\DOCUME~1\ANDYNI~1\LOCALS~1\Temp\
Photoshop Elements scratch has async I/O enabled
Scratch volume(s):
C:\, 122.2G, 74.6G free
Required Plug-ins folder: C:\Program Files\Adobe\Photoshop Elements 11\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Photoshop Elements 11\Plug-Ins\
Additional Plug-ins folder: not set
Installed components:
   ACE.dll ACE 2011/03/29-16:11:44 63.457850   63.457850
   adbeape.dll   Adobe APE 2011/01/17-12:03:36 64.452786   64.452786
   AdobeLinguistic.dll   Adobe Linguisitc Library   5.0.0
   AdobeOwl.dll   Adobe Owl 2012/06/20-18:39:56 4.1.9   78.509892
   AdobeOwlCanvas.dll   Adobe Owl Canvas   3.0.68   61.2954
   AdobePDFL.dll   PDFL 2011/03/29-16:11:44 63.378681   63.378681
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
   AdobeXMP.dll   Adobe XMP Core 2010/10/12-08:45:30   63.139439   63.139439
   AdobeXMPFiles.dll   Adobe XMP Files 5.0   61.134777
   adobe_caps.dll   Adobe CAPS 4,0,42,0
   Adobe_OOBE_Launcher.dll   Adobe OOBE Launcher   2.2.0.4 (BuildVersion: 2.2; BuildDate: Wed Apr 27 2011 21:49:00)   1.000000
   AGM.dll AGM 2011/03/29-16:11:44 63.457850   63.457850
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   1.486530
   aif_ogl.dll   AIF   3.0   1.486530
   amtlib.dll   AMTLib   4.2.0.4 (BuildVersion: 4.2; BuildDate: Wed Apr 27 2011 21:49:00)   1.000000
   amtservices.dll   AMTServices   4.2.0.4 (BuildVersion: 4.2; BuildDate: Wed Apr 27 2011 21:49:00)   1.000000
   ARE.dll ARE 2011/03/29-16:11:44 63.457850   63.457850
   asneu.dll    AsnEndUser Dynamic Link Library   1, 7, 0, 1
   AXE8SharedExpat.dll   AXE8SharedExpat   3.3   49.279053
   AXEDOMCore.dll   AXEDOMCore   3.3   49.279053
   AXSLE.dll AXSLE   3.3   49.279053
   Bib.dll BIB 2011/03/29-16:11:44 63.457850   63.457850
   BIBUtils.dll   BIBUtils 2011/03/29-16:11:44 63.457850   63.457850
   boost_threads.dll   DVA Product   5.0.0
   cg.dll NVIDIA Cg Runtime   2.0.0015
   cgGL.dll NVIDIA Cg Runtime   2.0.0015
   CoolType.dll   CoolType 2011/03/29-16:11:44 63.457850   63.457850
   data_flow.dll   AIF   3.0   1.486530
   dvaadameve.dll   DVA Product   5.0.0
   dvacore.dll   DVA Product   5.0.0
   dvaui.dll DVA Product   5.0.0
   ems.dll Elements Organizer   11.0
   ExtendScript.dll   ExtendScript 2010/03/05-08:21:15   61.423205   61.423205
   FaceDetector.dll   FaceDetector 0000/00/00-00:00:00   2.0.1.1   2.0.1.1
   FileInfo.dll   Adobe XMP FileInfo 5.0   61.134777
   filter_graph.dll   AIF   3.0   1.486530
   hydra_filters.dll   AIF   3.0   1.486530
   icucnv36.dll   International Components for Unicode 2009/06/17-13:21:03    Build gtlib_main.9896
   icudt36.dll   International Components for Unicode 2009/06/17-13:21:03    Build gtlib_main.9896
   image_compiler.dll   AIF 3.0   1.486530
   image_flow.dll   AIF   3.0   1.486530
   image_runtime.dll   AIF   3.0   1.486530
   JP2KLib.dll   JP2KLib 2011/03/29-16:11:44 63.196876   63.196876
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler 10.0
   LogSession.dll   LogSession 2.1.2.1640
   MPS.dll MPS 2011/05/24-09:45:42 63.464027   63.464027
   MSVCP100.dll   Microsoft® Visual Studio® 2010 10.00.30319.1
   MSVCP71.dll   Microsoft® Visual Studio .NET 7.10.3077.0
   MSVCR100.dll   Microsoft® Visual Studio® 2010 10.00.30319.1
   MSVCR71.dll   Microsoft® Visual Studio .NET 7.10.3052.4
   pdfsettings.dll   Adobe PDFSettings 1.04
   Photoshop.dll   Adobe Photoshop Elements Editor   11.0
   platform.DLL   Adobe Help System   1, 0, 0, 1
   Plugin.dll   Adobe Photoshop Elements Editor   11.0
   PSArt.dll Adobe Photoshop Elements Editor 11.0
   PSViews.dll   Adobe Photoshop Elements Editor   11.0
   ScCore.dll   ScCore 2010/03/05-08:21:15 61.423205   61.423205
   shfolder.dll   Microsoft(R) Windows (R) 2000 Operating System   5.50.4027.300
   Tbb.dll Intel(R) Threading Building Blocks for Windows   2, 2, 2009, 1011
   updaternotifications.dll Adobe Updater Notifications Library 2.0.0.15 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   2.0.0.15
   WRServices.dll   WRServices Thursday January 21 2010 12:13:3   Build 0.11423   0.11423
Required plug-ins:
   Accented Edges 12.0
   ADM 3.11x01
   Angled Strokes 12.0
   Auto Divide 11.0.0.0 (11.0 (20120830.r.32025))
   Average 12.0.2
   Bas Relief 12.0
   BMP 12.0.2
   Chalk & Charcoal 12.0
   Charcoal 12.0
   Chrome 12.0
   Clouds 12.0.2
   Color Halftone 12.0.2
   Color Variations 12.0.4 (12.0.4x001)
   Colored Pencil 12.0
   CompuServe GIF 12.0.2
   Conté Crayon 12.0
   Correct Camera Distortion 12.0.2
   Craquelure 12.0
   Crop and Straighten Photos Filter 12.0.2
   Crosshatch 12.0
   Crystallize 12.0.2
   Cutout 12.0
   Dark Strokes 12.0
   Difference Clouds 12.0.2
   Diffuse Glow 12.0
   Displace 12.0.2
   Dry Brush 12.0
   Extrude 12.0.2
   FastCore Routines 12.0.4 (12.0.4x001)
   Fibers 12.0.2
   Film Grain 12.0
   Filter Gallery 12.0
   Fresco 12.0
   Glass 12.0
Glowing Edges 12.0
   Grain 12.0
   Graphic Pen 12.0
   Halftone Pattern 12.0
   Ink Outlines 12.0
   Lens Blur 12.0
   Lens Flare 12.0.2
   Lighting Effects 12.0.4 (12.0.4x001)
   Liquify 12.0.1
   Matlab Operation 12.0.4 (12.0.4x001)
   Mezzotint 12.0.2
   MMXCore Routines 12.0.4 (12.0.4x001)
   Mosaic Tiles 12.0
   Multiprocessor Support 12.0.4 (12.0.4x001)
   Neon Glow 12.0
   Note Paper 12.0
   Ocean Ripple 12.0
   OnEdge 1, 0, 0, 1
   Paint Daubs 12.0
   Palette Knife 12.0
   Patchwork 12.0
   Photocopy 12.0
   Picture Package Filter 12.0.4 (12.0.4x001)
   Pinch 12.0.2
   Pixar 12.0.4 (12.0.4x001)
   Plaster 12.0
   Plastic Wrap 12.0
   PNG 12.0.2
   Pointillize 12.0.2
   Polar Coordinates 12.0.2
   Polar Coordinates 12.0.4 (12.0.4x001)
   Poster Edges 12.0
   Radial Blur 12.0.2
   Read Watermark 4.0
   Reticulation 12.0
   Ripple 12.0.2
   Rough Pastels 12.0
   Save for Web & Devices 12.0
   ScriptingSupport 12.0.4
   Shear 12.0.2
   Smart Blur 12.0.2
   Smudge Stick 12.0
   Solarize 12.0.2
   Spatter 12.0
   Spherize 12.0.2
   Sponge 12.0
   Sprayed Strokes 12.0
   Stained Glass 12.0
   Stamp 12.0
   Straighten and Crop Image 12.0.4 (12.0.4x001)
   Straighten Image 12.0.4 (12.0.4x001)
   Sumi-e 12.0
   Texture Fill 12.0.4 (12.0.4x001)
   TextureSelect 12.0.4 (12.0.4x001)
   Texturizer 12.0
   Tiles 12.0.2
   Torn Edges 12.0
   Twirl 12.0.2
   Underpainting 12.0
   Water Paper 12.0
   Watercolor 12.0
   Wave 12.0.2
   WIA Support 12.0.4 (12.0.4x001)
   Wind 12.0.2
   ZigZag 12.0.2
Optional and third party plug-ins:
   Frame From Video 6.0
   Magic Extractor 12.0.4 (12.0.4x001)
   PhotomergeUI 12.0.4 (12.0.4x001)
Plug-ins that failed to load: NONE
Installed TWAIN devices: NONE

Actually, I can’t update raw in pse10 either…and the other odd thing is when I download and install DNG converter it seems to install just fine but then gives an error message when I attempt to run it. Must be the AMD processor, I know there are some other photo programs that don’t run under AMD (Photoshop CS series included). Really too bad…Elements 11 isn’t much good to me unless I can process NEFs from the D5100. Guess I’m stuck with Nikon Capture (or View), making a 16 bit TIFF and loading that into pse11. Kind of a clumsy work around.
Andy Nielsen
Please note: message attached

Lightroom to Photoshop questions and ACR problems

I have Lightroom 5 and Photoshop CS5.
I've been working between the two with no problem until recently.
When i move a photo from LR to PS5:
1. I get the message that "This version of LR may require Camera Raw Plug in version 8.5 for full compatibility. Please update...."
When i go into PS it says no updates available.
2.When I move the photo anyway from LR to PS5 the file is blurry. Slightly off definitely not the same.
Help
Thanks

Anyhow: Please look here: Re: Photos from Lightroom 5 to Photoshop CC (2014) and back...

CS4 ACR problem

Received and installed CS4 tonite. Disc wouldn't open automatically, so I had to copy to the desktop and install from there! Oh, well, that went, OK, I think.
When in Bridge, trying to enter Camera Raw Preferences, or clicking on the round 'open in ACR' icon(for a jpg OR a RAW image), or double clicking on a jpg, I get an error message, saying:
"Camera Raw editing is not enabled. Camera Raw editing requires that a qualifying product has been launched at least once to enable this feature."
When I double click on a RAW image, Camera Raw 5 opens normally.
Any ideas??
Thanks,
Barry

Hi Barry,
Please Launch Photoshop CS4 once. Now through Photoshop , launch Bridge.
Thereafter on clicking the "Camera Raw Preferences", you will not get the message "Camera Raw editing is not enabled. Camera Raw editing requires that a qualifying product has been launched at least once to enable this feature."
The Creative Suite Management will give the same message as it gets launched only when you have a Creative Suite CS4 on your machine.

Previewing 5D Mark II RAW files in CS4 Bridge

I have just updated to the 5.7 version of RAW for my CS4, but I still can't preview them in Bridge. Any suggestions or remedies? Please HELP!!

From the list http://kb2.adobe.com/cps/407/kb407111.html it looks like you need anything above
5.2. So it should work.
Most acr problems are one of 2 items: ACR in wrong folder, or more than one version in the folder. Check download page to see where they should go.

Canon EOS 5D images not displaying in ACR3.7 even in .dng format

If I view the RAW images from my Canon 5D in Canon Digital Photo Professional, everything looks fine and as expected. But I want to use Photoshop.
I am using CS2, I have downloaded ACR 3.7 and the 4.0 DNG converter. If I convert the RAW images to .dng files and open them with ACR3.7, the colors are off quite a bit and some of the highlights and shadows are clipped. It's so bad that I can't tell what I should edit. If I then click "Open" and import them to Photoshop, I can convert the profile to a profile specific to my LCD display and they look OK. But I have defeated the original purpose of having ACR and being able to directly edit in RAW format.
Question: Is this an ACR problem and should I upgrade to CS3 and ACR4.0? I thought DNG 4.0 was a workaround to get ACR 3.7 to support the same list of cameras as ACR 4.0. Or is this just a problem with my display? Remember that Canon DPP doesn't have a problem.
Thanks.

> I found the problem. I went into the Windows settings for my display adapter and associated the sRGB-IEC61966-2.1 profile to my display. Everything works now. The old profile assigned to the display was the problem.
I don't believe this would be the right thing to do. The monitor profile that should be associated with "desktop properties" should be the monitor profile created with Adobe Gamma applet, or a profile created with a 3rd-party profiler (e.g., Colorvision+Spyder).
In any case, SRGB is
not a monitor profile ... it is a color space which is intended to match
"most" monitors.
Edit: Which naturally begs the question as to how the profile associated with your monitor got there, or how you calibrated your monitor?
HTH :)

Lastest camera raw update doesn't work. Bridge no longer recognises my raw files.

I'm using CS 6 and lastest camera raw update doesn't work. Bridge no longer recognises my raw files.

Let's see if I can simplify it for you...are you using CS6 (yes, it seems), are you having ACR problems (yess it seems). So, do you want to fix your issues? Then read this (pay close attention to the details)...
http://helpx.adobe.com/bridge/kb/acr-84-bridge-cs6-metadata.html
It pretty much says you need to download a different version of ACR and install it (if it's not too diffucult for you to understand) to get ACR & Bridge to work properly...or not. Your choice...

HELP. ............Hi folks hope some one can help me please.Having a problem in Bridge I open my images in ACR, as I open files in a folder and lets say they are labeled in yellow they are all going back to the camera raw default , in other words no ma

HELP. ............Hi folks hope some one can help me please.Having a problem in Bridge I open my images in ACR, as I open files in a folder and lets say they are labeled in yellow they are all going back to the camera raw default , in other words no matter what work I have done, inc cropping they all go back to ,as they came out of camera. What on earth is happening? I am on PS CS6. I might point out everything was working normally up to yesterday, when this first started.
I recently changed computer to 64bit from 32bit, not sure if this causing the problem or not. Any help would be appreciated.

Robert,
Would you be so kind to rephrase your question with concise, precise information and without any "let's say that" hypotheticals? Sorry, I can't quite follow you.
Also please give exact versions of Photoshop CS6 (13.what.what), of Bridge and of your OS.
Thanks.
BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand, such as your platform (Mac or Win), exact versions of your OS, of Photoshop and of Bridge, machine specs, what troubleshooting steps you have taken so far, what error message(s) you receive, if having issues opening raw files also the exact camera make and model that generated them, etc., someone may be able to help you.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

Problems viewing RAW photos properly in Photoshop/Lightroom/ACR

Hey folks. New here and looking to find some assistance with a problem I'm having in Photoshop CS4, Lightroom 2 and Adobe Camera Raw 5.7 when attemtping to view RAW photos straight from my Canon 450D. My computer is a Mac PowerPC G5 running OS X 10.5.8 with a single 1.8Ghz CPU and 3.5Gb of RAM. Photoshop CS4 is version 11.0.2. Lightroom is version 2.7. Adobe Camera Raw is version 5.7.
What I am having problems with is viewing RAW photos from my camera in all of these applications. No problems are encountered with any other file type such as PNG or jpg.
I have attached a screen capture of what I am seeing when I open a .CR2 RAW image in Camera RAW before opening in Photoshop. As you can see, the software seems to be having a difficult time rendering the photo properly. I can view these files on other computers using the Canon software that came with my camera. I get this same problem if I view the image in Lightroom.
As far as I know, I can't upgrade to PS CS5 or LR 3 because I am still running on the PPC architecture, so I need to find how to fix this without having to buy a Mac Pro and the newest software.
Any ideas on how to troubleshoot? If the screenshot is too small, I can provide the full-res version.

I'm well-versed in forum ettiquette, thank you. I do, however, see no problem why posting about this problem once in each forum covering the software involved in my problem would be an issue. If I posted about the problem in only one forum, let's say in the Lightroom forum, and the problem was experience by another person who did not use Lightroom and would not be browsing the Lightroom forum for help, how would they have come across this post? Unless they also looked in the Photoshop forum, they might not have seen this post. So where's the harm in having it viewed by a greater number of individuals?
With that aside, my problem is now resolved. After looking around a bit more on the forums here last night, I came across a thread started by a fellow who was experiencing the same issue as I, except he had newer versions of the software. Someone had replied to his post suggesting that it could have been faulty RAM modules and that they once experienced similar issues which were resovled by replacing the RAM. This was good news to me, since I had just purchased additional RAM for my Mac last week. It arrived today and I installed it and booted the Mac up. I purged any cache files used by these three software titles and then reattempted opening a RAW image in Photoshop. I took my latest RAW images from my camera, exported them to a USB thumb drive, and then from there exported them to my Mac. I tried to open on of the images in Photoshop and it opened successfully with ACR along with a complete and pristine preview of the image. Open the other RAW images in Lightroom, no problems.

Problem with ACR 4.2 in Bridge

After updating to ACR 4.2, I can no longer open RAW (or DNG) files in
Bridge. The files always open in Photoshop. Could I have done something
wrong?

Thanks for the help. I was the cache. I tried purging from "Edit -> Camera Raw Preferences...", and that didn't fix it. Then, I tried deleting the files manually (I must have missed some), and that didn't work. Finally, I purged from "Edit -> Preferences -> Cache" and everything works! Thanks again! - Jeff <[email protected]> wrote in message news:[email protected].. > Jeff > > You should read the part about ACR install on Windows, I Use Mac and can't > tell you where to put it but it is a very critical install, Not difficult > but you have the follow the instructions carefully and then it will work. > > Bridge 2 has a different cache management with it's own problems, there > are many treads about that in the Bridge forum. However, it does work! > > You should go to the Bridge preferences and check the box with > "Automatically Export Caches to Folder When Possible." > > Remember that the files are by default invisible, in the menu go to View > and select "show hidden files". If your cache is written to the folder > there should be 2 files (blank paper with above right corner folded) and > named: > .BridgeCache and > .BridgeCacheT

Problem with JPGs Downlaoded with Nikon Transfer - Can't Apply Develop Settings in Bridge CS4 and ACR 5.3 Settings Don't Stick

I have found what I believe is a "problem" with JPGs downloaded using Nikon Transfer (ver 1.4.1) and processing same in Adobe Bridge CS4 (Develop Settings) and/or Adobe Camera Raw 5.3 (Photoshop CS4 and Elements 6 as hosts).
Anyone using these programs in their workflow?
The problem, quite simply, is that neither ACR settings (nor Bridge CS4 Develop Settings) "stick" when applied to JPGs that have been downloaded via Nikon Transfer ver 1.4.1.
The same images from the same cameras (D300 and D90), downloaded moments later using Nikon's predecessor software PictureProject work just fine in both Bridge and ACR. Develop Settings appled in Bridge immediately are seen, and JPGs opened in ACR, and settings applied, then "Done" immediately stick and are reflected in Bridge.
If someone else is processing their JPGs in this manner, please let me know, as I have reported the problem to both Nikon and Adobe, and although I have tested it on two different cameras and two differnt laptops, I would like to get an impartial result as well.
One other test, the problem does not seem to affect Nikon's RAW (NEF) format files downloaded from a D2x using Nikon Transfer. More/different test are forthcoming.
Thanks
jeff

ALoverofNikon wrote:
I have generally thought that using the camera manufacturer's software was the safest and most conveneint
Can't say one way or another on that statement about using manufacturers' software. Since Adobe has to interpret each camera models' RAW format having the latest ACR seems to be the best option. But if the manufacturers' software is more convenient, and you get the same results then use it. But it does appear you are not getting what you want, so suggest you try a duplicate test run with images straight from the card reader to Bridge and see if you still have same problems.
I do know it is widely recommended that using a quality card reader gives you more reliable data than getting the pictures straight from the camera. Does not seem intuitive, but that has been experience of many.

ACR Problem

Similar Messages

Maybe you are looking for