Aperture 3 messes histogram when exporting to either PSD or TIFF

Hi all,
I wanted to ask a question regarding how Aperture 3 handles the PSD/TIFF files. I've noticed that when i export a RAW file to Photoshop or to any other plugin (Noise Ninja for this instance) and Aperture prepares the file (i.e. makes a TIFF/PSD copy of the RAW file) it messes my histogram. As a consequence in a specific case i am working on now, it brightens up the shadows and lowers contrast.
Anyone knows why this happens? Is there any way i can stop this from happening?
Thanks in advance

P.S: Setting the Black point to the default Aperture value (3) on the TIFF/PSD file generated, results in a very similar result with the RAW file. Could it be the case that during the file conversion, aperture ignores some Exposure settings?

Similar Messages

Why are my prints shrinking when exporting files from NEF to Tiff despite not ticking the re-size box!

When I export/convert my Nikon D7000 based raw files to Tiff files using Lightroom, in preparation for printing, the document size shrinks but the file size increases(see top image below)! This is despite not ticking the 'Resize to Fit' box on the export pop up.I know the file size will increase going from a raw to a Tiff file but I don't understand why this happens when the print size shrinks. This is even more puzzling if I export the same file as a raw file (+its related .xmp file) to another folder then save the file in Elements 9 as a Tiff folder since the size stays as it shoiuld be (see middle image below) I think it must be something to do with the way I am exporting directly to a Tiff format as if I export it as a .dng it still retains its size (see bottom image)
Tiff image exported from Lightroom as a Tiff file then just viewed in Elements 9
Raw file exported from Lightroom as a NEF raw file (with XMP) file then just saved as a Tiff in Elements 9
NEF raw image converted to .dng file through Lightroom & viewed in CS2

Sorry, I think I've obviously confused the issue by not comparing like with like so here are two versions of the exactly the same image, one a Tiff and one a dng. Both images are 6016 x 4016 pixels, 300 pixels per cm and were simply exported from Lightroom. If I were to simply print them without resizing, one image would be significantly larger than the other. Why does this happen is what I really want to know? If I was to resize the smaller version of the image to be the same size as the larger one, would there be any loss of detail in the print? I would expect there to be as CS2 would create data to fill in the gaps resulting in a file that was 859.2M in size.

"Not enough memory" when exporting DNG to PSD, noise opening it

Hi guys, I'm using LR 4.2 and trying to export to PS CS6 on my Win 7 Asus 4gb laptop with 45gb free space on my hard drive.
I have made substantial edits to a raw file in LR and am attempting to export it to PS for final edits (cloning out extraneous features) at 16cm and 150 ppi (less than ideal but still too large). The working file is 73 mb.
However, I am getting an unsufficient memory error when trying this on Tif or Psd, even Jpg. I can get it to export as original, which gives me a DNG but then I get the same lack of memory issue when trying to open it in Photoshop.
What I can do is open the working DNG file in Photoshop but then only some of my adjustments come through - all the noise removal I have done has gone and the image is very noisy in PS. I can also convert it to Tiff using VSO Image Resizer and open this in PS but again, the noise is there.
The image is to be used as the cover photo on an A4 magazine so needs to be of print-quality.
I'd be grateful if anyone could give me some advice on how to deal with this problem image.
Thanks in advance,
Jo

