Why do G3 raw files show as "Unsupported Image Format" in Aperture?

I am moving towards shooting in raw, and as an experiment I imported some sample raw files from the publicly available text images on the Photography Blog. When I try to look at these images, I get a black screen with a warning triangle and the message "Unsupported Image Format". This happens for all the different raws, including some G3 raw files (.rw2). Oddly, it can read the EXIF metadata and has all the information about shooting settings etc. If I import the same files into iPhoto, it displays the images properly and allows editing, etc.
I have a workaround, which I've also tried with my Fuji X10 raws (still not supported on MacOSX), of running them through the Adobe DNG converter, and then looking at the dng files which seem to work fine. But it's a pain.
This has to be one of those simple "D'oh" things, but I can't see what I'm doing wrong!

Thanks Leonie, the second part revealed that I have been an idiot, although the behaviour is still surprising. The folder has a mix of DMC-G3 raws, Fuji X10 raws, and DNG files produced from both. For the Fuji X10 files, the DNGs produce images and the raws produce the "Unsupported file format" message. The latter is not surprising, the former a little surprising (as I've heard that DNGs only work when the associated raw works). The last two remarks don't directly address my problem (or perceived problem), but they perhaps set the frame for my expectations.
For the G3 files, when I look at it more closely, the G3 raws DO display correctly, while the G3 DNGs give "Unsupported file format". I had managed to fool myself into thinking it was the other way round (Aperture does rather hide the full file name).
So I was completely wrong, Aperture does support DMC-G3 raw, it's just it's DNG support that's a bit weird. However, it's on my side if I need to use X10 raws (via the DNG step). In fact so far I've given up the latter, as the noise levels are so much greater than in Fuji's in-camera JPEG conversion.
So, thanks very much for your help. Now I remember the first rule of system support: never trust what the customer tells you! (I know you're not really customer support, but I guess the same rule applies.) Thanks again

Similar Messages

D800 Raw files produce occasional 'unsupported image format'

Is anytone else having problems with some Nikon D800 raw (NEF) files in the latest Aperture version? Most of the files are fine, but some are 'Unsupported Image Format'. Aperture sometime shows them, then they vanish and are replaced with a grey triangle. Then randomly they sometimes come back.
It seems to just be the Nikon D800 raws casuing this. Any thoughts on a fix?
Thanks

It is unlikely to be caused by the recent Aperture update because it started happening to me just a few days ago (Nikon D2x NEF/JPEG pix) and I have been using Aperture version 3.3.2 under OS 10.7.4 for a long time.
Reconnecting the files in a referenced workflow has been resolving the problem for me.
-Allen

Nikon D70 RAW files now get "Unsupported Image Format"

Prior to March 12th, everything was working fine with my D70 Raw files. I now get the maroon "Unsupported Image Format" (USF) when I select the images that were previously fine. They show up for a fraction of a second before I get the error. I tried rebuilding the database to no avail. I can export the RAW files and open them in Photoshop so they are OK. Also now when I import from my D70 I get the gray box instead of the image and a letterbox maroon USF message, the EXIF data still imports and is associated with the image. Help. I did upgrade to 1.1.1
Dual 1.8Ghz Powermac G5 2GB RAM Radeon X800 XT Mac OS X (10.4.6)

Well, I can't really put my finger on it. I know for sure it happened post 1.1 upgrade, but it happened with 1.0 as well (I didn't do any troubleshooting when it first happened, just re-imported and it was fine.) The last time it happened it was the last 20 images on the original CF card, mostly in succession, but there were a few images that were still able to be read okay inside of that 20 image string. I reimported from the original card (thank God I had not erased yet!) and it was fine.
At least I know to keep my originals outside of aperture, what a space wasting bummer! I don't think I have any bad RAM because I've been running for 2 years without any real problems... The minor problems have happened, I believe with very tough weather conditions (humidity) and I experienced problems on all my Macs and even at work on windows. Maybe it was sun flares or static electricity, I don't know. The other issue is that my a/c power dips to low voltage often and my UPS switched to battery. I have a better UPS which always outputs 120v even when things sag or jump.
The only other thing I can possibly think of is that I have my Aperture library on a new Seagate 300GB drive that has only been used for images and sits dormant in my system except for scratch disk and Aperture. Actually, I did use it for about a month or two mirroring my boot drive with no errors, so I think the drive is good. Grr!
Troubleshooting rare occurances without have access to trace level data *****! (At work we can take a trace dump from our equipment and the guys can see pretty quickly what happened, and if it is hardware or software issue.)
To clarify, which Dual 1.8 do you have? The June 2004 one with only 4 RAM slots, or the 2003 one that was added to the original lineup with 8 RAM slots?
Aaron

My RAW files suddenly says "Unsupported Image Format" and can't import new pics

Hi all,
A week ago I imported the latest bunch of RAW-images from my Canon EOS 30D (.CR2-files) and all was working great. I did take some of the pics and exported them to an e-mail and sent them off to a friend. Then after rearranging my home office I was trying to import some pics from my iPhone 4 - won't work!
And the RAW-images are not supported any longer!...??
Facts:
- iMac 2,66MHz Core 2 Duo/4GB/OS 10.8.1
- Aperture 3.3.2
- Aperture Library located on a Netgear ReadyNAS NV+
Have searched for a solution without finding anything that works...
Have tried to:
- repair permissions
- examine database
- tossed com.apple.Aperture.plist to the trash
- am right now trying to rebuilding database as a last resort
Anyone have a good idea as I'm very reluctant to belive that rebuildning will work?
BR,
Pete

Thanks for your reply!
I've looked into it a bit.
The ReadyNAS uses Linux Ext3/Ext4 file system.
Found that my rights to Aperture Library has been downgraded to "Read only" even though I'm the admin...
Won't take changes either... Get a message stating that I don't have the privilage to change file rights...!!
I've just started a copy session of the 125 GB large Library to the internal HDD... It seems like a good idea to have it there - even though it's eating massive amounts of disk surface! Almost 20%...
I'm calling Netgear tomorrow - how the heck can may rights be changed, just like that???
Funny thing it's been working fine for a pretty long time, it's after Mointain Lion it has started to acting up.
I did have similar problems the day after upgrading to ML but after a firmware upgrade of the ReadyNAS it worked like a charm again - until yesterday...
Hope that I'm allowed to change the rights when it's been copied to the internal disk... Been typing and researching file system type etc for at least 15 mins now and it's still "preparing to copy"
Here's what I found in Console, the line called "2012-09-13 01:13:16,238" gave it away for sure (while trying to import new pictures).
2012-09-13 01:06:28,704 WindowServer[91]: CGXDisableUpdate: UI updates were forcibly disabled by application "Aperture" for over 1.00 seconds. Server has re-enabled them.
2012-09-13 01:06:33,213 WindowServer[91]: reenable_update_for_connection: UI updates were finally reenabled by application "Aperture" after 5.51 seconds (server forcibly re-enabled them after 1.00 seconds)
2012-09-13 01:07:50,105 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:07:50,383 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:07:50,956 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:07:53,224 WindowServer[91]: CGXDisableUpdate: UI updates were forcibly disabled by application "Aperture" for over 1.00 seconds. Server has re-enabled them.
2012-09-13 01:07:56,045 WindowServer[91]: reenable_update_for_connection: UI updates were finally reenabled by application "Aperture" after 3.83 seconds (server forcibly re-enabled them after 1.00 seconds)
2012-09-13 01:08:04,033 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:04,166 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:04,337 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:05,588 Aperture[4027]: The function `CGCMSUtilsGetICCProfileData' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance. Please use `CGColorSpaceCopyICCProfile' instead.
2012-09-13 01:08:06,937 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:07,037 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:07,257 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:09,069 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:09,137 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:09,700 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:09,726 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:10,330 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:11,463 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:14,680 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:45,151 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:50,593 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:50,646 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:50,753 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:52,368 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:54,564 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:08:57,876 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:07,732 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:07,785 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:08,613 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:09,289 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:11,050 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:30,529 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:32,090 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:32,114 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:35,890 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:36,622 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:41,105 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:42,018 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:42,064 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:43,558 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:47,057 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:47,372 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:49,190 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:50,757 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:50,771 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:50,786 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:52,494 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:09:53,835 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:00,281 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:00,299 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:00,314 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:01,799 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:03,490 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:03,528 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:04,393 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:04,410 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:04,434 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:10,510 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:11,671 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:11,724 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:12,487 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:15,266 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:20,511 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:20,559 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:24,635 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:26,227 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:32,667 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:32,729 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:32,767 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:41,388 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:41,410 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:43,233 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:43,277 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:10:45,381 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:13:16,238 Aperture[4027]: Document destination folder is not writable
2012-09-13 01:15:01,576 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer
2012-09-13 01:15:02,317 Aperture[4027]: ImageIO: CGImageWriteSessionFinalize Could not write any more data to the consumer

10.5.2; Canon 1DsM3 Raw Files = "Unsupported Image Format" in Aperture

Just did the update and pointed Aperture to a folder of Canon 1Ds Mark III raw files (standard raw files, no sRaw or anything like that). Thumbnail previews are grey and Viewer says, "Unsupported Image Format".
Tried rebooting and verifying/fixing permissions. No help. No thumbnails, no images in Aperture.
Canon 1Ds Mark III raw files do show fine in the finder and in Quick Look.
Message was edited by: Jon Roemer

I have the same exact issue.
I do get the same error with 1Ds MIII raws.
Also the G9 raws are not working.
Finally after 3 months it's still not working
I could imagine that there is the need to edit some property file (like I have read before in the forum somewere) to add the new cameras to the list of supported cameras.
Are the D3, D300 raws working?

DNG files labeled as Unsupported Image Format

I have used the Adobe DNG Converter and LIghtroom 3 to convert some raw image files from a Fujifilm S100fs camera, and then tried to import them into Aperture 3. In all cases, DNG files from this particular camera are labeled Unsupported Image Format, while DNG files converted from other unsupported cameras have been imported successfully into Aperture.
I think this is clearly a defect in Aperture that should be fixed, and I would like to know how a user is informed by Apple that a behavior has been identified as a defect and put on a list of problems to be fixed.

I can now add more details to my problem with Apple's treatment of DNG files originating from .RAF files created by the Fujifilm S100fs camera.
I took this issue to the Adobe DNG Converter forum, to investigate whether the DNG Converter was creating a Linear DNG file from these originals. I had read on Apple forums that the MAC OS would reject DNG files that were linear, and that this sometimes happens when the Adobe Converter encounters raw file parameters that it cannot handle, such as barrel distortion correction figures.
I have established that these DNG files from my S100fs camera RAWs are NOT linear DNG's. I found a helpful reader on the Adobe forum who had the tools and knowledge to look inside my DNG files, and ascertain that they were not Linear DNGs.
So I have exhausted the possibilities that the MAC OS is rejecting my DNG files for a recognized valid reason, and I return to my opinion that this is an Apple bug and needs to be fixed.

"Unsupported Image Format" in Aperture after editing in Photoshop?

I've had random intermittent problems with some files that I store in Aperture (I'm on 3.4.3) and then edit in Photoshop. I shoot only in RAW format on a Nikon D300 (.NEF files), and the images import fine. Some of the images I edit in Photoshop CS6. Upon saving the image in CS6 and returning to Aperture, I get a black preview image with a silver warning triangle, and it says "Unsupported Image Format". The info tab shows me that the image is a .tiff file as I expect - and what's odd is when I re-import these images from the folder they're stored in, they display fine as expected.
What gives?

