RAW files corrupted in Aperture

With the upgrade to Mavricks and Aperture 3.5 I hoped my problems with RAW (ORF) images were over, but I am getting this again. Shooting RAW+JPEG and importing directly into Aperture, I'm seeing some image pairs like this:
I've gone in and deleted the plist, cleaned up the Aperture Library, no luck. Any suggestions?
Brian

leoni et al,
Seems there are two issues at work. One is the on-going problem with occasional RAW (ORF) images being corrupted. This post be a separate problem, e.g. using the Olympus in-camera "overlay" feature.
In the OM-D I can take up to 3 RAW images and overlay them in the camera; in this case I used 2 files, both are preserved and a new combined RAW image is recorded on the SD card.
Adobe Camera RAW, and the native Olympus Viewer handle this with no problem, rendering both RAW images plus a combined RAW image. However, when imported into Aperture one of the 2 original RAW files disapears and the other RAW file is corrupted and a JPEG combined file is produced (as pictured above in the OP).
Brian

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

Exporting raw files out of Aperture

How does one go about getting the raw files back out of aperture? I know that when opening the external editor it opens up in Tiff or PDS. I want to get my original Raw file out to being working with out the processing of the raw file in Aperture. Can any one help me?

Option 1. File>Export>Export Master... (also available by Right-clicking/Control-clicking on the selected thumbnails or by pressing Command-Shift-S)
Option 2. File>Relocate Master... and start storing the images as referenced files outside the Library.
Option 3. Use the search box in the top right of the forum pages...
Ian

Best iMac I can afford for Raw files work in Aperture 3

I'm looking to purchase a new iMac soon. I work mostly with a lot of RAW Nikon files with Aperture and I do a lot of adjustments with them. I'm debating between the 21.5" iMac but upgrading the processor to the i7, or, getting the larger 27", but can't affford the i7 with that model, would have to stick with the i5 processor. The xtra sceen real estate is nice of course, but would it be better to have the i7 processor since I could always add a second monitor to the 21.5" iMac for additional screen area for menus, etc...Would adding that second monitor affect my processing and/or graphics speeds at all, somewhat negating the xtra power from the i7 processor, or, would adding that 2nd monitor not really affect my processing and graphics power at all?
Also, the 21" and 27" base models have the same graphics card with 512mb vram, is that ok for Aperture with RAW file also?
Thanks!

All 2011 macs have nice performance improvements over previous models. However Aperture is a hardware hog: GPU, CPU, i/o, RAM. Those intending Aperture as an important app will do far better with the strongest available hardware in a given category.
The GPU will be key as to which iMacs are stronger, after that the CPU. RAM should be 8 GB via third party.
The second display will suck (some) power from the less-than-best GPU in the lower end iMacs. Note that every Mac is really a synergy of its parts to run Aperture, so it is hard to say how much effect a second display has onoverall Aperture performance, but I would not worry about it unless using a Macbook Air. I have a 17" MBP plus $300 Viewsonic VP2365wb and the setup works great. IMO for graphics desktop work a second display is a huge benefit.
IMO hard drives are obsolete as boot drives. If I was buying an iMac (I will not, preferring just-as-strong mobile Macbook Pros with their inexpensive SSDs instead) and could not afford the expensive iMac SSD configuration I would get an i5 model and have OWC retrofit an SSD into the Superdrive slot.
Note that iMac hard drives are not upgradable except by Apple so you might as well order a large hard drive now.
BareFeats.com has all kinds of relative graphics performance tests up (more coming), including this link:
http://barefeats.com/mba11_02.html
HTH
-Allen wicks

DMC-LC1 Raw Files Work in Aperture!

I've just imported a set of photos I took in New York with my Panasonic DMC-LC1, and was fully expecting the RAW files to be ignored, but they imported fine, I haven't had a chance to compare the quality with Camera Raw, but I'm surprised they imported at all. Does this mean OS X/Aperture actually support more Raw formats than Apple indicate?
2.1GHz iMac G5, 867MHz 12" Powerbook G4 Mac OS X (10.4.5)

