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.
Similar Messages
-
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 CampagnaHi 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. -
I'm looking for a smart way to set up an Aperture 3 workflow - where my propriatary camera raw files get converted into DNG-files when I import my files into Aperture. Aperture's Import menu allows for an Apple-Script to come into action as part of the Import settings. I was thinking if it would be possible for an AppleScript, as part of the import routine, to automatically send the files through the DNG converter app and back into Aperture? So that when the files were finally imported into Aperture they would be DNG-files?
Greatful for any answers and ideas!Thanks for a swift reply Frank! I will have to use the Adobe DNG converter then, prior to importing into Aperture.
Yes, OSX does support my Nikon D600 NEF-files. But once in a while I want to be able to use features found in other raw apps, within my overall Aperture workflow, but without ending with a TIFF or other 'destructable' file format when continuing my workflow back in Aperture. This should be possible using the routine described here: http://www.apertureexpert.com/tips/2013/8/28/guest-post-catapult-and-aperture-3. html
In my case the problem is that my "old" CS5 version of Photoshop cannot be updated to read D600 files (even though CS5 is not even 3 years old) - I would have to buy a newer version of Photoshop and I have absolutely no intention of doing that. And so I have to find a raw file fomat that is readable by both apps.
On a second note there is a discussion about what raw format is likely to 'live the longest' - also be accessable in 20-30 years. Some say that DNG stand a better chance here than propriatary ones. But I don't know about that and that is not my issue here. -
Why does Aperture not support all DNG files?
I have a Leica D-LUX 2 and an Epson RD-1. Both of these cameras create RAW files which are not supported by Apple. Why should the files, when converted to DNG, still require RAW support to be utilized. I understand the wrapper concept, but is this not the idea of DNG. What about cameras that create a DNG file, rather than RAW (i.e. the new Leica M8).
Thanks,
KenHi Kenneth,
You're missing the point Karl is making. RAW data is (in essence) proprietary to the camera. All DNG does is essentially encapsulate that proprietary data in a standard format. The data is still proprietary whether DNG or RAW.
By proprietary I mean that the sensor array and sensitivity to light, tonal correction across the gamut all are understood by the camera manufacturer and held as parameters (data) in the RAW or DNG file. It requires specific knowledge to interpret this data into a renderable image. Until such time as camera manufacturers agree that 1 = 1 and 2 = 2, we are stuck with this issue (and ALL our concern of x years from now when nobody supports what is our latest and greatest camera). An API included in Aperture (actually OS X) would at least allow camera manufacturers to write their RAW conversion algorithms and take Apple out of the loop.... as well as take dependence on OS X releases out of the loop too!
Hope this clarifies.
G. -
After upgrading to aperture 3.3 on mountain lion aperture no longer recognizes DNG files.
I have many DNG files already in my library. Aperture shows the thumbnail and will briefly flash what I think is the preview of the file but quickly changes to a gray triangle saying "unsupported image format". After which the thumbnail is replaced with an all black thumbnail.
Needless to say this is extremely disconcerting. I am concerned that aperture is not only refusing to display the existing DNG files but is also simultaneously corrupting the library and destroying my existing images.
fwiw, these DNG files were generated with a leica.
I have not attempted to import DNG images into my aperture library but I assume that would not go well.Susan,
if it is the native raw format, that no longer is recognized, then try, if registering the CoreTypes.bundle with the OS again will help. This will tell MacOS which raw format types (and other media types) are supported.
Open a Terminal window and paste following line into the window, hit return. This is one very long line:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
Regards
Léonie
P.S: Some browsers cause a blank to be inserted between /Frameworks/LaunchSe rvices.framework/Versions
But it is "LaunchServices.framework", without blank. All in one line - the only blanks are needed between "lsregister" and "-R" and after "-R" . -
Convert RAW Files in Your Aperture Database to Adobe DNG Files
The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files. In the example below I am assuming that your Aperture Library has ARW and CR2 files. These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library). The steps are:
1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu. From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
2. Drag the "Masters" folder out of the Package and place it on your Desktop. The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files. Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc. In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above). The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above. Do NOT put the .DNG files in your search criteria. Select all the files found in the search and move them to the Trash. This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
7. Select the Finder Window containing the Aperture Library Package Contents.
8. If there is a file called "ApertureData.xml" then open it with a text editor. Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search). Make sure you cover all the file types incorporated in your particular system. Save the "ApertureData.xml" file.
9. Traverse to the Database/apdb directory. Select the "BigBlobs.apdb" file and open it with a Hex editor. In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/). Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex. In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window. In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search). Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files. Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish. This process works because:
1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source. Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source. In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.A rather involved method, David.
I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
I convert selected raw files this way - without manually patching the Aperture Library:
Export the originals of the raw images that I want to convert.
Run dng-converter.
Import the converted originals back, flag them, and move them to the project they came from.
Sort the project by capture date, so that identical images are show side by side.
Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
Regards
Léonie -
Does any one have a suggestion as to how to get A3 to show the camera aperture setting on Leica M9 DNG files?
You will want to read this thread in its entirety.
The short story (as I understand it) is that the M9 body receives no information about aperture from attached lenses. It is able to derive an estimate of the aperture, though, and it lists this derived number in the metadata field "Approximate F-stop" (not the exact field name). Aperture (the program) does not report the contents of this proprietary field. -
Aperture won't import DNG files: Panasonic Lumix FZ28
Well, i went to a seminar on aperture and got all excited to use it, downloaded the trial and discovered that it won't import my camera's RAW files (even though it came out 2 years ago and is supported in PhotoShop)
I've tried various way of creating DNG files with DNG Converter (the one that works with PS CS3) but Aperture doesn't recognize those, either. (linear, non linear etc) (Will the CS4 converter do the job?)
Is there anything else I should be trying? Have any of you had success with the same camera and what do you do?
Thanks for any help you can offer.
ElizabethYep, that's what I discovered and it's the whole problem with the RAW files, but what about DNG?
I thought converting to DNG might allow them to be accessed: so you're telling me that I'm out of luck and have to stick with PhotoShop?
That dng is not a universal format recognized by Aperture?
I appreciate your input
Elizabeth -
Photo file issues with iWeb and Aperture....also too much duplicating!!
A little background, before I get into my iWeb issue.....
Years ago I tried iPhoto, but I didn't like how it duplicated all my photo files and I wasn't very fond of the file structure it created. Years later (last month) I got Aperture. Aperture (still has a long way to go) also duplicates all your files and places them in their own file structure. If I can get along with Aperture (and if it will get along with my other programs), I won't mind putting all my files into the file structure it creates. But for now, I still have my original files in the original file structure I have had for many years as a back up.
On to my issue with iWeb and Aperture....
To add photos to iWeb, you can either go into the iWeb media center or you can drag and drop photos from other locations.
1st: iWeb media center
To get my photos into the media center, I would have to load them into iPhoto (iP 6 does allow you to keep your original file structure, but it still creates .jpg files, which fills up your hard-drive. More duplicates I don't need or want). So that is out for me. iP6 will let you view and use your Raw files.
Another way is to drag and drop your file structure directly into the media center window. I don't think this duplicates any files (at least I haven't been able to find any), but it takes an awfully long time to thumbnail all your photos (several hours and still waiting for 22K + files). Also, it won't show any Raw files. Again, out for me.
Aperture won't let you drag and drop its library into the media center at all. So if I was to move all my files into the Aperture Library, I wouldn't be able to access them for iWeb at all.....Out for me.
2nd: Drag and Drop
I was able to drag and drop Raw files directly into iWeb from C1 Pro, Adobe Bridge and Adobe Lightroom.
As I said before, I am trying to move over to Aperture. However, Aperture won't let me drag and drop photos. What is the deal here??? These are both Apple programs and they won't play nice with each other. Very annoying.
Anyway, I put a link below to my iWeb test webpage I made. All the photos were Raw files that I did a drag and drop from C1 Pro, Adobe Bridge and Lightroom. There were no problems with the publishing.
http://web.mac.com/phil_navarro/iWeb/Site%202/Drag%20and%20Drop%20test.html
So, does anyone know if they can get photos from Aperture to work?? Thanks for any responses.
Phil
G5 Desktop Mac OS X (10.4.4)Jedi,
Perhaps you are right.
I am not a web developer and I will never be. I don't feel like spending countless hours learning how to use Dreamweaver or some other Pro web app. iWeb looked like a way to start making websites of my photos for my friends and family (much easier and better than Home Page on .Mac). All I was asking was for a way to drag and drop my photos (especially Raw files) with Aperture. Which I can do with Lightroom, Adobe Bridge and C1 Pro, and without using iPhoto.
I am not a Pro photographer either, but I purchased Aperture based on what was advertised on the Apple website. From that ad, Aperture fit my photo needs almost to a tee. I am looking to adjust Raw files, Crop, Archive and keep my use of Hard Disk space down to a minimum. I can use Photoshop for the other 5% of things I do. However, Aperture has some issues (if you own it, then you already know. If you don't, you can read the Aperture Forum) This is one of the reasons I never went to iPhoto for archiving. I didn't like the way it duplicated all my files, taking up more disk space and its file structure. So even though Aperture won't play nice with other programs, I was surprised that it wouldn't play nice with any Apple programs.
After reading your post and based on what you are saying, everyone either needs to have/learn/use Pro apps only or have/learn/use iApps only. Don't Cross the Streams!!
I guess that means Apple will need to fix DVD Studio Pro. It uses photos that are in your iPhoto library and music from iTunes (iApps in a Pro app??....for shame...."it was never intended"). Also, DVD SP won't read the Aperture library. Does that mean there are 3 platforms? Pro, iApp and Mediocre??
Now I have 2 questions:
1. Can someone please tell me which apps are Pro and iApp, or if there is Mediocre? I don't want to mix them up and "Cross the Streams".
2. Again....is there anyway to use Aperture with iWeb?
TIA,
Narvon -
Canon CR2 to DNG issue. DNG files too big!
I'm experiencing what I believe may be a few issues whilst converting from Canon CR2 RAW files to the Adobe DNG format.
(Camera is Canon 5D Mk2)
For example, I have a folder containing CR2 RAW files which size = approx' 410MB. But when I perform the DNG conversion to a new folder, the total file size of that folder containing the converted DNG images is over 800MB! Does this sound correct?
I thought converting to DNG reduced the overall file size of the RAW image somewhat?
For info, I'm using the latest version of the converter with no JPEG preview or embedded original RAW file selected.
THANKSWhen converting to DNG, is "Embed original Raw File" selected?
If it is, it will double the size of the DNG file.
I have not seen any reason to select this option, and the only time that I have seen reference to it (in Better Digital Camera, I think), it was suggested that this option be turned off. -
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. -
I'm sure there's a simple solution I've missed, but Aperture 3 won't open DNG files converted from Olympus RAW (ORF). Any suggestions?
BrianAperture 3.5.1 and the camera is the Olympus OM-D E-M5.
And yes, Aperture will convert the RAW/ORF files but the devil is in the details. And since you asked (sort of), here are the details:
I own and have happily used Photoshop CS4 for the layered compositing I like to do, but it won't support ORF files
I tried importing/converting them in Aperture then editing in PS4 ... but Aperture 3 and PS4 don't play together well, so many come back as "unsupported file format"
Apple can't fix the problem and Adobe no longer supports PS4... put another way, Apple can't do anythig but they care, and Adobe could do everything but they don't care
It got worse when I upgraded to Mavericks, so to get around that I had to upgrade to Photoshop CC and pay the monthly "rental"
Aperture and Photoshop now work, but the demands of running them both are beyond my aging iMac that can't be upgraded, so I have to buy a new one, but the monthly fee (which everybody assumes will only go up in cost) + purchase of a new iMac for a guy on a fixed income are too much
So, I thought if I used DNG to convert the ORF files I could import them into Aperture for all the basics and organization, then use PS4 for the compositing... but Aperture won't read the DNG conversions.
And that, as the man used to say, is the name of that tune,
Brian -
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.
SI 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. -
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>
Maybe you are looking for
-
Is there a way for a developer to detect if the Java plugin was blocked?
For best UX in my web application I'd like to know if Java has been blocked because of security vulnerabilities. If it's been blocked I'd like to show m own message that Java is out of date and they should update. I don't want to show it everytime Ja
-
OBIEE: Odbc driver returned an error
Hello All, While creating an answers on Oracle BI Answers, we are encountering the following error: Odbc driver returned an error (SQLExecDirectW). Error Details Error Codes: OPR4ONWY:U9IM8TAC I2DL65P State: HY000. Code: 10058. [NQODBC] [SQL_STATE: H
-
Mac OS X 10..4
-
Can we move account group from lower level to higher level
Hello Experts, I have now 1 level hierarchy in our organisation. Now we are planning to move from 1 level to 4 level. Now our problem is all sold to party (c002) and ship to party ( 5103) has same account group. We are going to assign sold-to-party
-
Hey Everyone, Just putting together an extension to get tracks from your iOS library into AIR as Sound objects inorder to access their SampleData. I haven't seen one around that needed what I wanted so I thought I'd share it with you all. At the mome