Problem in ACR

If in ACR on MAC I click save image and then I choose destination: save in new location the finder window doesnt appear and the buttons save and cancel dont respond at all. The solution is a command-alt-esc and shut down the application. If I create a new user account and I try in the new login all works perfectly. I tried to reinstall all but I havent resolve. Have you esperienced this behavior?
Sorry for my English and thank you
Marco

>but I am a beginner of MAC world.
Hehehe That's pretty obvious. It's Mac, not "MAC". :)
Welcome to the Mac world, Marco! Congratulations.

Similar Messages

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

Problems with ACR

Hi all,
Having a problem with ACR on the photoshop trial.
I'm hitting CMD + Option + 0 to go to 100% and it is doing so, but it is also going to the next picture at the same time. I then have to go back to the previous which is then at 100% as I asked but it has taken me a gazillion seconds to do it. On windows it was much simpler - how do I solve the problem?
Thanks,
Fred

Hudechrome wrote:
I suspect the two are related.
Highly doubtful...in the case of the BSOD, you have a hardware problem somewhere. Could be processor, memory, motherboard or other devices such as video card or driver but software should not be able to bring hardware down like that.
In terms of the DNG profiles, odds are when you rebuilt you didn't re-install the profiles (they were bundled with the DNG Converter). Download DNG Converter 5.6 and run the install.

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

Probleme mit ACR Editor 8.1

Hi,
ich habe bereits im Camera Raw Forum geschrieben (im schlechten englisch,hihi). Nun schreibe ich hier auch nochmal mein Problem, vllt. kann das jemand nachvollziehen und hat das gleiche Problem.
Ich habe Photoshop CS6 als CC Produkt. Dazu habe ich gestern das Update auf Adobe Camera Raw 8.1 gemacht.
Nun habe ich folgendes Problem, vllt. mag das jemand mal ausprobieren
Ich öffne eine PSD Datei. Ich vereine alle Ebenen auf eine Ebene (Strg+Shift+alt+e). Gehe auf den ACR Editor. Ebene wird zum Smart Objekt und das RAW Fenster öffnet sich (TIFF 8.1 steht oben im Fenster).
Nun kann ich etwas ändern, oder auch nicht ändern und klicke auf "Ok".
Jetzt wir das Bild verkleinert in die Ebene gelegt. Ich müßte es wieder hochskalieren, damit es über die bisherigen Ebenen passt. Gleiches passiert auch, wenn ich die Hintergrundebene einfach kopiere und den ACR Editor starte.
Klicke ich in der Bridge auf "Öffnen mit Camera RAW" passiert das übrigens nicht.
In den Einstellungen in Raw ist "In Bildschirm einpassen" nicht angehakt.Haken ist gesetzt bei "In Photoshop als Smartobjekt öffnen".
Hat jemand eine Idee? Der Adobe Support sagte mir, ich könne nur downgraden in dem ich Photoshop neu installiere (ich finde 7.4. nicht zum download ).
Danke & Grüsse

Naja gut,es war so gemeint, das ich CS6 als Creative Cloud Kundin nutze
Ich versuch es mal besser zu beschreiben
Ich öffne ein jpeg in Photoshop CS6. Ich kopiere die Hintergrundebene. Ebene 1 öffne ich über Datei---->Skripten (müßte skripten sein, hab PS grad nicht vor Augen) -->Adobe ACR Editor.
Nun ändere ich beispielsweise Farbtemperatur oder auch gar nichts und klicke auf "ok". Nun sollte die Ebene 1 ja die Hintergrundebene überlagern. Das macht sie auch, aber ca. 30% verkleinert als ursprünglich kopiert.
Klicke ich in Camera Raw auf den blauen Link, sind keine Haken gesetzt bei "In Bildschirm einpassen" und die originale Grösse der Datei wird ebenfalls korrekt angezeigt.
Den alternativen Weg habe ich auch probiert-->Filter Camera RAW - das Problem mit der viel kleineren Ebene bleibt dann aber leider trotzdem bestehen.
Danke

A problem with ACR in Photoshop CS 6 (Mac).

When using "Edit in Photoshop CS6" from Lightroom 4 I just go into Photoshop CS6, not Adobe Camera Raw (ACR). Cannot access ACR directly from withion Photoshop either. It works from Bridge tho'. Have checked out many forums and see other people with this problem, but main help responses, to remove com.adobe.Photoshop.plist from Library/Preferences, or reinstalling Photoshop and Lightroom, do not resolve it for me. All software, including Camera Raw (7.2.0.46) is up to date. Use 16 GB iMac and OS X 10.8.2.
Any help much appreciated.
Peter