Ah, thanks. Apple must have updated the list recently.
So far the quality of the images looks good, but not all metadata is imported for LC1 raw files, e.g. ISO is missing.
2.1GHz iMac G5, 867MHz 12" Powerbook G4 Mac OS X (10.4.4)

Raw Files Corrupted or Software Issue?

Hi guys, first post here! I have been looking for info on this particular issue but can not quite find an aswer. So here is my issue...
I shoot on a Canon 60D, have so for 2+ years always in RAW and now using Photoshop CS6 with the latest raw plugin. I just shot some photos and am having major issues, see below. This is how all of my RAW files look. Blown out, pixelated and just all around awful.
When looking at them in camera, they look fine as well as the thumbnails when transferred to my computer. However when I open them up in Photoshop this is what I get. Also, if I convert the imges in camera from RAW to JPEG and then transfer them to my computer they are fine and look the way they should. Any thoughts? Thanks!

The difference of the reply #4 shot and the initial shot that has very strong blue coloring, appears to be the use of flash which brightens the foreground with daylight-balanced flash lighting and minimizes the overexposure of the colored lighting, so while you can see the various colors, they aren't overexposed, which leads to banding as the channels clip at different points on the way to white. One issue with the reply #4 image, of the DJ, is that the blacks are not very black.
Back to the original topic: the files do not appear to be corrupted, nor does there appear to be a software issue. But the Adobe Camera Raw defaults don't look good for these pictures in extreme lighting.
I was able to extract the camera embedded previews for each shot using ExifToolGUI. These are reduced-size but should show the toning and color processing the camera would apply to its own JPGs. If these are not what you see for the JPGs from your camera then you might supply those as part of your shared dropbox folder.
I am using Lightroom 5.3 to do the comparisons which should duplicate the processing done by ACR 8.3, but it provides an easier to show side-by-sides as well as the processing applied in the last example. I am using a Windows 7 64-bit computer with a standard-gamut monitor that is profiled but that profile is close to sRGB so I have not taken the time to convert my screenshots to sRGB since they will almost be the same either way:
A comparison between the camera processed raw files and the Adobe processed raw files shows us that the default Adobe processing is more saturated, more contrasty and with harsh color transitions as compared the camera jpg. The Copy 1 is a virtual copy in Lightroom so I could reset it to default values and not touch the original user processing supplied in the XMP:
However, by merely changing the camera profile in the Camera Calibration section from Adobe Standard to Camera Standard we see almost the same rendering between Adobe and Canon, so if you're trying to start with the same place the camera rendering is, then just switch your camera profile to Camera Standard:
Now, the dropbox version of IMG_3277.CR2 came with an XMP file that has user settings that are much improved compared to the default rendering, and this includes quite a bit of change in the Camera Calibration sliders to reduce saturation and shift hues a bit.
Here are those user settings with the Adobe Standard camera profile at the left, compared to a pay-for VSCO Fuji film simulation profile along with using Auto Tone, Exposure -1 and Tint -150 to reduce the purple, on the right, but not quite as much as the OP's settings. I'm not saying mine is an improvement or that VSCO profiles are useful, just that there are many ways to adjust an image and color profiles can make a difference especially in extreme lighting situations as we have, here:

Raw file support in Aperture 3.2.2

Have recently purchased a Fujifilm EXR 600 compact camera. It can capture jpeg and RAW, but Aperture does not seem to recognise the RAW format - "Unsupported Image format"; neither does iPhoto recognise RAW. Is there any way to access and process these files?

Apple have historically been rather unresponsive with regard to supporting new camera RAW formats. Until they support your camera (if they ever do) probably you have to use the software that came with the camera (or some other 3rd party software) to convert the RAW file to a TIF and import that into Aperture.
Good luck.

Imported RAW files corrupted but JPEG ok. Will this be ok in my library?

One of three of my SD cards imported about 10% of its RAW files with great chunks missing. I actually saved the folder onto external hard drive before trying to import with LR, and I CAN see quite normal RAW file images using iPhoto, but the same images are still fragmented when I import them directly from the external hard drive.
EXcuse use my ignorance, but can I import the jpeg images using Lightroom's DNG copy option (so that they are more stable); and will I be able to use them, and work on them, just as effectively as with all the successfully downloaded RAW images?
OR do I have to go back to Iceland for these 100 photos?!
Thanks, Sandoise

