LR4 and PS CS5 ACR modules aren´t compatible.

Each time I want to edit an image from LR in PS (edit in PS as hdr, edit in photoshop as panorama,...) I´m asked to update the ACR module from PS CS5 to ACR 7.3 which is not possible.
Is there a possibility that this incompatibility will be abandoned in future updates of PS and/or LR?

Lightroom 4 has features that ACR 6.7 simply doesn't have. There's no way ACR can render it correctly in this case. So rather than send a crippled file to Photoshop, you get that message. What you do is not "Open Anyway" but "Render Using Lightroom".
This has no practical consequence. Whether Lightroom renders the file and exports it to Photoshop or ACR does it from within Photoshop - the end result is exactly identical.
And FYI - I'm in exactly the same situation. It doesn't bother me for a second. The only downside is not being able to open in Photoshop as smart object. But PV 2012 in Lr 4 is so effective, especially in recovering highlights and opening shadows, that there's really no need anymore...

Similar Messages

LR4 and Photoshop CS5 cut and paste?

I've begun using LR4 for website photo editing, but I'm finding that I still need to move the LR modified images into PS for cropping, final size, and resolution adjustments. When I chose Photo>Edit in>Edit in Adobe Photoshop CS5, I've been selecting, "Edit a Copy with Lightroom Adjustments", which works fine.
However, when I cut and paste the resized LR image into another PS document, usually a master template, ALL of my LR adjustments dissapear and the photo is restored to its original settings. How can I keep all of the LR adjustments during a cut and paste operation within PS?
Thanks!

Cut from Ps and paste to Ps?

Nikon D5100 and D700, CS5, ACR 6.4.1: not enough memory when I convert many nef in jpg

The discution was ( and is) also here: http://forums.adobe.com/message/3781380#3781380

Using ACR from PS3 or PS4, no problems. Using ACR 6.4.1. and making a batch convert, from nef to jpg ( or to other formats) I receive "not enough memory" sometimes, and all the times when I select reducing noise and lens corrections. It happen also when I try to transform only one nef to jpg.
I have win 7, i7, memory in triple channel, the system on a SSD, the scratch disk of win on another free SSD and the scratch disk for PS ans ACR on another SSD. I have tryed all imaginable settings, and no hope to use the ACR. Old ACR are OK, only this 6.4.1 have a big problem on my system.

7600+RSP 720-3CXL and 6500 Gbit ethernet modules (WS-X6748-***) compatible?

Hello all,
We are planning the replacement of a 7206 with a 7603-S, 7604 or 7606-S with RSP 720-3CXL to support full internet routing. The problem is RSP720 comes with only 2 x SFP and we need more L3 interfaces to terminate on the router.
Can the above configuration (7600 with RSP720-3CXL) work with WS-X6748-** line cards?
The "relevant interfaces and modules" link for the 7600:http://www.cisco.com/en/US/products/hw/routers/ps368/products_relevant_interfaces_and_modules.html does not list these as options.
If these are compatible, whats really the difference between a 6500 linecard and a SIP+SPA gbit configuration? (besides price)
Thanks in advance

Mario
They are listed under the Ethernet part of the table -
Cisco 7600 Series / Catalyst 6500 Series 10/100 & 10/100/1000 Ethernet Interface Modules
10/100 & 10/100/1000
Data Sheet
still worth checking the release notes to check your supervisor/IOS supports them.
As for difference, well the 67xx cards are purely ethernet, they don't support any other encapsulation whereas the SIP, from a quick check supports many encapsulations, although not ethernet.
I'm not that familiar with the SPAs but for example on the 67xx cards you cannot configure shaping which may be an issue for you. I don't know whether the SPAs permit shaping or not. Obviously you get a lot more port density using 67xx cards.
Only thing i can suggest is going through datasheets to see the difference.
Jon

Sharpening in LR4 and CS5