Peter Sanderson wrote:
Until a few days ago, when working in Lighroom 4, when I clicked "edit in photoshop", it always opened in Camera RAW, which I found useful. Now it just opens in Photoshop. I cannot figure out why this is happening. [...]
Suspect from my readings on further forums, that the previous mode of opening in Camera Raw may have been a bug, which I had assumed to be the norm!!
Yep, sounds like there was a bug and now you're seeing correct behaviour.
Something that might be useful to you is Lr's "Edit In > Open as Smart Object in Photoshop". That'll open a document in Ps with a SO containing a duplicate of a file. Double-clicking that SO will open its contained file in Camera Raw.

Problem Installing ACR 6.7rc1

I tried to install ACR 6.7 rc1 on my Win7-64 bit system, and the first error I got was the installer told me that "Adobe Application manager is needed to update your product" It is either missing or damaged,- download a ne copy of Adobe Application manager or reinstall the product.
I downloaded the Application manager, and when I ran that, it failed as I got another error message "Installer failed to initialize" Please download Adobe Support Advisor to detect the problem.
So, I downloaded Adobe Support Advisor, and ran it and it told me it could find no problems, contact Adobe support for help, and to create a support package with a unique token number (00-74372-144712032012) to open a support case with Adobe.
I called Adobe technical support, and after talking to 3 individuals, and 2 hang ups with no return calls (they asked for my home number - why??), finally got someone who told me since it's a release candidate, Adobe support cannot help me, I need to post the issue on Adobe forums so it can be factored into the feedback from the community before Adobe officially releases it.
After searching the forums, am I the only one with this install problem??
Hank

Hank, all I can say is that it's a bit hard to read your post through the tears of laughter given the username you chose.
For what it's worth, I didn't have any problem installing the 6.7 RC. You might try running the installer As Administrator, but I don't have a huge amount of hope for that.
The actual plug-in .8bi files are in the package, but they don't have their final names... If you want to get down and dirty with the files you can dig into the download zip file, and you'll find two embedded zip files called Assets2_1.zip. Each of these is in a subfolder that will tell you whether it's the 32 or 64 bit version, and they contain the actual plug-ins (one for 64 bit, one for 32 bit).
On a 64 bit Windows system:
The file named 1002 that's 24,400 KB becomes the 64 bit plug-in: C:\Program Files\Common Files\Adobe\Plug-Ins\CS5\File Formats\Camera Raw.8bi
The file named 1003 that's 21,277 KB becomes the 32 bit plug-in: C:\Program Files (x86)\Common Files\Adobe\Plug-Ins\CS5\File Formats\Camera Raw.8bi
-Noel

Problem with ACR 7 support of Canon 5D Mark III

Just purchased LR4 with ACR7 (upgrade from LR3.6 - not happy about that either, but I am mostly over it) and tried to import photos from my Canon 5D Mark III. Import feature sees all the .CR2 files but when I try to import them it complains that it does not recognize that file format. Not happy.

Unfortunately two important cameras, the Canon 5D.3 and the Nikon D800, came out during the transition between LR3/4 and PS-CS5/6 so Adobe released beta versions of LR and ACR to help tide people over, but what gets released when is kindof messy during the transition.
A major version release requires debugging and testing so the functionality, including new camera support, must be frozen earlier as compared to mid-version camera-support releases that have minimal coding changes. ACR7-beta functionality was frozen back in February so has even less camera support than ACR6.7 beta, which confused PS-CS6-beta users as well.
Just so you’re aware, there is a bug when doing extreme adjustments in the new toning model and geometric lens-corrections have been applied, so be careful with that in the new LR4.1 RC2. Eric Chan has said the bug will be fixed in the release version of LR 4.1. The same bugs exist in the final ACR 6.7 that came out within the last week, so it is unclear what the status of a bugfix is for PS-CS5 users.
Here is a forum post with more information. Also check out the other threads people refer to with other examples of the bug:
http://forums.adobe.com/message/4380573#4380573

Problems with ACR v8.3 and grayscale

I've upgraded to ACR v8.3. Now when I save from ACR to a jpg, and bring it later into PS CC it is grayscale. If I open it in ACR into PS, it is in colour. Have I inadvertently ticked a box somewhere please? It's happening with all raw files. Thanks

Sounds like the setup in the DVD-player is wrong. Enter the menu in the DVD set-top player, and tell it what kind of TV you are using (4:3/16:9).
Also make sure that you have tagged the tracks in DVDSP correctly. In the Inspector, select 4:3 for the 4:3 track, and 16:9 Letterbox for the 16:9 tracks.
Message was edited by: Olse

Problem with ACR 7 auto tone?