Sandoise wrote:
looking at images on the camera screen
That does not verify raw data, only embedded jpeg preview, which you already know is OK.
Sandoise wrote:
I can see both RAW and JPEGS in iPhotos and they look perfectly good.
Well, seeing them in iPhotos does not mean raw data is good - it may also be showing just the embedded jpeg preview, which doesn't count.
Sandoise wrote:
Lightroom is the third way I've checked
Lightroom is for sure showing the raw (re-rendered) data, so it's the one to use to judge raw data integrity, as read by OS, from card, through your reader...
Sandoise wrote:
How else can I check the card?
It's "impossible" to tell whether problem is card or reader, unless you try a few different readers. Try a few different ports and a couple different systems too if you can, to rule out system/port/reader possibilities. If raw data is bad no matter which system, which port, which reader you use - it's bad on the card. You still won't know for sure whether the card is bad or the camera is bad, or something else happened.., but bad card is the most likely..

D90 Import Issue - RAW file corrupted

Hi Everyone,
Since moving from my Nikon D60 to a Nikon D90, I've been experiencing issues importing RAW (NEF) files into Aperture. Most pictures will transfer fine, but some will be corrupted. The corruption occurs regardless of source (from card reader or directly from camera) and is not deterministic (will import photo correctly one time and not the second time around). I have verified that this corruption is at the master level and not preview, since I can see the corruption displaying the image in a different application. I have not run into this problem using applications such as Picasa. Below are links to two example photos of the corruption. Has anyone experienced this too? (I am running Aperture with all updates installed)
http://home.comcast.net/~brycerocket/apertureissue.jpg
http://home.comcast.net/~brycerocket/apertureissue2.jpg

Are you perhaps importing directly into Aperture? I feel pretty strongly that card-to-Aperture or camera-to-Aperture handling of original images puts originals at unnecessary risk. I suggest this workflow from an earlier post of mine, first using the Finder (not Aperture) to copy images from CF card to computer hard drive:
• Remove the memory card from the camera and insert it into a memory card reader. Faster readers and faster cards are preferable.
• Finder-copy images from memory card to a labeled folder on the intended permanent Masters location hard drive.
• Eject memory card.
• Burn backup hard drive or DVD copies of the original images (optional strongly recommended backup step).
• Eject backup hard drive(s) or DVDs.
• From within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location." This is called "referenced images." During import is the best time to also add keywords, but that is another discussion.
• Review pix for completeness (e.g. a 500-pic shoot has 500 valid images showing in Aperture).
• Reformat memory card in camera, and archive originals off site on hard drives and/or on DVDs.
Note that the "eject" steps above are important in order to avoid mistakenly working on removable media/backups.
Also note with a Referenced-Masters Library that use of the "Vault" backup routine backs up the Library only, not the Masters. Masters should be separately backed up, IMO a good thing from a workflow and data security standpoint.
HTH
-Allen Wicks

File corruption in Aperture 2.1.4

recently I went back to work on photos I have opened many times. RAW CR2 format shot with canon 50D. The thumbnails look good but when I select one, it appears briefly in the large screen, but then I get a red screen with "unsupported image format". I exported as CR2 file and imported into lightroom and was OK. Aperture 1.5 was perfect and this version nothing but trouble. I get "black outs" when I try to adjust some images. After cropping and coming back to the photo later, it is uncropped. Just to mention a few problems.
Can you go back to 1.5??? What is going on??
Thanks for your help.

I had the same problem where photos were coming up with that **** red screen. Here's what someone suggested to me and it worked like a charm. Do a consistency check for Aperture. Launch Aperture while holding down the Command and Option keys until a window comes up with the option to do a consistency check or rebuild library. The consistency check will correct any issues with the permissions. Hope that helps.

Rebel SL1 RAW files unsupported by Aperture?