I shoot RAW with Nikon cameras and use both LR4 and CS5 for post-processing.
My question is about sharpening in LR4 and/or CS5.
Can I do sharpening in LR4 and then again in CS5 by "Edit in Photoshop CS5"?
I recently read an article descrbing that in case we do sharpening in CS5, it did not recommend re-sharpening in CS5.
Could someone advise me which approach is the best for sharpening images between LR4 and/or CS5?

Big question, and one with a lot of answers and also a lot of differing opinions (certainly in forums!). My take, having studied this aspect of image processing a great deal over the past couple of years (this assumes you're shooting in raw):
Break up your sharpening into two (or three) stages. Two of them are key - capture and output sharpening:
- Capture sharpening. Sharpen in the Develop module of LR to "bring back" sharpness lost during the process of capturing the image and converting it into a digital form. Sharpness is lost during the conversion, and also due to the anti-moire (or anti-aliaising) filter that typically is present in most digital cameras (there are some expections, the only Nikon one without this filter is the new D800E), and the Bayer colour filter. The capture process robs some of the sharpness from the image (even when using top-end gear), and you need to recover that in Develop: this is specifically what the controls there are designed for. Note that in-camera sharpness settings have zero effect in LR. Note also that the beauty of being able to do this in LR is that you can tailor the sharpening to your particular image attributes. IMO, capture sharpening is a vital part of any post processing workflow.
- Creative sharpening. Optional (don't do this very often myself, but as with all things, that depends on the image), but you can do this if you want to emphaise a part of your image (the classic example that tends to get rolled out is a portrait where you may wish to add additonal sharpening to the eyes). This can, and generally should, be done in PS (in theory you can do it in LR using the adjustment brush, but from my experience that doesn't tend to give the best results.
- Output sharpening. This should be done at the very end of the process to an image that has been re-sized to it's final output dimensions (so for example if it's for a print, set up the print dimensions/ratio and the ppi before output sharpening). Furthermore, output sharpening depends greatly on the output device: print sharpening will typically need more (and use a different "thickness") than screen sharpening (for web viewing, etc). LR has built-in capture sharpening (available in Export and the Print module) which I'm finding to be very good, but some prefer other tools for this task. You can also do it in PS, but it will be more labour intensive to do so. Do this on a copy of the master file - never on the original.
This is a very brief overview, and there's quite a bit more to it than that, in particular the actual techniques and tools to use (and how to use them). Like I say, a big subject. If you're serious about learning more, I highly recommend the Real World Sharpening book (2nd ed): of all the material I've read on this subject, that's by far the most comrpehensive and informative work. Yes, a whole book just on sharpening - said it was a big question!
IMHO the "sharpen once and once only" approach is outdated, and it's just not flexible enough to cover all the bases. But not everyone will agree with this I'm sure...
M

Lightroom 4.3 and Photoshop CS5 Crashing

For several months, I have been trying to troubleshoot random blue-screen crashes when (and only when) using Lightroom 4.3 and Photoshop CS5 in Windows 7 64-bit. The Windows stop error code is always 124 (hardware related). The crash dump files have not provided much help. They just keep referring to "ntoskrnl.exe" and "hal.dll" as possible causes, but that doesn't help isolate specific hardware. Without going into all the excrutiating details of what I have done to try to find a hardware problem, I am now 99% sure that hardware is NOT causing the crashes. I recently ran "Who Crashed, Professional Edition 4.01" to analyze the crash dump files. It identified "cameraraw.dll" and "tliadjust50.dll" (a file installed byTopaz Labs plug-ins Adjust 4, DeNoise 5, and Fusion Express 2) as possible causes of the crashes. I would like to refresh "cameraraw.dll" to determine if it is in fact causing the problem. My question is how to replace my existing "cameraraw.dll" file with a new one. Can I just download a new "cameraraw.dll" file (from where?) and replace my existing "cameraraw.dll"? Or, do I have to reinstall LR4 and/or CS5 to refresh "cameraraw.dll"? I really hope I don't have to do that, because I think I would probably have to also reinstall all the third-party plug-ins and extensions I have installed to work with LR4 and CS5, and that would be a major pain. Does anyone have any suggestions/

in each, click help>deactivate.
then uninstall each.
then install each on your new computer and activate using your serial number.

LR4 and CS5 Raw versions

LR4 says it uses Camera Raw V 7.0 I only see version 6.7 in the Adobe labs. Are these the same? What if I use CS5, how do I maintain process compatibility?

ACR 6.7 is for LR4 compatibility. ACR 6.7 knows how to convert PV2012 so you can view your LR4 processing in CS5, but the UI for PV2012 is not part of ACR 6.7. For that you’ll need CS6/ACR 7.0, presumably.
So in answer to your question, just say Open Anyway, and ACR 6.7 will do the PV1012 rendering on the way into Photoshop.

Output sharpening in Adobe Camera Raw (ACR) and Photoshop CS5

Output sharpening in Adobe Camera Raw (ACR) and Photoshop CS5
I want to do two-pass sharpening - capture and output - with output capture done just before I print. I do the initial (capture) sharpening in the ACR Detail/Sharpening panel, with Amount slider set to, for example, 100. Then, I open the image to PS CS5 as a Smart Object, and use layers and masks for further editting.
My question is, can I go back to ACR for the final (output) sharpening pass? When I re-open the file in ACR, the Sharpening Amount slider is back to zero, but the other three sliders are still at the settings I used at the start of the process, i.e., the capture sharpening. If I again set the Amount slider to a positive value, then again open the image in PS for printing, will my second pass through the ACR Sharpening panel take effect - will it accumulate on top of the initial sharpening?
By the way, the reason I want do output sharpening in ACR rather than, say, PS Unsharp Mask, is so I can use the Masking slider in ACR, which is much easier than the comparable techniques available in PS. I am aware that some say you should not do any masking for the output sharpening. I'd like to though.
Thanks for ideas.

This is pretty much the way I do it, and I also always found ACR sharpening superior to anything in Photoshop. There is the "sharpen for output" in ACR, but you have little control over it.
The tricky part is feeding the file through ACR a second time. I don't think re-opening the Smart Object will do anything more than you could have done the first time. I do it with a rendered TIFF, and have an intricate set of actions that I run in the Image Processor Pro. It's a mess, and you don't want to know.
The frustrating part is how to action ACR. I just can't figure it out. It'll work, and then I have to change some setting and the action stops working. I suspect you need a script, but so far I haven't found any.
So I've come to a compromise: I first process to TIFF in a temp folder, then I bulk open them in ACR to sharpen, then a second process to finish up.
For less critical files I have a sharpening action that comes close, involving edge masks and blend ifs, using smart sharpen which tends to preserve edges better than unsharp mask, and with less accumulation of noise.
Bottom line: I'm also very interested in further comments to this. BTW, I recently bought Lightroom 4, so maybe there is a posibility using that in a mixed workflow.

In Cs5, ACR I could select crop, right click and on custom, put in a size in millimetres or inches , the latest CC version seems to lack this. Any advice??

In Cs5, ACR I could select crop, right click and on custom, put in a size in millimetres or inches , the latest CC version seems to lack this. Any advice??

In Camera Raw? The Workflow options are now responsible for actual image size. See Julianne Kost's blog post. (There's a video that discusses this in detail at the beginning there as well.)

