Preferred image format & resolution?

My linked images in a brochure project add up to a huge folder, and I'd like to reduce it as much as possible without degrading image quality. I've been using flattened, PSD files around 4" x 6" at 300 dpi with a file size around 6MB each. The images as they appear in the brochure will be about half that size.
Should I resample them down to 200 dpi (cuts the size in half)? Should I save them as jpgs or some other format?
What's recommended for getting the best quality from smallest size file?

300 ppi at 100% is a safe resolution, more than suitable for most photos
in most commercial printing situations.
But as John said, you really only need 1.5xLPI. So if you're printing at
133 lpi (ask your printer), you should be okay at 200 ppi *at 100%*.
That means if your images are double their printed size, you should be
able to safely resample/resize them to 2 x 3 at 200 ppi. Don't save in
JPEG. Save in PSD or compressed TIFF.
Incidentally, I agree with Bob. Sounds like a lot of work just to save
some space, especially because you really have to keep the originals at
their original size/resolution anyway. You could archive the originals
to CD-ROM, I guess, but don't throw them away. As soon as you throw them
away the client/boss is going to change his mind and ask for you to
print the photos bigger.
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com

Similar Messages

Preferred image format for RH 7 html

I am working on updating the help documentation for a piece of software my company distributes. We insert copius amounts of screen shots to help demonstrate how to use our software. I've used the RH screen capture tool and it appears more than satisfactory.
My question is, is there a preferred image format that most people use when inserting images into RH projects?
I'm trying to find a happy medium between picture size and picture quality, since many of our customers download our products we want to streamline it as much as possible. Any input would help...thanks!

Hi there
For what it's worth and speaking only for myself, I'm almost exclusively using .PNG as my preferred format.
Cheers... Rick
Click here for Adobe Authorized Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.

Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.

There may be a few links in Apple Support, regarding articles about how to use iBooks Author
and iBooks Store, etc; these would be separated into two general categories by device used.
Since there is an iOS and an OS X version of each, you may have to look to see what Apple
Support says about the one you are interested in; and how far their database goes toward an
answer to your question. Otherwise, a general search engine approach may be necessary.
Not sure if anything along the lines of what you seek would be available in an App.
References to iBooks Author and iBooks Store, etc appear within these two categories in Support:
For Mac OS X:
http://www.apple.com/support/mac-apps/
For iOS:
http://www.apple.com/support/ios/
Appears a community host moved your earlier post into one of the iBooks Author or Store sections
after I'd replied to what otherwise may be a similar post. Not sure if the links to the Discussions area
of iBooks you are interested in, have similar questions or answers by others who'd visited previously.
Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.
In my reply to your earlier thread, prior to it being moved, those links to sections of iBooks Author, etc
are posted. You can also find them from the main Apple Support Communities page.
Sorry to not be of much help in this matter.
Good luck & happy computing!

"Unsupported Image Format" all of a sudden, with previously workable files

