Workflow for unsupported RAW files

Aperture doesn't recognize RAW images from my Leica D-Lux 2 so I will need to use ACR to convert the files. I'm wondering what other people have set up in terms of workflow for unsupported RAW files. I'm thinking I will have to open in PS, convert, save as TIFF, and then import into Aperture--keeping the original RAW files classified somewhere on my hard drive. Anyone have a better workflow idea?

Aperture doesn't recognize RAW images from my Leica
D-Lux 2 so I will need to use ACR to convert the
files. I'm wondering what other people have set up in
terms of workflow for unsupported RAW files. I'm
thinking I will have to open in PS, convert, save as
TIFF, and then import into Aperture--keeping the
original RAW files classified somewhere on my hard
drive. Anyone have a better workflow idea?
If you like using ACR this is a great thread for how to do so easily:
http://discussions.apple.com/thread.jspa?threadID=260641&tstart=0
I myself am in the same boat (unsupported RAW), what I've been doing is saving 16-bit TIFFS from my RAW editor and importing those into Aperture. I just batch convert first and load them in all at once.
When Linear PNG's are supported that is the option I will favor for import I think (until my camera's RAW format is supported, but I think linear RAW will come first).
Powermac G5 1.8GHz DP   Mac OS X (10.4.3)   Radeon 9800 Pro Mac Special Edition, dual monitors