LR4 and ACR still in sync?

As most here will know LR uses Adobe Camera Raw as its engine.
Now what got me wondering is the fact that LR4 has been released as a final product while ACR 6.7 is still at the release candidate state.
How is this possible?
Has LR4 been released prematurely?

martin-s wrote:
I would have preferred them to take their time. I will give both a miss for the time being.
Not practical...LR4 and Photoshop CS6 (and ACR 7) are on separate but similar release cycles...no, they don't mess up exactly but Adobe has a history of releasing a "last" ACR version (ACR 6.7) before Photoshop CS6 and ACR (ACR 7.x). Do you want LR4 to be delayed because the dev cycles are different? Do you really want LR to be that tied to Photoshop?

Color rapresentation and calibrating ACR module...

I enjoyed lightroom very much , it semplifies my workflow a lot.... but....
looking at images I noticed that are really different from the one in DPP .
what you think ? it's better to stick with DPP for we canon users ?
file is a RAW ISO 200 Canon 20d + Ef 50mm - sunlight out of the door
Left is lightroom TIFF and right is the RAW , both opened in DPP as viewer.
No correction were applied to each file. only opened and saved.
http://www.nickbox.eu/stuff/colors.jpg
I tryed to calibrate colors in the ACR module in Lightroom but can't get so close at the reality
as DPP can do. Any help to correct that ?
thanks a lot.

