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.

Similar Messages

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

I am running InDesign CS5.5 and trying to open an In Design File but getting an error message. " Cannot open the file "PDavidLCover.indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file

I am running InDesign CS5.5 and trying to open an In Design File but getting an error message. " Cannot open the file "PDavidLCover.indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file me be open in another application."Please help I really need to get this file open.

Since you've shown us the folder contents it's a good bet it isn't in use (no lock file). And it doesn't look like the file is mis-named as there doesn't seem to be anything else there that would be the .indd file (but just in case, open it in TextEdit and paste the first few lines here so we can see what the file header says), so the most likely case is the file is damaged. Is that on a removable device of some sort?
You can try the tool at Repair corrupt InDesign Adobe files on Mac OS X or send me a link to the file by private message and I'll try the recovery tool I have for Windows.

How to fix file when it says, "Cannot open file " ". Adobe Indesign does not support the file format, a plug-in that supports the file may be missing, or file may be open in another application." It worked one second, I saved and closed the file, then tri

How to fix file when it says, "Cannot open file " ". Adobe Indesign does not support the file format, a plug-in that supports the file may be missing, or file may be open in another application." It worked one second, I saved and closed the file, then tried to reopen and now it won't work. I am using Adobe InDesign CS5. It is the only version on my comp. I have tried opening on another comp & copying the file – same error comes up. PLEASE HELP

First check the version of the document with Jongware's script "Identify.jsx" (ExtendScript/JavaScript).
You can find it here:
[Ann] Identify Your InDesign File
If it is CS 5.5 or above, you need someone to open it in the version the script says and export an IDML representation from that. Another way would be to install a 30days version of CS6 or above (CC) and do it yourself.
In regards of the script showing a result for InDesign files higher than CS6:
CS7 = CC v9
CS8 = CC v10 = CC-2014 or CC2014.1
Uwe

Getting error "Cannot open the file "*****.INDD". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file may be open in another application."

How to fix this problem
"Cannot open the file "*****.INDD". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file may be open in another application."

When I have seen this message it is either when I try to open a document with an older version of Indesign E.g. an indesign 2014 document with Indesign CC.
The other time I have seen it is to open an Indesign CC document with Indesign 2014 which does not have Mindsuite - a plugin I use. Mindsuite, as yet, has not upgrade the plugin for Indesign 2014 therefore it recognises that a the document was created withe a plugin that the 2014 version does not have installed.
I believe your problem will be something like that.

How do I resolve the issue Cannot open the file ".indd". Adobe InDesign may not support the file for

How do I resolve the issue Cannot open the file ".indd". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing , or the file may be open in another application?

Shouldn't the CC version be able to open any file created in an older version on InDesign?
Yes, it ought to.
If the older file wasn't yours (if someone emailed it to you,or burned it on a disc, or whatever), then I am almost willing to bet you a beverage in the city of your choice that it's not a complete InDesign file. That is, maybe it was zipped and renamed, or the beginning or end of the file was chopped off during download, or something like that. The only reason I'm not actually making the bet is that there is a remote chance that I'd lose, and maybe you're in Adelaide or Khabarovsk or somewhere where the cost of airfare to me would make that bet a very expensive bet for me to to lose. So no latte for you if I'm wrong!
The script that Jongware posted will tell you what version of InDesign made the file to begin with. Additionally, if someone did something like rename YourFile.PDF to YourFIle.INDD, it'll report that it's Not An InDesign File. Because while SpectrumPCS is kinda right and that message can be generated when attempting to open a CS5 file in CS3 or whatever, it also spits out the same message when you just try to open an Autocad file, or a Windows system file, or a PDF, or any file that InDesign actually cannot open at all.

Panasonic tz60 raw not supported in Aperture 3. How to fix?

can anyone help me?

panasonic tz60 raw not supported in Aperture 3. How to fix?
Aperture's raw support is camera specific. The list of currently supported cameras is here:
Apple - Aperture - Technical Specifications - RAW Support
Apple focusses on cameras, that are most likely used by professionals. Your camera is an excellent camera, and I wish I had it, but so far none of the cameras in the Panasonic Lumix tz-family have been supported in Aperture. So send feedback to Apple, that you want this camera to be supported. You can use this form for a feature request: Apple - Aperture - Feedback
To be able to use your raw files in Aperture, you could try a few work-arounds:
Use the software, that came with your camera, to convert the files to another lossless format, eg. TIFF.
Or do, what I am doing with the raws from my Lumix FZ28 - download the free Adobe DNG converter and convert your RAWS to DNG format: Adobe - Adobe Camera Raw and DNG Converter : For Macintosh, I don't know, if that will work for your tz60 files, but give it a try.
If you have hopes, that Apple will support the camera soon, shoot RAW&JPEG for the time being, and work with the JPEGs, until hopefully the raw support will be released.
-- Léonie

