Aperture not exporting metadata when exporting masters

It says here (http://docs.info.apple.com/article.html?artnum=302943) that "by Design" Apple doesn't allow you to embed the metadata into an exported master file. Any idea why this is 'by design'? It doesn't make sense.
Their 'work around' is to double your work by exporting masters (with no metadata) and then exporting versions (say, as JPEGs with metadata) and keep both files together.
I am trying to archive copies of Masters along with their metadata and want to avoid duplicating work that is grossly inefficient.

Well, DNG export could really be the option for
people who require raw + added metadata in one file.
There's another thing that interested me _soooo_
much in your reply% it's about connection between raw
files and editorial. I don't shoot for magazines yet
(though I will be soon enough ))) ) but I'm surprised
clients require raw. Or it is your preferrable way of
giving your work out?
As a PE, I require RAW files, as 9.9 times out of 10 my color house is going to be better than the photographer at preparing the image for print. This is the same for most of the higher quality publications out there.

Similar Messages

Aperture 3.1.2 When exporting files to Finder is creating a folder for each file, that means export 200 files is creating 200 folders for each files. Does anyone knows how to fix this. Thanks

Aperture 3.1.2 When exporting files to Finder is creating a folder for each file, that means export 200 files is creating 200 folders for each files. Does anyone knows how to fix this. Thanks

