LR4.x "Edit in" CS5 compatibility - ACR 6.x vs. ACR 7

So I am struggling with whether I need to upgrade to CS6 now that I have LR4 to preserve 100% LR-ACR compatibility. Can someone explain what I would lose if I didn't? Would I have to render to TIF every time I wanted to edit from LR4 into CS5? I've also read that ACR 6.7 would minimize the impact, rendering the LR4 edits straight into CS5, but that there's still something missing that only ACR 7 can address (open as Smart Object, perhaps)? Can someone clarify the compatibilities and impacts of not upgrading? Thanks.

crspybitsmn wrote:
…I cannot find Camera Raw.8bi on my system. I tried Spotlight and locate (from the command line). I also tried searching for just 8bi. Same result…
That's because there's no such file on a Mac. 
".8bi" is an extension that denotes a Windows file, which would not belong in a Mac—ever.
On a Mac the correct Camera Raw plug-in is labeled "Camera Raw.plugin". 
Tangentially, I recommend downloading and using the free Easy Find utility, which will find any file on your Mac, including many that are off-limits to the intrusive, useless Spotblight.
Wo Tai Lao Le
我太老了

Similar Messages

  • Image sent from LR4 to edit in CS5 crashes Photoshop

    Running Windows 7 Pro, 64bit on Intel i5, 2.80GHx, 12GB RAM, with ATI Radon 5770.  All drivers are current. 
    PS will crash after only one or two applications.

    When PS crashes, the first thing to try is trashing your Photoshop preferences. Press and hold Alt+Control+Shift (Windows) or Option+Command+Shift (Mac OS) immediately after launching Photoshop. You will be prompted to delete the current settings. (Mac OS only) Open the Preferences folder in the Library folder, and drag the Adobe Photoshop CS Settings folder to the Trash.

  • Lightroom says I need ACR 6.1 when editting in CS5 but I already have it

    I have Lightroom 3, Photoshop CS5 and Windows 7 Home Premium. All are 64 bit.
    I have upgraded to ACR 6.1 but when I try to edit a raw image in CS5 from Lightroom I get the 'render using LR vs open anyway' dialogue saying that I may need ACR 6.1. As I have upgraded already (and confirmed from Help/About plugins in CS5) to ACR 6.1 should this message appear or do I have to tick the box stopping the dialogue appearing again? Does Lightroom even know what plugins CS5 has?

    How did you update the ACR? Maybe something went wrong.
    On a 64-bit Windows you might have two Photoshop installations: 32 and 64-bit. Thus, you may need to update both ACRs - the 32 and 64-bit.
    Confirm you have ACR 6.1 in both 32 and 64-bit folders:
    C:\Program Files\Common Files\Adobe\Plug-Ins\CS5\File Formats
    and
    C:\Program Files (x86)\Common Files\Adobe\Plug-Ins\CS5\File Formats
    Also, check which version of Photoshop Lightroom is launching: 32 or 64? You can see it in Photoshop in Help->System Info.

  • Why is there a difference between LR4 image and PS-CS5 version which is much darker

    if i get an image to look great in LR4 (v. 2012) after upgrading the cat from LR3,(version 2010) -  and it looks great in the new develop mode, then I open  up the image in the latest PS CS5, version 12.0.4 x64,  the image then looks much darker in PS and in no way matches the image in LR 4.
    NOT ACCEPTABLE! WHY, Adobe?? 
    I'm on a 64 bit Mac, OS 10.6.8  -- my catalogue settings in LR are for the largest monitor, highest preview, don't discard... and it writes changes immediately to xmp
    is it because the RAW processor in PS doesn't yet match the one in lightroom? and it won't be the same till CS6 is out, and I upgrade to that?  Adobe says all my software is up to date. How do I get things to match? never had this problem with LR3 or any earlier version. What's up?  I'm not on the beta - i just downloaded the real thing from Adobe - read all about it online and I've been very comfortable wiuith LR for years, but I should be able to hit command E on my mac and open it up in PS, looking exactly the same in PS as the image in Lightroom. the new develop mode in LR4 is awesome - so much better than LR3 which was so much better than 2. Why is this happening? How do i get the images to match? what am i doing wrong, if anything? any clues anyone? thanks in advance.          ( would love to include a sample, but I don't see how i can attach a scressn shot of the two.)
    anyone?
    owen

    thanks for replying, Jeff. You may be a user ( that sounds funny )  but you are certainly one well connected user.  thanks for getting back,
    I just click command E  using the shortcut for "edit in CS5." I never go to the menu, if i know the shortcut.  My basic color settings for PS has for years been what i have set up as a ProPhoto /rel. colorimetric color space on both PS... and in LR, my edit in PS-CS5 set up is for a PSD in 16 bit ProPhoto as well - should look the same, right?  You'll probably scold me for saving as a layered PSD instead of a layered tiff - I can't remember why - but I do have my PS preference set for ALWAYS maximize PSD and PSB compatability. Could you give me your advice and reason for tiff vs PSD. I hear that PSD can be "less efficient" than tiff with respect to metadata updates. Not sure exactly what less eficient means or what problems may arise with PSDs.
    Years ago I got into RAW files with the D65 workshops with Seth Resnick and Jamie,before there ever was a lightroom - in fact i first downloaded the first ACR plug in from adobe before it became a part of PS -    ( early 2003? ) - and perhaps you pixel geniuses don't always see eye to eye on certain things but i respect both of your opinions and your work and I'm thankful that you are both out there helping us... and Thomas and all the hard working people at Adobe too.
    So...  after posting, in the deveop mode in LR4 - I switched process versions from 2010- (there was a slight change)- then i switched it back to 2012 - then reopened the file ( exported it to CS5 ) in PS - and lo and behold - it all looked good. the lightroom and PS versions looked like a match - perhaps I should chalk this up to user error. not sure.
    that said,  when i take a canon CR2 file and just drop it into PS on my dock and it opens in CS5's ACR - I still see the ACR equivalent of LR3- which is to say - the exposure, recovery, fill light system- not the new development modality of exposure/contrast - highlights, shadows, whites and blacks -- do you know if we have to wait for CS6 to see the new ACR that matches Lightroom4 - or is an update soon forthcoming? what do you say, Big Guy?
    and many thanks for your attention, your knowledge , and your sense of humor.
    ~oc

  • LR4 Problems after upgrading CS5 to CS6

    Hello,
    I encountered problems with LR4.0 after I upgraded my Photoshop CS5 to CS6.
    LR4.0 hangs (crashes) whenever I switch to the Develop module (from any module). All other modules work just fine.
    I worked with LR4.0 a few months now, with no problems (running W7 Home Premium 64-bits SP1)
    - can this be Adobe Camera Raw related?
    - are LR4 and CS6 using the same ACR (how can I check this)?
    - can I (completely!) remove and re-install ACR and how?
    - can this be Develop preset related (presets did not change, however)?
    - is there a specific order in with to (re)install LR4 and CS6
    - is there a way to completely(!) remove CS6 and LR4 with no traces, and start from scratch?
    I will be switching (upgrading) computers in a few days from now, so I want to fix the issue until this switch and I want to be sure I do not encounter the same problem on my new machine.
    Any hints and tips will be appreciated!
    Cheers!
    Dirk

    I really wish I could be more help to you.  I am running Lightroom 4 on both a 64 bit and a 32 bit system.  And I'm having no problems with either one (using 4.1 RC 2).  You could try uninstalling both programs and start over.  Install Photoshop first, then Lightroom will see it and use it for external editing.  Other than that, hopefully someone else will have some good ideas.
    Just one other thought, if you haven't installed 4.1 RC2, that is the first thing I would do before anything more drastic . 

  • LR4 - Perferences - Edit on PhotoShop Elements Error

    I updared to LR4 from 3.6 which worked perfectly with external editing. I configured LR4 to Edit in PhotoShopElementsEditor.exe. When selecting it I then get "Unexpected Error Performing Command: bad argument #1 to 'lower' (string expected not nil).
    So my guess is it either doesn't like the file name (I tried several) or it doesn't like one of the default parameters being passed as I did not change any defaults. Not the friendliest error message so I could use a little help sorting it out.
    I am using Win 7 64bit and LR 64bit but PSE is 16 bit but I hope that is not a problem.
    Thanks!
    Joe..

    The inability to invoke any external editors from LR4 is a known issue and Adobe is working on a fix.  In the meantime, a temporary workaround involves installing the free trial version of PSE10 or CS5.  You do not have to run these programs but merely install them on your machine.  You can get more information, read the replies by Adobe reps, and add your name to the list of people having this problem at the Adobe feedback site:
    http://feedback.photoshop.com/photoshop_family/topics/lr4_external_editor_failure
    You can also see the response by Tom Hogarty, LR Product Manager on the LR blog:
    http://blogs.adobe.com/lightroomjournal/2012/03/lightroom-4-hot-issues.html

  • Does anyone know why Adobe CC is failing recognise or open files taken on a Nikon D4 that have been previously edited in CS5?

    I'm just migrating some of my image archive across from one hard drive to another.  During the process, I checked the files in Bridge to see that they'd copied correctly.  It was here that I noticed that for some reason, in every folder that I've moved, there are at least a few images that it fails to recognise.  These images are listed as having no camera model and no serial number.  Attempting to open them in Photoshop CC says that it is an unrecognised file.  Bridge struggles for a while, manages to eventually recognise a lot of them but always leaves a few that it cannot work with.
    Having looked at the original drive, the files are fine and open perfectly.  One thing that I've noticed is that some (not all) of the now corrupt files have been previously edited in CS5.  Removing the sidecar xmp file makes no difference.  Purging the cache makes no difference.  Repairing permissions makes no difference.
    I am running OSX Mavericks (10.9.3) and have the latest updated version of CC.
    Please help!
    Leon

    I'm using an Intel iMac, 3.6Ghz Intel core i5 with 12GB of 1333 Mhz DDR3 RAM.
    The iMac has OSX 10.9.3 installed with all of the latest updates.
    I'm using Adobe CC with all of the latest updates installed so Bridge is version 6.0.1.6.
    I have repaired permissions, rebooted the Mac, re-started Bridge and cleared the Bridge cache.
    The raw files are .nef files from a Nikon D4.  They are currently stored on an external Western Digital red hard drive and all of the images are accessible and load correctly.
    In moving the files across to a new Western Digital green drive, Bridge is failing to create some of the thumbnails.  After waiting for all of the thumbnails to be created, the remaining files are simply displayed with a nef files icon.  Any attempt to open them fails, with Adobe Photoshop CC displaying a message stating that the file is not in a format that Photoshop can understand.
    On investigating further, I have found that the images that are causing issues are ones that have been edited before and have sidecar .xmp files.  These .xmp files were created during editing when using Adobe Photoshop CS5.1.
    I hope that's everything that you requested.
    Leon

  • Do I really need to overclock a i7 2600(k) for HD editing in CS5?

    Dear All
    After reading a lot in this forum (thanks to everyone!), I pretty much decided to buy the i7 2600k or i7 2600 (I know the difference) for the system I´m putting together.
    I´ll have a student´s edition of CS5 and will be using Premiere and AE and have one huge doubt left:
    Do I really, really need "Overclocking" for HD video editing?
    A few background infos so you know who "I" refers to:
    I´ll be doing small projects for my own private amusement, most of them likely to be less then 20 minutes long, but effects/filters/layers will definitely be involved.
    I´ll buy a Nvidia 550 for cuda, the three "obligatory" harddrives, 16 GB of RAM...
    Think of fiction short movies, music videos etc. and you get the idea.
    I am not a hardware enthousiast or a very impatient person - if a final rendering/conversion into another format takes 8 minutes instead of 6, for instance, I do not care.
    What I DO care about is smooth editing and previews when working with HD formats (yes, also the "difficult" ones). I don´t want to be on the top of any benchmarks, but
    the performance with HD still should be "good"...
    I have no previous experience with OC, but I understand it´s quite easy with this last generation of processor and motherboards.
    Yes, I am tempted to get more "Bang for the buck", but I am also reluctand to spend more money and time if I don´t really need it, or if the difference will be so minimal I won´t notice it.
    As I understand it, for OC I´ll need to get a better case with fans, a better cooler, better power supply, better who-knows-what... all decisions I need to take now...
    I also wonder:
    - Is it still true that my processor/system will have a shorter life spam with OC?
    - In case I don´t overclock, can I go with the factory cooler of the i7 2600 or is it still wise to get a better one?
    - Any suggestion which Z68 motherboard to buy with and without OC? (should be around 100-150 Euros)
    Please allow me this additional question in order not to open another threat just for it:
    - I want to get  Kingston DDR3 4GB/1333 RAM simply because it´s cheap - is that okay with the i7-2600 or should I go for 1600 instead?
    Thank you so much in advance for any kind of suggestion, I hope your answers will be useful for more users out there.
    Andy

    Thank you, Harm. Does everyone agree? I´d be happy to save the money for all those fans...
    The time issue is really relative. My last editing adventures laying about a decade back when one could go for a coffee when applying a filter to a couple of minutes in PAL
    and even a brightness filter applied to a short shot would have me staring for endless seconds at the screen. I hope these days are gone, EVEN with HD?
    I´m just trying to imagine how and when OC would affect things while using cs5, or if it would affect the "smootheness" of the editing process at all.
    As said, a conversion into another format or a final rendering that takes many minutes anyways is not a problem for me.
    But say I want to apply a filter to a couple of seconds, or render an AE effect, would I have to "wait" at all for previews with the modern i7 system I want to build?

  • While in Lightroom, i press command e to edit in cs5, however my picture won't open in cs5. It was working just fine, then just stopped.

    while in Lightroom, i press command e to edit in cs5, however my picture won't open in cs5. It was working just fine, then just stopped.

    Please do not post questions more than once. It makes it difficult for you as well as those who will try to answer. I don't have an answer for you. However:
    What operating system?
    What version of Lightroom?
    How much RAM?
    Did you install anything new?
    What version of Camera Raw are using in Photoshop CS5?
    If you can provide more details, it might make it easier for someone to provide you with an answer.

  • After I use the Develop module in LR4 I edit in PS-CS4, now the develop changes do not show in CS4.

    After I use the Develop module in LR4 I edit in PS-CS4, now the develop module changes do not show in CS4.

    You need to send the file over to CS4 as a PSD (with Lightroom Adjustments checked)
    CS4 cannot interpret the newer processing version used by Lightroom 4

  • How do images edited in CS5 not return to LR3?

    I have just upgrade to CS5 and then downloaded LR3 trial version as I am waiting for the software to arrive.
    I was editing a shot in LR3, then decided to edit in CS5 for content aware fill to remove some wires that I could not work around.  After completing the edit in CS5, it asked me to save the images and I said yes.  After that, it did not return the file to LR3.  After doing several other edits, I finally did a search on my system to find the images that I edited in CS5.
    To my surprise, they were in different directories on my system!
    Is there something that we now have to specify to get them to return to LR?  I would like to keep the images all in one collection since this is what I have done in the past.
    It also did not ask me when going to CS5 if I wanted to use the edited version like it did in V1 & 2.  Has anyone else had this happen?
    Thanks,
    David

    Did you have any filters set in LR to exclude any other images? ... there seems to be a bug in PS returning images with ratings, color labels and filters  ... or any of the above. Try removing the filters to see if your edited image is there.
    The team is looking into the issue.

  • Editing in CS5 from Lightroom 3

    Similar question to others in the forum with a couple of twists.  Hopefully someone can point me to the solution.
    System:  iMac 2.4GHz running in 32bit, 4Gb RAM
    Software:  Lightroom 3, Photoshop CS5 running in 64bit (same problem if running in 32bit), NIK Complete package plug-ins (updated for 64bit operation)
    PS is the external editor for LR per Preferences; Camera Raw is 6.2 version.
    When I select an image in LR to edit in PS via Photo>Edit in CS5 the following happens:
    PS opens
    Palettes appear
    Finder dialogue box opens asking me to pick a file for editing.
    Or:
    PS opens
    Palettes appear
    No file opens - just sits there doing nothing.
    Or:
    PS Opens
    Palettes appear
    File appears for editing.
    It's irregular enough to drive me crazy.  Sometimes switching from 64 to 32 bit PS will result in normal behavior.  Sometimes selecting Edit In via right click on image will work.  Sometimes selecting a .psd file in LR will work and then all other file types (.dng, .tiff) will work.  Sometimes I have to shut everything down and restart for it to behave normally.
    Anyone see this particular version of the Edit In CS5 bug and found a solution to it?  Seems to have started a couple of weeks ago but not after any upgrade or installation on my part.
    Thanks to all for thinking about it.

    I don't know what anyone else will say, but I would try uninstalling and reinstalling.  do _NOT_ remove your catalog file, or images. They will be fine and dandy.  They are not related to software installs at all.  I'd remove PS as well.  Then install PS first, then install LR.  See if that fixes the problem.
    Cheers!

  • Color in both Bridge CS5 and ACR look yellow.

    The color in my images are all yellow.  I've seen some posts but so far no answer to the problem. Can anything at all be done to fix this problem. It it very, very frustrating. Because it's so yellow I cant use ACR for anything at all.  Please help
    Igor

    Ok, for anyone having this problem with both Bridge cs5 and ACR. Here is what solved my problem. All images were looking yellow both in bridge and Camera Raw, so after I did a back up of my harddrive as a System Image all problems were gone! I have no idea what happened, but now the colors are just fine. The problem corrected itself. So, there you have it. Problem fixed.

  • Concerning Lightroom preferences: Getting back to editing in CS5

    After installing the BETA CS6 Photoshop, how do we get back to editing in CS5 from Lightroom 4?  I don't have the choice to choose the prior editition of Photoshop from the edit in option in Lightroom 4.

    http://forums.adobe.com/message/4287340#4287340

  • Cannot edit in CS5 from LR3

    When I'm working in LR3 and try to edit in CS5 I get the following error msg. "Could not complete your request because it is not a valid photoshop document".

    As a test, you might Open the file in another app, like the free IrfanView, and just do a Save_As to a separate location, so as to not overwrite the original. Then see if PS will Open that resulting file.
    If so, then something is likely munged in the header info for LR3. What it is, I cannot say.
    Good luck,
    Hunt

Maybe you are looking for