Still trying to get a handle on this beast, playing with various controls. Here's a snapshot with default settings and then after auto is invoked. Default appears ok, just a small bit of clipping, but unless I'm missing something something is wrong with auto.
Richard Southworth

'Auto Tone' is simply not good enough to bother using, IMO. (not a big deal for me, since I prefer to "manual" tone anyway, still...).
PS - I have seen this over-darkening behavior in the past which I believed was due to a single overextended channel, which for reasons I don't understand, was not shown in the Lightroom histogram, but you can see it in the histogram of the Mfr. software.
Rob

Problem Installing ACR 5.7 Update

I have all programs closed when I try to install the Camera Raw 5.7 Update so I can edit photos in Photoshop CS4 from Lightroom 2.7. Every time I try to install, an "Installation Incomplete" window pops up saying "Please close the following application and retry to continue installing update: ADOBE BRIDGE." I have cleared the cache in Bridge, but I can't get this to install.

You probably have Bridge set to start up automatically at login. Check the Advanced section of Bridge Preferences.
Richard Southworth

Problem updating ACR 5.7

when I try to install the Camera Raw 5.7 Update so I can edit photos in Photoshop CS4 from Lightroom 3 Every time I try to install, an "Installation Incomplete" window pops up offering options to retry, continue later or quit, none of which help.

You probably have Bridge set to start up automatically at login. Check the Advanced section of Bridge Preferences.
Richard Southworth

ACR 3.7 White Balance Problem

I have just installed Photoshop Lightbox 1.0 on my Windows (XP SP2) PC. After importing a few hundred adjusted DNG files into this software, I noticed that many of the images had severe (thankfully easily spotted) pinkish colour casts indicating a serious white point shift. Viewing the same images in Bridge using ACR 3.X (3.2?) revealed no problems. Now I am a bit confused here. Lightbox claims to use ACR 3.7, which is supposed to be a shared resource with Photoshop. However my version of Photoshop CS2 indicated it was using an earlier version. Anyway, I then upgraded my ACR plugin to v3.7 and low and behold the same problem appeared in Bridge / ACR 3.7.
The problem does not affect all images. It seems, though I am not sure, that it is only those images where the white balance had been set to a custom value that are affected. Other settings: exposure, contrast etc, seem to be unaffected. It is possible to fix the problem in the Bridge + Photoshop + ACR 3.7 environment using the previously saved "fixed" images as references. However the problem remains in Lightroom, presumably because the RAW adjustments are stored separately, and is not so easily fixed, as it does not seem to be possible to have two different images side by side while carrying out fine white-point adjustments.
Anyway, to cut to the chase, I am quite furious that this could have happened at all, as it raises serious questions about the backward compatibility of the software and/or the ability of RAW (DNG) files to preserve adjustment information securely against changes in the software environment. What has occurred should be impossible, but evidently is not. Maybe these digital negatives are not so safe after all.
Anybody got any idea what went wrong and how to fix it? Is there a way to reset Lightroom to the externally applied RAW adjustments?

Actually the product I am talking about is ACR 3.7, which is common to Photoshop CS2, Bridge and Lightroom. The Read Me! notes accompanying my installation of Lightroom clearly states that it uses ACR 3.7 (and that upgrading ACR 3.7 in Photoshop would be necessary to ensure consistency, which I have done). The reference to Lightroom was important, as unlike the Photoshop ACR, in my setup, Lightroom does not store the adjustment settings in sidecar XMP files, or, in the case of DNG files, within the files themselves. The problem manifested itself inside Lightroom first, and then, only after I upgraded Photoshop to ACR 3.7, did the problem occur within Bridge and Photoshop. This clearly demonstrates that the problem is ACR 3.7, and not some feature of Lightroom. [It might help therefore, if, in future, you forgot I mentioned Lightroom.]
To answer your next question, the DNG files were created in my camera (Pentax K10D firmware v1.0 & v1.1). ACR defaults are as out of the box except that sharpening is set to be applied in preview only. Data are "written to XMP" rather than a database.
The auto settings may have changed. However, the fault, when it occurs, is a major, and very obvious, shift of white point, not the sort of thing one would expect from a tweaking of the default/auto settings. Anyway it is only adjusted whitepoint settings, not auto ones, that have changed.
I cannot be sure that the problem is specific to DNG, though I suspect it probably is. My older PEF (Pentax RAW) files are unaffected.
I do not think it is acceptable that changes to software should cause changes to the rendering of an image, particularly where that rendering may have been created by careful adjustment. This is a fundamental issue of backward compatibility.

Problems sharpening high ISO-files from Sony A700 in ACR 4.2

