Open CR2 in photoshop CS5.1

I can't open my CR2 (Canon EOS 70D) files in this version of Photoshop, do I need a different plugin for raw files? anybody has the same problem?

The camera requires Camera Raw 8.2 or newer. There isn't a version of Camera Raw that is compatible with your version of Photoshop that will support the native raw files. You can download the latest DNG converter and create digital negative copies of your raw files that you can use with what you have now. Or you can subscribe to the creative cloud photography plan ($9.99/month) and have the latest versions of Photoshop and Lightroom. Or you can purchase Lightroom 5 and had it to your workflow.

Similar Messages

  • Raw files from the new Nikon D810 will not open with either Photoshop CS5.1 or Lightroom 4.  When will a real Adobe solution be available to work with Raw (NEF) files in their native format, using CS5.1 and LR4?

    Raw files from the new Nikon D810 will not open with either Photoshop CS5.1 or Lightroom 4.  When will a real Adobe solution be available to work with Raw (NEF) files in their native format, using CS5.1 and LR4?

    Clarification: this is a user forum; you are not addressing Adobe here.
    The answer to your question as phrased is: never.
    CS5 is history and it is not longer supported.  There will not be any updates or bug fixes for CS5.
    You need to convert the raw NEF files from your D810 to raw DNGs using the free, standalone Adobe DNG Converter 8.6 RC (beta), the first version ever to support that camera.. 

  • Opening .CR2 files in CS5 Photoshop from Canon T4i.

    Mac OS 10.6.8.  Photoshop CS5.1 V12.1 x64.
    I am trying to open and edit RAW images shot on my new Canon T41 Rebel. Will not open.
    Tried to convert using Adobe DNG Convertor. Did not work. Is there a way without
    upgrading to CS6?

    Is there a way without upgrading to CS6?
    Well, DNG Converter is free, is it not? You just need the right version. Other than that  - no. ACR 7.1 and above is onyl available for LR4 and CS6.
    Camera Raw plug-in | Supported cameras
    Mylenium

  • Can't open CR2 files in CS5, updates fail

    I have some CR2 files I need to edit.  I have CS5.  When I try opening the files I get the following message "Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw.  Please visit the Camera Raw help documentation for additional information." 
    After looking online for some time, I read that updating my adobe applications should allow me to open these CR2 files.
    I go to the adobe application manager and it lists I need updates for bridge cs5, photoshop cs5, and photoshop camera raw.  I click the update button, watch the progress bar go from 0-100% in about a minute as if everything is just peachy, and the this pops up-
    "the following updates were unable to install.  If you wish to install these updates, please fix the problems below and retry:
    Adobe bridge cs5 4.0.5 update, there was an error downloading this update.  Please quit and try again later.
    Photoshop Camera Raw 6.7 Update
    There was an error downloading this update.  Please quit and try again later."
    I've "tried again later" several times over the last month, and get the same thing each time.
    When I click the "contact customer support" link it takes me to a page that says-
    Error "This serial number is not for a qualifying product..." when installing an upgrade or upsell
    All I want to do is edit these files.  I am happy with CS5, and not interested in paying a monthly fee to upgrade, just so I can open these files.  Help Please?!

    I had this issue today trying to reinstall CS5 on a new laptop.   After many hours and trying to get chat support, i read a forum post that suggested installing each update manually from the adobe website.  I tried and it was successful for me........
    Product updates
    good luck!

  • Can't open CR2 files in CS5

    What do I need to download to pen Canon CR2 files in CS5?

    without know what camera you're using, I would say that you need to download the Adobe DNG converter 8.8 is the current one. That will create dng files that can be opened in CS5.

  • Can't open RAW in Photoshop CS5?

    Can't open RAW-files in Photoshop CS5. It all worked okej in CS3.
    Now Photoshop tells me it's a disk error ”skivfel". Converting to DNG won't help. Desperate!

    Have you tried resetting prefs? http://adobe.ly/PS_Prefs
    Does it happen with *all* raw files? or only certain ones?
    - Jeff

  • After CS6beta install, how to I tell CS5 bridge to open images in Photoshop CS5?

    I am not ready to do all of my work in CS6 now, I am just trying to learn the interface.  But now I cannot opening anything through bridge or windows explorer using Photoshop CS5 at all.  The only way that I can open any image file in CS5 is to do it directly from Photoshop in the file open menu.  How can I set Bridge CS5 to at least have Photoshop CS5 as an option, if not the default?

    Open Photoshop CS5, and launch Bridge from there (Ctrl Alt o) That will open Bridge CS5, and load images into Photoshop CS5.

  • Lightroom doesn't open image in Photoshop CS5 but does open PS CS5

    I just installed CS5 and uninstalled CS4.
    Now, Lightroom 2.7 when in try to "Edit in Photoshop CS5" Photshop CS5 does open, but the image I am trying to edit does not open in PS-CS5 .  Photoshop just opens and the image from Lightroom is not present.
    Looking at previous threads I have tried the solution:
    Mac OS
    On Mac OS, try the following solutions in order:
    Solution 1: Rebuild the Photoshop plist file.
    Close Photoshop Lightroom.
    Navigate to the Users/[username]/LIbrary/Preferences folder.
    Drag the com.adobe.Photoshop.plist file in the Trash.
    Start Photoshop. Photoshop will recreate the plist file.
    I have updated LR , Mac OS and PSCS to all current versions
    Any other ideas to get LR2.7 and PS CS5 to work together again ?
    Thanks,

    I did delete the LR plist file,
    And yes I have the latest version of Camera Raw updated and installed,
    but the Lightroom still opens PS CS5 but will not open the image too.
    Any other sugestions
    Thanks,

  • Aperture fails to open after installing Photoshop CS5

    Aperture fails to open and I cannot access my photo files. This happened after I installed Photoshop CS5. I uninstalled CS5, and have not reinstalled. I uninstalled Aperture and reinstalled it but nothing changed.
    I searched the forums and could not find anything similar.
    Aperture is stored on my hard drive, my iBook and on an eternal hard drive as well. On my iBook there are 5 Aperture aliases (and the Aperture Library), which I don't understand.
    Is there anybody with advice on this matter?
    Thanks,
    Patricia

    Patricia,
    Below some of your posts, but not all, your system configuration is listed as a Power PC G4 with 10.4.2 -- you should eliminate this info.
    When you had CS5 installed, and in Aperture Preferences/Export, was Photoshop CS5 offered as a choice for external editor, or could you not get that far?
    It might be that you would only need to purge the preference file for Aperture to make this work, and I would not have really expected CS5 to not work. Did you have another app for use as External Editor before installing CS5?
    Ernie
    Ernie

  • Double click does not open CR2 in Photoshop CS 6

    I just moved Photoshop CS6, Bridge CS6, and Lightroom 4.1 to a new MacBook Pro Retna running Lion 10.7.4
    Camera Raw 7.1 is installed.
    If I double-click a JPG image in Bridge or Mini-Bridge, it will open in Photoshop.
    If I select a JPG image in Lightroom 4.1 and then select "Edit In" Photoshop CS6, I will get the normal dialog box that asks "What to Edit" with the three options. The image then appears in Photoshop.
    If I double-click a CR2 (Canon 5D mk III) image in Bridge or Mini-Bridge nothing happens (the image does NOT open in Camera Raw).
    If I select a CR2 (same camera) in Lightroom 4.1 Photoshop immediately opens (no "What to Edit" dialog), no image appears in Photoshop and Camera Raw is not launched.
    If I select a CR2 (same camera) in the Mac Finder, Photoshop is launched with the image in Camera Raw.
    How can I fix the behavior of Lightroom, Bridge, and Mini-bridge?

    I also have Photoshop CS6 installed on a Windows 7 x64 laptop. In Windows double-clicking on a CR2 image in either Bridge or mini-Bridge loads the image into Camera Raw.
    Edit in Photoshop CS6 from Lightroom 4.1 launches Photoshop without the dialog box, the same as on the Mac. The image is displayed directly in Photoshop and does not launch the Camera Raw window.
    My guess is that there is an issue with Camera Raw 7.1 or Lightroom 4.1 that is causing this behavior.

  • Can't view open files in Photoshop CS5 on Mac

    I can open files and see that they are open in the layers panel, but there is no window that opens to actually view or edit the open file. Assistance is greatly appreciated in getting this resolved!

    TUrn pff GPU aceleration in the Performance prefs.
    Common Photoshop Issues | Mylenium's Error Code Database
    Mylenium

  • Why are the color images turning gray when I open them in Photoshop cs5

    My images are going gray when I open them so is there any on knows how to solve this issue

    what images
    if RGB, that sounds like a bad monitor profile or Photoshop setting

  • The file appears to unsupported or damaged - not opening in LR5, Photoshop CS5 or any other software

    I've just returned from traveling round asia and found a fair few images show 'The file appears to unsupported or damaged' error message, I can see the preview but can not develop, this is in LR5
    After shooting on the road I took the SD card and imported the images straight from the SD card to the HD on my macbook air ver1 through LR4. I then moved the files to an external drive through LR4.
    Now I've returned I'm now using my Macbook pro 15'' and LR5 and these files aren't opening, they didnt open on the Macbook air either.
    There are possibly 30 files and they all come from one import so i'm guessing they all corrupted on import.
    Is there any software i can use that will open these files and allow me to rescue them?
    Your help would be greatly appreciated as one of the files looks like one of the best i took during the entire 6 week trip.

    Where are the photos located? Can you physically locate them and see that they are full sized?

  • Bridge & Photoshop CS5, opening Photoshop files from Bridge

    If I open Bridge in Photoshop CS5, & double click on a jpeg thumbnail in Bridge, it will not automatically open the file in Photoshop. Why?
    How can I change my settings so that the files selected in Bridge will automatically open in Photoshop when double clicked?

    Hi, when you go to Bridge/Preferences/file Type Associations, & you see the box with a list of file formats in bold on the left, you will see a program name or the word 'None' next to each one, & an arrow to click on, to the right of each one.
    If you have 'None' written there, it means it hasn't got a program allocated to it, or it may have some other program written there instead.
    What you need is to see Adobe Photoshop CS5 in the list on the right, next to every file format that you use.
    You could try clicking on the Reset to Default button at the bottom of the box to see if it brings up Adobe Photoshop CS5 automatically.
    If it doesn't, or brings up other programs instead, click on each of the arrows on the right inside the box, then hit 'Browse'', then look on your hard disk for the program file for CS5, & select the actual application set up file 'Set-up.exe''.
    That's what worked for me.
    Good luck!

  • Photoshop CS5 won't open a PNG pct exported from Quicktime

    I exported a move to still from Quicktime Pro, using the PNG compression settings, and when I try to open it in Photoshop CS5 I get the error message "Could not complete your request because the PICT contains data that is no longer supported in this version of Photoshop." Photoshop CS4 has no such compunction. And I was able to open them in CS4 and recompress them and get CS5 to open them, but this is really annoying. I often have to make screengrabs of Quicktime movies. Looks like I will have to do it staight from within Final Cut and not use Quicktime to do it.
    I have included a still of the error message:
    And a still of the Quicktime compression settings:

    "I am curious. How can changing the the extension of a file format trick photoshop or software in doing something that it can not do.
    I thought that it did not have the engine to translate the data. So what happens to a file by simply changing the extension. Is the data altered ?"
    That's a real good question and something that's been a frustration since the introduction of OS X. Such behavior was never a factor in an Apple OS until Unix. Such nonsense was always part of Windows behavior. It seemed to me it was actually worse immediately after the transition from OS9 to OS X, then improved, now is very stringent again.
    I have thousands of Illustrator files (suffix .ai). I have been working with several other vector programs lately, including Intaglio, a Cocoa product. Intaglio refuses to recognize a .ai file, although it is nothing but a plain text file with proper PostScript code. If I save the file out of Illustrator as an EPS file (suffix .eps) Intaglio has no problem opening it. The difference between a . ai file and the same image as a .eps is only a subtle change in some of the PostScript comments in the file, but nothing that really changes the graphic data. So why does the program give an error message with the .ai file that it is an Unsupported File type?
    Even more perplexing, if I simply change the .ai suffix to .eps, Intaglio is perfectly happy with the file. It opens and displays perfectly. Nothing has changed in the file data by changing the suffix.
    This kind of behavior seems to be an interaction between applications and the OS. The application calls the OS to perform certain functions and the OS demands a particular convention of the file name, or it sends back an error message and the application stops at that point.
    Have you noticed that the OS asks if you really want to change a file name suffix? That's how insistent it is that the name be a certain type.
    TextEdit is a program with no graphic capabilities. If I try to open a PostScript file with it, it balks. (I don't want it to display the graphic page layout - I want to edit the content of the file) A PostScript file has mostly plain ASCII text that can be read and changed by anyone who is familiar with PostScript. (There also can be some long streams of binary image or font data. Such data can't easily be edited, but a programmer could locate it, remove it, or move it around in a text editor program). TextEdit will not open a .ai or .eps PostScript text file as text, unless I change the suffix to .txt. Older (OS9) editors have no such problem and other "programmer editors" ignore the suffix also.
    Programs should (and can) open and display (or reject) files correctly by the nature of the data in the file without any need to examine the file name.
    Apparently, some applications (Graphic Converter?) have decided to ignore the file name nonsense and deal with the actual file data, as they should just like OS9 and previous Mac Oses did. But OS X "conforming programs" insist on the strict Unix way of doing things.
    I have always felt there was some kind of passive-aggressive, arrogant insistence on this by the Unix/NeXT programmers who came with Steve Jobs when he returned to Apple. Early NeXT/OS X implementations of the Mac Desktop were very un-Mac-like and were eventually changed after howls of protest from the Mac community. But they never relented on the file suffix thing, apparently insisting that the human-readable file name was critical to the machine's understanding of the file type.
    All this nonsense is unnecessary as the very simple workarounds prove and very inconvenient for the user. There's just finger pointing and standing on principle and insisting on adherence to some pedantic specification, rather than operational effectiveness.
    Rich

Maybe you are looking for