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

Similar Messages

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

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

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

Aperture gets "Unsupported Image Format" on some JPG images

I'm using Aperture 1.5.2 "trial" on PB 15" with OSX 10.4.9. I am getting "Unsupported Image Format" on about half of the 15,000 JPG images that I have on my HDD. But not all of them - even though all images come originally from my D100 camera and are JPEG images. These are all JPEG images with extensions JPG, jpg and jpeg. No RAW or TIFF.
My images are currently catalogued in iVew MediaPro [IVMP] and I'm interested in switching to Aperture. So I've gotta find a way to import those photos.
Here's a clue: When I put the CF card from my camera into the computer yesterday and tried to add the images to Aperture it reported that all the images on the CF chip were "Unsupported Image Format." I was not copying the images - just leaving them im place. As a test, I then used IVMP to import from the CF card onto the HDD, into a directory. Afterward, I fired up Aperture and it could properly index and display the files. I noticed that the pre-existing images that are viewable in Aperture all have previews when viewed in the Finder. Also, they've all been imported from CF to HDD using IVMP, so there may be some processing going on there. I also tried reading files into Photoshop and rewriting them with previews, which I verified in the Finder, and those files also can not be viewed in Aperture. So it is not just a question of having a preview - it's something else about the files.
Another clue - when I shoot more than one CF of photos in a day, I use IVMP to import the first CF batch, and those are always visible in Aperture - but IVMP doesn't let you import two batches on the same date (pretty goofy huh?) - so to import an additional batch I have to (Finder drag-drop) copy from the CF to the HDD into a directory - and those files have no previews, have not been imported thru IVMP, and interestingly are not viewable in Aperture.
So I'd have to conclude that iView MediaPro is doing something to "tame" the files' format that makes them acceptable to Aperture. But I want to dump IVMP, so there has to be some other way to make these D100 files acceptable to Aperture.
I either need to "fool" Aperture into reading the files or find a way to tweak 'em and make 'em acceptable to Aperture. Any ideas from other iView/Aperture users out there?
PB 15" Mac OS X (10.4.9)

Good idea, but I checked it... I mentioned reading right from the card in order to illustrate that the JPG files are "unsupported image format" even *right from the camera*. *In fact* the CF is not the differentiating factor between renderable and non-renderable. The real factor is whether the files went thru iView Media Pro or not. Files that were drag-dropped from the CF into a folder are not renderable by Aperture and files that were imported first (from the CF or from another folder) thru IVMP into a folder are renderable.
Yesterday I confirmed again that GraphicConverterX does not fix the files if I import and then rewrite with additional options turned on. It also sees the same IPTC data and EXIF on both a "good" file and a "bad" file. Identical. I also fixed the OS9 creator and filetypes so they're <none> and that didn't fix anything - some good files and some bad files have this configuration.
Ah another COOL THING - I just loaded a CF card into the computer and brought up Aperture - it immediately recognized the card and showed me two previews - one for a NEF (Nikon RAW) and one for a JPG. The previews looked fine. I clicked to have it import the photos. Once imported, the NEF looked OK, but the JPG had a grey preview and then "Unsupported Image Format" on the large version. I think this confirms the file format is a problem, but then why was Aperture able to gen a preview when the file was on the CF chip but not after it was copied to the HDD?
I double-checked this by copying in Finder drag-drop from the CF card to the HDD and then importing the same two photos (NEF and JPG) from the HDD, and indeed the NEF was renderable and the JPG was not. For me this confirms that there's something about the file format that Aperture can't deal with.
I then imported the same two files using IVMP (Media Pro) and as expected, both files could then be "imported" and rendered by Aperture. So IVMP is doing something that makes Aperture really happy.
In case someone can actually compare the two files - I have put up a "bad" and a "good" JPG - it's the same image from a Nikon D100, but one of them (bad) is right from the camera and the other (good) was imported by IVMP and somehow is acceptable to Aperture. Any intelligence that anyone can add based on these files would be useful.
http://fire.red7.com/aperture-tests/DSC_0070-good.JPG
http://fire.red7.com/aperture-tests/DSC_0070-bad.JPG
PB G4 15" Mac OS X (10.4.9)

After loading Lion I cannot open some pictures. I get Unsupported Image Format. It tells me picture was taken with Canon EOS Rebel with unknown lens

After loading Lion I cannot open open some pictures in Aperture. I get Unsupported Image Format, all files even the ones I can open are .JPG. Also it tells me picture was made using Canon EOS Rebel with unknown lens.