According to the reported problems with sharpening/noise-reduction high ISO-RAWs from Canon-cameras, the same issue seams to appear on ARW-Files of the Sony alpha 700.
Many of A700-users claim, that the pictures show a sort of watercolour effect. These effect will be the more recognizable, the higher the ISO-setting at the camera was. To explain what I mean, heres a 100%-crop of an shot at ISO 1600:
[sorry, I don't know how to loadup images here]
The writing seems somehow rough; there are a lot oft artifacts at the edges. Settings were:
Basic: Dynamic/Vibrance 0
Detail: Amount 33%, Radius 0.6, Detail 0 (!), Masking 20, Luminance 14, Color 10.
(The edges would have been much rougher, if I had set Detail to 25 (default) ore more.)
And here is what the Sony Image Data Converter did:
[sorry, I don't know how to loadup images here]
The edges are clear, I cant see any artifacts.
Now my questions:
Is this problem typical for the Sony A700 or does it appear to other cameras too?
How can I avoid this problem using ACR 4.2? I really dont want to use the Sony-Converter, because its slow and complex to handle.
Which are the best settings for sharpening and NR files from the A700 in ACR 4.2?
Please excuse my English Im German.
Anna

>[sorry, I don't know how to loadup images here]
Anna, you can't upload images directly to the Adobe forum, but must upload them to your own photo sharing site and then use a HTML link to the picture or the site.
If you don't have a photo sharing site, there are several free ones, such as
eSnips, and
Pixentral
If you need help with HTML, this site has a good :
tutorial
> Wait for Camera Raw 4.3...
Very interesting, Jeff. I'm sure you can't provide any further information at this time, but it would wonderful if ACR offered a full fledged noise reduction program such as Bibble does by incorporating the major functionality of Noise Ninja.

High ISO or Push The RAW File? (ACR/LR has a problem here!!)

This topic has been discussed numerous times.
Should you shoot with high ISO or can you just push the exposure in your RAW converter?
What looks better?
What has more noise?
I tested. Nikon D300, shot inside, crappy tungsten light. Each scene I shot with a higher ISO and with the same aperture and shutter speed one stop lower ISO.
For instance:
- f/4, 1/80s, ISO800
- f/4, 1/80s, ISO1600
Now I went in ACR 5.2 and pushed the lower ISO shot 1 stop. Noise Reduction all off.
Here are the results:
- In ACR pushing 1 stop isn't enough. You need to push somewhat around 1.3 stops
- The color shifts in the pushed shot - more saturation, more contrast. Wood for instance gets significantly redder.
- Noise stays virtually the same!
Hmmm. So what would Nikon Capture NX 2 do? Again, NR all off.
That's what happens:
- Pushing 1 stop is enough. It does exactly what you'd expect.
- Color stays exactly the same.
- Noise stays exactly the same.
The shots are virtually indistinguishable!!
So what about 2 stops?!
The exact same results. The "problem" in ACR magnifies, you need to push around 2.6 to get there and saturation and contrast shift significantly now, to an extent where clipping and blocking happens.
Capture NX on the other hand again works flawlessly. No difference between ISO 1600 and ISO 400 pushed 2 stops. Noise? The same. Shadows? The same. Colors? The same.
Shadows don't get lost any more in an underexposed shot that's pushed 2 stops than they are in a shot with ISO two stops higher!
Very interesting. So with NX you could probably shoot the whole evening on ISO 200 and then push it later. Unfortunately NX can only go +2 stops ...
Last comment here:
Adobe need to do some homework here. A lot that is. The non linear increase of exposure, the shift in color and saturation and also the severe, blocky color noise that ACR/LR show in very high ISO shots are way below what we can expect.
Do you trust me or do I need to post the shots?
Cheers!
Thomas

Jeff Schewe says:
"Of course I don't trust you ..."
Sorry, it took me a while, but here are the shots. Initially I did a more sloppy handheld test but I wanted to do it right and now used a tripod and cropped exactly.
http://www.gg-images.us/misc/isovsev
The image names show the ISO, if it says -1 or -2 it means it was 1 or 2 stops underexposed and then pushed accordingly in the RAW converters.
The RAW files are at http://www.gg-images.us/misc/isovsev/raw
Lee Jay says:
"The "exposure" slider in LR/Camera Raw isn't a pure raw*2^exposure, and this is quite intentional."
And why is this so? And what is the intention?
Gordon McKinney says:
"And remember, the camera does an electronic amplification "push" of exposure on the sensor. It should perform better than software since it provide the A/D converts more signal to work with. ..."
The results from Capture NX look as if the software is doing just as good as the in-camera "push" that high ISO does.
Thomas

Problem in ACR

Similar Messages

Maybe you are looking for