Strange "unsupported format" error with jpegs

I'm trying to help a friend who is running the most recent version of Aperture 3 (all updates installed). When we import a single jpeg from her hard drive, it comes into Aperture with the "unsupported format" icon and an exclamation mark where the preview should be. Double clicking the thumbnail opens the same error in the viewer, so it's not just an issue of the preview. The files themselves are fine and are named with the proper extension.
If we import 2 images at the same time, one comes in okay, and one does not. Importing 3 at a time yeilds 2 good, one bad. So, essentially, there is always just one image that is bad. It will successfully import the very same file that it rejected moments before as long as it is not the only file being imported. Make sense?
This is not a RAM or hard drive space issue. The only thing I think it may be is that she is running 10.6.7 (on a quad core Mac Pro). I'm wondering if the OS update to 10.6.8 resolves this particular issue. I will definitely update it as soon as I can, but I need to know if it could be something else. (I'm not with the machine now, and I need to bring the solution with me because she is not at a location where she can download the update herself.) Has anyone else seen this behavior before?
Thanks in advance for any helpful suggestions. This has me stumped!

Upgrade and then see.  10.6.8 is the current minimum requirement.
http://www.apple.com/aperture/specs/

Similar Messages

  • I am getting an unsupported format error when trying to import the.aaf file.

    When I select File > Import > File, and then select my .aaf file, nothing happens.
    When I select File > Import > Pro After Effects and then select my .aaf file, it imports the files, then I get an unsupported format error for .mov files.
    Help!

    Kbuggle,
    Which video in the tutorial does this step apply to (i.e. importing the AAF file)? Are you importing from the sample files that accompany the tutorial? Finally, can you post a screen shot of the error message you're getting?
    Also, please confirm which version of After Effects you're running, as well as the operating system.
    Thanks!
    Stefan

  • .mp3 "unsupported format" error

    Hello,
    I am trying to upload two .mp3 lectures using the Public Site Manager and am repeatedly getting an "unsupported format" error. I already have three .mp3s uploaded into this Collection and just need to add two more. All files by this faculty member were created using a Sony USB Digital Voice Recorder and this has never been an issue before. This faculty member has been patient as I have been trying to upload them for two days now. Is anyone else experiencing this issue? Is there a fix for it?
    Thanks,
    Nikki
    Roane State Community College

    Hi.  I am sorry you are having trouble streaming the radio.  I can certainly look into it for you.  Is this an application that you downloaded or are you going directly to that website to stream the radio?  Did you download any applications to your phone before the radio stopped working? 
    Another possibility could be the particular website you are streaming radio from may have changed the format.
    Waiting on your reply 
    Thanks!

  • Unsupported Format Error

    I am getting this error when trying to import an .avi file
    into Flash 8 Professional on a Windows 2000 machine:
    quote:
    The source file stock_1.avi contains video in an unsupported
    format and cannot be encoded.
    On another machine, the same video imports fine in Flash 8
    Professional (though it's an XP Pro machine).
    I had tried uninstalling Flash 8 and Flash Video Encoder, but
    get the same results.
    Thank you,
    Joshua Cane

    I opened Flash Pro 8, created a new Flash document, then
    Imported a Video.
    On the XP, I select the .avi file and go through the steps to
    encode the video to a .flv file. No trouble.
    However, on the Win 2000 machine, I get the above error after
    selecting the video and clicking Next.
    I also tried just opening Flash Video Encoder and adding the
    file to the queue. When I start the queue, I get this error:
    quote:
    The instruction at "0x00000008" referenced memory at
    "0x00000008". The memory could not be "read".

  • FAQ: How to resolve "Unexpected File Format" error with Flash Professional CS5.5?

    You may encounter errors when you attempt opening or saving files using Flash Professional CS5.5.  To address the above problem, Adobe released an updater for Flash Pro CS5.5 (version 11.5.1).
    The following article explains about the errors and Flash CS5.5 updater released to handle them in detail:
    http://blogs.adobe.com/flashpro/2012/07/24/unexpected-file-format-error-on-opening-flash-f iles-using-flash-cs5-5/

    Which operating system are you using?  If you look in the Adobe Download Assistant is it still downloading the install files?

  • IDVD unsupported file type with jpegs

    Hi,
    I am working with iDVD 7.1.2....and trying to insert jpegs and/or Tiffs into the opening drop zones.
    I keep getting the error : "Unsupported file type : Unknown format"
    I haven't had this error before. I am getting my files from iPhoto, and/or dragging from the finder.
    What should I try?
    Thank you in advance!

    Try this basic troubleshooting fix:
    1 - delete the IDVD preference file, com.apple.iDVD.plist, that resides in your
    User/Home/Library/Preferences folder.
    2 - delete the contents of IDVD'S cache folder: User/Home/Library/Caches/com.apple.iDVD.
    3 - launch IDVD and try again.
    NOTE: If you're running Mavericks or Yosemite go to your Home folder and use the View ➙ Show View Options menu to bring the this window:

  • IDVD keeps giving Unsupported format error

    When importing jpegs into iDVD I keep getting the error "Unsupported File Type"... I have checked permissions and all seems to be in order

    Where are the photos being imported located? Whare are you importing to in iDVD? 
    What system and iDVD versions are you using? 
    What type of jpeg are they?  Have they been edited by an image editor? 
    OT

  • Property loader in .csv Format : Error with list of Numbers

    Hi,
    I need to change property files from the .xls format to the .csv format so that I won't need to install Ms Office on the Test Station PC.
    Everything works is .csv format except for variales containing lists of numbers.  Here is an example.
    This variable contains the channel list to send to a Digital Multimeter.  A string containing all channel numbers seperated by comas (The DMM model is Agilent  34070A). 
    I create a variable named ChannelList of type string containing : "101,102,103,104,105"
    When exporting to property file (Using Tools-Import/Export properties), TestStand will write the following line is .csv format :
    ChannelList,"101,102,103,104,105"
    When trying to import this property value with a property loader I get the following error :
    Runtime Error Occured
    Error evaluating expression:Runstate.Sequence.locals.ChannelList = (""101")
    Unexpected Token: 101
    What puzzles me is that teststand is not even capable of reading its own exported property within a newly created file.
    Any ideas?
    TestStand 2013
    Thanks in advance
    Nien

    Nien,
    This is a known issue and we are looking into this issue in future version of TestStand.
    There are couple of approaches for fixing the problem:
    1. Use a different character for comma in the property loader file. After importing the data, replace the character with comma using TestStand expression in the sequence file.
    2. Use Tab Delimited Text format instead of CSV format.
    3. We can see that, property loader is using expression to update the value of the property (The exact expression is specified in the error message you have posted). In a text editor, update the csv file to have the value as
    ChannelList,101""+Chr(44)+""102""+Chr(44)+""103""+Chr(44)+""104""+Chr(44)+""105
    This will create the expression such that, the value of ChannelList property will become 101,102,103,104,105
    Note: This is just a workaround and you should use this approach with caution.
    Thanks,
    Shashidhar

  • Unsuported Image Format error with referenced images

    Hi,
    importing referenced images does not work for me: when selecting "store images in their current location" (i.e., referencing them), the preview is visible for a moment and then becomes gray; the large preview says "Unsupported Image Format" (if AP doesn't crash at all).
    When moving the same images into the library, it works fine. This applies to Nikon RAW (NEF) files (from a D70 and D2H) as well as plain JPEGs.
    I'm using Aperture 1.5.2 / OSX 10.4.8 on a Mac Pro; DigitalCameraRAWUniv200601.dmg is installed.
    Thanks in advance for any hints,
    Bernhard
    Mac Pro 2.66   Mac OS X (10.4.8)  

    Just if anyone cares (somehow this seems to be a rare issue), using referenced images seems to work if I choose a specific location ("Pictures") in the import dialog. The images get copied to a project-specific subfolder of ~/Pictures/ from where they are referenced, seems to work ok.
    BB

  • NI PAL nimxs.exe error with jpeg

    Hey all - having issues getting MAX to see my chassis and observed this at startup.  I don't know if this is the symptom, but I can see my camera under devices.
    I read thru some forum posts indicating that someone may know where I can start re-installing.
    Please see attachment - thanks for any help.
    VG
    Message Edited by VisionGumby on 01-29-2008 02:10 PM
    Attachments:
    NI PAL Exception.JPG ‏49 KB

    Hi VG,
    I read your post and looked at the JPEG files you attached.  You seem to be experiencing a MAX database connection error.  Please follow the steps in this Knowledge Base to correct it.
    I hope this helps!
    Regards,
    Ima
    Applications Engineer
    National Instruments
    LabVIEW Introduction Course - Six Hours
    Getting Started with NI-DAQmx

  • Timestamp/Date format error with Java 1.6

    I'm getting this error trying to getObjects from a ResultSet query for an Oracle Lite 10G table that has colums of the TIMESTAMP or DATE type. This works fine under java 1.5. Java 1.6 seems to have broken TIMESTAMP/DATE compatibility with Oracle Lite. Are there any plans to make 10G compatible with Java 1.6? We would like to port our application from Java 1.5 to 1.6, but this is an obstacle. I suppose one work-around would be to use TO_CHAR on all the DATE fields and convert them back to java Dates programatically, but that would be a hassle.
    Update: I changed the column types of the table from TIMESTAMP to DATE. The same exception occurs when calling POLJDBCResultSet.getObject() on the DATE columns. Again, this works fine under Java 1.5, but not 1.6.
    java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]
         at java.sql.Timestamp.valueOf(Timestamp.java:194)
         at oracle.lite.poljdbc.LiteEmbResultSet.jniGetDataTimestamp(Native Method)
         at oracle.lite.poljdbc.LiteEmbResultSet.getVal(Unknown Source)
         at oracle.lite.poljdbc.POLJDBCResultSet.getTimestamp(Unknown Source)
         at oracle.lite.poljdbc.POLJDBCResultSet.getObject(Unknown Source)
         at oracle.lite.poljdbc.POLJDBCResultSet.getObject(Unknown Source)

    I just found a pretty easy java work-around for this that doesn't involve changing the table column types or the SQL:
    Check the column type from the ResultSetMetaData before calling ResultSet.getObject(). If the type is DATE, TIMESTAMP or TIME, call ResultSet.getString() which doesn't throw an exception. Then convert the string to a java.util.Date using java.text.SimpleDateFormat. That can then be used to instantiate a Timestamp.
    This seems to work.
    Message was edited by:
    user490596

  • Date Format error with af:selectInputDate

    Hi ,
    I am using <af:selectInputDate> in my application for one of the page.I have added <af:convertDateTime pattern="MM/dd/yyyy"/> for formatting user entered date value.i have also added valuechange listener for this component as well, just to check whether user has actually modified the value in this textfield either manually or by Date picker.
    However, if user enters manually value in the textbox, say 04/09/2007, in the valuechange listener method when i have retrieved the user entered value from ValueChangeEvent object using following snippet:
    code:
    Date d=(java.util.Date) valueChangeEvent.getNewValue()
    i could see the date in the following format when printed on console
    04/09/0007
    due to this incorrect format, i am facing problems in subsequent operations.
    can anybody help me in understanding the reason behind the same as well as can you suggest me code changes (if any) so that i will get proper date in the listener method?
    Thanks,
    Shriniwas

    Thanks Frank for a quick reply.
    I have used the SimpleDateFormat for formatting with the pattern as, "MM/dd/yyyy" and it is working fine if user enters 4 digit year.
    However, for a entry with 2 digits for a year e.g. 04/10/07 when i parse the date using SimpleDateFormat,it is giving me date as 04/10/0007.
    Is there a way by means of which i could force the user to enter 4 digits for the year?
    I have tried using dateStyle attribute of <af:convertDateTime> tag with 'shortish' as its value, it converts a 2 digit year into 4digit on the browser side & displays on the screen e.g. if user enters 04/10/07 it will appear as 04/10/2007 on the screen however, in value change listener method, i could see date as 04/10/0007.
    Any help in this regard is highly appreciated.
    Thanks in advance,
    Shriniwas

  • Aperture suddenly displaying "unsupported format" for Nikon D300s RAW files

    I am using Aperture 3.1.3 on my iMac 24 with Snow Leopard 10.6.8.   A couple of days ago I applied an update for Aperture RAW files that was in my update list, even though I don't use any of the cameras involved. 
    After that update Aperture gives me an "unsupported format" error on all my Nikon D300s RAW files. Every RAW file in the library.  I have never had a problem with this at any time over the last 2+ years of using Aperture.
    I have tried using time machine and rolling Aperture back to the end of July (my most recent backup) along with rolling back the RAW file plist. I then did a repair permissions, and reimported the photos after this.  I have rebooted numerous times.  All to no avail.  I have not yet tried a library rebuild that would be next if I must.
    I use a Referenced library, so I was able to check out individual RAW files with Adobe Camera RAW.   They open fine so there is no file corruption issue. 
    Any thoughts on what might be happening?  Any other file(s) associated with RAW conversion that I might need to roll back?   I do not see any mention of a problem like this when searching the web or the forum (although I may have missed something by not searching the correct terms).
    Any help would be greatly appreciated!

    The raw camera bundle is  /System/Library/CoreServices/RawCamera.bundle
    Go to /System/Library/CoreServices with the Finder, locate the the RawCamera.bundle package, select it and then do a File->Get Info on the package. You should have version 3.8.0, that is the latest and the one that you should have downloaded last week. If it is not 3.8.0 stop here and post back what version you do have, something isn't right.
    Assuming you have 3.8.0  use the Finder to navigate to /System/Library/CoreServices and then delete the RawCamera.bundle package. The Finder will ask you to authorize the delete.
    Then go to Digital Camera RAW Compatibility Update 3.7 download and install it. That will put you back to the last CameraRaw update before this one.
    See if that fixes your problem.
    As always when messing around with system files it is possible to mess things up so make sure you have a good backup before proceeding, And if any of these instructions make you nervous you might want to hold off doing them.
    good luck

  • "unsupported format" message

    Working in Aperture 2, I get intermittant blank screen and "unsupported format" error message when in edit view.  No problems in thumbnail view.  Only format used is CR2 (Canon RAW).  The only way to clear error is by exiting Aperture and re-starting.  Anyone else seen this / have a fix?

    A Loud Cheer Is Heard From The Crowd!!!
    OK, sucess with Vista Ultimate. Monday, I can check it out with XP, but I am predicting that will be a success as well.
    Being brand new to the world of video and Premier, everything I do is an act of faith at this point. What I was reacting to with my previous comment was the fear that working with the files was not going to be a staright forward Import, Modify, Export Final Product path. I was afraid I'd have to make a detour to import into some intermediate format, then bring it into Premiere.
    Glad that's not the case at all!
    I will do my best to report sometime on Monday if XP is as straightforward as Vista. If Idon't have a problem, I will be real curious what caused the problem qim010 is reporting.
    Regarding AVCHD . . .  are there different "flavors"? From my still photography background, I found that RAW is not the same across the board: Nikon RAW is not quite the same as Olympus RAW and, at least when I got my first Olympus that did raw, there was differences withing the Olympus line. I had to wait a while for the an update to Photoshop even though an older version of Olympus RAW could be read. Maybe that is why qim010 is reporting a difficulty with Sony AVCHD.

  • Formatting error with_item-wt_withcd in transaction code FBV0

    Hi,
    When the user is posting the parked vendor invoice using transaction FBV0, there is an error message reported as
    below: Message no. 00298 - Formatting error in the field WITH_ITEM-WT_WITHCD; see next message.
    Even after executing the transaction RFBIPPG0, the above formatting error with withholding tax code field is not resolved.
    As a solution for the problem, it is required to execute the note no. 709736 which resolves the formatting error.
    Ramanand Bhatt

    Hi Maurizio
    We are facing the error “Field WITH_ITEM-WT_WITHCD(5) does not exist in the screen SAPLFWTD 0100”. We are having an interface here for posting an Invoice document through T code FB01.
    When we execute this in foreground we don’t get any error and when thesame is executed in background, we are getting the error “Field WITH_ITEM-WT_WITHCD(5) does not exist in the screen SAPLFWTD 0100”.
    We have gone through various threads and found that the same is concerned with the number of withholding tax codes assigned to the vendor codes i.e. it should be limited to 4. If the same is more
    than 4, the screen SAPLFWTD 0100 gives the above error. However we have the scenario where in more than 4 withholding tax codes will be assigned to a vendor code.
    We also raised a OSS for the same, but the same being a Z development, we are net getting a satisfactory response from them.
    Please provide the solution for the same.
    Thanks & regards
    Nitesh

Maybe you are looking for