Folks,
I've got an issue that seems very strange indeed.
Months ago, I bought a Pentax K20D. I also bought a 17" MacBook Pro and Aperture. Camera and Aperture played well together.
I encountered the known issue with white spots on the image when using the 2-second timer for long exposures. I read about how the Pentax firmware update 1.01 changed the EXIF Make information, causing Aperture to be unable to read the K20D PEF RAWs. So I waited.
When Aperture 2.1.1 was released (and I think the Apple RAW update), I installed both of those. When I heard through this forum that the updates fixed the problem, I also updated my camera's firmware and confirmed that it worked.
So smooth sailing for a few months on Aperture 2.1.1, OS 10.5.3 (or .4, I forget), and K20D firmware 1.01.
Then I bought a Mac Pro 8-Core with 10.5.4 on it. I sold the 17" MacBook Pro. I used the Migration Wizard to move my user account from one machine to the other, but did a fresh install of all applications. (I've been an Apple tech for the past 7 years, and have various certifications. I know the user transfer process isn't perfect, but it should have the following results... read on)
Now, in Aperture 2.1.1 on 10.5.4 with all updates, PEF RAWs taken with K20D firmware 1.01 that were previously edited, manipulated, etc just fine on my MacBook Pro say "Unsupported Image Format" in a big reddish-black box when I try to view the master. If I switch to Quick Preview, it displays just fine, but is un-adjustable. Additionally, any NEW images I copy from my K20D show in the Import window as being 0x0 pixels (or occasionally 160x120 pixels) and will only show a tiny preview or "Unsupported Image Format." All PEF RAWs taken with K20D firmware 1.0 are just fine.
So here's what I've done:
1) Tested a fresh install of 10.5.4 on another HD in the Mac Pro. Installed Aperture 2.1, updated to 2.1.1. This should be perfectly clean. It gives the "Unsupported Image Format" error with any new images from my K20D. Copying the library from my other partition gives the same problems as described earlier.
2) Tested a fresh install of 10.5.3 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. Applied the Apple RAW update and iLife enhancements. It gives the same errors as before.
3) Tested a fresh install of 10.4.11 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. This worked perfectly for all PEFs and DNGs.
4) Took a month-old backup (from when everything was working just fine) of my Aperture Library and loaded it into all of the above configurations. Same results!
So what is the deal here? Aperture all of a sudden can't read images that it itself was able to edit a month ago? How come it works just fine in 10.4.11? This seems really messy. I have essentially lost a lot of the work I've put in.
I can use DNGs moving forward, but my past work is now messed up, and the DNGs are almost 75% bigger than the PEFs!
Anyone have any ideas for resolution or should I just call Apple?
Message was edited by: MonsieurBon

If it's any consolation, I had the EXACT same problem today; just opened Aperture 2 and my entire library of images shows "unsupported image format' -- the thumbnails are still intact but clicking on any image suddenly shows the red screen.
Same situation, these images were previously editable and accessible. We had a power outage an hour ago and initially I thought my library had crashed, but I was not actually using Aperture 2 at the time of the outage so I don't think that's the case.
Given the relatively sparse attention Apple gives to these forums, I don't expect there will be a quick response.
I have Leopard 10.5.4 installed, I don't have access to another version of the OS to see if I can get it work. If I'm not mistaken, wasn't there a series of Software Updates recently? I click on these without really checking the apps that are affected; could Aperture have been one of the apps 'revised' by the recent update?

Image Size/Resolution for ProShow Producer ?

Need to prepare images for a slideshow I am creating in ProShow Producer. Not understanding their suggestion to convert my images to jpeg 1.5.
The projector is 1920 X 1080 and will be shown on a 26' wide screen at a movie theater.
I correct the RAW image and then Save As tif (dimensions are 5184 X 3456 at 300 ppi).
Usually I resize the tif at this point and Save As jpg. When I resize I have always put in the dimensions 1920 width for landscape images and resolution 300 ppi.
Would you just change the pixel Dimensions and leave the Document size alone?
They want me to Save As jpeg 1.5 and I don't understand what they are asking me to do or how to do it.
Can anyone explain this to me?

try google. It appears to be a webcam format.

How to convert EPS(image file) file in to other image format e.g NIGMAS

Hi friends,
I want to make a tool which will help to convert the EPS image file into other image format BY USING JAVA TECHNOLOGY. I havent done this type of file conversion before, so any body please explain it to me from the basic how can i go for it, what r the require things, where should i get the help of it, which java API should i use etc. i ll be vry thankful.
My actual requirement is i want to convert the EPS file into the NIGMAS(Nihon computer graphic mapping System) file format.
Thank you in anticiption.