All good questions, thank you for asking.
- Aperture is set up to export to 8-bit TIFF files.
- Photoshop is set as my external editor.
- To edit an image, when I'm in Aperture I right click on the image and select "Edit with Adobe Photoshop CS6"
- I don't use Layers in Photoshop, so when the image is returned to Aperture there's only the background layer.
- The images are saved in PS using "Save", not "Save As".
- I verified that the file names are .tiff rather than .tif
That is exactly what I am doing, when editing my Canon Raws in PS-CS6, and there is no problem with unsupported image formats. that should work!
and what's odd is when I re-import these images from the folder they're stored in, they display fine as expected.
Where is this folder? Are the images referenced? And if referenced, are they on an external drive? How is the drive connected and formatted?

CR2 as "Unsupported Image Format" on Aperture 2.1.2?

I just installed aperture on OS 10.5.5 and immediately installed the available update via Software Update. Then, I imported a day's worth of shooting from my EOS 1D Mark iii (one of the models listed on Aperture's Supported Raw Formats webpage - http://www.apple.com/aperture/specs/raw.html). The .jpegs display fine but my CR2 images only appear as preview thumbnails - when I click on the preview a red box appears with the text: "Unsupported Image Format." I'm a bit incredulous that Apple would fail to support this enormously popular image format - say it ain't so.
Message was edited by: Alexandra Latta

