Raw processing - camera compatibility

I own a Panasonic DMC-FZ18 camera, and was about to buy the newer FZ45. However, I note that Aperture only appears to support RAW processing with the FZ100 in that range.
Does this mean I will not be able to process RAW images with either the FZ18 or FZ45? If so, is their any likelihood that these older models will to be added to the supported list?

Correct. Also we have no way of knowing if any particular camera will be added.
Regards
TD

Similar Messages

  • My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

    Any ideas?

    My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

  • Why my raw looks different in lightroom and camera's raw processing software

    Hi, I am using a Sony A-100 and just start using Lightroom to process my raw file. I quite like lightroom's interface and its workflow, however, a a problem disturbing me is the image look quite different in sony's raw processing software and in lightroom (just import without any editing). In sony's software, the WB and exposure is correct and I don't need to adjust so much. But in lightroom, the color always looks warm and image is underexposure.
    Is it a common problem or it is just a special case as to sony's dslr camera.

    The main reason is that each different software is interpreting image and color data in its own way due, I guess, to different processing methods.
    In that way, digital is not different than film : no film render colors and contrast the same way.
    You have to choose what fits the best for you.
    As an example, I think ACR / LR handle Canon files pretty well ( quite close to Canon's propietary raw converter - neutral settings - ). On the other hand, Nikon owners have more troubles and seem to prefer Capture 4 or NX renderings.
    Gilles.

  • I just updated mavericks itunes 11.1.4 and raw camera compatibility update 5.3 and my keyboard wont work. How can i fix it?

    So I updatedmy macbook pro 15in. App store had 1 update for iTunes11.1.4 and RAW camera compatability update 5.3. Minutes after it installed my keyboard quit working. Te only way it works now is by bluetooth keyboard and mouse.  What can I do to fix this? Has anyone else had this issue?

    So I updatedmy macbook pro 15in. App store had 1 update for iTunes11.1.4 and RAW camera compatability update 5.3. Minutes after it installed my keyboard quit working. Te only way it works now is by bluetooth keyboard and mouse.  What can I do to fix this? Has anyone else had this issue?

  • How to combine Camera-Raw processed files to be viewed within Windows Explorer as processed

          The problem I have with  camera processed files is that when viewed within Explorer what you did on the file, the crop, and other effects are not visible within Windows Explorer. What is visible there is the original file--this seems to be true of the original nef file in my case.  The change does appear if you save it as a .tif, .dng or .psd but not the NEF. But if you were to open again the NEF file and the RAW Window opens you can see your changes immediately.
            I know it is because  with an original raw file nothing has been done to the image except give it instructions so to speak but Bridge does see it as such so why not let Explorer (Or other viewers, for ex. XnView) view it as such as well? Perhaps this is more a Microsoft Windows issue or what-have-you but I thought I would start to present it here first.
    Where's the question? The question is not actually for someone to explain why this is so, I think I may understand this a little but rather the question is, would it be possible to let other software such as Explorer see the raw processed file--to let it see it as Bridge sees it? Yeah I guess this may be a Windows issue but.....
       Why does this bother me? Since I don't use Photoshop or Bridge professionally I view images more often in Explorer then I do in Bridge or PS (The former is instantaneously viewable while the latter take way to long to open--and Bridge vs. XnView needs an extra step.)
            Side note: Sometimes I feel I am wasting my time and yours in writing such silly questions nevertheless they present themselves in my brain and in the process I hope to learn something from it regardless of its silliness/stupidity. It is such questions which at times creates something original, therefore creativity, after all, does it not? (Or so I tell myself in order to justify it all :-)

    You can't...
    Camera Raw plug-in | Supported cameras
    Camera Raw-compatible Adobe applications

  • Would like to purchase PSE 12 to process Camera Raw files for the following cameras: Nikon D800, Nikon DF, Canon G9 and Pentax K-3 does the Raw Converter that comes with  PSE 12 when purchased recognize  the cameras listed in the question or do I need to

    Would like to purchase PSE 12 to process Camera Raw files for the following cameras: Nikon D800, Nikon DF, Canon G9 and Pentax K-3 does the Raw Converter that comes with  PSE 12 when purchased recognize  the cameras listed in the question or do I need to download  the camera Raw Version 8.3 ?

    While the G9 RAW files can be read by Adobe Camera RAW and Lightroom, these file are unsupported at this time. Here is a link to Adobe's latest list of cameras that are supported and this list came out yesterday http://www.adobe.com/products/photoshop/cameraraw.html
    I have not done a comparison between Lightroom and Canon's software but others have and say that Canon's software is clearly better. I am sure when Adobe updates their software again to include the G9 it will be a very good RAW converter as it is will most other cameras.

  • Photoshop Elements Help | Processing camera raw image files

    This question was posted in response to the following article: http://helpx.adobe.com/photoshop-elements/using/processing-camera-raw-image-files.html

    gegjr wrote:
    When I selected "Save Image" there is an option to select the size of the JPEG preview. Is there anyway to extract the JPEG and does the JPEG contain the adjustments that were made to the Raw image?
    The "Save image" command just saves (really converts) the original raw into another raw format : the DNG format created by Adobe to get a universal raw format instead of a specific raw format for each camera in the range of each camera manufacters... Using that feature is your choice.
    And what you see in the bottom line : 8 bits or 16 bits has nothing to do with a preview, it is the choice of 'color depth' for the image the converters sends to the editor.
    So, your choice is either :
    - to click 'Done' which saves the settings of your conversion (white balance, exposure, clarity...) to a very small 'sidecar' file of the xmp type
    - to 'Open' in the editor where you can work with all features of the editor (which include saving the output file in any format - jpeg - psd - tiff - png...
    http://forums.adobe.com/thread/1030798?tstart=0

  • RAW Processing Change?

    Today, I believe after installing the version 5.01 Digital RAW Compatibility Update, all of the pictures in my library produced by my Nikon D2x and D3 cameras are listed as being adjusted using an "earlier version of Apple's RAW processing." And clicking on the button to reprocess the RAW images does result in very minor changes.
    These cameras are pretty old models. Did Apple really sneak in some changes to RAW processing engine for older models along with the added models listed in the RAW Compatibility update? Nothing was said about this in the update page, and this happened before only with a major Aperture version introduction. Did this happen for anyone else?

    I'm seeing changes for many, perhaps all, my Sony camera bodies.  But first, note that the Images aren't -- iirc -- marked as "needing" to be re-converted -- they are simply marked as having been converted by a superannuated version of Digital Camera RAW.  I create my own RAW tuning settings, and save them as the default.  With DCRAW 5.x, I had to create new ones and save them again as the default.  But I didn't have to change any Images that had been converted with any of the older DCRAW versions.
    I think the notice I got was very similar to the one that shows up when you use the old "Highlights & Shadows (sic)" adjustment brick.

  • Canon sx40 RAW processing

    I shoot RAW with Canon SX40 HS using CHDK. Aperture reportedly has a profile for Canon SX50 (not 40) RAW. Does anyone know how Aperture might interpret a RAW image that's associated with the SX40? And is there a way to change the camera model to "fool" or force Aperture into using it's SX50 profile for RAW processing? I don't see any controls for telling Aperture to use a particular camera profile. (Of course, all this may be for naught since Aperture is being discontinued...)
    thx
    mike

    I am having the same exact problem with my 60D. All of my photos process with a dark magenta hue in the blacks. Upping the exposure or brightness on any of my RAW photos causes the pinks to come out of the blacks and the photo looks even more overly saturated with pink. If I shoot in both JPEG and RAW simultaneously, the JPEG looks as it should be. But once the RAW version reaches Aperture, or OS X in general, the pink hue is very apparent and has ruined all of the photos I've shot since I first got the camera.
    It should also be noted that processing the RAW files with the factory software supplied by Canon with the camera processes the photo as expected without the dark magenta hues. Could there be an issue with the RAW compatibility that Apple delivered in the OS X 10.6.5 update? I doubt this is a problem with the camera as the RAW file looks fine when processed with any software that isn't Apple related such as Aperture, iPhoto, or Preview.
    Attached is a screenshot of a normally processed RAW file (top) and an Apple/OS X processed RAW file (bottom), same exact photo:
    http://imgur.com/K9jQs.jpg

  • How do I update a folder of DNGs to the new 2010 (Current) Raw Process?

    Is there an efficient method to update an entire folder of DNG images to the newer RAW process in Camera Raw 6.1 - to "2010 (Current)"?
    And as an added bonus, it would also be great to simultaneously update the Camera Profile - to "Adobe Standard".
    I have lots of folders of DNGs that were processed in ACR 5.7 or Lightroom 2.7, and so they were processed in the older, 2003, process version.
    I see that when I update a single DNG in Lightroom 3's Develop Module that I am asked if I want to update all of the photos shown in the Filmstrip at the bottom of the window.  This is very convenient!
    My father does not yet have Lightroom 3, but does have Photoshop CS5 and ACR 6.1 installed and he wants an efficient method to do the same using those tools. We found that if we open the folder in Bridge, select all the DNG images, open the multiple images in Camera Raw, click on the "Select All" button in the upper left corner of the window, that we can then go to the Camera Calibration panel and make these two changes to all of the images simultaneously.
    It seems like there should be some method of doing this from within Bridge. When we go to Edit -> Develop Settings -> Copy Camera Raw Settings and then select all of the other DNGs in the folder and go to Edit -> Develop Settings -> Paste Camera Raw Settings.... and choose only the Camera Calibration checkbox, that only one of the two settings actually gets changed; the Camera Profile setting does - the Process version does not.

    austinmirage wrote:
    Is there an efficient method to update an entire folder of DNG images to the newer RAW process in Camera Raw 6.1 - to "2010 (Current)"?
    And as an added bonus, it would also be great to simultaneously update the Camera Profile - to "Adobe Standard".
    You CAN easily make a Camera Raw preset or use Copy/Paste develop settings to change a folder's worth of files to "Adobe Standard"...that's simple. However, currently the Process version is not captured in a preset not copy/paste settings...the only current method is to actually open images inside of Camera Raw, select all and change the Process version to what you want...note, even Sync won't sync the Process version...only select all and then change the setting.
    It's hoped in the future this will be somehow addressed...it will require that the subsetting for Process version be a separate item in the Camera Calibration settings.

  • Apple's Camera Compatibility list

    I am wondering if anyone knows what this list means. This is how Apple words this:
    Camera compatibility
    Aperture supports digital cameras from a wide variety of manufacturers. It offers optimized support for the RAW formats of the numerous digital SLR cameras.
    See our updated list
    Once you click on the link you get a list of "the numerous digital SLR cameras". As I noticed that my Fuji Finepix S2 Pro is on the list, I assumed that my camera is fully supported in what is advertised as a Professional program that organizes RAW images. Well... after paying $600CAN, Aperture acknowledges my RAW files as an unsupported format. I don't know why considering Photoshop can see them. When I went back to make sure my camera was on the list, I noticed that only about a dozen have a graphic behind them that says RAW. There is no explanation on the page on what this graphic means. Are they implying that raw is only supported on those select few cameras. If so I've been mislead
    I based my purchase on the wording Apple used to describe this list
    "It offers optimized support for the RAW formats of the numerous digital SLR cameras.
    See our updated list"
    Am I wrong here or does this say that if your camera is on this list, you will get optimized support for RAW

    Thanks for you reply sam. I never saw that 2nd list you mentioned. I would have assumed that the list I read on the order page was good enough but I guess I was wrong. I just assumed that a supported camera meant that you can use the most prominent feature of the product "RAW workflow"
    I guess my next question is what does supported camera mean?
    I think Apple better make this more clear or they are going to be taking in a lot of returns. I just checked the box out and it doesn't mention camera compatibility anywhere. Just that you get a RAW workflow. Last time I checked it wasn't compulsory to check out a website before buying a product. If someone comes in a store off the street and purchases based on the boxes info, people will have every right to return the product.
    For me. I guess it was my fault for misinterpreting the list and I will eat the $600 I wasted, however, this has left me with a very sour taste in my mouth.

  • This photo was adjusted using an earlier version of Apple's RAW processing

    It is May 16 2012. A couple of days ago there was an update to OSX. I am now at 10.7.4. My Aperture version is 3.2.3. Digital Camera Raw 3.12.0 build 615 and a bunch of zeros.
    Last night when I imported a slew of photos, everything seemed to go well, but when all processing was complete all of the photos changed to a deep green hue. I finally found the message in the title line: "This photo was adjusted using an earlier version of Apple's RAW processing" and somewhat resolved the problem by individually reprocessing each master.
    Does anyone know what has caused Aperture to act this way and how the problem can be fixed? From a timing perspective, I feel that it was the OSX update, but I cannot be sure.
    Thanks in advance for any assistance.

    I am on a MacBook Air (mid 2011) running Lion 10.7.4 and Aperture 3.2.3 with Digital Camera Raw 3.12.0.  I have the exact same green photo import problem described above.  I have a Panasonic Lumix DMC-GF3 and I shoot RAW.  Sometimes (I can't seem to determine what triggers this), when I click on the photo and Aperture brings it up in the Split View, Aperture briefly re-processes the photo and displays it without the green tint, but now the photo is over exposed.  If I right click->remove all adjustments, then the photo finally displays correctly.
    Sometimes, Aperture tells me "This photo was adjusted using an earlier version of Apple's RAW processing".
    The fix suggested by Snoop Dogg at https://discussions.apple.com/thread/3942768?start=30&tstart=0 took away the green tint.  But now the recently imported photo is still over exposed.  By default, I turn on "Auto Enhance" on on my imports into Aperture.  I still have to right click->remove all adjustments, then the reapply the "Auto Enhance" quick fix before my photo finally displays correctly.
    Any thoughts on this would be appreciated.  Thanks.

  • ACR vs Aperture for Raw Processing

    I have been using Lightroom for over a year (including beta versions on my old PC), but have grown tired of it's lack of worthwhile output options. I have a trial version of Aperture and think that it is a far superior product on the management and output side of things, but I am having problems getting my raw files to look good to me.
    I could process all the files in Bridge first, then create tiffs or PSDs to import into Aperture, but that would negate have the purpose of Aperture. I need help with an Aperture workflow and probably with raw processing controls in Aperture.
    Specs: 17" MBP with 10.5.1, Aperture 1.5.6
    Camera: Pentax K10D ver 1.3
    I typically convert my PEF files to DNG due to better compression in DNG, but have tried using the original PEF with identical results. Any help is appreciated.

    I too came back to Aperture after a year of Lightroom's "workflow". It really is possible to match or surpass LR's output. There's a good guide to the adjustment tools here:
    http://www.insideaperture.com/Site/AdjustmentToolGuide.html
    Also lots of tips about workflow, etc. here:
    http://www.bagelturf.com/
    You probably won't want to spend too much money if you're just using the trial, but Ben Long's book
    Aperture Pro training Series: Aperture 1.5 is very good.

  • RAW Native Camera Settings for Nikon - do they convert?

    Question on RAW processing in Lightroom. Can Lightroom show ALL of the the in-camera settings (WB, saturation, etc.) selected when the shot was taken? I prefer not to have to re-cook the RAW photos from scratch on every picture. Nikon NX2 provides this option (i.e. the RAW and JPEG can look identical as starting points on your screen) which I find helpful versus dealing with uncooked RAW images to start with each time. I am considering Lightroom for lots of other good reasons but this is a threshold issue for me due to time, etc.
    Would love to hear anyone's experience on this. I use a Nikon D80.
    Thanks much.
    Gary

    Robert,
    Specific camera settings,etc, are in fact stored in Nikon Nefs and can be read by NX2--or changed, if one wishes in NX2, but nowhere else, as has been stated.
    Eric,
    Presets, or profiles, may come close in some instances to reasonably good starting points for NEFs in LR2, so if that is all you need or use NX2 for, then your advice is reasonable.
    However, at this point in time, NX2 has some distinct advantages, most notably much more advanced and faster local corrections tools than LR2 and soft proofing, to name two.
    However, LR2 editing is integrated with a catalog database, and NX2 is browser based, and that may make LR2 worth the tradeoff for some users. Both, of course, offer non destructive editing.
    Each has it strengths and weaknesses, so I use both to take advantage of the unique tools each offers.

  • Leica D-LUX 4 (LX3) RAW Processing

    Hi all,
    Just wanted to report some interesting behavior regarding the long-awaited RAW processing ability for the D-LUX 4 and Panasonic LX3. I did not see this happen on the first library I coverted, because I let Aperture do the image processing, so the files were already converted when the Library upgrade process finihed.
    Anyway, this time I did not process images when doing the upgrade of my personal library, because I wanted it to finish the task quickly. It did about 3 hours for some 40K photos.
    I had been shooting RAW + jpg since I got my Leica D-LUX 4 in the hopes that Aperture would support it some day...and that day came!
    Anyway, the .RWL RAW files show up in the browser view as black boxes with the warning triangle. They convert when you select them individually, and that was pretty much as expected.
    What was cool though, was when I had opened an .RWL image into Split View, and then arrow key selected the next unprocessed image. Aperture displayed "Unsupported Picture Format" on top of a low res image that had really severe lens distortion for an instant in what appeared to be a 16:9 or longer aspect ratio image, then displayed the properly converted 4:3 RAW file.
    This is obviously the lens correction processing that is part of the way the camera operates, and that A2 was incapable of converting correctly. I thought it worth mentioning that you can sort of see it at work in A3.
    It is so great to have A3 do such a good job on these files, and be so responsive. Really enjoying getting to work with my Leica RAW files finally.
    THANKS APERTURE TEAM!
    Sincerely,
    K.J. Doyle

    Tonys264 wrote:
    I have been waiting for over a year for RAW support for the Leica D-Lux 4 using Aperture 2. It seems that this support is only going to be offered for Aperture 3 users. I have asked at my local Apple Store for an explanation without any success. Is it really just a marketing ploy for A3, or was there a technical reason why A2 could not have support for this camera??
    Hi Tony,
    Now I am not sure if this conversion works on a machine without Aperture 3 on it, because all of the machines here have A3 on them...
    BUT...
    I just dragged a .RWL file into iPhoto and it opened, no problem.
    I have no control over the conversion, of course, and the better control system for RAW is what you are paying for in A3.
    I shot over 30K images with my DL4, storing RAW + JPG hoping for this, and seeing them come up in A3, and be so workable (better that Phase one) was a very happy day for me.
    Sincerely,
    K.J. Doyle

Maybe you are looking for

  • I get a unwanted correction (cmyk-lab) in spotcolors when I import a PDF in Indesign or Illustrator. How do I turn of this correction?

    Hello, I hope someone can help me with this issue:

  • Syncing by Audio

    Hi there, When syncing by audio, what's happening when I offset the audio frames from the video frames? I was looking around for official documentation on this, but couldn't find any. I'm thrilled that the new Premiere Pro CC (7.0.0) can sync by audi

  • ALE Error Message Handling

    Hi,          In ALE: (1) If it is a error means it has to be send to a particular user---> where we will configure these this thing. (2) How the user will be intimated for the error in the IDOC, what's the medium he will be intimated whether by e-mai

  • Why won't my iphone backup to the icloud?

    I had it checked out at the apple store today.  My phone kept crashing at 75% and no one knows why. I was first told to take off all video and extra pics and podcasts to get my "free" up to at least 2 GB.  I did that and it kept crashing.  I went bac

  • Issue with popup menubutton

    i am using a popup menu button in my application. the menu is big such that i am unable to scroll and cant see the remaining items in the dropdown.  please find following image is there any way to get the scroll enabled for this? thanks in advance. g