The easiest, but not necesarily the best, way is to use ImageMagick's convert utility. From Java you can use Runtime.exec to invoke convert.exe ... ImageMagick is opensource and supports many different formats ( www.ImageMagick.com )
     * Converts an eps file to a graphic that is suitable for the web.
     * We use ImageMagick's 'convert' utility to convert .eps files into either gif or png format.
     * The output format is determine by the extension that you set for the output file.
     * Sample command:
     * convert -density 208x208 /export/home/kpmg/tomcattest/jsp/1.eps
     *                                    /export/home/kpmg/tomcattest/jsp/1.png
     * Although convert supports about 100 different parameters, we are only using 1:
     * -density     (sets the vertical and horizontal resolution in pixels of the image)
     * Density sets the vertical and horizontal resolution in pixels of the image.
     * It should be changed based on the resolution of the user's monitor
     * (e.g. if hi-res display settings, then density will need to be greater
     * than if running on a low-res display, which would make the same image look really big )
     * You may want to use other convert parameters, such as -sharpen
     * to make the image look better, or -compress and
     * -quality to change the kb size of the image.
     * For the full list of parameters see:
     *      http://www.imagemagick.org/www/convert.html
     * @param inFile The absolute path to the eps file to be converted
     * @param outFile The absolute path to the desired output graphic file.
     *                         NOTE: the format of the output file is determined by the
     *                         extension that you give for this parameter (e.g. file.png will
     *                          be written as a png file )
public void eps2www(String inFile, String outFile, String density) throws Exception
          // use ImageMagick's convert program to make the www version ( png or gif, etc)
          String call = convert +
                    " -density " + density +
                              " " + inFile +
                              " " + outFile;
          try
               Process child = rt.exec( call );
               child.waitFor();
               log.debug("Convert process exit code is: " + child.exitValue() );
          catch (Exception e)
               // TO DO: this could probably be more explicit
               throw new Exception(e);
          // log the command strings for debuggin purposes.
          log.debug( "Convert Successful: call = " + call);
     }

"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

Unsupported Image Format Nikon Super Coolscan 9000 ED

I see many posts for the dreaded "Unsupported Image Format" that it seems that Apple has ignored to fix in Aperture. My images display correctly while "loading," but then I get the "Unsupported Image Format Red Screen of Death" after the loading is completed.
I tried to lift and stamp to no avail. Has anybody found a work around?
Thank you,
Tim

tgb412 wrote:
I save the files in TIFF format, and they are 460 MB. I don't think that it is a file size issue because the files open in my Photoshop CS3 without any problems whatsoever. The preview images in Aperture work some of the time. I close and reopen Aperture, and they usually come back up.
Well, that still makes it a file size issue for Aperture! You are correct, there is nothing wrong with the files, you have not exceeded any known limits of TIFF file format, etc. But as we've discovered Aperture simply can't handle files that big. (I'm not it's ever been conclusively determined whether it's a file size thing or a pixel dimension thing, but they are of course tightly linked for any given scan resolution, so it probably doesn't matter anyway.)
I'd say the misleading error message is one of the worst parts of this bug. Especially for those of us with files that are slightly smaller, which open and work for a while before doing this. Obviously the file format is supported at first! "Memory limits exceeded" would work better, or perhaps "memory leak limits exceeded"
Duncan

How to change the bar chart rendering image format in SSRS

Hello all,
I am working with SQL Server 2008 R2 and I have a SSRS bar chart report, when the report got rendered over online or if the take Export (PDF and PPT), the image is in png format always, which is taking too much of time to execute the report in case of large
data.
Can, It be possible that the rendered image is in jpeg format instead of png.
If Yes, please share the appropriate steps to follow:
Thanks in advance
Pankaj Kumar Yadav-

Hi Pankaj067,
According to your description, you want to change the bar chart rendering image format as JPEG format when previewing the report or exporting to a PDF file .
In Reporting Services, the chart rendering image format is PNG by default. It’s a by-design behavior. And it doesn’t open any API for us to change the image type when exporting a chart to a format. So in your scenario, your requirement can’t be achieved
in Reporting Services currently. I would recommend you submit a feature request to Microsoft at this site:
https://connect.microsoft.com/SQLServer. So that we can try to modify and expand the product features based on your needs.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Firefox for Mac preferences shows .qif file format for quicken as "quicktime image format"-wrong application and won't let me select anything else