Excellent information that confirms my experience. It has only happened to me in the midst of an editing session, and has always been corrected by a restart of the application.
I don't know if it answers Alexandra's original question.
I have also found that Aperture has gotten progressively slower over the last few months, perhaps a function of a growing managed library?? It's to the point where if I edit to fast, I'll start getting beachballs, and have even had the app quit -or go to the red screen/unsupported file type message.
I don't have the latest machine, but it is a fast one, (Mac Pro Quad 3.0 Ghz 11 gb ram and the nVidia 8800 GT graphics card driving 2 23" Cinema Displays) My startup drive is a 750GB Seagate Barracuda partitioned 250/500 with everything but the Aperture library on the 250 partition (100 gb free space left) and only the Aperture library on the 500 partition (aprox 200 GB free). (there are also 3 more 750 gb drives in the machine for Time Machine & other stuff.
This machine should be really fast (it once was) so I may be doing something wrong, but can't figure what is wrong.
Is anyone aware of an article on speeding up aperture? My previews are limited to the default (2500 x2500 aprox) yet my activity window always seems to have a backup of previews to be built once I'm going in an edit session.
Any advice would be appreciated.
Thanks

"Unsupported Image Format" in Aperture and iPhoto....

I recently purchased a Nikon D7100 and when I try and upload the RAW pictures to Aperture 3 and iPhoto it gives me the error message "unsupported image format". It only happens with the RAW files, JPEG's are fine. Is this a problem with the program?