You mention that 'most' of your files are DNG. Try
running the effected files through Adobe DNG
converter again and then import your reprocessed
files to Aperture and see if the problem persists.
I had a problem with a batch of D2x files converted
to DNG which had been metadata tagged by
PhotoMechanic (the evil app).
B.T.W. You mention that you had been using Bridge.
Are you getting any of the embedded XMP metadata
coming into Aperture during the import process?
Already tried that multiple times...no luck. I'm wondering though if it might be related to metadata as you suggest. I'm still trying different things to see what happens.
I was able to alleviate the problem on one set of images by painstakingly searching my external drive for the oldest backups I could find - CR2 files from before DNG conversion. I then ran those through DNG Converter and tried importing them again (this time, I embedded NO thumbnail, but I'm not sure if that made the difference - I think it was more likely a fluke in the original conversion that caused the problem). This time, it worked.
Now, the big problem is that I still have a couple hundred images for which I can't seem to locate the original CR2 files. I don't typically keep them after conversion, as I don't have the space for both.

NIKON D70 RAW files do not work since upgrading to Aperture 1.1.1

Prior to the software update to 1.1.1 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. I have not seen any posts relative to this issue and wonder if there is something else going on.
Dual 1.8Ghz Powermac G5 2GB RAM Radeon X800 XT Mac OS X (10.4.6)

Try this...it seemed to have solved several people's instability issues:
If this doesn't work, post one of your images for people on the forum to check your images.
repairing disk permissions in safe boot mode:
1. To Repair Disk Permissions in Safe Boot restart your computer while holding the Shift key
2. Do not let go of the Shift key until your screen says Safe Boot
3. Once you see the screen with the words Safe Boot let go of the Shift key. If you need to login, login
4. Open Disk Utility located in the Utility folder of your Applications folder, it'll be down at the bottom
5. Select the hard drive that contains your OS & make sure that First Aid is selected (highlighted) in the Disk Utility window
6. Select Repair Disk Permissions
7. When Disk Utility has done its job you'll see the words "Permissions repair complete"
8. While you're at it & since the system is in Safe Boot I'll Verify the other hard drives & Repair them if they need it
Once the utility program has run through the operating system you can quit the application and restart the computer
I routinely use the Repair Disk Permissions feature in the Disk Utility application on Mondays (Maintenance Monday) so I park an icon of it in the Dock. It is a good idea to Repair Disk Permissions more frequently if you are power editing for many hours at a time or the application you are working on begins to misbehave.
Regardless of what application you are using (unless there is a known bug in the application) Repairing Disk Permissions will take care of many problems.
It is recommended to Repair Disk Permissions before & after installing software or software updates

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.

Get Unsupported Image Format

I have a library that is iPhoto maintained(V 9.4.2). I am trying to read the library with Aperture (V 3.4.3). I get many thumbnails which are black with a triangle and opening the Project I get a black image with "Unsupported Image Format". I do not have this problem when viewing the same library with iphoto - but on checking, the projects concerned in Aperture are not present as Events in iPhoto. Also within a Project in Aperure I am getting "black" images. When I compare the equivalent Event in iPhoto those images are not shown. It seems as if Aperture may be picking up photos which perhaps have been deleted in iPhoto?
Has anyone else seen this? It is not the result of importing since I am only pointing each of the two packages (in turn) at the same library.

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

Errors converting Nikon D70s RAW files since yesterday

Yesterday i've installed "Digital Camera RAW Compatibility Update 2.2" which seems to be the cause for some really nasty problems with Nikon D70's RAW files.
Now (some of the) files will simply display a dark red image just displaying "Nicht unterstütztes Dateiformat" (means "unsupported file format").
Will there be a fix like "Digital Camera RAW Compatibility Update 2.3" quite soon?
Is there any chance to go back to 2.1 ?
Please, provide me some hint on what to do next.

I have this problem myself, and others have reported it too, and that was before the this new "Digital Camera RAW Compatibility Update 2.2" was released.
It looks like a bug in Aperture.
Just search for "Unsupported File Format Error" to see more reports.
Try sending them feedback with the pulldowm menu item.

Nikon D70s Raw files extremely noisy

I have a bunch of NEF files from my Nikon D70s that look terrible when imported with Lightroom (or Photoshop on the Mac or iPhoto or Photoshop on the PC, for that matter). Here is a screen capture of one of the photos at 1:1 zoom:
http://solace.stanford.edu/~beers/Photo/lightroom.png
And another, from iPhoto:
http://solace.stanford.edu/~beers/Photo/iphoto.png
Note the "maze-like" pattern that is embedded into the image, making it useless except when downsampled and blurred.
Here is the same image read into Picasa (which also apparently reads camera raw files) on the PC:
http://solace.stanford.edu/~beers/Photo/picasa.png
The pattern is gone and the image is usable.
This is happening on my Mac running Leopard in Photoshop CS3, Lightroom (both using ACR 4.3.1), iPhoto, and Photoshop CS3 on the PC. Anyone have any idea what is going on?
Andrew

> I believe only pictures from that particular setting (grey background, grey rug, softbox lights, etc.) exhibited the noise in question
Hold on. Did you use some filter as well? Was there some strong light from the side?
> you suggest that there are multiple raw images which are combined?
No. I am not sure what you mean, perhaps the two different greens?
The pixels sites have filters over them: green, red or blue. They are arranged in a regular pattern; in case of the D70 this pattern consists of two rows of two pixels each. The first row contains a blue and a green pixel, the second row starts with a green and then a red.
If you download this image and view it in at least 600%, then you see this arrangement. (This image is very greenish, mainly because half of the pixels is green, while only 1/4 of them is red and another quarter is blue. This is a non-demosaiced image.)
http://www.panopeeper.com/Demo/Andrew_DSC_0014_crop.tif
The values of green pixels, which are "diagonally neighbours" should be close to each other on the relative uniform areas, like the face, but they are not. You can verify that on this image as well if you increase the magnification even more, so that you can navigate over the pixels; however, the numerical differences you see here are much reduced from the original differences.
Anyway, I was referring to the green pixels in the alternating rows, once beside reds, once beside blues; they responded very differently.

IPhoto won't import Nikon D70 raw files after upgrade to Leopard

I recently upgraded to Leopard, and yesterday, I hooked my Nikon D70 up to the computer. iPhoto auto starts, and tells me that there are pictures to import. When I click the import button, iPhoto tells me that it is importing the photos, (which are in Nikon raw format) but in fact, it is not. The photos don't "flash" across the screen as they are being imported as they used to. When iPhoto thinks it is done, there are no new photos on my hard drive. A spotlight search confirms that fact.
Jpeg photos still import just like they used to. Only raw photos don't import.
If I manually open iPhoto, and click on file then import, I can find my cameras CF card, and highlight the photos I want to import, and iPhoto will then import raw photos. It won't import them with the simple attach the camera, one click import that I have grown used to. My D70 is a supported camera for iPhoto, and it used to work in OSX 10.4. Is there a setting I'm missing somewhere?
Thanks in advance for any help offered.

I had the same prob with my mac and my D70.
I did an upgrade to leopard from tiger. After that, iPhoto would not import photos. The camera and pics would show up in the app, and would let me try an import, but it would come up with an error saying "20 photos were in an incompatible format and could not be imported".
Since upgrading to Leopard, image capture wouldn't work either. App would run and then wouldn't. Would crash and error. Wouldn't import photos at all either.
I was able to manually drag photos from my camera to the desktop and then import into iPhoto.
iPhoto wasn't the only thing playing up on my mac (networking, file permissions, backlit keyboard, software update, ffmpeg app were all problematic), so I backed up everything I wanted to keep to an external drive and did an erase and install of Leopard. This has fixed practically every problem I had. Do the same if you can, cos it has made my mac a pleasure to use again.

Suddenly getting "Unsupported Image Format" throughout library

What happened? I have lots of projects, with Nikon D3x, and I'm suddenly getting this message, along with the maroon background.
I tried regenerating library, that didn't solve it. I tried using Quick Preview, that didn't solve it.
What could be doing this?

Also this is happening on my Mac Pro with Snow Leopard. Quad core Nehalem model, 32 GB memory, 4x2GB Drives with Apple RAID card, ATI Radeon gfx card.
my MacBook Pro works fine.

Canon G7x and unsupported image format icon with RAW files.

When RAW files downloaded from Canon G7x get "Unsupported Image Format" message. Using iMac with 10.9.5 and Aperture 3.5.1. This is a new camera and is not on the supported list. Is there a way around this? Now that Aperture is static will new cameras continue to be added to supported list?

The only way 'around' it is to upgrade to the required Aperture and/or OS version. So you will need to wait for that to happen. In the meantime you could shoot Raw+JPG, use the JPGs now and when (and if) the camera is supported (or you move to a different program) you will have the Raw files.
As for camera updates in Aperture, no one here can say what Apple intends, we;re just users here like yourself and even discussing this is technically against the TOU of these forums.
But I think it is safe to assume, as Apple will continue to support Raw processing and that the Raw processing is done at the OS level and they have said they will support Aperture at least through Yosemite's life cycle that any new Raw format added to OS X will reusable by Aperture. But that's only a guess.

EOD350D/ Digital Rebel raw - unsupported image format ?????

From the raw tech spec page:
Supporting the RAW formats from all leading digital camera manufacturers (including Canon and Nikon), Aperture provides optimized support for such market leading cameras as the Canon EOS 1Ds Mark II, Canon EOS 20D, and Nikon D2x as well as the highly popular Canon Digital Rebel and Nikon D50. It also supports the Adobe DNG format.
URL: http://www.apple.com/aperture/raw/
Well, I must be doing something wrong. Ik can see the thumbnails, but once imported I always get 'Unsupported Image Format'.... This is what most aften see in Aperture. I must be overlooking things....
EOS 350D with firmware version 1.0.2
iMac 2GHz/1.5GB RAM Mac OS X (10.4.3)

Ok, messing around in the raw.plist fixed this. Is not an Aperture issue, more an OS X 10.4.3 issue --> http://minimal.cx/2005/11/01/make-os-x-1043-understand-canon-eos-350d-raw-files/

Nikon D70 RAW files now get "Unsupported Image Format"

Similar Messages

Maybe you are looking for