Pentax k5 DNG underexposed in Aperture

I noticed a constant underexposure (about 1 stop) of the DNG generated by my pentax k5 when opened in Aperture. I suspect the problem is related to Aperture not reading correctly the information in the DNG files related to the application of the highlight and shadow correction function setting of the camera (on on my user configuration). Any clue? does anyone developed a custom developement profile for k5 thath correct the problem?
Thank

That has been reported here frequently for Canon and Nikon cameras, that Aperture's raw processing ignores in-camera settings like "Preserve Highlights".
You could try to add one of the "Exposure" Quickfixes as an Effect preset as a default in your Import settings:

Similar Messages

  • Leica X Vario DNG files support @aperture?

    Leica X Vario DNG files support @aperture?

    Aperture's camera support comes from the OS. Does not look like the Leica X Vario is currently suppored. See http://support.apple.com/kb/HT5371.
    -scott
    <Link Edited by Host>

  • Using Sigma DP1 Raw X3F files via Adobe DNG Converter to Aperture 2.1.2

    I wish to use Aperture 2.1.2 with my Sigma DP1 raw ( X3F format) photos.
    I used the latest Adobe DNG converter 5.1.0.30 to successfully convert Sigma DP1 X3F to DNG format files. After importing the DNG files into an Aperture directory, they were not an acceptable file format, and thus I could not use them.
    Does this mean that Aperture is not reading the DNG file correctly or Adobe has got it wrong with their DNG conversion of the X3F file format ?
    Do I need to wait for an Aperture update to fix the problem of using the X3F file format ? Is there a solution around in using Aperture with Sigma X3F raw photos ?

    Aperture does not currently support Sigma X3F or linear DNG (only raw DNG), and Adobe's DNG Converter can only yield a linear DNG from an X3F. So your only choices right now are to use a different product such as Lightroom which does support X3F, or use the supplied Sigma Photo Pro software to generate 16 bit TIFFs which you can then import into Aperture. Because Sigma Photo Pro is unstable and slow on Macs, I've been effectively forced to use Lightroom. Lightroom is a capable product, but it lacks the elegance of Aperture, so I remain dimly hopeful that Apple will eventually support X3F, and somewhat more hopeful that it will at the very least eventually support linear DNG.

  • DNG Problem in Aperture 3.0.1

    Just upgraded to Aperture 3.0.1 right after installing the 3.0 upgrade (I have been using 2.1.4 for some time). Am trying to convert RW2 RAW files to DNG. I use the latest Adobe RAW converter (5.6), but although Aperture can read the RW2 files, it can't read the resulting DNG files. It DID read DNGs when I first tried it last week. Today, it no longer works. Aperture DOES read DNGs created from PEF files though. Both file formats are supported and Aperture 3 DID read DNGs from RW2s last week.
    Any idea what's going on?
    Steve

    I've seen the notes about not using linear conversion, and I don't think I am. I say I don't think because I only see one place in Adobe Converter to check linear conversion. That's in the 'compatibility' box and then only if I do a Custom setting. The default in the Custom setting comes up without linear checked. I am assuming that if I leave compatibility set to the default of "Adobe 5.4" that linear is not checked. However, I also went ahead and used "Custom" with linear unchecked and it still doesn't work.
    The weird part is it worked about 4 days ago with the last set of RW2-DNGs I imported. Today, it doesn't work with new RW2-DNGs OR the ones that did work 4 days ago. Have tried reloading Adobe Converter and restarting Converter and Aperture, to no avail.

  • Pentax Lens Model Data in Aperture

    I have finally figured out how to get Aperture to display Lens Model EXIF data for Pentax cameras.
    The problem is that Aperture is looking for that date in one specific field, but Pentax stores it in another. The solution is rather like what we did back when Aperture could not import PEF files. Using exiftool, it's possible to copy the the lens model data from the field Pentax puts it in to the field Aperture expects to find it in.
    This is a procedure you can use (a) for importing new pictures and (b) modifying selected pictures in your Aperture library.
    Assuming you've installed the exiftool library, here are the steps I have used successfully:
    1. Have the pictures you want modified in a folder +in your user folder+. For this example, we'll call the new folder "lenschange." These might have been exported from a project or imported from a camera. I have verified this works on PEF and JPGs.
    2. Open the terminal and type the following command exactly except put your actual user folder name in place of "YourUserFolderName":
    exiftool '-Lenstype>Lens' /Users/YourUserFolderName/lenschange (hit return)
    It will take exiftool a while to do this. It will open each file, move the lens model data, and write a new file, renaming the old one with _original at the end of the filename.
    3. Import the new files into Aperture wherever your want them.
    You should now see the Lens model data in the "Lens Model" field for the EXIF data.
    Clunky, yes; but if you really want that data visible in Aperture, this is (for now) how it has to be done.
    Message was edited by: Lawson Stone

    clawhammer, OMG that is VERY strange. Given what I have read like using exiftool in terminal and sRGB vs adobe profile that this works is odd. Obviously the theory that Aperture is looking for the lens info in the wrong place is not totally true.
    Here's what I did with one Pentax. pef image. In the adjustment HUD in the 'RAW Fine Tuning" brick (Aperture 2.1.2) I switched from 2.0 to 1.1 then back. For a very quick moment I saw the lens info appear in the metadata for Lens. But it went right back to blank. BTW the 1.1 image was awful (green!). So I tried the same thing with 2.0 to 1.0 and back. This time it stuck and I can see the lens info "smc PENTAX-DA 50-200mm F4-5.6 ED".
    To me this is very weird. Obviously it is there somewhere AND accessible to Aperture but either Apple or Pentax is screwing up. Now this is only one image but now I'm thinking can I use Automator or AppleScript to run through my whole library to make the correction (man this would take a lot of time). And then how could I automate this on download.
    I'd be forever grateful if either Apple corrected what now seems like a very simple problem or some script guru solved the library conversion and the download issue with a one step process. Clearly the info is still there so HEY APPLE FIX THIS!

  • Beginner question about RAW/DNG files and Aperture + Adove

    I used to use Microsoft Expression Media. When I would edit a .DNG file in Photoshop and update the sidecar or JPEG preview, EM would show the .DNG with the new adjusted preview in its catalog.
    I noticed Aperture 3.0 doesn't read these adjustments from my .DNG files. Is there a way to get Aperture to properly read my .DNG files?
    Conversely, when I make RAW edits in Aperture, can I view these on the .DNG master in Photoshop? How?

    Adrian:
    I have been using DxO Optics Pro in conjunction with Aperture. The easiest workflow that I have found is to run the images through DxO before bringing them into Aperture. I have DxO export the converted images as 8-bit TIFFs. (Sixteen-bit TIFFs are really big.) I, then, import the TIFFs into Aperture. There are two disadvantages to this approach: I do not get to bring the original RAW file into Aperture and using DxO on all images, even those that turn out to be rejects, takes a lot of time.
    I have also played around with adding images to Aperture, exporting masters before doing any Aperture image manipulation, running the exported images through DxO, exporting the converted images as 8-bit TIFFs and reimporting the TIFFs into Aperture. This can be done without Catapult. I think the advantage of Catapult is that it will automatically stack your processed TIFFs with the original RAW files in Aperture. The advantage of this approach is that I can use Aperture to decide which images I want to process in DxO. Remember that DxO will not see any work that you have done on the image in Aperture; this is why I do my DxO work before doing any Aperture manipulations.

  • Importing DNG files to Aperture 2.1.4

    Hi,
    I am very new to RAW image files and using aperture. I want to be able to take RAW image pictures and make use of them on aperture and so I have added CHDK on my canon ixus70. I know this topic has come up before but I can't seem to add to those.
    Problem I am having is that once the pictures have been taken Aperture doesn't seem to support them. I have tried to convert the .CRW files using dng4ps2 which creates .DNG files (these were blank black files in aperture) and then converted those using adobe dng converter (these imported, but then said that they are unsupported by aperture).
    I want to use Aperture as it has been the most recommended photography software, unless experts here can state otherwise.
    Any help or guidance would be much appreciated.
    S

    I had a similar problem with my Canon SD1100 IS. I was converting the .CRW file to .DNG using DNG4PS2, compiled on Snow Leopard, then converting to Adobe DNG with Adobe's DNG converter. By generating the .DNG file right on the camera, as described here:
    http://www.flickr.com/groups/canonpowershots5is/discuss/72157610078065768
    I was able to use the newest version of Adobe's DNG converter on the camera's DNG files and then import into Aperture. An older version of the DNG converter did not work. You will need to run a program on windows to generate a badpixel file per the instructions. Hopefully this works for you.

  • Why can I not see previews of DNG imports in LR 5 from Pentax K3 (DNG) files.

    Same files preview in LR3 without problem. MAC OS X 10.7.5 LR 5.3 CR 8.3
    LR 3
    LR 5 - Am I missing a preference setting?

    I have a similar problem. I found out that my macbook air created a new USER with my former's computer user name. You can check that by going into System Preferences -> User & Groups, and see if a "Other user" has been created. You have to login under this new USER to find your transferred contacts in the address book.
    My problem is that I do not know how to merge the 2 USER logins or transfer the data from the new USER created into the existing one.

  • Aperture RAW For Pentax 645D

    Looking for advice - have a brand new Pentax 645D (from Japan) and Aperture 3 does not recognize the RAW files it produces. Any suggestions?

    Shoot RAW, import using the provided software, convert to .dng and then import into Aperture.
    Tony

  • Aperture does not support Pentax K 3 RAW format. Any advises?

    I just bought a Pentax K - 3 camera. Aperture does not support RAW format. Does anyone else have the same problem? Is there going to be Digital Camera RAW Compatibility Update for Pentax K 3?
    I would be very pleased if someone could give me some advise,
    Heikki

    Only Apple knows when and if a specific camera's Raw format will be supported and they never say before they release the update.
    In the meantime there a few different ways to work around this. One is to shoot Raw & JPG and use the JPG now and the Raw if and when the camera is supported. The other is to convert to DNG.
    In the meantime let Apple know you want support for the camera, Aperture->Provide Aperture Feedback. Don;t know how much good is does but it can;t hurt.
    regards
    The list of supported cameras is here http://support.apple.com/kb/HT5955
    Message was edited by: Frank Caggiano

  • Adobe DNG files not supported in Aperture 3.1.2?

    Those of you that follow this forum may have read my previous post - https://discussions.apple.com/message/15009745#15009745 - about RAW files from my old Windows machine whice look fine in iPhoto, but when I imported my iPhoto library into Aperture 3 they have this red haze over them like a flash coloured gel.
    As I said, the older files came from my old Windows machine, where they had been stored in Photoshop Elements, and in the past I had converted them from Canon's .CRW file format to Adobe's .DNG format. I've just checked in Aperture, and it is indeed only these which are washed out - all of the Canon .CRW files look fine, it's the Adobe .DNG files which are a mess. I'll hazard a guess that Aperture doesn't support the Adobe .DNG format I have and that is the issue, but why they are supported in iPhoto and no the professional app I can't imagine. A call to Apple tomorrow morning is in order to sort this one out I think unless any of this excellent forum's followers can offer help. Has anyone had a similar experience importing .DNG files into Aperture 3? I should add that they bad either form the original import from iPhoto, or directly importing into Aperture.
    Thanks James.

    Hi Bob, here's a quote from the link Stephen provided:
    "Adobe Camera RAW converted DNGs won’t work because the fine print of Apple’s DNG support shows that it only works with unconverted DNGs—and the new lensdata support of Adobe’s DNG specification generates converted DNGs. While, Adobe may disagree with me (and there is a good reason why they should), this is just the sort of moving-target that causes me to argue against converting to Adobe DNGs."
    As I said in the post this provides some useful background information, but I can't imagine that iPhoto uses a better DNG converter than Aperture (although perhaps older, so maybe that's why I can see the files okay in iPhto and not Aperture?). As for my OS, it's the latest version, I've done two software update checks this week so would for sure have run that when it came around, but I appreciate yours and others thinking on this problem of mine.

  • Aperture 3 will not read LX3 .dng files

    I was a Lightroom user for the past several years, but have decided to give Aperture a try. I converted files from my Panasonic Lumix LX-3, Canon 5D Mark II, and Canon s90IS to .dng when they were imported into Lightroom. I no longer have the original RAW files.
    I have imported these .dng files into Aperture 3. The two sets of Canon files import properly and our easily edited. The .dng files from the Panasonic Lumix LX3 do not import properly. I get the "unsupported image format" message on the thumbnail.
    I have installed the latest Apple update that allows for support of the LX3.
    This has happened on both my Mac Pro and Macbook Pro.
    Is anyone else experiencing a similar issue?
    Thanks,
    Fred
    Message was edited by: Fred Campagna

    Hi Fred. Saw your post about this on dpreview, too. I'll repost my response here for other Apple folk.
    I'm seeing this with DNGs from my G1, too. The problem seems to be that Aperture 3 lacks support for lens corrections in DNG.
    It is probably not a problem with Linear DNGs -- though you'd have to check yours. Adobe forced Linear DNGs on G1 and LX3 users for only one version of DNG converter (5.4, if I remember right). After that, they figured out how to do lens correction inside regular raw DNGs -- the kind that Aperture supports.
    Except that the lens correction in those DNGs seems to confuse Aperture 3. It's odd because for the G1 and LX-3, Aperture supports those same corrections in the native RW2 format. Let's hope it's a bug that the same corrections don't work in DNG.
    In the meantime, there are a couple of options:
    1. Wait for RW2 support. For the GF1, this is your best choice. And save those RW2 files! Extract your original RW2 files from the DNGs or pull them from a backup (you did embed the the RW2, right?). If you've shot with Panasonic micro 4/3 lenses, this is your best option.
    2. If your DNGs were shot with legacy lenses, there is a good work-around. Only native Panasonic (and maybe Olympus) micro 4/3 lenses add the lens metadata. If you don't have that, the only thing keeping Aperture from recognizing your photos is the camera model name embedded in the DNGs. You can use something like exiftool to change it to one that doesn't do lens correction. Here's what I use to get my G1's legacy lens DNGs to work in Aperture 3. (This is not terribly dangerous, as exiftool can just as easily undo this change.)
    exiftool -Model=DMC-L10 blah.dng
    3. If your DNGs do have lens correction (as they must with the LX3) you could use a tool like DNGSanitize http://punainenkala.livejournal.com/588.html, which purports to strip the lens correction from the DNGs. This is a last-resort sort of thing to do, you will lose that lens correction data. You would probably also have to change the camera model name, as in option 2 (try DMC-FZ50 for the LX3). Keep backups. And, really, don't do this -- wait until the next release of Aperture when we'll find out if Apple intends to fix DNG support.
    Whatever you do, test this with your DNGs -- especially if you're trying option 2 or (especially) 3. Just because option 2 works for me, that doesn't mean it will for you. And I've not had to try option 3. And pray you don't have linear DNGs, as only Adobe can help you then.
    I can't believe that Apple would mess up DNG support this badly on purpose. In the meantime, please file a bug report to let Apple know that losing DNG support for these cameras is a big deal. You can do this from inside Aperture itself. Choose Aperture > Provide Aperture Feedback from the menu.
    Here are the gory details, with links to helpful resources -- http://elstudio.us/notes-on-aperture-3-and-panasonic-gf1-rw2-and
    Good luck! And let us know how it works out.

  • DNG file Issue in Aperture

    Until Apple decides to support Nikon D300 NEFs, I am forced to convert NEFs to DNGs (using Adobe Camera Raw 4.3.1) and then import the DNGs into Aperture (I am using version 1.5.6 under Tiger 10.4.11). However, I have just run into a very strange problem that I cannot solve. I had used ACR to remove some camera sensor dust spots on several images before saving the images to DNGs. Then I imported the DNGs into my Aperture projects. However, when I look at the DNGs, none of the changes that I made in ACR appear. In other words, it's like all of the image adjustments made to the NEFs in ACR (and properly saved as DNGs) have been ignored in Aperture when I open the DNGs. To clarify, Aperture is reading the DNGs, but the image adjustments are not there. I cannot figure out what's going on.

    Jim F wrote:
    The file has been converted to a DNG - it's no longer a NEF. Aperture can read DNGs, right?
    Only normally when it's for a camera it already supports. That's because the combination of Mac OS X plus Aperture only supports DNG files that contained the original RAW image data (i.e. not linear DNGs, which have the image data decoded into an intermediate form.)
    (There have been various lively threads about this very issue in the past. Here's one of them: http://discussions.apple.com/thread.jspa?messageID=6041001)
    Apple's "Tech Specs" page for Aperture (as of version 1.5.6, today 28 Dec 2007) still has the footnote "1. DNG files must be generated by the Adobe DNG Converter, with the "Convert to Linear Image" option turned off, and created from RAW formats that are otherwise already supported by Mac OS X 10.4.3 or later."
    But it sounds like you're saying that you've successfully got D300 NEF data, encoded into a non-linear form of DNG with the latest Adobe Camera Raw converter, being displayed by Aperture? This is interesting news indeed.

  • Aperture 2.0.1 and DNG

    With the 2.0 version, I could not export DNG raw files with IPTC data included in the file. With the 2.0.1 version, I am now able to export DNG with embedded IPTC data, but for some strange reason the image date in the EXIF gets set back exactly 16 hours. Can anyone else try this to confirm the bug?

    I have a similar problem. Here is what I do:
    1 - Convert original ORF files to DNG with Adobe DNG converter.
    2 - Import DNG files into Aperture.
    3 - "Image Date" that is displayed in Aperture is exactly 10 hours behind the original capture.
    I think that this problem must be an OS thing because I opened both the original ORF and the DNG files with Preview and they are displayed in Preview incorrectly as well. Here is an example of #3 above: I took a picture of my son's basketball game this morning at "3/8/2008 8:40:19 AM". The original ORF shows this in the metadata. The DNG version of this picture shows the "Image Date" as "3/7/2008 22:40:19 PM".
    I have also imported these same DNG files into Adobe Lightroom and Lightroom displays the date correctly.
    Dwayne
    Message was edited by: dwayne_bradley

  • Pentax K100D support?

    Does anyone have any ideas on how to get support in Aperture for the K100D's PEF file? I tried editing the Raw.plist file and renaming the Pentax-*ist DL key to Pentax-K100D, repaired permissions, and rebooted and it wont import in Aperture, iPhoto or Preview, etc.
    I also tried to convert it to DNG and that didn't work either. I keep getting an Unsupported Image Format error in Aperture
    any ideas?
    Powermac G5   Mac OS X (10.4.7)  

    Yes, Apple's kinda slow adopting the more "exotic" brands and camera makes out there. They're focusing on the cameras that users buy most, which makes sense from their point of view. Sadly, that leaves a lot of us in the dust.
    I believe that the reason for the very slow integration of new and more exotic cameras into the system is due to the very rigorous quality standards that Apple sets with Raw development.
    Other Raw interpreters basically have camera specific color matrices, all other parameters for Raw development are applied regardless of camera make. With Aperture, they do a lot of camera-specific Raw development upon import - not only the colours but sharpening, black point, contrast... that needs lots of testing and balancing, and thus a lot of time.
    Frankly, although I've been really sad about the lack of Pentax *ist DS support in Aperture (and that's not likely to change soon according to the above), I'm glad that they implemented such high standards for their Raw development. No one else does this, afaik, not even Adobe with Lightroom.
    And as long as I can hack the Raw.plist to get my camera to be kinda supported, I'm ok with it. Their Raw developer is very, very good. I'd like to see it stay that way.
    Of course, if there's any way to help to accelerate adoption of currently non-supported cameras... I'd gladly help out if I only knew how!
    Cheers,
    Karl

Maybe you are looking for