For me, my reds, blues and greens are shifted... with my Canon 350d.
Nick, the best you may be able to do is use the calibration panel to get it to a good starting point. (Even adjust the tone curve to look good, then save those settings as a preset to apply as a starting point for all your images.)
If you have CS2 + macbeth color checker, there is a script (Thomas Fors?) that you can run to help get the calibration settings down.
My settings are still a work in progress, but much improved over the standard ACR settings, also you could try not using the AUTO tone button, as it often overbrightens the image.

LR4 and Camera Raw 6.7

Hello,
This is my first post, so please bear with me if I do something wrong.
I got LR4 (update from 3) right after it was relesed. I also have Photoshop CS5, so I ran into the PS/LR4 interoperability issue like everybody else. I just checked the status of this issue and I read the followinng in the Lightroom Journal (posted by thogarty on March 12, 2012 under the title "Lightroom 4 Hot Issues":
The team would like to provide an update on several issues discovered since last Monday night’s launch. Thanks for your patience while we investigated and compiled this list.
Edit in Photoshop Workflow
Currently, the Edit in Photoshop workflow asks that you have the Camera Raw 7 plug-in installed. Please note that the Camera Raw 7 plug-in is not available at this time. The correct plug-in for Lightroom 4 and Photoshop CS5 compatibility is Camera Raw 6.7, currently available on Adobe Labs Please keep in mind that currently Camera Raw 6.7 is a a Release Candidate version of the plug-in. A “release candidate” label indicates that this update is well tested but would benefit from additional community testing before it is distributed automatically to all of our customers.
This is a little confusing. When I start up LR4 and go to Help>About I get the About window in whose upper right corner I see "Lightroom 4.0, Camera Raw 7.0". What is going to happen when the Camera Raw 6.7 gets released and I install it. Is it going to upgrade my PS plug-in only or, perhaps, downgrade my LR4 plug-in at the same time?
REgards,
Andy

I don't have Lightroom 4. And from what I had seen so far in the forum, I don't plan on getting it. But from what I have seen I don't think things are any different than they have been with previous versions. Lightroom 4 has been designed to work with Camera Raw 7, which will be part of Photoshop CS6. I don't have the CS6 Beta, and don't plan on getting it. But apparently ACR 7 is not yet ready for release. When you don't have the current release of Camera Raw my experience has been that Lightroom has always given that warning and provided you with the opportunity to edit a copy which includes the Lightroom adjustments. The reason this has to be done is that when you send a raw image from Lightroom to Photoshop Camera Raw Has to interpret the adjustments. And if you don't have the current version the best thing to choose is to send a copy that includes the Lightroom adjustments.
But there seems to be a problem at this point because Lightroom 4 has been released ahead of Photoshop CS6 and so things are out of sync at the present time.
When I was still using Lightroom 2 and even Lightroom 3 I was using Photoshop CS3. So my option was always to send a copy of the raw image to Photoshop. In those two versions of Lightroom the adjustments carried through and I felt the results were acceptable. Apparently, that isn't the case right now with the new version.
Sending a copy to Photoshop doesn't really cause problems, in my opinion. Even if you don't have to do that, once you have completed your adjustments in Photoshop that image has to be saved as a new image. The adjustments cannot be applied from Photoshop to the original raw image. That has never been the case.
In light of all the problems a lot of people seem to be having, I am steering clear of Lightroom 4, at least for the time being. I still get good results with Lightroom 3.6 and have full support for all my cameras. But it seems to me that it's going to take some coordinated effort from Adobe to get this Lightroom/ACR discrepancy resolved. Good luck to all of you. I'm just having a lot of fun with my Lightroom 3/Photoshop CS5 combination.

Should I Avoid LR4 and Get LR3 Because of My Huge Hierarchical Keyword List?

I abandoned LR2 several years ago because it crashed from my hierarchical list of 12,000 keywords. (Botanical and common names and other terms.) I have been using CS5/Camera Raw/Bridge to manage and edit my images. The hierarchical list is necessary for my stock photo business.
I will soon be needing to compare and edit images for a book publication and gallery show and I am thinking I may need to return to LR so I can work more effciently. I do not care about not exporting some keywords or synonyms etc. I think (right now anyway) that it is fine that all keywords associated with the images get exported for my stock submissions. I ususally check off only the sub-keywords or sub-sub-sub keywords.
Here are my questions:
1) Is LR 3 able to handle my huge list of hierarchical keywords which is now larger than 12,000 words?
2) Should I upgrade to LR3 and not to LR4 to avoid the keyword mess I have been reading about but don't understand very well?
3) Is it possible to even upgrade to LR3 now that LR4 is released?
3) Would LR4 handle my keywords better or worse than LR2? Than LR3?
4) Is there a work efficiency reason to upgrade to CS6 without using any version of LR and continue using Bridge and Camera Raw as I have been?
5) Is there anything else I have not thought to ask? I am somewhat technically challenged and dread learning new software, having been burned in the past with ExpressionsMedia disaster and LR2 which crashed etc.
Thanks for any and all input from the forum!