Post to Firefox forum; Oct.2011
Re: Quicken 2007; Mac OS 10.5
Problem: can’t import or download Qif format files into quicken from bofa or Chase. Mac can’t recognize; how do I set preferences in Firefox (or Safari).
https://support.mozilla.com/en-US/questions/new?product=desktop&category=d1&search=Firefox+for+Mac+preferences+shows+.qif+file+format+for+quicken+as+%22quicktime+image+format%22-wrong+application+and+won%27t+let+me+select+anything+else&showform=1
Hello,
I previously used Firefox on my old Mac G4 with OS 10.3.9; the above issue existed with that system and Firefox 2.00.2 (or similar). I then "tried" to move to a G5 Mac with OS 10.5, hoping that an updated Mac Operating system and updating Firefox would solve that problem.
I'm now working on my son's MacBook Pro, OS 10.5.8, 2.4 ghz Intel Core 2 Duo; 2gb Memory; 2 gb 667 Mhz DDR2 SDRAM.
I still have a problem in Firefox Preferences trying to download .qif files. BofA Mortgage accounts only allow downloading of .qif files. My .qfx download works fine, but the error message is as follows:
The error message is that this is a corrupted file or one that Preview doesn't recognize.
and it is still a problem when trying to download Quicken .qif format files for our B of A mortgage.
The preferences for Firefox under File Helpers won't let me name the extension I want; instead, it CONFUSES .qif (Quicken Interchange Format) with .qtif (Quicktime Image Format) for Mac.
Therefore, when I download .qif files and try to import them to Quicken, I get a message that this is a corrupted file:
thanks for any help.
Val in Seattle

Well, in the end, I just gave up and deleted the photos, in the hope that it was something to do with them. Took some more photos and they seem to have imported without any problems at all.
Given that the same irksome photos loaded on the wife's macbook without so much as a murmur, how weird is that?
Still- all's well that ends well. Thanks for the suggestions- much appreciated.
Matt

PDF image format?

From what I understand, the PDF file format can contain text, vector graphics and raster graphics in many different formats. When I print to a PDF (via Save as PDF... in the print dialog box), what type of image format is actually used inside the PDF (which I assume is just a container format, really)?
Say I come across a full quality RAW file from a 10-megapixel camera. If I open that image in an image editor and then print it as a PDF, what ends up in the PDF file? Is it a JPEG? A PNG? Some type of otherwise unknown lossless format?
I assume the screenshot mechanism in OS X that saves to PDF uses similar technology. In that case, is a screenshot saved as a PDF better or worse quality than a PNG or JPEG (using a utility like TinkerTool to change the default screenshot format)?

Actually, it doesn't matter what you set on a folio level. The article settings override the folio settings. The folio settings are supposed to appear as the default when you create articles, but it doesn't work that way at this time.

Canon EOS 350D .CR2 pics still 'unsupported image format'?

I was releaved to see updates in Mac OS X (10.4.8) and Aperture 1.5 the other week, hoping it would solve my problem, being able to finally work with my RAW files (.cr2) from the Canon EOS 350D (yes, being in Europe these days).
I followed the posts on the forum throughout the summer, which recommended waiting for the next OS X update (which should support the camera in that raw definition file) and I didn't want to use the workaround, which clearly had problems with the colors on the pics.
After all the updates the other week, nothing has changed on my MBP. Still the 'Unsupported Image Format' on my RAW files. On the other hand, I don't see any posts on problems with the 350D camera anymore as well (only on CR2 files in general).
Am I missing something really basic here (tried rebuild library)? Or, have all the CR2 formats gone down the drain on Aperture 1.5?
Any help is appreciated, as I have already looked into Adobe Lightroom Beta and although I don't want to switch, the files seem to work there...

Yes, the import thumbnail is as you describe, the low res. JPG that is embedded in the RAW wrapper.
10.4.8 needs to be installed prior to Aperture 1.5 .... from a functionality point of view. I am not aware of a dependence that says AP 1.5 has to be uninstalled before a 10.4.8 upgrade or any such, not that AP 1.5 should need re-installing after a 10.4.8 upgrade .... assuming it was working correctly beforehand.
But to this last point, since you have an issue which may be related to AP or OS X, it is likely worthwhile updating both and in order.
Final thought. do you import directly from the CF card / camera vs. using an intermediary tool such as ImageBrowser or DP Professional? I am wondering if Aperture is very OCD aboout the image format wrapper and chokes at the least excuse that other apps. and tools ignore.
G.

