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

Similar Messages

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?

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/

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

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

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

Aperture error Unsuported Image Format on my previously fine photos

My Aperture librery is located on an external hard drive.
In the same iMac I shared the same library among the family users.
By doing so, most of my previously fine photographs on all projects show the error message "Unsuported Image Format"
Need to solve it as this is frustrating. There is a lot of work behind those pics.
Any ideas?
Manuel

I read in the info you sent that probably I need another external driver or create an image in the same one. Correct?
Hi, Manuel,
Your current drive will do, as long as it is formatted for mac - to be exact, as long as the file system is MacOS X Extended (Journaled) and you have set the "ignore Ownership" flag as shown in my screenshot.
To enable this flag, select the icon of your external drive in the Finder and use the command "File > Get Info ⌘I". In the Info panel disclose the "General" brick to check the filesystem, and disclose the"Sharing & Permissions" brick.
Enable the "Ignore Ownership..." flag, if it is not set.
I do not understand the question about the library being Managed or Referenced. Please explain.
Then your originals are probably managed.
"Managed" means that you are storing the original image files inside the Aperture library
and "Referenced" means that you are storing the original image files in a folder outside the Aperture library. Aperture is only referencing files somewhre else, and you are responsible for taking care of them. Typically you would use a referenced library, if your drive is running out of space and you need additional storage for a growing library.
Where the original image files will be stored is set up in the "Import" panel, when you import your images. The default is "Sore Files in the Aperture Library".
Prior to seeing your emai I recover al pics using the command "Reprocess Originals" and now I see all pics apparently unchanged from my editing.
That should not happen - please check, if all your adjustments are still enabled.
Select one of the images in the browser and open the "Adjutment" tab in the Inspector panel. Are all edits still enabled? Are the checkmarks in the adjustment brick checked, for the edits you applied? Like this?
If your adjustmenst are enabled, but not visible, select all affected images andrebuild your thumbnails and previews:
Photos > generate Thumbnails
Photos > Update Previews (or hold down the ⌥-key and select "Generate Preview").

What's with the occasional "Unsupported image format" errors?

I get this error randomly -- suddenly Aperture can't show me anything but a brief flash of the image, and then I get the maroon screen "Unsupported image format" error. Restarting Aperture returns things to normal. I've seen this in both version 1.5.6 and 2.
I can count on this occurring about every hour or so. This is quite frustrating. I use CR2 files almost exclusively, written from a Canon 5D.
Any ideas or workarounds for this behavior?

I was getting this all the time with 1.5, I have not seen it yet with 2. I think it's a memory thing, it happens more quickly if I am running Safari and other stuff. Sometimes quitting Aperture then starting again does the trick, more often shutting the machine down and rebooting clears it. I also have some very large tiff's in the library, Aperture can't (I've not tried it in 2 yet) cope with them, always the unsupported error message. These files are between 300mb to 1gig, sometimes it justs hangs on to the 300mb but mostly not. By the end of the day it was a real problem, I could only export images 2-3 at a time, if I tried to email 10 low res I would get either an out of memory warning or unsupported etc.
Something holds onto the memory somewhere either in Ap or Safari or all things running.
Kevin.

Unsupported image format error

Hey folks,
I've read several older threads on this topic and have not seen any new information. I am hoping there is a fix and someone out there knows it.
When I fired up aperture today I discovered that all of my images display with the dreaded unsupported image format error.
Thinking that my 215gb library had gotten too large, I tried to create a new library. Same result. When I import new images from my Canon 40D they show as a tiny preview and then quickly turn to the red message. It appears the raw files are not even imported into the library.... which made me think permissions. I repaired permissions and went so far as to set my ~/Photos/ to 777 ... still no dice.
I tried rebuilding my library - did not help
I have tried restoring from TimeMachine backup - no help
I deleted the plist and ~/Library/Application Support/Apreture - no help
I'm getting really worried that I have lost my library. I understand that the files are still there, but what about my edits and metadata. Seeing that this is a wide-spread issue is not helping my situation.
Any suggestions? Thanks in advance!