I am having trouble importing CR2 files from my EOS100D/Rebel SL1. Aperture is reporting that the file type is unsupported. I'm guessing that it's due to it being a new file format? Does anyone have a solution for this as yet? many thanks in advance.

The list of all cameras currently supported is here: http://www.apple.com/aperture/specs/raw.html
I don't see your new camera on the list.
Until it will be supported by Aperture you have several options:
Shoot raw & jpeg, and work with the jpegs as masters, until the raw support will be available, then switch to the raw master as original file.
Develope the raw with the software that came with your camera and convert it to another supported lossless format - e.g. tiff. Use the tiff in Aperture.
Convert your raw to dng with Adobe's free dng converter and work with the dng files in Aperture.
Regards
Léonie

Not all RAW files recognised by Aperture 3

I am running the lastest update of Aperture 3 with the most recent RAW compatibility pack. (Can't remember what number but I updated last night).
I have a Leica D-Lux-5.
I import RAW photos using the card slot on my iMac i5 running Snow Leopard.
The card is a Sanddisk Extreme 16GB (might be 8GB)
The problem is that some (not all) are listed as 'unsupported file type' where the photo thumbnail should be.
Has anyone got any thoughts?
Craig

Ir. Bob,
Thanks for the response. Not sure if this worked - The RAW's I took last night still show up as 'Unsupported Image Format' - but then it may not work retroactively - I will take another sample batch and let you know.
Thanks,
Craig.

Preview thinks RAW files corrupt

I used to be able to open my .CR2 files from my Canon Rebel XSi w/ Preview after I installed the Camera Raw pack 2.1. Now I get this error (screenshot: http://img399.imageshack.us/img399/1658/errorfk5.png). This is happening around the time I began using Adobe Lightroom. Is there anyway I can reset Preview? Like is there a library folder or something I can look into?
Thanks.

HI Andrew,
Might be a corrupted Preview preference file... try this:
go here; MacintoshHD/Users/Library/Preferences. Open the Preferences folder, locate this file:
com.apple.preview.plist Drag that folder to the Trash, empty the Trash and reboot.
See if that makes a difference.
Carolyn

RAW files being corrupted by Aperture

Some of my RAW files stored in Aperture come in clean but eventually show up as corrupt. Specifically, a rectangular portion of the image will become banded with colors that don't belong there.
Sometimes I see this happen to a file just after some simple operation--say, adding a keyword. Whats' going on?
Here's an example.
http://lyonsimaging.smugmug.com/gallery/3547082

Just to add my own recent image corruption problem. I was getting a pattern on some images, almost like heavy rain in vertical streaks. I thought it was an Aperture bug at first as it only appeared in Aperture. However, I could transfer images to other apps, and the fault had gone. The fault was only occurring when using the Highlight and Shadow tool.
Thanks to a suggestion here, I finally found it was caused by my graphics card. I upgraded from my original Nvidia 5200FX 64MB, to a Radeon 9600XT 256MB. I was able to refit my old card, and the faulty was fixed. Turned out that the Radeon was overheating (these appear a lot in other forums, and an upgrade to the cooling is recommended). I have now refitted it with a Zalman copper cooler, and heat sinks to all the chips, and the problem seems to be cured.
It does seem strange that yours are corrupted back to the master though.

Aperture wants 825 MB more diskspace, but my HD has 630 GB free space. A perture doesn't let me import my latest raw files. What's the problem?

Hi, I have Aperture 3.2.2 installed on a iMac with OS 10.6.8
While I plug in my Nikon to import my raw files from today, Aperture tells that I need 825 MB more space on the disk.
But actually I have more than 600 GB free space on my HD. So what is the problem? What should I do?
Any ideas?
Cheers
Andreas

Not sure.
Try these, though:
. Empty Aperture Trash
. Close Aperture
. Empty system trash
. Reboot
. Try the import again.
What does Finder tell you about the free space on the drive volume in question after you've emptied the system trash?
Are all of your Image's Masters managed?
Are you sure you have Aperture set to import to the drive you want?

RAW files corrupted in Aperture

Similar Messages

Maybe you are looking for