I try to answer your questions. I also have a large list of hierarchical keywords (funny ... also botanical names) but not as much as you have.
1) I think that Lr3 is able to handle your list of keywords. I have not heard from anybody that there is a limit to the number of keywords that Lr is able to handle.
2) There seem to be some keyword issues in Lr4. My keywords were perfectly fine in Lr3 but after upgrading to Lr4 some of my keywords were not populated, meaning that the keywords themselves were listed in the keyword list but the image count showed 0. I still have my Lr3 catalog so was able to check (with Lr3) that, indeed, in Lr3 all the keywords in question were populated with the correct number of images. Fortunately there were not too many of these not-populated keywords, so I corrected the issue manually.
Since correct keywords are mandatory for your stock business, you are right in hesitating to upgrade to Lr4. In my opinion, the improvements that Lr4 offers over Lr3 are mainly in areas that are - probably - not so important to a stock business: improvements in the Develop Module and new Process Version, the Book Module, the map Module. On the other hand I would think that image management is paramount for you and in this area Lr4 is not much different than Lr3.
3) You will not be able to get an upgrade to Lr3 from Adobe now that Lr4 has been released. So you had to find a 3rd party vendor (B&H? Amazon?) who still sells Lr3.
4) Apart from the issue described above, I don't see any difference in keyword handling between Lr3 and Lr4. Lr2 is too far back for me - I don't remember.
5) My suggestion for you would be: You have to upgrade at some point. The longer you wait, the more difficult the transition will be because the differences of future versions to Lr2 will become greater. Since at the moment version 4.1 is in the works (there have been two RCs (Release candidates) of version 4.1 already), maybe it would be wise to wait until the final 4.1 version is out. maybe the keyword issues have been fixed.
6) You can "upgrade" to Lr4 and still have Lr2 on your system. All the Lr versions are stand-alone versions, not "plug-ins" for the previous versions. So you can have two (or more) different Lr versions on your system. So I would suggest that you upgrade to Lr 4.1 (once this version is out) but leave Lr2 on your system. When you Lr4 you will be asked if you want to upgrade your Lr catalog to Lr4 and you have the option of saving the Lr4 catalog as a different file, so that your Lr2 catalog is still available for Lr2 (Lr2 will not be able to work with the Lr4 catalog!). That way, if anything is amiss in Lr4 you can go back to Lr2 and work from there.

