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.

Similar Messages

  • 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)  

  • Unsupported Image Format After External Editor

    I have Aperture set up with Photoshop Elements 6 for MAC as the external editor. I have PSD(16bit) 300 dpi. I have used this external editor several times in the last two days. The most recent time I had a problem. It started PSE 6 as requested and displayed the picture with a *.pdf filename. I used the filter option I wanted and was satisfied with the result in PSE 6. I saved the file and quit PSE. It came back to Aperture and displayed two images: the original on the left and the edited on the right. After one or two seconds the image on the right (the result of the edit) was replaced by a dark red background with the black text Unsupported Image Format displayed. If I click on the right image, the edited image appears briefly and then reverts back to the error display.
    As I said, I used this only the night before several times with no problems and I have not changed my Aperture preferences since then. The master file is a Canon cr2 file and I did some Aperture corrections before I decided I needed to run a filter in PSE 6.
    Thanks,
    Bruce

    I'm having a similar problem with unsupported images. The problem has occurred when I use an external program to create an image. I've tried creating them as TIFF and JPEG. If I use the Sony Image Data Converter (v2 or v3) I get the unsupported image format.
    Last night I was scanning film with Silverfast, creating TIFF files and using them in Aperture 2 as referenced files. Everything was fine. This morning I did the same thing and got the red Unsupported Image Format screen from the same original image.
    I have found if I import the unsupported image into the Aperture library instead of using it as a referenced file it usually works. I don't like this solution because it messes with my work flow and I'm trying to keep the size of my Aperture Library under control.

  • 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

  • After upgrading to Mountain Lion, I cannot open my File Maker Pro files. Can I use Numbers to open these files?

    After upgrading to Mountain Lion, I cannot open my File Maker Pro files. Can I use Numbers to open these files?

    Numbers is a spreadsheet program and FileMaker is a database program, so you probably can't use Numbers to open them unless you had first exported them from FileMaker in a spreadsheet-compatible format.
    If you upgraded from 10.6 Snow Leopard or earlier and your old copy of FileMaker won't open anymore, it might be a PowerPC application that is not compatible with 10.7 and later. If that is the case, to work with your FileMaker files you should upgrade your copy of FileMaker to the latest version, which seems to be FileMaker 12.

  • After loading Lion 10.7 I'm no longer able to use Quicken 07. Any work around?

    After loading Lion 10.7 to my Desk Top, I'm no longer able to use my Quicken 07. Is there a work around? All my financial records are in Quicken 07 or do I need to remove Lion 10.7 from my computer

    Quicken is a PPC application. They will not work in Lion because Lion no longer supports Rosetta emulation.
    1. You can downgrade to Snow Leopard.
    2. You can switch to Quicken Essentials.
    3. You can purchase a different application that provides similar services for you. Examples are MoneyDance or MYOB.
    Downgrade Lion to Snow Leopard
    1.  Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button.  When the menu bar appears select Disk Utility from the Utilities menu.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Quit DU and return to the installer. Install Snow Leopard.
    This will erase the whole drive so be sure to backup your files if you don't have a backup already. If you have performed a TM backup using Lion be aware that you cannot restore from that backup in Snow Leopard. I suggest you make a separate backup using Carbon Copy Cloner 3.4.1.

  • Just upgraded to Lion and cannot open files on my old SL partition - permissions error

    I have just installed Lion on my 2008 MacPro on a new internal HD and cannot open word/text etc  files on the original Snow Leopard disc.  I get a permissions error.  I can preview the file but not open it.  When I do a get info, I can add my user and give it R&W permissions but still cannot open the file.  I have a third disc with just videos and no system and this is OK.
    For information my upgrade method was as follows:
         Install blank hard disc and fromat it.
         Clone original HD onto new drive using CCC
         Give it a new name
         Boot from the new clone and go through the lion install
         Update the new system to 10.7.4
         Repair disc permissions
    Through this method, I have a duplicate set of files on the Lion partition and these I have no problem opening, it is just those on the SL disc.
    Any ideas as to how to fix this.  I did the duplication as I still want to be able to boot from SL for some old applications and hardware (a film scanner being one).
    Thanks
    Dave

    Softwater,
    Well, I booted back into SL, and as I mentioned, I did have filesharing enabled.  So I added the whole disc as shared and re-booted back into Lion.
    Still no luck. I get exactly the same permissions error and cannot open any files.  This seems crazy that from Lion I cannot open files on other bootable partitions.
    I added myself as a RW permission on the disc via Get info and still cannot see the files. This is very strange behaviour.  According to get info on the disc, I have full read/write access and on the file itself.
    I can see all the files on non-bootable partions.
    Dave

  • Why Safari 4.0.4 cannot open some web pages?

    Safari 4.0.4 cannot open some web pages, while Firefox 3.5.7 works like a charm.
    I tried to open http://www.bdnews24.com/bangla/ for which Safari gets stuck (never opens the page, except for the first word of the first line), but Firefox shows the page very well. The same problem happens for some other web sites as well (e.g. http://www.prothom-alo.com/).
    (I have Ekushey Bengali AAT fonts, and they are working fine in Firefox and other applications. So this cannot be a font issue.)

    HI,
    From the Safari Menu Bar, click Safari / Empty Cache. When you are done with that...
    From the Safari Menu Bar, click Safari / Reset Safari. Select the top 5 buttons and click Reset.
    Go here for trouble shooting 3rd party plugins or input managers which might be causing the problem.
    http://support.apple.com/kb/TS1594
    Make sure you are running Safari in 32-bit mode. Right or control click the Safari icon in the Applications folder, then click: Get Info In the Get Info window click the black disclosure triangle next to General so it faces down. Select 32 bit mode. Also, (in that same window) make sure Safari is NOT running in Rosetta.
    In case it could be a font issue in the future this may help.
    Try clearing the font cache. In order to do that you need to boot in Safe Mode.
    Shut down your Mac.
    Press the power button.
    Immediately after you hear the startup tone, press and hold the Shift key.
    Release the Shift key when you see the gray Apple and progress indicator. During startup in Mac OS X v10.4.x or later, you will see "Safe Boot" on the login window, even if normally you log in automatically. Boot time is a minute or two longer than a normal boot.
    After your Mac boots to the Desktop restart the computer normally, without holding any keys during startup.
    What this process does... It moves to the Trash all font caches normally stored in /Library/Caches/
    Restart your Mac and try Safari.
    Carolyn

  • Quicktime not working after loading Lion. It is in Applications folder. It is dark when trying to play. Audio is there, no video. Is something set wrong?

    Quicktime not working after loading Lion. It is in Applications folder. It is dark when trying to play. Audio is there, no video. Is something set wrong?

    It is supposed to be dark.
    Is it all videos that don't display or just some. You may have installed something like Perian or Flip for Mac that translates the video codecs for Quicktime. They may need updating.

  • Problem:  this mac is not reading an excell file after upgrading to yosemite.   My Mac is from 2009, it use to work perfectly but it wasn´t able to open some apps, thats why i upgrade it.   Now it once i donwload the zip it appears with an ".ods" ext

    Problem:  this mac is not reading an excell file after upgrading to yosemite.   My Mac is from 2009, it use to work perfectly but it wasn´t able to open some apps, thats why i upgrade it.   Now it once i donwload the zip it appears with an ".ods" extension
    i even already download a link
    http://www.microsoft.com/en-us/download/confirmation.aspx?id=44026
    which i read on another support page... but it doesnt allowed me to install it cause it says that i already have the disk of this program....
    Im afraid to erase it and not being able to get it back...
    What can i do!??
    Thanks in advance for this kind answer!!!

    fsolution wrote:
    Problem:  this mac is not reading an excell file after upgrading to yosemite...   Now it once i donwload the zip it appears with an ".ods" extension...
    If the "it" refers to a compressed (zipped) spreadsheet that you downloaded, the ".ods" extension is used by LibreOffice and probably OpenOffice (which are free versions of MS Office) for spreadsheets, which would suggest that wherever you're getting that "Excel" file from has switched to one of those programs. I've tried opening an .ods file from LibreOffice using MS Office 2013 for Windows and it does open though with a warning that some things have been changed. I don't know if Office for Mac can normally open .ods files. But if your need is to just open .ods files, take a look at LibreOffice.

  • After migration to a new macbook i cannot open photoshop. I get error message "you can't open this application "adobe photoshop cs" because powerpc applications are no longer supported"

    after migration to a new macbook i cannot open photoshop. I get error message "you can't open this application "adobe photoshop cs" because powerpc applications are no longer supported"

    You cannot run Photoshop CS on a new Intel-based Mac running OS X Mavericks. CS is far too old.
    You'll have to buy Photoshop CS6 or Photoshop Elements 12. Or subscribe to CC.

  • After Loading Lion I now get 5 windows w/ a graphic of a Red Stop sign with an ! mark and the following text message: "DAVE Networking  Dave kernel extensions could not be loaded! Error 71 - Too many levels of remote in path."

    After Loading Lion I now get 5 windows w/ a graphic of a Red Stop sign with an ! mark and the following text message:
    "DAVE Networking 
    Dave kernel extensions could not be loaded! Error
    71 - Too many levels of remote in path."
    I have uninstalled DAVE and used Clean App to remove trace elements of program, however I still get the message and am unable to eliminate the error messages.  When I click OK the message goes away briefly and then comes back up.
    Any solutions would be great.

    Dave,
    Thanks....What I did was load the free eval version of Dave 9.0 and then used the uninstaller which must have deleted the kernel giving me the problem. 
    Thanks for the response.
    Razor

  • Cannot open some PDFs on Macbooks

    Hi folks! I have Macbook (2008) and Macbook Pro (2010) and both cannot open some PDFs. I got an error message 'there was an error opening this document. the file is damaged and could not be repaired'. I tried to use Mac's Preview, Adobe's Acrobat (9 and 10, with latest updates) and Adobe's Photoshop CS5 - none did work. Both laptops have OSX 10.6.7 with all latest updates. The funny thing is that files work fine in old Adobe Acrobat 6 Pro on Windows XP though before opening it shows a message that the file was created in newer version of software and you should update yours but then it opens the file.
    The problem is completely random and I cannot find any correlations with Acrobat's options/settings. Does anyone have any ideas?

    Since you say that the file opens in Acrobat 6, why don't you do a Save As in that version to rewrite the file. Then it may work. (Basically, the file sounds corrupted.)

  • Cannot open some links

    I clicked a bad page the other day and installed some malware. I [carefully] removed them manually, but perhaps I deleted a wrong registry key. Anyway, I'm left a little bit lame as I cannot open some links or pages, and I cannot restore previous versions
    of Windows.
    Win 7 home
    IE 11
    Issues:
    1. Wikipedia .png images will not respond at all to a left-click. I can open them by right-clicking.
    2.  wordpress.com the reader link and a few other links hang. 
    generates the error Line: 4235
    == Error: The system cannot find the file specified.
    The line of code is ... if( !window.localStorage ){
    3. System restore would not restore previous versions. It was unchecked in system, and I have since re-enabled it and allocated space. I have not tested it.
    actions performed:
    - Googled for a day and a half
    - tried re-registering dlls
    - checked file associations
    - reset security and settings in IE
    - ran IE with no add ons
    - ran IE in safe mode
    - rolled back to IE 10 and reinstalled IE 11 (with much pain with failing updates needing manual uninstallations)
    I am now at a loss at what to try next for the IE issues. Any help or ideas will be appreciated. I'd rather not reinstall or upgrade right now.
    Thanks
    John
     

    Hi Power Unit.
    Considering the machine has been injected by some malware,I suggested you to perform a full scan with the antivirus software in safe mode to have a double check .
    According to your description ,it seems that there is something wrong with system files.We can run "sfc /scannow"to have a health check of the system files.
    I noticed you have tried to reinstall the Internet Explorer 11 .How did you do that ?
    We can run the following command line to uninstall the Internet Explorer 11 and then download it to install it .
    "FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*11.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /quiet /norestart"
    Internet Explorer 11 for Windows 7
    http://www.microsoft.com/en-hk/download/internet-explorer-11-for-windows-7-details.aspx
    If the issue persists ,we may need to do a in-place upgrade to have a repair .We may lose some configurations.Here is a link for reference :
    How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2
    https://support.microsoft.com/en-us/kb/2255099
    Best regards
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • After loading lion, I get an error message "There was a problem connecting with the server.  URL's with the type "file" are not supported."

    After loading Lion, I have been getting an error message "There was a problem connecting to the server.  URLs with the type "file:" are not supported."  There does not seem to be any actual problem with internet connectivity, but it is persistent and annoying.  Any idea of its cause and treatment?

    Take a look at this link, https://discussions.apple.com/message/16156214#16156214

Maybe you are looking for