Similar Messages

  • Is this a sensible workflow for Nikon NEF files?

    Hi,
    I'm new to the world of digital SLRs having received a Nikon D40 for Christmas. After comparing Aperture 2 and Lightroom 2, I've decided to go with Aperture, as I already use Logic Pro so like the user interface and (I know a lot of people don't agree) I prefer the way Aperture renders the Nikon NEF files without extra adjustment. I'm also evaluating Capture NX 2, but am undecided as to whether I need it at this point.
    Up until now I've been using Nikon Transfer to transfer the photos to my iMac, and View NX to view them. I like the automatic naming of folders in Transfer, plus being able to see Nikon's interpretation of the raw files. I've then been importing the photos as referenced files into Aperture for proper cataloguing, etc.
    Is this a good approach? I'm a hobby photographer, mostly landscapes and townscapes, and deal with hundreds rather than thousands of images.
    I'm a bit confused by all the options, so any advice would be very welcome!
    Chris

    Is this a sensible workflow for Nikon NEF files? YES!
    I shoot Nikon NEF files and use Aperure exclusively with occasionally a little blending of layers made from versions of the same raw file (to improve the dynamic range a little more).
    You like Nikon Transfer's "automatic nameing of folders" Check out the Subfolders drop down menu in the Import Window in Aperture; you can do that and much more too.
    "...plus being able to see Nikon's interpretation of the raw files." You need to choose between the Nikon route and the Aperture route I think. You don't drive from A to B in one brand of car and then go back and do it in another brand of car just in case it might be better do you?!
    "I'm a hobby photographer, mostly landscapes and townscapes, and deal with hundreds rather than thousands of images" Can you keyword images and then use them to sort and group images in View NX? You can in Aperture.
    From my humble experience as a Nikon owner using Aperture for two years I suggest you use Aperture to download, organise and edit your raws. I prefer referenced so that I can archive large numbers of Raws to free disk space and for protection but still search the previews or do a keyword searches. I used to use Capture NX to process any files that needed more work but now that Aperture2 is so good and has so many plug-ins I have left the slow, clunky Nikon Prog' alone. Be brave and jump in to Aperture. It is great once you are in!

  • For Eric Chan - is Adobe using legacy (or Sigma's) code to do NR for Foveon raw files ?

    Hi Eric,
    is Adobe using legacy (or Sigma's) code to do NR for Foveon raw files ?
    it was stated (I think it was either you or mr Schewe) that Adobe nowadays do not use NR behind the scenes when NR sliders are zeroed - however this is clearly not the case for Foveon raw files... hence the question - is it Adobe's legacy code that for whatever reason was not changed from old days or Adobe is using some SDK provided by Sigma ?
    compare two screenshots - one is ACR, another is SilkyPix v5 Beta... we do not have any demosaicking for Foveon, so it is clear that ACR despite zeroed sliders does NR behind the scenes... can that be fixed and modern Adobe's NR made available for Foveon raw files, like Adobe has it for other cameras ?

    > Is it possible that this file has defaulted to the 2003 process version by accident?
    ACR shows "Process: 2010 (Current)"
    I think that foveon related code was kind of neglected for quite some time... however if Sigma indeed will start selling SD1 that might cause some influx of new customers and it is time to dust off whatever is for foveon inside ACR/LR.

  • Will there ever be support in Lightroom 4 for Olympus raw files

    Will there ever be support in Lightroom 4 for Olympus raw files?

    Which camera exactly?
    Support varies camera by camera.
    Supported cameras
    Camera Raw plug-in | Supported cameras
    Compatible Adobe software
    Camera Raw-compatible Adobe applications

  • Just bought a Nikon d750 and confused about adobe LR4 and PS6 support for the RAW files. I have DNG 8.7 but wondering if LR and PS will import direct soon Thanks for any advice

    Just bought a Nikon d750 and confused about adobe LR4 and PS6 support for the RAW files. I have DNG 8.7 but wondering if LR and PS will import direct soon Thanks for any advice

    Support for the Nikon D750 was introduced in the latest version of LR 5.7 and ACR 8.7 on Novemder 18th 2014.
    Further updates to LR 4 were stopped when LR 5 was released on June 9th 2013. No further updates for bug fixes and new camera support.
    Nada, LR 4 will never support Nikon D750. The Nikon D750 was introduced into the market in September 2014 some 15 months after further development of LR 4 was discontinued.
    You can use the Adobe DNG program (free download for the package) to convert the Nef (raw) files from your Nikon D750 to the Adobe DNG format which will permit you to import those into LR 4. This is the crutch provided by Adobe to allow for the processing of raw files with outdated versions of LR and ACR.
    You can also update the ACR plugin for PS CS6 to version 8.7 which can also work with the raw files from the D750. For direct support in Lightroom you will need to upgrade (paid) to version 5.7.

  • How to download module for opening raw files from D80o. I have CS6

    How to download a module for opening raw files from Nikon D800? I just bought a CS6 not containing this possibility

    Adobe Camera RAW 6.7 and upwards support Nikon D800 RAW files.
    You can download Adobe Camera Raw (ACR) 7.1 from here:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5390 - Mac
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5391 - Windows
    Download & Install it. You can open RAW from D800.

  • Updated Camera list for converting Raw files in PSE7

    I am looking to instal an updated CameraRaw.8bi file to accomodate recent cameras. 
    Camera updated needed for Canon powershot G15.
    Regards Daz.

    Photoshop Elements 7 supports Adobe Camera Raw from version 4.5 to 5.6 only.
    Please refer following document for you reference:
    Camera Raw-compatible Adobe applications
    http://helpx.adobe.com/x-productkb/global/camera-raw-compatible-applications.html
    Canon Powershot G15 starts supported from Adobe Camera Raw version 7.3.
    Hereby,raw files from particular camera is not supported in Photoshop Elements 7.0.
    However, you can use DNG converter to convert Raw files into DNG and import in CS4 aaplication.
    The Digital Negative (DNG) format is Adobe’s proposed standard format for camera raw files. DNG files are useful for archiving camera raw images because they contain the raw camera sensor data and data specifying how the image should look. Camera raw image settings can be stored in DNG files instead of in sidecar XMP files or the camera raw database.
    You can download the latest DNG convert from following place:
    Windows:
    http://www.adobe.com/support/downloads/product.jsp?product=106&platfor m=Windows
    Mac:
    http://www.adobe.com/support/downloads/product.jsp?platform=Macintosh& product=106

  • Editing unsupported RAW files.

    Hi there,
    Can anyone explain why I am able to edit an unsupported RAW file (DNG from a Ricoh GRD 3 camera) in Aperture 3. If it is not supported I would have expected that Aperture would be unable to read the data let alone process and edit the file.
    Many thanks
    Sean

    But Aperture does support DNG's see http://www.apple.com/aperture/specs/ under file formats.

  • Unsupported RAW Files

    I doubt very much I am telling anyone anything they had not already worked out for themself, but today was the first time I'd shot a batch of RAW files with my Canon G1X in several weeks, so I was able to see how CS6 coped with them.  I knew they were not directly supported with CS6, but that they are supported by ACR6.7, so as discussed here already, I imported them as DNG files with Bridge CS5, and then switched to Bridge CS6 tp process them with PV2012.   It all worked perfectly of course.  There have been a few people complaining about cameras that were supportred with ACR6.7 which would not open in ACR7.  They must have CS5 to know that ACR6.7 worked, so in the remote chance any of them have stumbled upon the above workflow...  Now you know.
    I'm still not entirely comfortable with ACR7.  It definitely works heaps better, but it is taking me much longer to home in on the right settings so far.

    Trevor.Dennis wrote:
    I'm still not entirely comfortable with ACR7.  It definitely works heaps better, but it is taking me much longer to home in on the right settings so far.
    VERY interesting.
    I have had just the opposite experience with ACR 7.   To me, it feels like coming home, and I have been getting better images more quickly.
    I have always had a fairly easy time of grokking the transform between turning a knob, seeing the results, then making the best of it I suppose.  What the various sliders in ACR 7 do seemed immediately clear and beyond that they just felt to me like "by golly THAT's what I've always wanted to be able to do").
    Having worked with the prior version for all the years since the day it was released, through thousands of photos, I can say I was intimately familiar with ACR 6, yet ACR 7 just "feels" more right.  And I love that it produces better looking output at the fringes (it rescues highlights better, it fixes CA better, it keeps the image looking natural through extreme control adjustments better).
    Only thing I would have done differently is that we see they've been organized so that what the software designers thought we should do is work generally top to bottom, and I admit that seems like a good idea, but to me I think breaking up Shadows and Blacks with Whites in between just seems odd.
    If I had chosen the order of controls, I think I'd have put the four toning controls in order of brightness, e.g.,
    Exposure
    Contrast
    Blacks
    Shadows
    Highlights
    Whites
    Or maybe the other way around.
    But the way it is now is certainly something I can get used to.
    -Noel

  • Aperture support for unsupported raw formats

    I was doing some tests with Aperture to see if it could fit my workflow. My concern was support of old files from a Nikon Coolpix 5400, raw (thanks to firmware update at the time) as well as a recent Nikon DSLR. No problem with the DSLR. 5400 was not supported. After some internet research I found out there is a pref file (Raw.plist in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources) that has info about all supported cameras. This add raw support for the cameras listed in the file for Preview, iPhoto, Aperture (system-wide). Same list that Apple provides as camera compatibility list.
    In that list I chose to duplicate the NIKON-E8400 array and renamed it NIKON-E5400. Didn't change any value in the array. To my surprise, even without rebooting, this added support for the Nikon Coolpix 5400 images. The image looks pretty much the same with these default settings (when opened in Preview for example) than it does in ACR in CS2. The only odd difference is the image size loosing 10 vertical pixels (from 2592x1944 opened in ACR CS2 to 2592x1934). I have no idea why it does this but it is no big deal really as it is no scaling, just loss of pixels.
    I am a bit concerned of course about the possibility to carry on this tweak in the next OS updates.
    I guess any raw from any camera could have support this way.
    Just need to name the array in Raw.plist properly. For mine I just opened a raw in text edit and saw first line the name of camera, was "NIKONE5400". I compared the format of this name to other names in the array and decided to add the "-" to look like others so "NIKON-E5400", and that was it. Now I was lucky the default setting for the 8400 I used as a base worked for the 5400, apparently. It could have not been the case and then I would have had to play with the values in the array. Quite a few so a long process I am afraid, but possible.
    The deal would be to release a little utility software that would let us play with these values easily and see a result live on a sample image, and once satisfied it would modify this Raw.plist file. This way people could add support to their own raws.
    If anyone in the know sees a big issue in doing what I did please tell.
    Of course playing with this Raw.plist file is at your own risks so keep backup and bee careful.
    The tweaking of this raw.plist file had been talked about in different forum in the past concerning the support of Canon 3xxD that had a different US name Rebel something. The change of name of the corresponding array added support before an OS update did it for everyone.

    I also modified my Raw.plist file to import RAW files from my Olympus C-5050Z. But that doesn't make Aperture import a type of RAW file it didn't support before. It just turns out that your Nikon 5400 RAW files are the same format as the Nikon 8400 files except for size, just as my Olympus C-5050 files are substantially similar to the Olympus C-7070 files. I think the Raw.plist file used by ImageIO contains hints on how to treat the data and color in the images and as long as the cameras don't behave too differently, substituting one model with another will work.
    The RAW.plist file is a standard plist file that can be examined and modified with the Property List Editor. What I would like to see is documentation of the parameters so that we can more easily add support for cameras that aren't supported out of the box.
    MacBook Pro   Mac OS X (10.4.7)   2.16GHz 2GB RAM 256VRAM

  • Any solution for Panasonic Raw files and/or DNG support?

    Hi folks - in addition to my Nikon cameras I shoot with a Panasonic LX3 and soon a GF-1 - and so far I haven't had any luck getting any sort of raw files from the panasonics to be read by Aperture. I had thought that with Apple's DNG support that there would be a way to convert the files to DNG and then import, but so far I have had no luck.
    I realize that the GF1 is brand new, but the LX3 is over a year old and supported by all of Apple's competitors. I really don't want to switch to lightroom, but it is getting harder and harder to stick with Aperture.

    Eric: Great, Aperture 3 might be out by spring 2010? That's only 6 months or so from now. [/sarcasm]
    I appreciate the pointer to the AI article, but personally I'm more interested in whether Apple is working on adding additional RAW support for Aperture/Mac OS X any time soon, and certainly before Aperture 3 is out. Both Aperture 2 and Lightroom 2.5 are more than capable for my workflow and editing needs.
    This week only added to my dismay re: Aperture v. Lightroom update likelihood and frequency; still radio silence from Apple, and Adobe releases a public beta of Lightroom 3, even as Lightroom 2 was released subsequent to Aperture 2 and has had more updates since its initial release than Aperture 2.
    Brian, can you elaborate on the DNG conversion process that worked for you? Having tried every possible profile (I believe) in the latest release of the DNG Converter app, I have to say I'm skeptical that there's a setting that works with the GF1. But I'm ready to be pleasantly surprised!

  • Options for Canon RAW files?

    I have a PowerPC at the office running 10.5.8. I am a graphic designer & photographer. Previously I was able to use iPhoto with my older DSLR to import Canon RAW files. I've upgraded to a Canon 60D and iPhoto no longer reads these new Canon CR2 files. As you know, CS4 is the latest version of the creative suite I can use on this Mac, and Photoshop CS4 doesn't open these RAW files either.
    I checked out Adobe DNG converter but it won't run on this system.
    Are there any options or is it just time to upgrade to a new Mac?

    I don't currently have the install disc with me, but I can try that later when I remember to bring it with me.
    I went to the Canon site to download a driver and it either is not available for my OS, or says I don't need it.
    I want to do all of the above (import from camera/SD Card, open, convert/modify) in a seamless workflow. I use Lightroom 4 at home which I love but only have access to iPhoto at work.
    Thanks for the help!

  • Support for Canon raw files in panther and iPhoto

    I can't get iPhoto 6 to import the raw files (.cr2) from my Canon 400D.
    I can use image capture and also Elements 4 with Raw support, so I am not sure if its the operating system level (panther) or something else.
    I did use iPhoto with my previous Canon with .CRW files and that worked fine to import them, organise them and then edit etc externally in Photoshop.
    Is there any way out there to do this without upgrading the OS or iPhoto, I appreciate I have a way to continue working but miss the convenience of the easy import.

    Suggest you buy (about $10 - $20) a USB memory card reader. Just plug your camera's memory card into it & copy the pic files to your Mac. Quicker & easier than interfacing the camera for pic transfer.
     Cheers, Tom

  • Can't download a patch for Camera raw files for Photoshop Elements 9.

    Can't open RAW files from a Canon 60D camera on Photoshop Elements 9. Went online and suggested solution is to download a patch for PE9, which has been done. Tried to open program and message says Adobe Application manager download required. This done, and back to opening patch for PE9. Message says AAM failed, please download new version (hey, already been there). Going round in circles again. Does anyone non geek check these things. Please help!!!

    Adobe - Adobe Application Manager : For Windows
    Adobe - Adobe Application Manager : For Mac
    Anything else requires more information on your part. We do not know anything about your operating system nor the exact error message(s).
    Mylenium

  • Support for CR2 raw files in Photoshop CS

    Newby here!
    I've used Photoshop CS (the original CS version) for some years processing CRW canon 10D raw files. Now I've upgraded to a later Canon 40D, which produces CR2 files which CS can't read. 
    Is it possible for me to download an update / plugin?    Or do I need to upgrade to a newer version of Photoshop?
    At present, I'm opening the CR2 file using Canon's ZoomBrowser software, then I'm able to edit it with Photoshop CS.
    Any help would be appreciated,
    Roger

    Hi and thanks very much for your responses.
    I've tried the DNG route, firstly the most recent version which, although it converted my .CR2 files, could not be read by Photoshop CS.
    Realising my mistake, I removed this DNG converter and installed the older version 2.4 designed to work with CS.
    But still no joy. The .PNG files created still can't be read by photoshop CS and, although I was careful to update the Camera Raw .8bi file in the Plug-ins folder, CS still won't open a .cr2 file OR .dng file.  Despite the fact that both file types are apparently 'available' in the File/Open dialog box!
    So it looks like it's back to using Canon Zoombrowser to open each file before editing in Photoshop...or buy a new version.
    Anyway, thanks for your responses. Much appreciated.  Roger

Maybe you are looking for

  • In arch, can we install krita without koffice?

    Well... just that... in arch, can we install krita without all the other apps of koffice? Currently I want to try/use features in krita, not the other apps of koffice... any idea? Last edited by luuuciano (2007-05-29 22:58:11)

  • Ringtone and slide shows

    Seriously, why did Apple not think we would not want to use our own (already purchased once) music for our ringtones, I don't like any of the silly sounds they supply, and why also can we not use a slideshow option, music and picts, it's all there, b

  • Viewing a OneNote 2013 notebook in a browser.

    I attached my OneNote notebook to my SharePoint library. I set the SharePoint site setting to view file in a browser; however, every time someone clicks on the file the operating system looks for the appropriate program to open the file. I want the f

  • Safari browser running slow!

    Hi, I know this seems to be a common problem, but my iMac Safari browser has been running increasingly slowly for the last few months, when I first try to launch a new webpage it can take up to 20-30 seconds to load up. I appear to up to date with my

  • Open Hub with Attributes and Texts

    Hi, I´d like to know if it´s possible to have one open hub (database table) with texts and attributes. There´s no problem when I create it or it´s transformations and DTP´s, but when I try to load texts, after attributes load, it always generates a d