Your memory issue isn't addressed here but try this to see if you can get a usable file before your deadline:
Hit CTRL S to make certain your metadata is saved (although it shouldn't matter). Then don't export as Original but rather export as DNG from Lightroom.
Does the image import properly now to PS?
On a side note: regardless of the flie format PSD, TIF, JPEG, the image takes up roughly the same amount of RAM when open in PS.

Colors get messed up when exporting to adobe pdf

I am working on a book cover that is mostly black. I have an image that has a black background that i have placed on the cover, and then i created a box and filled it with black for the rest of the cover. When i convert to pdf there is a noticible difference between the black of the picture (darker) and the black of the filled in box (lighter, almost looks grey). If i export to a jpeg it is fine, the colors blend seamlessly. What is going on? How do i fix it?

There is a lot that goes on with Blacks and exporting. First off, your image is probably photographic, or some sort of continuous tone raster image. If it is, and you are dealing with a naturally captured background, the black will have some variation from area to area, and it will have either R,G, and B components, or it will be a blend of the four CMYK channels. There's a good chance, from your description, that the black background you are placing it against is a frame filled with the [Black] color swatch, which is just 100% K ink without other components.
Adding other inks with 100% K results in a darker black, possibly with a cast toward another color, but still a color you would call black. Themore additional inks you add, the darker that black becomes, and 100% k, when printed, looks like gray in comparison. You may also have your preferences set to deceive you. In the Appearance of Black section, make sure that you have Display All Blacks Accurately set to show you the difference on screen.
When you export, colors can be preserved or converted to a destination profile. If you are converting RGB to CMYK, you will get a 4-color "rich black" equivalent. If you are converting to a different CMYK space than you have set for your working space, and you don't "preserve numbers," your 100% k will also convert to some four-color mix, but one that is lighter to simulate the single component black. If you convert to RGB, your blacks will convert to three-color RGB mixes.
What this means is that unless your image has a "dead flat" color (i.e. an artificial background that you've added in compositing an image) and you fill your drawn background in ID withthe same color mix (and are using the same color space as the image for your working space), there is virtually no chance of getting a seamless transition from image to ID background.

Aperture locks up when Exporting Versions

After upgrading from 2.1.2 to 2.1.3, whenever I export versions Aperture locks up until the export completes and I cannot do anything in the meantime. Sometimes this is accompanied by the SPOD and sometimes not. Also, the time taken to export varies greatly, by up to a factor of 3.
In effect, all these problems mean that I don't have background processing which was one of the big improvements of v2.1.
Regards,
Terry

I'm having the very same problem. This is bad news. I upgraded to Mavericks last week, and then had to update Aperture. Now it says my 400+GB library has to update, and then at the end it won't complete. I've done this with a three months older copy of the library.
Apple, you need to figure this out--I'm a working professional and now I don't have access to 4-5 years worth of work--this is serious. My library appears to be corrupted.

Text fades mess up when exporting to AVI

Hi,
I'm doing some pretty simpe text fades in flash by changing the alpha from 100% to 0% for a piece of text.
This works fine in the SWF export, but when I export to AVI the text corrupts (shifts, expands and looks interlaced) during the fade portion.
I've tried doing this with a brightness shift, and even ticking he "cache as bitmap".
I tried exporting as 32bit movie with alpha. That stops the corruption, but now there's a flicker juse before the fade that's not there in the SWF!
Anyone know what I'm doing wrong?
I'm using Flash Professional CS5 by the way.
Many thanks!

Another option is to do a screen capture. Lots of choice in software.
Google "screen capture software" for more info.
Best wishes,
Adninjastrator

How to save or export a multichannel PSD or TIFF to JPG?

I have a file that has one layer and 9 channels each channel is a diffrent color in the design.
the design looks great on the scream but there are no options to save the file as a jpg or png or to export for web.
to get this file to jpg this is the steps I have to do.
1. File Print and select Microsoft XPS Document Writer as the Printer
which gives me an "*.xps" file.
2. Open the *.xps file in the XPS Viewer then do File Print then select the Adobe PDF as the Printer.
which gives me a *.pdf
3. Open the *.pdf in Photoshop and I will be about to save it to what every format I want.
Note when I try to print directly to Adobe PDF the print becomes small, i have adjusted settings and same result aways.

NM
-Noel

Aperture 3: Losing quality when exporting to jpg

I'm downloading raw (nef) images to my hard drive from a Nikon D7000 then importing into Aperture 3. I make changes mostly with Enhance within Aperture 3 and using the Color Efex Pro 4 plug-in. Looks great in Aperture and if I export using any of the tiff options. Quality remains the same. But if I export to jpg (any of the options) or open the tiff in Photoshop Elements and convert to jpg I loose quality. The photo looses sharpness. I have a tif and jpg side by side and the difference is huge. I want to upload to my website so therefore need to use jpg but I'm hating how poor the quality is.
Any suggestions? I see other people are having similar issues.
Thanks!

How are you viewing the exported JPG? What is the size of the JPG file?
If you open it in Preview and then go to Tools->Show Inspector you'll get some info on the makeip of the file.
Here is an example of an exporte JPG at quality 12 and original size:
Whats your's look like?

Exporting RAW to JPEG and TIFF

Evaluating LE to hopefully improve some workflow. I noticed however, that when export to a JPEG or TIFF format the file size seems much smaller that I'm accustomed. A D100 9.5MB RAW file converts to appx 2.7Mb JPEG at 100% and appx 7MB in TIFF. Currently when I convert I get a 17-20MB JPEG. I'm I missing something in the setup or is this the larger file size LE produces.
Murray Edwards

Excuse me Lightroom. I currently use Portfolio 8 to review and tagged a large number of images for production. They have a conversion process that allows you to convert a NEF file to JPEG or TIFF. When converting to from a NEF file that is appx 9.5MB in size to a JPEG at 100% @300DPI which is what my clients require, it produces a a JPEG file that ranges from 17-23MB depending the amount of information. But I still have to pull that image into editing SW to do some cleanup or slight exposure adjustments. It was my hopes that by using Lightroom, I could slimline a couple of these processes. But if LR only provides a exported JPEG file size of what I've seen thus far, then I would unable to accomplish this.
Is this better clarification of my question?

What is the best settings to use in the export manager when exporting from Aperture 3.5 to Photoshop cc. tiff? psd? 16bit? dpi?

What are the best settings to use in the export manager when exporting from Aperture 3.5 to Photoshop cc for editing?
Should I use tiff or psd?
8bit or 16bit?
How many dpi?

That will depend on the photometric resolution of your originals. For jpegs it would be a waste of space to convert them to a higher resolution than 8bit, but if your images actually have already more than 8bit, you will want to preserve this quality. Then he 16bit format will help to prevent color clipping.
Both tiff and psd will preserve the lossless workflow. With Photoshop as external editor I would use he psd format for better support of layers and transparency, e.g., when you want to create watermark files.
The dpi will only matter, when you export the file for printing.

Where can I give feedback regarding Aperture? I'd love to see the ability to removes EXIF data when exporting, especially to social networks.

Where can I give feedback regarding Aperture?
I'd love to see the ability to removes EXIF data when exporting, especially to social networks.

Robert,
For any normal Export, simply cilick the list of option and further click on Edit. There deselect to include Metadata, and there will be no EXIF data exported. But no copyright info either.
The option already exists to do what you want. Once a normal Export has deselected that, I believe even exports via plugin for say FB will not have it either. I tested with an export to SmugMug after deselecting in an earlier ordinary export, and EXIF info was not transmitted.
Ernie

When exporting files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might do 524 images but not the full 600. I've tried resetting Aperture, it's the latest version etc etc. Help please!

If anyone can help me with this I would be seriously grateful.
When exporting mutliple files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might make 524 pages but not the full 600. I've tried resetting Aperture and its persmission and am using the latest version of 3.
I have 3600 images which I need to upload as sublfolders, each with their own URL and at the moment Aperture is dropping of anything from 1 to 90 images.
This is critical as people need to see each and every on of these images online. So if a file has 600 photos in it, Aperture should make a URL with 600 full image pages. And this is what it's not doing. On small files, say 30 or so it seems to work well, it's when it gets to more than that the problem starts.
I've used Aperture in the past under previous versions and not had this problem.
Any help would be great.
Thanks.
Bob.

Hi Jack,
Thanks for responding (as it seems as though no one else has been able to provide any insight as of yet)! Not sure if you saw my recent post, but the version of Aperture on the 2008 MacBook has been upgraded to 3.1.2 (not sure how; I bought it in 2009, but only have OS X 10.5.8... which apparently can't house 3.1.2 of Aperture, but hey, like many other anomalies i'm encountering, I'm no longer surprised!). I am unable to upgrade it any further, as it warns me that my OS X does not fit the requirements. I exported the projects as libraries; however, like I posted before, apparently these are from too old of a version for the new Aperture (3.3.1) to handle and import.
It's getting to the point where I'd almost pay to upgrade the OS X on my previous MacBook (10.5.8) to something newer in order to THEN update Aperture to a newer version; however, my previous MacBook simply cannot handle this (the specs are awful -- hence my decision to save up and upgrade to the newest MBP with Retina).
I've spent hours upon hours transferring files, libraries as projects, previews, versions, even masters (though, apparently some of them aren't accessible?) with no luck. I've rebuilt the library and reprocessed everything. And this is all after having to return one MBP already since Aperture 3.3.1 is glitch-y as it is, and froze everything for having a "managed library". So, now that I know that I have to deal with a referenced library in Aperture... I just need to actually transfer my previous library to my new one (hopefully WITH adjustments since these are years worth of photos and work).
Again, any help is appreciated. I've lost enough sleep, time, and vision health over this at this point.
Also, I know Migration Assistant is an option, I was told that it wouldn't work properly anyway because of the different operating systems, and the potential for problems.

How to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

how to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

Within Aperture you have Images, which are constructed on-the-fly from two files (the Master and the Version). You get an image-format file _only_ when you export an Image. You select the file name (usually a scheme) when you create an image-format file (that is, when you export). Look under "Aperture→Presets→File Naming" for built-in Presets. You can, of course, create your own or customize any provided.
The Preset is applied to only the file newly created by your "export" command. It is not applied to the Image in Aperture (unless you rename your Versions or your Masters).

Colour loss when exporting jpeg from Aperture 2.1

I'm having a problem with colour loss in images i'm trying to export to a website.These are jpegs that have been worked on as RAW in Aperture,when exported to desktop and viewed in preview there is no colour loss at all, but when viewed on the site the colour saturation seems very dull and lack lustre - any ideas?? I have checked all the export presets (been going through all the posts to see if i could pickup anyone else finding the same) and they are all at the same settings. Thanks

Go to the tools menu and then assign profile. Choose the display profile that your monitor is using. This will effectively stop preview from doing any translation to your monitor. See if this matches what you are seeing when you upload to the web. If it does then somewhere in your upload, process, web server chain the profile is being removed from the jpg or the browser you are using ignores color profiles (most windows browsers ignore image color profiles, that's why adobeRGB profile images look like crap to most windows users when viewed in Explorer)
Ps if this is the case nothing is wrong you are just getting a preview of how most windows users will see your image on the web. Adjust to taste.
RB
Ps. Some good info and humor here:
http://www.rwboyer.com/RBDesign/Blog/Entries/2008/4/16_Color_Management_and_Other_Stupid_InternetTricks.html
Message was edited by: rwboyer

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
~/Library/Application Support/Aperture/Plug-Ins/
where ~ is the home location for the current user account. All the other plug-ins however were installed in
Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

Aperture 3 messes histogram when exporting to either PSD or TIFF

Similar Messages

Maybe you are looking for