Problem opening Samsung NX1100 SRW files in CS6 and Lightroom 4

I bought a Samsung NX1100 and want to shoot in Raw format. My CS6 Bridge and Photoshop will not open the SRW files though. I downloaded the lightroom 4 that came with the camera and that will not read the SRW files either. How do I access my SRW files?

I'm having much the same problem, except I'm shooting with an EX2F. I've tried reinstalling CS6 (I have extended) and updating to the latest patches, but no go. Photoshop and Bridge can see the files, but cannot open them or draw thumbnails for them. I have also tried installing the latest version of Adobe DNG converter, I get the same result with this.
I'm on a Macbook Pro, lastest OS with latest updates.
I saw on another thread somewhere that changing the file extension from .SRW to .CRW is the fix. I tried this with a couple of files but again I am still unable to open the files.
Apparently there's a raw converter for Samsung cameras but I haven't been able to find it. which is available on the Samsung website NX200 - DOWNLOADS | SUPPORT | SAMSUNG I don't know if it converts to JPG or another RAW format yet. Hopefully the link doesn't get wiped and it's useful to someone else.
EDIT: Looks like it's a standalone RAW developer. It only outputs jpg or TIFF.

Similar Messages

  • I have just purchased the new Canon 7D II.  I am using CS6 and Lightroom 5.0, neither of which can open the RAW files although I see from the list of supported cameras that the 7D II is covered.  I have updated both CS6 and LR so that is not the problem.

    I have just purchased the new Canon 7D II.  I am using CS6 and Lightroom 5.0, neither of which can open the RAW files although I see from the list of supported cameras that the 7D II is covered.  I have updated both CS6 and LR so that is not the problem.  Not sure what to do next.

    It has been indicated that both of those cameras will be supported in the final release of Camera Raw 8.7. But there is no announced release date. There never is. I assume it will be before December 31. But that is only my guess based on the fact that the release candidate expires then.

  • Error: "We're having a problem opening this location on file explorer. Add this website to your trusted sites list and try again"

    Hello,
    When i try to open document library from SharePoint Production portal then it throws the specified error. However, when i open document library from SharePoint Development portal then it opens it in file explorer quite easily.
    Production portal is on https whereas development portal is on http. Also, UAG has been configured on production portal.
    Any idea where it's getting stuck up? Surely, this is not a browser issue on Windows 7 as it's opening the development portal's document library on the same machine.
    I've also done following things:
    - Configured Desktop Experience on production environment
    - Installed the hotfix for Windows 7
    Regards,
    Sohaib
    Sohaib Khan

    Hello Sohaib.
    Here is the list of causes defined here.Hope it helps you
    The cause and the resolution methods are the following:
    Cause: There is a missing Root site collection...
    Resolution: Check and ensure,  that the “Managed Paths” are not changed in the web Application’s page, there is a (root) explicit for
    this web application and there is a working Root site collection.
    If for any reason this is not the case in your environment, you may try the following:
    - Apply (if not already) the following Hotfix to one of those clients:
    Error when you open a SharePoint Document Library in Windows Explorer or map a network drive to the library after you install Internet Explorer 10 in Windows 7 or Windows Server 2008 R2 
    http://support.microsoft.com/kb/2846960
    Then, try to delete the cache of the IE browser before reproducing the issue. Check the result..
    - Try to temporarily disable the Antivirus and test again.
    - Check if you have installed the Desktop Experience feature on the SPS13 server.
    - Check if you face this behavior with all users, Or only with some specific ones, Or with all different client OSes.. 
    Otherwise you will need to collect the logs to further analyze...
    http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/sps13-quot-open-with-explorer-quot-random-error-quot-we-re-having-a-problem-opening-this-location-in-file-explorer-add-this-web-site-to-your-trusted-sites-list-and-try-again-quot.aspx
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Sharepoint 2013 explorer view error - problem opening this location in file explorer (HTTPS + Win7 Enterprise 64 bit + IE9 32 bit + Office 2007 32 bit)

    Hi,
    We have a problem using Sharepoint 2013 explorer view. (Error - We're having a problem opening this location in file explorer. Add this web site to your trusted sites list and try again).
    I'm using Windows 7 Enterprise 64 bit, Office 2007 32 bit and IE9 32 bit. And the sharepoint site is a https site.
    Some people in my organization are able to browse and some users getting the above error. (with the same client machine configuration)
    If I clear my browser cache, closes the browser and open it then the explorer view is working. But after a minute if I try again I'm getting the above mentioned error. This 1 minute expiration happens is since the first time I have used explorer
    view, not since I opened the browser.
    I have tried the following on my machine:
    1. Modified the web client service to run automatically.
    2. Verified the sharepoint site is part of trusted sites (https://*.spsite.com/)
    3. Compatibility mode is turned on.
    4. Tried adding
    AuthForwardServerList in the webclient registry settings under parameters. (restarted the web client)
    5. Verified the BasicAuthLevel set to 1 (since we are using SSL). Tried setting the BasicAuthLevel to 2 as well. (restarted the web client)
    6. Tried installing software update for web folders (KB907306).
    Verified the below on the production server:
    1. The web application has the root site collection.
    2. It has WebDav Publishing disabled under IIS Web Server feature.
    Could some one please help me in resolving this issue?
    Thanks.

    Hi  Deepak,
    According to your post, my understanding is that you failed to use "Open with Explorer"  in a document library.
    For your issue, please verify the following:
    ActiveX controls must be enabled in IE.
    As you are using Windows 7 Server as the client computer, you must install the Desktop Experience feature from Server Manager.
    Make sure there is a working Root site collection.
    Install this hotfix for windows 7 work with sharepoint 2013 :hotfixv4.microsoft.com/.../463266_intl_x64_zip.exe
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

  • I am having problems opening images renerated in lightroom5 into cs6. Cs6 bridge does not see the lightroom libarary. If I open lightroom and right clik the image, edit in cs6, 6 opens but the picture doesnot follow. What is going on? Give me a hand.

    I am having problems opening images renerated in lightroom5 into cs6. Cs6 bridge does not see the lightroom libarary. If I open lightroom and right clik the image, edit in cs6, 6 opens but the picture doesnot follow. What is going on? Give me a hand, thanks.

    What edition of LR 5? What edition of ACR does PSCS 6 contain. If they are not parallel (same edition number x in [5 or 8].x ), is LR making a tiff or psd rendition of the image?

  • Unable to open d800 files with cs6 and camera raw 8.3

    unable to open d800 files with cs6 and camera raw 8.3

    Have you used Nikon Transfer on those files? Early versions are known to corrupt files so that ACR can't read them. Nikon has since fixed the bug so new versions are safe.
    Here's a thread (with a fix) in the Lightroom forum: https://forums.adobe.com/message/6253962

  • CS6 and lightroom cannot open NEF files from Nikon D7100

    My CS6 and lightroom 3 will not open the raw files form my Nikon D7100. Checked updates, all updates are current.

    You need Lightroom 4.4 or later for the D7100.
    For Photoshop, you need Adobe Camera Raw 7.4 or later.

  • Problems opening a certain CR2 files

    Hi,Can anyone help with this one, in May last year I shot some images on a Canon 450D in RAW, when I imported them into Aperture, they showed the unsupported message, Apple then updated aperture and now they only open as a thumb nail, I thought I might have mistakenly shot these in sRAW so tried opening in the Canon software but still no joy. In the metadata it shows a pixel size of 170 x 256 but a file size of 15.55mb which really doesn't make sense.
    Please help if you can.
    Regards
    Steve

    There are 2 issues here that combine to cause them not to open: the way the files were written, and how much memory Photoshop will allocate for decompressing a single image tile.
    Image Width: 14101 Image Length: 18206
      Resolution: 400, 400
      Bits/Sample: 8
      Compression Scheme: PackBits encoding
      Samples/Pixel: 3
      Rows/Strip: 18206
      Number of Strips: 1
    The images are written as one huge image tile/strip that decompresses to something around a Gig per tile.
    Decompressing that quickly is going to require allocating a buffer over a Gigabyte to hold the data.  Photoshop sets some limits on how large a tile buffer it will allocate so that you don't wait hours for the OS and Photoshop to free up the required space. Yes, we really had user documents that were spinning for an hour or more trying to allocate the buffer space to decompress them, even on a 64 bit system with quite a bit of RAM - hence the limits.  Your documents, written as a single huge tile, exceed the limits that Photoshop will allocate for a single tile.
    The TIFF spec recommends that documents be saved in smaller tiles (though one line per tile is excessive).  Even moving to a few hundred Meg per tile would allow Photoshop to decompress the image data successfully.  Either you should choose different TIFF output options when scanning, or communicate to the makers of the scanner that they should read the TIFF specification and talk to Adobe about improving their TIFF implementation (which would send them back to me).
    Also, the images are also written using PackBits (a run length encoding scheme) that is not a great compressor.  Using LZW or Flate would have decreased the size of the files considerably (half the size, or better).
    For the time being, you can use some of the libTiff command line tools to unpack and repack these files to work better with Photoshop and other applications.

  • Which version doesn't produce this error: "there was an error opening this document. the file is damanged and could not be repaired"?

    This error message occasionally occurs with Acrobat 5 on XP 2.  However the same files can be opened with Acrobat 6.0.4 on Win98(se2).
         "There was an error opening this document. the file is damanged and could not be repaired."
    I'd like ot upgrade 5 on my XP system, but have read many posts complaining about the same error with newer versions.
    Is there a version that never produces this error on files that aren't actually damaged? And has anyone figured out what produces this error? (The posts I've seen suggest solutions that don't seem to work.)
    Thanks.
    Ellen

    Thanks, Prasanth.
    I've read posts about this problem happening on all versions, and wanted to see if it was least likely to happen in one version.
    I just need the basic function - the ability to read a pdf file.
    Of course, it seems to be a problem only for some, and there's no way of knowing the extent, so I will try an upgrade or two.
    Ellen

  • There was an error opening this document. the file is damaged and could not

    Dear all, I am simpley reading pdf file & producing to browser with this servlet
    ( which i got this from same forum)
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    public class Isotest2 extends HttpServlet
    public void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, java.io.IOException
    //String file = request.getParameter("file");
    String file = new String("d:/xyz.pdf");
    if (file != null)
    File f = new File(file);
    if (f.isDirectory())
    //Do something that identifies the file as a directory...
    } else
    //otherwise, open a stram, and begin the download...
    InputStream input = new FileInputStream(f);
    response.setContentType("application/pdf");
    response.setBufferSize(8192);
    response.setHeader("Content-Disposition","attachment; filename=\"" + f.getName() + "\"");
    OutputStream output = response.getOutputStream();
    int count = -1;
    byte[] buffer = new byte[8192];
    while((count=input.read(buffer))!= -1)
    output.write(buffer, 0, count-1);
    output.close();
    input.close();
    but it is unable to open pdf file giving error
    "There was an error opening this document. the file is damaged and could not be reapired"
    what is the problem? [ PDF  file is not damaged !]
    pls help me out
    thanks

    Probably because you aren't writing the last byte read every time through the while loop.

  • How to deal with "There was an error opening this document, the file is damaged and could not be"

    Hello, everyone:
    I open one pdf document with Adobe Reader 9.3, but it appeared that "There was an error opening this document, the file is damaged and could not be repaired".. and I found that another several pdf document in the same folder that I have not opened for a long time is also "damaged and could not be repaired".
    But in the same folder, other documents of different types are ok, does that mean there is something wrong with my hard drive?
    Has anyone else run into this issue or have any suggestions?
    Thank you very much

    It could be that the directory is damaged. It could be that at one time you had a virus that did damage, it is hard to say. Do you have a good backup?

  • Acrobat 11 there was an error opening this document. the file is damaged and could not be repaired

    we are receiving an error when opening certain pdfs saying "there was an error opening this document. the file is damaged and could not be repaired"
    i've tried a few things to fix this issue with no luck
    tried on a brand new windows 7 install without any added software like anti-virus software, etc
    tried on my home pc (I forwarded the document from my work pc to my home pc and still receiving the same error)
    don't think it's anything related to the computers, thinking it's more an issue with the pdf. i've tried the basics like deleting temp files from IE, going to %temp% and deleting that out, doing an acrobat repair, trying in reader instead of acrobat, updating users from acrobat 10 to 11, and still receiving the same issue. the odd thing is, some people can open this document and some receive the error. the other thing is i've tried alternative pdf programs with no avail, same errors from those as well
    i work on the helpdesk with one other person  for the company and not sure what else we can try
    don't think this is a pc issue - tried on pcs in the company, home pcs, personal pcs and all get this error
    got to be an issue with either the pdf, or the way its being sent
    i did reach out to OUR e-mail team here (lotus notes admin) and they've ruled out anything as far as an encryption causing the conflict may go, so notes isn't the issue either
    would it be possible it's on the persons end that's sending the file?

    Unfortunately, CR 10.5 is not supported on WIN 2012 Server. See this wiki for more details. In order to work in a supported environment you will have to upgrade to CR 2008 Service pack 7, or SAP Crystal Reports, developer version for Microsoft Visual Studio (2010 / 2012 / 2013).
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
    Follow us on Twitter

  • Pls help. My Camera Raw, CS6 and Lightroom won't read the NEF files from D610.

    I recently upgraded to Nikon D610 and the NEF files were not readable from my old version of Camera Raw, CS6 and Lightroom. So downloaded the recommended upgrades and I now have Camera Raw 8.4.0.199; Lightroom 5.3; CS6 13.01. But still did not read my D610 NEF's. Please help. Thanks.

    oh wait, i got it. Just in case for those who will have the same scenario. I downloaded the NEF files from my D610 using the old ViewNX 2.1 software and that was the cause of incompatibility. So i upgraded my ViewNX to 2.9 and downloaded my images again. And it worked this time.

  • Cannot open Canon CS2 Raw files in Bridges and Photoshop

    I cannot open Canon CS2 Raw files in Bridges and Photoshop. I have never been able to open it.

    Here are what cameras are supported by what version of the ACR plug-in and Lightroom:
    http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    Here are what Adobe programs use what version of the ACR plug-in:
    http://helpx.adobe.com/x-productkb/global/camera-raw-compatible-applications.html

  • Update of Camera Raw 7.2 for Photoshop CS6 and Lightroom 4.2 - now Bad color

    Did the auto update of Camera Raw 7.2 to Photoshop CS6 and Lightroom 4.2 now the color is green and flat in all images after I save them. I do use a Nikon Camera profile and lens correction. Everything was working fine until the 7.2 update. Now the only way to save correctly is to Save for Web. Where do I match the color/profiles?
    Mig

    Color Settings are :     RGB     sRGB IEC61966-2.1
                                       CMYK     U.S.Web Cooated (SWOP) v2
    Color Management:     All say preserve embedded profile
    I had marked the Profile mismatch boxes to see if I got an error message, but I never did, so I cleared them again.
    Conversion Options:     Engine     Adobe
                                                Intent     Relative Colorimetric
    Advanced Control     Only one checked iis Blend Text Colors using Gamma at 1.45
    As far as what settings do I open images with.  File > Open and find the file. During the edit process everything looks perfect - only after I save is the file trashed.
    Under Preferences: File Handling > File Compatibilty > checked are Prefer Adobe Camera Raw for Supportred files
    Everything has been fine for months with PS CS6 & Lightroom 4.2 & Colorchecker software profiles, until the Raw Camera update. And I can still save perfect images as long as I save they with the File > Save for Web.

Maybe you are looking for