My raw files go to unsupported file format when I load them in. Sony RX 100 had for one year. Never happened before.

my raw files go to unsupported file format when I load them in. Sony RX 100 camera shooting RAW had for one year. Never happened before.
Can only load the files in by running them trhough Adobe Camera RAW first and loading them as TIFFS into Aperture. JPEGs form the Sony load into Aperture just fine. Have repaired datebase, permissions ect but no change. Aperture 3.4.5 on a Power Mac. Whats up? Anyone know?

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

  • Can only view file in its blue psd format when I open them in CS6

    Can only view file in its blue psd format when I open them in CS6
    Is anyone else having this problem?

    Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
    * Don't make any changes on the Safe mode start window.
    * https://support.mozilla.com/kb/Safe+Mode
    If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.
    * Use "Disable all add-ons" on the [[Safe mode]] start window to disable all extensions.
    * Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")
    In Firefox 4 you can use one of these to start in <u>[[Safe mode]]</u>:
    * Help > Restart with Add-ons Disabled
    * Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)
    * https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

  • File open error: unsupported file type Mpeg Streamclip

    having a problem... I am using mpeg streamclip to convert vob files from a dvd. the problem is that the program says that the first vob file is an unsupported file type. I know that this is not true. The DVD plays, and the remaining vob files are opened and processed by the program correctly. Any advice or suggestions?

    I am having the same problem. The first VOB file in the sequence will not open in either Streamclip or Quicktime. This is not the menu display image, but the first chunk of the video (the menu image actually will open). All the ones after it can be opened either individually or joined as a group.
    The DVD plays fine on the mac and also in the regular DVD player. Any idea if this is perhaps some equipment fault when the DVD burner "finalizes" the disk? Am using a combo VHS/DVD-R unit. It is not super high-end, but then neither are these old home videos I'm converting.

  • DVD-MOV mpegstream clip error: "File open error: unsupported file type"

    I do it all the time this is the only time i've gotten this error, i use mpeg stream clip. I have a dvd I got from a DVR recorder, I open the dvd which shows 2 VOB files in the TS folder. the MENU gives "Warning: the stream may have timecode breaks." I "Fix Now" and it works fine. But i dont want the menu. the other VOB file in the TS folder, which should be the "movie I want" gives this error when opened,
    "File open error: unsupported file type"
    when I open anyway, I get an audio bar which has no sound, and no video.
    ANY IDEAS? I've been on this for hours PLEASE

    Hi,
    Do you have the [MPEG-2 component|http://www.apple.com/quicktime/mpeg2> installed on your computer? If not, you will need it to be able to convert VOB files.

  • I backed up my bookmarks to an external drive, rebuilt my system, and now when I try to restore from that file, I get "unsupported file type" How can I restore from this file?

    I backed up my bookmarks to an external drive, rebuilt my system, and now when I try to restore from that file, I get "unsupported file type" How can I restore from this file?

    Make sure that the backup file with the bookmarks has the correct file extension: .html for a HTML backup and .json for a JSON backup.<br />
    You can check that via the right-click context menu of that file and open the Properties.<br />
    If you are not sure about the file type then you can open the file in Firefox via "File > Open File"<br />
    A JSON backup will show as one long text line without line breaks and a HTML backup as a web page with clickable links.<br />
    A JSON backup starts with: {"title":"","id":1,"dateAdded":<br />
    An HTML backup starts with: <nowiki><!DOCTYPE NETSCAPE-Bookmark-file-1></nowiki>
    You may need to add quotes ("") around the name to rename the file to the correct file extension.
    See also:
    * http://kb.mozillazine.org/Backing_up_and_restoring_bookmarks_-_Firefox

  • When I try to open video files purchased through iTunes in Quicktime, I get the message: 'Error 23132: an unknown error occurred. This never happened until I updated iTunes, but when I try to go back to the previous version, I still get the message.

    When I try to open video files purchased through iTunes in Quicktime, I get the message: 'Error 23132: an unknown error occurred. This never happened until I updated iTunes, but when I try to go back to the previous version, I still get the message. It is more convenient for me to play videos in Quicktime since iTunes is such a memory hog. Please help.

    You may get better results if you switch to this alternate version: iTunes for Windows (64-bit - for older video cards) and, if needed, reinstall QuickTime. The new (nearly) all 64-bit version doesn't seem to play well with QuickTime. Perhaps if DRM authentication is required QuickTime needs to be able to see something that is part of the older 32-bit code.
    tt2

  • I have a folder and 3 files stuck on my desktop.  When I drag them to the trash I am asked to enter my administrator's password.  I do this but the files and folder will not delete.  I have checked 'Get Info' on each of them and they are not locked?

    I have an empty folder and 3 .jpg files stuck on my desktop.  When I drag them to the trash I am asked to enter my administrator's password.  I do this but the files and folder will not delete.  I have checked 'Get Info' on each of them and they are not locked and I have full read & write access.  Grateful for any assistance in solving this problem.

    Back up all data.
    Triple-click anywhere in the line below to select it:
    ls -@Oaen De* | open -f -a TextEdit
    Copy the selected text to the Clipboard (command-C).
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V).
    A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.
    If any personal information appears in the output, anonymize before posting, but don’t remove the context.

  • After installing Reader 11.0.07 update on my Mac OS X 10.8.5, when I open an Adobe pdf file I see Chinese script next to the blue loading bar at the bottom of the screen.  This never appeared before and I am concerned that my computer is being hacked into

    After installing Reader 11.0.07 update on my iMac OS X, v.10.8.5, when I open an Adobe pdf file I see Chinese script next to the blue loading bar at the bottom of the screen.  This never appeared before when downloading pdf files and I am worried that my computer is being hacked into or I acquired a virus.  Is this normal or do I have to uninstall this update?

    After installing Reader 11.0.07 update on my iMac OS X, v.10.8.5, when I open an Adobe pdf file I see Chinese script next to the blue loading bar at the bottom of the screen.  This never appeared before when downloading pdf files and I am worried that my computer is being hacked into or I acquired a virus.  Is this normal or do I have to uninstall this update?

  • Went to work on my photos and  something pops up that says file off-line for missing. This has never happened before. Can someone help? thank you

    "Went to work on my photos and something popped up that says, file 0ff-line or missing. This has never happened before. Can someone help? thank you!

    This means that the photos (or the folders that contain them) have been moved, renamed or deleted outside of Lightroom. On Windows it can also mean the disk drive has changed letters.
    To fix the problem see: Adobe Lightroom - Find moved or missing files and folders

  • When I click on my finder to put a new folder on my desktop, it apears  on the desktop nut it conatins all the files on my desktop. What I want is a new untitled folder. By the way, this has never happened before, in my many years of using imacs

    When I click on my finder to put a new folder on my desktop, it apears  on the desktop nut it conatins all the files on my desktop. What I want is a new untitled folder. By the way, this has never happened before, in my many years of using imacs

    Are you sure you are choosing "new folder" rather than "new folder window" - new folder results in an empty "untitled" folder on my desktop whereas new folder window shows all my files.

  • 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

  • When I try to import raw files from my nikon d600 I get the message Unsupported image format, When I try to import raw files from my nikon d600 I get the message Unsupported image format

    When I import raw files from my Nikon D600 into Aperture I get a tryangle sign with "unsupported image format"

    Latest Adobe DNG converter (7.2) DOES indeed convert NEF pictures coming from a D600.
    Head up to Adobe's website and download the app.
    You'll only miss the focus information (focus distance and focus sensors used), but you'll be able to work with raw and not rely on jpg only!

  • 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

  • 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

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

Maybe you are looking for