Mapviewer performance problem using image format FORMAT_RAW_COMPRESSED

I am using the MapViewer.FORMAT_RAW_COMPRESSED map image in my (java) map application because some features must be clickable and as far as I can work out, this is the only way to achieve this in a Java client. On my local system, running the map server in an oc4j container, this works about as fast as using FORMAT_GIF_URL and loading the image from this url. There also doesn't seem to be much difference in memory and cpu usage.
When I direct the request to a map server running on a remote Application Server the rendering time grows exponentially. The same maprequest using FORMAT_GIF_URL runs as fast as it does in my local OC4J container. The problem seems to be in "packing time" in RealWorker:
Remote AS:
Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...
Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 99ms
Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 5560ms
Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 142605ms
Thu Jun 30 13:59:34 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 148264ms
Local OC4J:
Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.MapperPool] freeMapper() begins...
Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] preparation time: 540ms
Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] querying/rendering time: 2490ms
Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] packing time: 120ms
Thu Jun 30 15:34:42 CEST 2005 DEBUG [oracle.lbs.mapserver.core.RealWorker] [RealWorker] --------------- total time: 3150
The test server is smaller than my local system and more applications are running on the AS, generating the map takes all the available memory and cpu, but the difference between the time it takes generating a GIF image and generating a Java image of almost a factor 50 is puzzling.
What could cause this enormous difference? Any idea's about how we can analyze or solve this? What could RealWorker be doing in this packing time? Any hints would be greatly appreciated.
Many thanks,
Ida

Thanks for the replies!
1. Which AS version are you using? -> 10.1.2
2. Just as a test, if you restart AS (if possible) do you still get the same values? -> yes, we restarted the AS and the results are the same.
The server is indeed running low in memory. It is a 512MB machine, just big enough to run the AS. The production server will have some more, but not very much. Could I estimate how much extra memory it will need to keep a good performance when generating maps with live features? And maybe I'm wrong, but shouldn't the extra load for the java image only be on the client, since that's where the image is made? On the server it's just the image data, isn't it?
I tried removing the basemap, but that reduces the loading time just with a few seconds. The live themes are jdbc themes and result in only some 20 to 30 geofeatures. Removing them from the request so only an empty image with a title is retrieved still takes about 117 seconds. Reducing the device size does reduce the loading time, so it does seem to have something to do with the amount of pixels in the image space, not with the data. Could it be that in the "packing" of the image something happens that takes a lot of memory, related to the amount of pixels?
In my situation it would be handy if the live features were also returned when the image format is not set to FORMAT_RAW_COMPRESSED, it is also possible to draw shapes onto an existing image and this would bypass the memory problems.
Thanks for any further help.
Ida

Image cannot be rendered because Aperture does not support image format