No. This is NOT true. I've been battling with this for a couple hours.
I choose Export>Versions
choose
Subfolder Format: Project Name
no custom subfolder
Name Format: Current Version Name.
Aperture creates project folders for each image and names them Projects1, Projects2, Projects3 etc.
To be sure, I have no project named Projects
x
This particular Aperture library has 16 projects. you can see in the screen grab it's created more than 30 folders
If I uncheck the Subfolder, that is say NONE, I just get images and images and images, not in their project folders (of course, because I've said NONE, so why would it put them in project folders?)
I just want to export the entire library and have the versions placed in folders named by the projects from which they came.... ez enough, no?

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.

"Non rectangular objects will not appear correctly when exported using CSS."

I am using Ind CC 2014 exporting a document to a reflowable epub. The document contains an .ai image. The image exports correctly in some parts of the.epub but not others, where it is distorted. There is a warning on export :"Non rectangular objects will not appear correctly when exported using CSS." Any suggestions appreciated.

Thanks!
>
"Non rectangular objects will not appear correctly when exported
using CSS."
created by pooja2087 <https://forums.adobe.com/people/pooja2087> in
/InDesign EPUB/ - View the full discussion
<https://forums.adobe.com/message/6886892#6886892>

Missing file number suffix metadata when exporting

Hello All,
I export files from Lightroom 2 (LR2) using custom filenames that include file number, i.e. "Original number suffix", metadata. This metadata is not being picked up by the export module and will therefore not be included in the exported filename. This happens with files that have been edited in Photoshop (CS3), but not with the original DNG files.
So if I have a master file named "Davison-20080809-1234-Master.psd", I in Lightroom 1.x (LR1) I set up a custom filename scheme in the export dialogue box that will export the master as "Davison-20080809-1234-BW-Web.jpg", or similar. This has worked with no problems to date.
In LR2, when I look at the Example field under File Naming in the Export dialogue, I see only "Davison-20080809-BW-Web.jpg"--the original number suffix is missing along with one of the hyphens around it. When I create a custom file naming scheme with only the "Original filename suffix" metadata in it, it shows "_.jpg" in the Example field.
It looks like maybe two things are happening.
In LR1, if a piece of metadata was missing, it would still export a filename with all the hyphens around the missing data, so I would get "Davison-20080809--BW-Web.jpg" if the number suffix were missing. Someone probably tweaked that in the new version of Lightroom so that the unsightly double hyphenation would not appear. So this doesn't look like it's related to the problem.
The second thing that appears to be happening is that Lightroom 2 is either not exporting (in file metadata) or not tracking (in the LR catalogue) the number suffixes. I've looked for the number suffix in Photoshop's metadata and it's not stored in the metadata at all. When I copy a Photoshop file with a suffix that does export correctly in LR2, rename the file "Test-20080809.psd" and import it into LR2, Lightroom parses the date (YYYYMMDD) as the number suffix and "20080809" is what I get when I export that file. This indicates that LR1 and LR2 store the number suffix in the catalogue and for some reason LR2 is not preserving the number suffix in the catalogue metadata when a file is edited in Photoshop.
So has anyone else run into this problem? Or is someone interested in reproducing it? It looks like a bug to me.

I'm also running into this same problem. For what it's worth, when I import my RAW files (as DNGs), I rename them using a naming scheme which looks like the following:
(2008-08-13) -019- (7108).dng
This scheme is created with the following elements (separated by line-breaks):
custom date formula
import number
original file suffix
In Lightroom 1, I had no problem. Now, I'm wondering if the parenthesis after the end of the file suffix is what's causing Lightroom 2 to think that there is no suffix?

SWF animations not working properly when exported as PDF from InDesign

I'm using InDesign CS5 and have created a document that I want to add interactivity and animations to. I've created buttons and page destionations, etc, which all work perfectly when exported to a PDF but the simple animation that I wanted to include don't work. The animations have been created in InDesign then selection exported as a SWF file and then imported and placed in InDesign and then exported as an interactive PDF where the animations either don't work, haven't been picked up or don not work as they should. What am I doing wrong, how do I get the animations to work correctly?

Try this tutorial:
http://tv.adobe.com/watch/csinsider-design/indesign-creating-interactive-pdfs-with-page-tu rn-and-flash-animations/

How to preserve metadata when exporting non-jpgs from iPhoto?

I have a problem with an iPhoto library, and need to move the photos to an undamaged library. (I have been able to confirm that the problems are specific to the library and not to individual images or with other iPhoto libraries on the same computer, and rebuilding options have not helped.) I can export the processed jpgs intact with the metadata (titles, descriptions, keywords) that I added manually in iPhoto, import them to another library, and the metadata is intact. But unless I convert the TIFF and NEF originals to jpgs, they lose the metadata on export.
Is there a way to get these original format files into another library with their format and metadata intact?

1. Why not simply rebuild with iPhoto Library Manager
This will do that process for you - and preserve as much of that metadata as possible, along with Albums and much of your organisaion.
2. You can't export the Original plus the added metadata, then you wouldn't be exporting the Original. You can export the Tiffs as tiffs though, and that can include the additional metadata.
3. There is no way to write the additional metadata to the NEFs.
Regards
TD

Trouble maintaining original "date taken" info and metadata when exporting TIFFs from original CR2 files.

When exporting TIFFs (from original RAW), I noticed my metadata said the "date created" was the day of export. I want to be able to access the date the original image was taken as opposed to the day I exported it. Is there a way to maintain original date of image taken in my info? I couldn't seem to find it after I exported my TIFFs...

I just tested this with LR 5.5 Mac OS 10.9.3 and it works correctly for me.
To troubleshoot your problem:
1. Which version of LR and which platform (Mac, Windows)?
2. Which tool or command are you using to examine Date Created of the exported TIFF?
3. Upload a sample TIFF showing the problem to Dropbox or similar and post the URL here. This will allow us to take a look in detail.

Songs not loud enough when exported to disk.

Hey guys.
I exported my songs I recently recorded as mp3's. I uploaded them to Mypace, and unlike previous recorded in GB, they were much softer. I have no idea what's causing the problem. Just to show you all, here's my page.
The two I uploaded today are Drum Demo and Samba Sample. The others were uploaded a pretty long time ago.

ZachPlaysDrums wrote:
I saw the topic about exporting to iTunes and I saw the suggestion about turning auto nomalizing off. I did, but now some of the louder fills (it's only a drum track) clip.
The issue is that there is too much dynamic range between the loudest notes and the softest. Normalizing brings the loudest notes up to the loudest value (0 dBFS), but since there is still a leap between the loudest and softest notes, the average notes will still be well below the top values, making the overall track seem soft. Turning off normalizing allows you to bring the overall level up, but as you found out, the loudest notes will clip when you get the average levels where you want them.
The solution is compression.
If you compress your tracks, you reduce the overall dynamic range (the softest notes aren't as far away from the loudest notes as they originally were), which lets you raise the average (and perceived) volume on the overall track without clipping.
The danger is over-compression.
If you over-compress, and reduce the dynamic range too much, the track can sound dull and lifeless. However, a little compression is the way to tame the dynamics and increase levels without clipping.

Video Editing changes to inpoint and outpoint not being saved when exporting.

I'm editing .mov 1080p video clips from my DSLR in Lightroom 4.4. I,m using the slider bar to set a new "inpoint" and "outpoint," shortening the video. When I export, I am using the original format and new file name. Lightroom tells me the video is shorter in length, but when I play it back in Windows, the new file is the original length. What am I failing to do/see here? I'm using Win 7

In my experience when you export in the original format (MOV) you lose all adjustments, including length shortemimg.
Maybe someone can explain what the use is of this setting?
The adjustments are only reflected when exporting as H.264 (MP4) and maybe DPX which I never have used.

Why are 16x9 photos from PSE8 not filling screen when exported to PRE8?

I batch cropped a bunch of photos to (JPEG) 16x9 and created a slideshow in PSE8 (about 100 slides, 3.2 sec duration, random pan/zoom, random 1 sec transition). I had to click on each photo "properties" and choose "fit on slide" since it was defaulting to "crop to fit" (which was further cropping my 16x9 photos down to something not desirable).
When I "Output to PSE8" it shows up in the sceneline as not filling the entire space. If I click on this slide show in PRE8 and use the "properties" then "motion" and increase the size of the pictures, they come out blurry. However, if I insert one of the 16x9 photos directly into PRE8, it fills the entire screen and is perfect focused.
PLEASE tell me there is an easier solution than having to create the entire slideshow in PRE8. I really like the random transitions, easy batch duration pan/zoom, control.

Thanks for such a quick response Steve. I will attempt to add more information to help clarify your addtional quesitons
The pan and zoom I am using is the default (very minor- just enough to give the perception of movement).
If I import directly into PRE8 the picture(s) look perfect. It just seems to occur after I port to PRE8
I am not sure what workflow I am following but will be a bit more specific as to the steps I have been taking:
1. I open the PSE8 workspace and choose "organize" (not edit)
2. I click on "create" then click on "slideshow"
3. Next I set my specific defaults (for this project) 3.2 sec interval, 1 second Random transitions, apply pan and zoom to all slides and leave the "crop to fit slide-landscape" checked ( thanks for the tip to uncheck this next time, so I dont have to do it to every slide!!)
4. I then import my media from "add media" "photos and videos from folders" place the photos in the order i am looking for then save the project.
5.I next click "output" and "edit with Premiere Elements" - which open PRE8
6. in PRE8 setup I choose the "HDV 1080i 30" configuration.
The slideshow has now ported over to PRE8. The slideshow bundle does not utilize all of the space in the sceneline, hence my problem (black bars top and bottom of screen). Ironically, when I import via get media (directly from PRE8) the same pictures from my computer file (not in the organizer), they fill the entire space in the sceneline (no black bars on top or bottom). I have this problem regardless of whether or not I am using the pan/zoom or the unchecking of crop to fit slide landscape in PSE8.
I can send a screen print if you think that might help??
I sure hope this helps, all the other video items that are not related to this slideshow are perfect and this is killing me!!
Thanks, again, Mike

HELP! Aperture corrupting my library when relocating masters

I keep my aperture library on my system disk, and I use referenced masters on a NAS. Everything seems to have been working fine until now. I had a rather large project that I was cleaning up, wanting to delete my no longer needed masters (about 2200 out of 3500 files). Unfortunately, I forgot to check the box to delete referenced masters - I didn't even realize it was there until I went searching when it didn't delete them. Anyway, what I thought I would do is simply relocate the masters from by project to a new project, then I could delete the masters left behind.
What happened was that Aperture started moving masters from other projects into the new project - Files that were not selected in Aperture when I executed the relocate masters command. Now these other projects have lots of images with "unsupported image format", I'm assuming for the masters that got moved into this new project. What happened?

I've attempted to fix this by restoring the JPEG files that I had originally "removed". This did not seem to resolve the problem as when exporting the masters I still find many, many files from other projects being exported as part of this project.
Granted, I brought this problem on myself by deleting the JPEGs, however this seems like a pretty serious defect in Aperture. I could understand if after deleting a JPEG Aperture could not locate the JPEG master and displayed some sort of indicator of such. However there is no indication that anything is wrong, it's just picking up random files in place of the JPEGs, and in those other projects, the images are "unsupported file format" with the filename showing some sort of metadata in an iPhoto library on the same disk.
I have a vault that probably has the database from these other projects intact. Is there a way to restore that information? (remember that all the masters are relocated).
Thanks in advance for any advice you can offer to help fix this.
- Howie

Error: Invalid Export dll when exporting to Excel from VB,NET 2008

Version: Crystal Report 2008
Front End: Visual Basic 2008
Hello,
I am trying to export a report to Microsoft Excel [2003] when I get the error "Error in File_Temp......Invalid Export dll or export format".
from the Windows Form Viewer.
I have looked in C:\Program Files\Common Files\Business Objects\3.0\bin and found crxf_xls.dll and crxf_xls_res_en.dll, but am not sure if these dlls' are the error source.
Do these dll files need to be reregistered? Re-installation hasn't worked.
Thanks
eburton

Duplicate

Aperture Not Recognizing Duplicates When Importing From iPhone. PhotoStream is Involved.

Apple makes great software. Aperture is not some of it.
Here's my setup:
'11 MacBook Air OS X Lion
Aperture 3.2.2
iPhone 4 ios 5.0
1.5 TB External Drive. Aperture Masters and Library reside there, separate from each other.
I keep my photos in a structure such as: Aperture Masters > Year > Month > Date > original_photo_name
I'm running into trouble with Aperture not recognizing what photos are duplicates when it comes time to import photos. My workflow is that I'll import photos every so often, leaving them on the iPhone, and delete them twice a year.
ISSUE 1 (The Annoying One):
Aperture is showing a lot of photos that have already been imported even if I select "Don't Import Duplicates". Aperture has done this for a long time. I know that when it comes time to importing them, it doesn't import the duplicates, but this is just a sign that something doesn't work very well. (Maybe it's because I switched to an iPhone 4S and then back. I synced all my photos, and then back again to my iPhone 4, so the sequential number of the photos remained intact. I don't think that's the problem though.). This is just a minor annoyance that shows that Apple can suck at software (remember MobileMe?).
ISSUE 2 (The serious one):
short version: Some photos on my iPhone won't sync to my Aperture library because it thinks they've been synced through PhotoStream. They are not in my Aperture Library or in my Aperture Masters in the filesystem. How can I fix this. What bloody file do I have to delete for Aperture to stop being confused?
longer explanation: When iOS 5 came out, I was excited by PhotoStream. I had enabled it on my MBA, through iPhoto (I hadn't installed Aperture on it yet, as I was using an iMac to manage my Aperture Library). I believe it synced a bunch of photos from my iPhone, but then I stopped using it on my mac. Left it on on my iPhone. Installed Aperture. I initially enabled PhotoStream but swiftly disabled it once I was not sure how it would deal with photos being uploaded from my mac etc - just seemed like too much magic was going on. I then proceeded to sync my iPhone, not importing duplicates, and it synced a bunch of photos, but didn't sync some of them, displaying the following message:
Any tips on how to fix this and be able to import those images would be greatly appreciated.
P.S. - I thought that iPhoto might be causing the problem. I checked there and there were some images imported through PhotoStream, but not some of the ones which were not imported on Aperture. Putting that another way: the iPhoto library accounted for some of the images that were not imported, but not all of them. I deleted the iPhoto Library and tried reimporting with Aperture. Still no luck.

I have precisely the same problem. Very annoying. Worked fine with iPhoto, borked with Aperture 3.

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

Aperture not exporting metadata when exporting masters

Similar Messages

Maybe you are looking for