You are just going to have to wait until Apple adds support for the D7100 RAW format.
Allan

Why does my raw file show editing changes in the Organizer?

When I edit a raw (CR2) image and then save as a .tiff file and close, my original raw file also appears edited in the Organizer.
I have received advice telling me how to reset to default to get back my unedited CR2, but this is time consuming and I never had to do this in the past. How can I retain my CR2 in the Organizer after editing?

brevardlady wrote:
When I edit a raw (CR2) image and then save as a .tiff file and close, my original raw file also appears edited in the Organizer.
I suppose everyone expects the edits in the conversion of raw files to be shown in the organizer thumbnail... but that's your choice.
I have received advice telling me how to reset to default to get back my unedited CR2, but this is time consuming and I never had to do this in the past. How can I retain my CR2 in the Organizer after editing?
Instead of using 'Open', try using 'Alt Open'. The edited conversion is transferred to the editor, but the edits are not saved in the xmp sidecar filee. They are lost, and you are shown the default ACR settings, if that's what you want.

Why are my RAW files created by Vuescan so dark in Aperture?

I've been scanning images using Vuescan and saving as 16/48 bit RAW images. These images always look great in Vuescan but when I import these images into Aperture, the images are very dark. I need to do an exposure correction of +2 just to start seeing anything in the midtones. Ed Hamrick, the author of Vuescan, says this is because the RAW files have a gamma of 1.0 (coming straight of the CCD). If I save the same scan in TIFF format, the images look pretty much the same in Aperture and Vuescan.
My question is what benefits does saving in RAW bring given the large adjustments that I must make. I know I can automate the adjustments at import which might make this less of an issue but I wonder if saving in TIFF is nearly as good. Some of the pictures have a wide dynamic range with lots of shadow detail.
Any suggestions?
Thanks for any help.
Bob

My frustration has been that I am doing the processing twice which is pointless. I need to choose a workflow. Mind you that if Apple supported the full DNG specification, it would be able to deal automatically with these RAW scanned DNG files (I believe they are linear DNGs) and automatically compensate during import just as Lightroom does. I am using the trial version of Aperture - which I feel really comfortable using - but I think I may take Lightroom for a spin prior to making a final choice of software.
As I tried to clarify, there is no benefit in saving as RAW from a scanner. Just save as a normal 16-bit TIFF and you'll and up with a simplified workflow and no loss of data nor detail. Actually, a DNG is internally just a TIFF.
Mind you that if Apple supported the full DNG specification, it would be able to deal automatically with these RAW scanned DNG files (I believe they are linear DNGs) and automatically compensate during import just as Lightroom does. I am using the trial version of Aperture - which I feel really comfortable using - but I think I may take Lightroom for a spin prior to making a final choice of software.
If Apple fully-supported the DNG specification, then the RAW Fine Tuning adjustment would be available with its auto-exposure button to get a good starting point for tweaking the images.
You could provide Apple with feedback via, Aperture>Provide Aperture Feedback.
If I continue with Aperture, I am thinking that I will save these files as RAW TIFFs and do the gamma adjustment at import. This should streamline the workflow by making it possible to scan two 4x5s at one without the need to tweak each one in the scan and then do all my processing in Aperture (or Lightroom). I will just trust the scanner.
You shouldn't trust your scanner, just as you shouldn't always trust matrix metering or 'I'll fix that in post". Aiming for the best starting material is aiming for the best results. So instead, carefully examine each scan, which will not take you that long BTW.
I will still create the scanner profile of the IT8 target which I should then be able to use as a proofing profile to compensate for any color bias in the Fuji Provia film used. Perhaps I am wrong about this.
Actually, you're wrong on this. The IT8 provides an input profile, and not an output profile or working space. Imagine scanning a slide and printing it. Softproofing for IT8, then you can't softproof for your printer and vice versa.
Your post has allowed me to really think through my workflow and I really appreciate the input I've received in this thread. Now, I just wish I could get Apple to add support for Linear DNG (or whatever format Vuescan RAW DNG is which I know contains three colors per pixel rather then one as in Camera Raw) which would provide the additional tools to deal with these DNGs at import.
Although linear DNG support would indeed be nice for unsupported camera's, it is not necessary here. If Vuescan DNG has three channels, than it is a TIFF. (since demosiacing MUST have been applied, there are no scanners with a Foveon sensor as of yet)
Well to cut a very long story short just use TIFF for scans. It's a necessity for proper colormanagement and will simplify your workflow.