Raw files not supported

I have a new Canon T2i and can't seem to get the raw files to open in Elements 8. I have downloaded the 5.6 camera raw update and the DNG converter and both say camera raw files not supported......now what?

function(){return A.apply(null,[this].concat($A(arguments)))}
I have also an EOS Rebel T2i since a few days and I experienced the same issue with Photoshop CS4. What next? !!!!
It's likely the next version of Adobe Camera Raw will handle it; Adobe updates ACR about every three or four months, and the most recent version was released in December:
http://www.adobe.com/support/downloads/product.jsp?product=106&platform=Windows

What Raw camera files are supported by Aperture Ver 3.6. I have tried to file a list of compatible camera models, but as yet can't find one.

What Raw camera files are supported by Aperture Ver 3.6. I have tried to file a list of compatible camera models, but as yet can't find one. My OS is OS X Yosemite 10.10.1. I have recently bought a Canon 7D MkII and have found Adobe Lightroom does not as yet support the 7D MkII. So I though Aperture may support the 7D MkII because Yosemite 10.10.1 now does.

Hi Folk,
I just found the answer to my question. Yes it is supported with OS X Yosemite 10.10.1. See the link below and the ***** Note at the bottom of the list.
http://www.apple.com/aperture/specs/raw.html

Just upgraded to Lion and can no longer import any .mov files ("file not supported") to 3.1.3. Also can no longer view any .mov or .mp4 files already in library.

Have been using Aperture 3.1.3 with no problems. Importing from a Nikon D80 (RAW & JPEG), Casio (.MOV) and Flip (.mp4). Could import and view all videos without issue prior to Lion upgrade. After Lion installation, can no longer import .mov files (get "file not supported" error) or even view any .mov or .mp4 files currently in library (even though thumbnail is present). Can watch the .mov files directly on my camera using Quicktime in Finder but can't even drag & drop that file into Aperture. Anybody else having similar problems?

Still no resolution and Geniuses at store could not assist. Unfortunately, it looks like not all the applications were ready to support the Lion operating system. We could not import any .mov files, could no longer view any .mov files already in my Aperture library and could not email any .mov files. Totally frustrated. Use Aperture almost daily and can't lose the video functionality. Was also running dog-slow. Constantly looking at the spinning wheel. Geniuses suggested that I wipe out hard drive and reinstall Snow Leopard. Had full backup on external drive with Time Machine.
Not an easy process though...had to reinstall several times (at 5 hours each time) because I continued to have issues. Finally figured out that I needed to delete every backup file from Time Machine on external drive from the date I installed Lion because some of the hidden files were still migrating back to Snow Leopard.
I had to:
1. Delete all time machine backup files from date/time of Lion installation forward
2. Do "clean" installation of Snow Leopard (wiped hard drive using disk utility and booted with Snow Leopard disc)
3. Chose option to reinstall from backup off Time Machine which eventually got me back to Snow Leopard desktop
4. Deleted Aperture program and reinstalled (I had to install Aperture 2 and then install Aperture 3 upgrade.
5. Reinstalled iLife apps
5. Applied all Apple updates available (again this took a few hours because there were several updates from Snow Leopard's original release plus Aperture 3 and other application updates)
Still doing some tweaking on some of my other apps but got everything back to where I originally was. Now plan to wait on a few version updates from Lion before reinstalling.
I am one of Apple's biggest fans, but was very disappointed in the fact that I lost functionality in one of their own pieces of software (which I use the most!) by installing Lion.

HT202020 Why are certain videos that I have taken with my iPhone 4 not supported by Aperture.

Why are certain videos that I have taken with my iPhone not supported by Aperture? That's weird. I expect that since both iPhone and Aperture are Apple products, file support should be seamless between the two.
Also, iPhone 4 does not appear as Camera Model in the metadata of the unsupported video file in Aperture . But other videos I have taken with the same iPhone 4 appear in Aperture and the Camera Model appears correctly. Why is that?

Have you done some cleaning and cleared caches on your Mac? Maybe the com.apple.xpchelper.cache file is missing. Check the folder /System/Library/Caches/
Re: Import video to Aperture library on Mountain Lion https://discussions.apple.com/message/19304702#19304702
If this file should be missing, you need to restore it from a backup or reinstall it by reinstalling your system.
Regards
Léonie

Acsm files not supported

when i try to download e-book it ask save/open when i click either it says acsm files not supported what am i doing wrong as it was working several weeks ago

Adobe Reader can only open PDF files; for .acsm files you need Adobe Digital Editions.

Requested extension com.adobe.Vibration is not supported for Windows-x86 Problem with Cs6,air3.4.

While compiling my application on Flash CS6 with Air for iOS 3.4, I am getting the error given below:
The content cannot be loaded because there was a problem loading an extension: Error: Requested extension com.adobe.Vibration is not supported for Windows-x86.
I am using vibration.ane file which got it from Adobe (http://www.adobe.com/devnet/air/native-extensions-for-air/extensions/vibration.html)
Anybody out there who knows how to solve this problem!
Thanks.

1) The vibration ANE from Adobe does not support Windows.
2) The iOS simulator (adl) is not a virtual machine but rather it is a native Windows app, thus the platform your app runs on is Windows not iOS.
What Adobe needs to do to avoid confusing everyone is one of two things:
1) Include a stub for Windows (and MacOS) in the Vibration ANE.
2) Make it possible to deploy an app to a platform where the ANE is not supported, but produce a runtime error upon an attempt to use the ANE. The developer could then put logic in the app to detect the underlying platform and make adjustments.