Lightroom 4 and Photoshop CS5.5

If I upgrade Lightroom from 3.6 to 4, but leave Photoshop at CS5.5, will there be any problems with Camera Raw? Will I end up with two versions of Camera Raw or any incompatibility between the new Camera Raw and CS5.5?
I have Windows 7 x64.
Thanks
Greg McCormick
Got a partial answer from chat. Will now just do it.

GregMcCHA72JY wrote:
If I upgrade Lightroom from 3.6 to 4, but leave Photoshop at CS5.5, will there be any problems with Camera Raw? Will I end up with two versions of Camera Raw or any incompatibility between the new Camera Raw and CS5.5?
You will not get two versions of the ACR plugin itself installed, because LR incorporates this internally within its program. CS5.5 and its own ACR will be unaffected.
However the communication method between the new LR and your PS version, and also the nature of adjustments saved by LR onto images which are then opened into PS, will suffer some reduced compatibility compared with how you work now.
There are options for passing images from LR to PS, whereby LR renders its adjustments into a bitmap file which PS then opens directly (completely bypassing ACR) - and in that case, ACR support of Raws or editing metadata becomes accordingly moot. LR steps fully into this role, in other words.
This workaround does restrict the functions of passing multiple images for HDR or stitching or as layers.
It also impairs the use of Smart Object workflow since embedded image data may have LR4 edits saved onto it, which cannot be properly used when the Smart Object is later opened into the older-version ACR for further adjustment.
Where a particular image has been worked on inside LR4 using the older process version (2010) - which is fully LR3-compatible (as your current ACR is also) - there will in that special case, be the same compatibility of metadata and adjustments as you currently experience. In effect, for that particular image, LR4 emulates LR3.
RP

Lightroom 4 and photoshop cs5

hi all
we pay all this money for these clever new software and carnt get them to work??????
when i edit an image in LR4 and export it to PS,it asks me weather or not to edit a copy using LR4 adjustments,so i click on yes.when that image apears in PS ,for some reason its exposure has increased quite alote,,,what the hell????
i need help please any one

GregMcCHA72JY wrote:
If I upgrade Lightroom from 3.6 to 4, but leave Photoshop at CS5.5, will there be any problems with Camera Raw? Will I end up with two versions of Camera Raw or any incompatibility between the new Camera Raw and CS5.5?
You will not get two versions of the ACR plugin itself installed, because LR incorporates this internally within its program. CS5.5 and its own ACR will be unaffected.
However the communication method between the new LR and your PS version, and also the nature of adjustments saved by LR onto images which are then opened into PS, will suffer some reduced compatibility compared with how you work now.
There are options for passing images from LR to PS, whereby LR renders its adjustments into a bitmap file which PS then opens directly (completely bypassing ACR) - and in that case, ACR support of Raws or editing metadata becomes accordingly moot. LR steps fully into this role, in other words.
This workaround does restrict the functions of passing multiple images for HDR or stitching or as layers.
It also impairs the use of Smart Object workflow since embedded image data may have LR4 edits saved onto it, which cannot be properly used when the Smart Object is later opened into the older-version ACR for further adjustment.
Where a particular image has been worked on inside LR4 using the older process version (2010) - which is fully LR3-compatible (as your current ACR is also) - there will in that special case, be the same compatibility of metadata and adjustments as you currently experience. In effect, for that particular image, LR4 emulates LR3.
RP

LR4 and PS CS5 ACR modules aren´t compatible.

Similar Messages

Maybe you are looking for