Good questions and thinking! I was vague about the chronology.
I first noticed the issue when I intended to import some images on my iMac which is home to my main 200+gb library. I never even got to the importing stage b/c I saw red, literally, when I launched the app.
I then created a new library and tried to import.
My final stage was to import onto the MBP, different machine, different library.
As for updates, I had applied the Dec. updates to the iMac but not the MBP.
While I know this will destroy my crediability as a troubleshooter (if you saw my images you'd know I have none as a photog ) I have realized that my Canon 40D somehow got switched into a custom mode during a few of the shots causing it to go into Canon's sRAW. I think that accounts for the behavior of the imported images on the MBP. It does not, however, account for my entire library turning red on the iMac.

"Unsupported Image Format" error ONLY on exposures longer than 4 minutes

When importing my photos to Aperture, I get an "Unsupported Image Format" error, but ONLY on images where my shutter was open for longer than 3 minutes or so. I'm looking at Aperture right now, and I've got one shot that was 184 seconds long - no problem. Next shot, 240 seconds - ERROR. I shoot everything in RAW and have no trouble with any of my "normal" exposure shots - thousands of them. Error shows up only with the shots where I've locked the shutter open for more than 4 minutes.
What the heck is up? I'm *assuming* it's a problem with Digital Camera RAW in OSX, as Preview.app is also unable to display the image. Photoshop CS6 and Lightroom 4 have no trouble with these images. Even in Aperture, I see a low-res preview of these "error" images for about two seconds before the error message replaces it.
Aperture 3.4.5
Digital Camera RAW 4.07
Nikon D600 (latest firmware) shooting .NEF RAW files, all images imported directly into Aperture from SD card in computer's slot
OSX 10.8.4

This problem, unsupported image format for long exposures, has been reported on and off for some time now.
Its not an easy search to phrase but for example I found this Aperture 3 will not recognize RAW files obtained from long ... at dpreview from a while back.
Sorry to say there are no resolutions that I can find. You might want to try and get in touch with Apple. They don;t make it easy to get software support even on there 'pro apps' but if you start with the normal Mac support number you might get to someone who can help.
Additionally you can leave feedback by going to Aperture->Provide Aperture Feedback. There is a setting to report bugs.
Sorry I don;t have anything better to report.
good luck, post back if you find out anything
regards

Image format error on my wordpress website from Photoshop CC file?

Why would only one particular image have a format error on my wordpress website ? the link is [ removed by admin ]. I'm using Photoshop CC and every other image I created has no problem, but one will now work nomatter what I try.
This driving me crazy. The error is during uploading, but only happens with one particular file. Every other file that I created and edited the same way uploads with no problem.

We don't generally like to click on strange links here. What is the file format of the problem file? Try duplicating the layer to another document, and saving that. This often bypasses problematic files. Just right click, and choose duplicate layer. Use the drop down and select New. Job done.

3.4.1 update unknown image format error

When I click on any images older than about three years in my library, they disappear, only to be replaced by the Image Format Unknown screen.
This is SO unnaceptable for a "professional" level program.
How does one report bugs to Apple? 'Cause this is a BIG ONE.

Me too! I've used Aperture since version 1, so cool it with the snark!
Since updating to 4.3.1 it now corrupts, apparently, images older than about three years. It's also doing a weird thing where it thinks it has an older processing engine, even on recent images created after installation of the new one.
Eight cored iMac i7 chip, 16 gigs of RAM, running on two terabyte internal with Referenced Images on a Drobo disc array.
Very bad bug. Can't export, it won't allow me, saying Unsupported Image Format. Thumbnails are there until I click on them, image starts to load, then goes to Unsupported Image Format.

PSCS4 Memory Error with Image Processor

When I use the image processor in PSCS4 to process a large number of raw files using ACR 5.1 (Nikon D3 NEFs), I consistently receive an error message after about 10-11 files have been processed that the instruction at 0x696336ab tried to read memory at 0x6C (or thereabouts) and the memory could not be read. I am saving as JPEGs with the color space set to sRGB.
I de-installed and reinstalled PSCS4, but the error persists. The image processor worked fine with PSCS3. A workaround that solves the problem is to process the files as a batch using a simple action to accomplish the task.
I am running Windows XP Pro Service Pack 3 with a dual Xeon processor and 2G of error correcting memory.

Hmm.. I was getting a similar error with CS3 and was very happy to find that it appeared to be cured in CS4. The CS3 issue would appear if I tried to process more then 100 NEFs. My workaround was to do them in smaller batches (60-75). Perhaps you might try reducing the memory alotted to PS or run it without any other apps running?
Russell

"Bad image format" error when displaying an image on Nokia 6600

I get a "bad image format" error when I try and display an image on a Nokia 6600 cellphone. The image displays correctly when I run it on the J2ME 2.1 Emulator, but gives an error on the phone. Plz help!!

More info please... what kind of an image are you trying to display?

Unsuported Image Format error with referenced images

Similar Messages

Maybe you are looking for