Tried Most Everything... Error Type of file not supported... codec not installed

Hi Friends: I have been battling with the error message of ... "Type of file not support or codec not installed." I have been throughout the forums searching for answers and attempting various suggestions. I am stumped and am reaching out for some wisdom and help.
1.)    System Gateway – T-6859u, Intel Core 2 Duo T6400 2Ghz, 4 Gig ram, Problem has existed on both Vista and upgraded Windows 7. I have used Premiere since Premier 5 (Full version not elements) including versions 6 and PRO. I have Elements on my laptop for convenience.
2.)    Assets- Problem exists with all AVI files. This includes files that worked previously but will no longer be recognized. I have used Elements since version 7 was new. It is only the last 4 months this has been and issue. These are AVIs that previously working in Elements 7 from Panasonic DV camera and other DV sources.
3.)    Problem first appeared when Windows Update installed security patch KB975560. Once the Security patch installed Premiere quit running AVIs. When the patch was removed Premiere worked again. However, windows update continued to reload the patch. The patch has now been removed and prevented from reloading. However, the problem now persists.
4.)    Other attempted repairs. Reloading Premiere Elements 7, Upgrading to Windows 7, Removing and reinstalling K-Lite Codec packs inc standard and 64bit. Loading LEADTOOLS. None has repaired the problem All the AVI files playback fine in other programs including Windows Movie Maker, Media Player Classic, WM player etc.
I'm not sure what to do next. I have been a dedicated Premiere user for so many years, I don't want to switch to another program. Any suggestions friends?
DrMark1105

Welcome to the forum.
What version of Apple's QT Player do you have installed?
PrE relies on this much more than its big-brother, PrPro, until CS5.
From my experience, QT 7.5.5 was my "last known good," and some problems have been reported with the 7.6.2 and 7.6.3 versions. 7.6.6 is out, and works well for many Adobe users.
I would investigate updating QT Player.
Also, FFDShow, an element in K-Lite has been death to PrPro for many people. Just having it installed brings PrPro to its knees.
Though Adobe hides its CODEC's pretty well, K-Lite has been known to shift the priority of the Adobe MainConcept CODEC's. While it does not overwrite them, or delete them, it sets up some of its CODEC's to take priority. There are some older threads on Registry editing and utilities to reset the priority of the Adobe MainConcept CODEC's. Seems that Robert Johnson participated in those discussions and may have furnished the link to at least one utility.
Those are all the thoughts that I have now, and none might be of use.
Good luck,
Hunt
PS - Robert has not been around here lately, but does spend time on the Muvipix Community forum. I'd post there in the PrE 7 forum, and ask if anyone has any ideas too.

[BUG] Adobe Bridge does not support OSX 10.10's "Go Back" keyboard shortcut and does not have a custom one.

Adobe Bridge does not support OSX 10.10's "Go Back" keyboard shortcut which is `command + shift + [` and does not have a custom one.
I tried "delete" key which is backspace for Windows. It will do delete identical to "delete X" key (which is delete key for Windows).
Sidenote: `command + shift + \` is to go back in views (switch views), not folder structure.

Exactly where do you want to use a GO BACK "shortcut" in Bridge? Maybe I don't even understand what you mean by Go Back. Bridge is only a file browser, nothing more. It doesn't open, edit, manipulate or save files at all.
Are you simply referring to going back to view a folder that you viewed before?
Please don't take this a criticism. As someone who will gladly pay money not to have to learn any shortcuts at all, I'm just puzzled and curious, that's all.

Adobe DNG files not supported in Aperture 3.1.2?

Similar Messages

Maybe you are looking for