Dear all,
I have installed apple Aperture 3.03 and the complete Nick software plug-in selection:
• Dfine 2.0 for Aperture
• Color Efex Pro 3.0 Complete for Aperture
• Silver Efex Pro for Aperture
• Sharpener Pro 3.0 for Aperture
• Viveza 2 for Aperture
History
Until a few days ago the system was running ok / no notable issues on performance. / all pug in seem to run good / no issues. Also
• I Run OSX10.4/ Aperture 3.03 ( 32Bit mode)
• My library contains just over 10000 images / approximately 140GB
• I have recently updated the OSX software update including the security update 2010-005
• as well as the Snow leopard graphic update 1.0
• As far as I am aware all updates where automatically recommended by OSX Software update ( no manual intervention).
• As far as I remember after update the system still was running ok but honestly I can not tell you how many times the Nick Plug in started out of Aperture.
After all, Several times I continued using the system / still no noticeable problem until the following was happening:
Problem:
After creating with "PT gui" a panoramic image File type: "TIF" Pixel size: 5112 × 2556 (13,1 MP) I imputed this file in to Aperture (drag and drop). During the attempt to eddied this file with "Nick Define 2.0" the system was hamming up No response for several minutes from Dfine 2.0 / Aperture" At the end I had to "force quit" the applications.
After the consequential reopening of Aperture I tried again to eddied images with any Nick software Plug-In but each time Aperture prepares any image previously stored in my Library ti open the Pug in the following Error message appears:
*"This image cannot be rendered for editing because Aperture does not support the image format"*
Currently non of my previously in the library safed images can be opened in a Nick software Plug-In this applies to all file types I have tied " Raw, tif, jpg"
• I am still able to eddied normally with Aperture ( so far I do not find any other issue)
• A newly imported Raw image after being taken with my EOS 5D can be edited in the completed Nick software Plug-In selection ( so far I do not find any other issue)
The following actions have been taken to overcome the issue (all not successful):
• I restored my Library out of my back Up ( to previous time of event ( no Time machine back up)
• Uninstallation of all Nick software Plug-In selection
• Uninstallation Aperture Reinstallation Aperture / Nick software Plug-In selection
• Repairing the library ( all three possibilities)
• installation of latest EOS utilitys
Questions
• Can you support me to overcome this issue?
• Have you heard similar issues of Nick user Running the Aperture plug-ins?
For me it is really strange that even after replacing the the library in my normally not connect back up the problem still exists (this should be not affected by the event as the back up was not done any more) / new imported images are editable with the Plug-In.
I would be happy if you could support me in this issue.
Best regards,
Matthias
PS: I have reported this issue to Apple (via Aperture feedback) as well as contacted the Nick software support and currently waiting for feedback.
Harware:
Modellname: MacBook Pro
Modell-Identifizierung: MacBookPro5,1
Prozessortyp: Intel Core 2 Duo
Prozessorgeschwindigkeit: 2,66 GHz
Anzahl der Prozessoren: 1
Gesamtzahl der Kerne: 2
L2-Cache: 6 MB
Speicher: 4 GB
Busgeschwindigkeit: 1,07 GHz
Boot-ROM-Version: MBP51.007E.B05
SMC-Version (System): 1.41f2

Dear Ma-Le / All
I have just had the same problem
I use
• Aperture 3.03 with a iMac 2.8 Intel Core 2 Duo with all files on external hard disks (mac extended fomat as apple suggests) with referenced masters.
• Camera Nikon D300, with probably 75,000+ images on 2 hard drives
• Photoshop CS2 with PhotoTools 2.5 plugin
This has been working perfectly until yesterday when the system froze when I was using PhotoTools 2.5 with Photoshop CS2 - as a result of which I resorted to a force quit.
Since then on most of my files it has not been possible to use an external editor.
A message appears saying: *Editing Error - This image cannot be rendered for editing because Aperture does not support image format*.
The problem seems to apply to the attempted use of any external editor (including Noise Ninja)
The following have each been tried, all unsuccessfully:
- Using each of Aperture's library 3 first aid options
- Rebuilding directory using Diskwarrior
- Checking for virus using Virus Barrier X4
- Defragmenting library hard disk using TechTool pro
- Changing permissions settings
- Using Disk Utility first aid to repair permissions and checking main disk
- Removing some plist elements when open 'show package contents' of library
- Setting up a(n almost clean) new system, with newly loaded version of Aperture, with a new library from a vault saved prior to the crash when the problem first occured
Several things seem to me to be totally bizarre:
1 - The problem is the same on the other library hard disk which was not in use at the time
2 - The problem still occurs when a back up vault saved prior to this problem is loaded - using a new hard disk with a new system and a newly reloaded and upgraded Aperture software
3- The problem seems inconsistent. It appears to affect some photos but not all. Even from the same shoot, some photos can be edited using an external editor, whilst others cannot (but as far as i can tell most of the photos in a particular album seem to be consistently affected)
4- The only way around it seems to be if I import a new (copy image) from the original master. Then everything works ok, and I can successfully edit that copy image in photoshop / phototools plug-in.
I am beginning to wonder whether what has been corrupted is Aperture's ability to make copies from the master file which it then uses with the external editor (I have no real idea whether this is correct)
Does anyone have any ideas or solutions - or has anyone else been suffering a similar problem?
Eric
PS: As a professional photographer this problem is a really serious issue for me - and I really don't really want to go to Lightroom or Capture One

Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
Please help.
William

Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

Preferred image format & resolution?

Similar Messages

Maybe you are looking for