Unsupported image format after moving from one project to another

I scanned several thousands of images to my Aperture library. Went thru all of them providing adjustments to many of them, keywords to all of them and adjust date/time to all of them. All of the pics were visible, format is jpeg.
This is a managed library (all pics within Aperture db).
This morning started to restructure the project files (had three of them). After moving couple of hundred images to newly created project file I started seeing "unsupported image format" red screen after clicking the jpeg. 20-30% of the pictures clicked showed on viewer "unsupported image format".
Tried regenerating the previews. Tried command-option start with first fix the preferences option. Then with rebuild option.
Tried moving the pictures back to their original project file.
No joy... Still 20-30% of the pictures show the "unsupported image format".
Aperture 2.1.
Amy other tricks I could try?
Reported this to Apple aperture feedback of course.
--h

Link the two Macs together: there are several ways to do this: Wireless Network, Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
But however you do choose to link the two machines...
Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
Then launch iPhoto. That's it.
This moves photos, events, albums, books, keywords, slideshows and everything else.
+Note: there is no importing involved+
The thumbs appear, but the images are added 2 or 3 times each and the events are all messed up.
This happens when you import one Library to another, which you've done by drag and drop:
Creating a black library and over writing the new with the old.
Your problem is arising because of the Network Share. iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.
Regards
TD

Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
Please help.
William

Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

Unsupported image format from iPhoto

I just installed Aperture and excitedly moved an album of jpeg pics over from iPhoto to play with and do some corrections on. To my dismay, quite a few of them show the "unsupported image format" screen though they will be identical in format to the ones next to them. I reverted them all to original before I moved them and they are all jpeg. Any help with this would be appreciated. Thanks.

i can't make it out from your screenshot. are your pictures managed or referenced? it's very easy to determine if the problem is with a picture or with aperture. if it's referenced, just look it up with the finder and see if the system can read it. that way you know aperture's the culprit, otherwise you have some kind of disk corruption. if it's managed, you'll have to dig inside the library to look up the picture and do the same thing.
if your library is corrupt, the easiest way to fix it is to hold command and alt during aperture launch and select rebuild library. depending on the size of it, this may take a while. this should normally fix things, but as i said, it's important to check whether the problem lies withing aperture, or on disk.
j

Sudden "unsupported image format" after using Dodge & Burn Plugin

After using Dodge & Burn plugin for first time (seems great) one of the images suddenly turned into "unsupported image format" in Aperture. Just happened to one but its a critical one so I need to figure it out. Any thoughts?
Thanks - Robert robert (at) robertholland (dot) com
<Edited by Host>

scott nichol wrote:
if you keep the console open when you're editing these photos and the "unsupported image format" message comes up, you'll notice that Aperture is throwing malloc errors on the console. this means that while its trying to load the image, it is running out of RAM. the core problem here is that Aperture can't address more than 2GB of RAM and i think the only way that Apple can address this problem is by moving to a 64-bit version of Aperture. it would be really nice if this issue was addressed in a 2.2 release sometime soon as this happens to me all the time now after round-tripping an image to Photoshop.
i would not expect to have to quit and restart a professional photography application every time i finish editing an image.
Good to know. But I don't expect a .2 upgrade to be 64bits, a next major version of Aperture is more likely to be 64bits (Aperture 3), considering AP 2 is at the end of its development cycle and a new major release is due before summer.

Why do G3 raw files show as "Unsupported Image Format" in Aperture?

Similar Messages

Maybe you are looking for