Minimise Embedded Metadata Confusion

I am sending images off to magazine publishers and need to be able to send them with Copyright,IPTC Creator info and caption. as far as i can tell LR has 2 pointless options when you minimised metadata on export:
a) JPEG: Just the copyright & rights usage field. Without the owner contact details this is pointless isn't it. No caption
b) TIFF: Copyright, rights usage, creator name, caption. However no contact details and includes all the EXIF info.
As far as i can tell I cannot use minimise metadata as always leaves out improtant things or adds things you don't want!!! Is it possible to do what I want?
Thanks

But wont that wipe out all the metadata I want to keep for myself? Also the EXIF data will still be attached. I'm not sure why people don't want to sent this out, but guess something to do with restriciting information about how the picturew was taken.
Seems a bit odd that the minmise doesn't include creator details as well as copyright as 2 go hand in hand. Also typically anyone you send it too wants the caption. Wondered if I was being stupid!!!

Similar Messages

  • Embedded Metadata Preservation and publication

    Will Muse allow me to publish web pages in html5 that expose my metadata currently embedded in photographs cataloged Adobe LR?
    We have populated the IPTC and IPTC Extension fields for our images with important metadata and do NOT want it stripped upon web publication.

    Andrew:
    What you describe is much like how Google Picasa Web Albums and Flickr "used to" do this.  The original was stored "as-is" and the images that were downsized for preview and thumbnail were stripped of all metadata.  After a number of users complained about this issue, they now preserve at least some of the embedded metadata for the previews and other derivative files. If I recall correctly, Flickr only preserves those values that are part of the older IPTC schema known as IIM or Information Interchange Model -- but this would mean that at minimum the owners copyright notice would remain intact (as well as caption/description, basic location information, credit and keywords).
    While better than nothing, that's still going against principle five of the Embedded Metadata Manifesto, "Other  metadata should only be removed from files by agreement with their copyright  holders." (http://www.embeddedmetadata.org/embedded-metatdata-manifesto.php).   Muse seems to ignore principals one through five in regards to all images except for the original!
    Does the Muse system give any warning to users that the application is removing all the metadata from these derivative images?  I would consider that to be the least that could be done. Then those that don't care about having additional potential "Orphan Works" floating out in public can continue. Those that do care about protecting their intellectual property can opt not to continue (until or if this is fixed).
    Why doesn't Muse operate like the Save for Web & Devices (SFW&D) save option in Photoshop?  It is part of the Adobe family right?  The default with SFW&D will at least retain the creator and copyright notice, though the user can use the pull down menu to choose several other options including ALL.  Talk to Alan Lilich (one of your Adobe Engineers) about how much overhead this really takes with most files. He and Dennis Walker from Camera Bits (makers of Photo Mechanic) both backed me up on this point when I presented findings from the SAA Survey of Stock Images at the Microsoft Pro Photo Summit in 2007 (Video summary of that presentation).  Even for smaller files it's really not that exhorbitant. See point three in the "Metadata Myths" article at (http://www.controlledvocabulary.com/blog/top-metadata-myths.html) for details.
    It's a real shame that you don't at least give the user the option of leveraging that embedded metadata already in the image by inserting it into an area around the image on the page. While having all embedded metadata appear automatically is an option,  I'm sure that for some this would be annoying as they would have to then  cut that copy from the page. However, is there a reason why there could not be a check book that the user can check to load this info into the Page text when the image is loaded?  That would save a lot of opening the image in another application to gain access to the metadata (or going to Photoshop or Bridge and using File Info) -- then Copying and going back to the page to Paste in the info would take.
    Many page layout programs for news operations automatically load the Contents of the Caption (Description) and Credit fields below an image when it's place into a layout.  I don't see any reason why Muse couldn't adopt the same approach. Or at least have this as an "option" in the preferences for a user.
    Should I log this as a "feature request"?
    David

  • Will FCE automatically log embedded metadata when ingesting QT .mov files?

    Hi --
    I'm trying to figure out whether to purchase FCE to help in a large project. I am about to create a couple of hundred QT files that I want to bring into FCE for editing. Each file will be tagged (logged) when created to allow searching in ITUNES. The tags reside in the INFO/COMMENTS field in the .mov container.
    *Will FCE recognize the QT tags on ingestion? Can FCE automatically populate each file's logs with the appropriate tags?*
    Obviously, a yes answer will save a huge amount of work. And, I welcome any alternative approaches.
    Much thanks,
    Ken

    Thx for the quick, helpful and somewhat unfortunate response.
    Any chance it works the other way, i.e can tags/log info be exported to the source .mov file.
    Am I missing some other strategy to share tags/logging between FCE (or any NLE for that matter) and embedded metadata in the source files (QT in this case)
    Again, thanks for the help.
    Ken

  • Minimize Embedded Metadata - only works for JPGs?

    According to the Help File, under export options for JPEG, TIFF, and PSD:
    "Minimize Embedded Metadata Includes only copyright metadata in the exported photo."
    But in my tests this is only true for JPEG. I can still find camera data in the EXIF for TIFF and PSD (although it is less than the full EXIF).
    The JPEG has only copyright as expected.
    Am I misunderstanding how that function is supposed to behave or is it not behaving correctly?

    Using exiftool, I just verified this too. Not only is the camera information present in the tiff file, but the IPTC Caption info is included in the tiff exif "Image Description" field. I didn't test for all metadata fields, so there could be more.
    Granted, when most folks seek to "minimize metadata," they're usually using jpgs targeted to the web. Still, I would think that LR would be consistent with what is omitted with the minimize metadata option.
    Edit: should have noted that I'm still on LR 2.1

  • Remove embedded metadata

    Hello,
    I was given an MOV document on which, the metadata info is embedded into the file.
    I'm trying to use Final Cut Pro to remove the embedded metadata information.  Everything is seen directly in the video.  Trying to see if I can remove that "layer" from my video.
    Any suggestions on how this can be done?
    Thanks !

    Are you saying that when you play a mov file in Quicktime Player you see text written over the video?
    If I understand what you are trying to say, the answer is you can't. That text is not separate, it is part of the video. No dice.
    But then maybe I misunderstood your problem, so please clarify.

  • LR3 JPEG/DNG Metadata Confusion

    Hi,
    I'm a little confused about XMP data and the LR3 catalog itself.
    First, I understand that DNG files can have embedded keywords and other metadata -- and 95% of my files are CR2 files that I bring into LR3 as DNGs and keep them as DNGs.  So I am NOT using raw files with sidecar files.
    But where I'm confused is the "automatically write changes into XMP" LR3 catalog option and how it relates to JPEG files.
    I was of the understanding that if I make changes in the develop module (eg. contrast)  to a JPEG file (not a DNG), then these changes will NOT be saved to the original JPEG file, but will be "recorded" in the LR3 catalog.
    But now If I allow LR3 to "automatically write changes into XMP"  -- will this WRITE these develop module changes (e.g. the contrast change)  to the original JPEG?  Or does the "automatically write changes into XMP" only refer to the keywords and other metadata in a JPEG file?
    Thanks for any help in clearing this up,
    R

    So just so I have this correct with JPEGs:
    1, If I make changes in LR3 to a JPEG (e.g. contrast), this contrast change is saved in the LR3 catalog.
    2. I can ADDITIONALLY save metadata (keywords, etc)  in XMP data into a JPEG if I have the "automatically write xmp." settings checked or if I save it manually to the file
    3. I can ADDITIONALLY save the develop settings (e.g. the contrast change I made in #1) by including the develop data in the JPEG in the same dialogue box.
    But now if I opened this keyword, added contrast-adjusted JPEG in another program,  only "XMP-aware" programs would allow me to see these keywords and contrast changes.  Is this a correct assessment?
    And lastly, if I do save the develop settings to the JPEG itself, doesn't that violate the "non-destructive" editing concept of LR3?
    Thanks again!

  • ITunes does not display embedded metadata for my podcast

    Tools in use:
    Garageband (.m4a formatted files)
    Blogger (http://gspodcast.blogspot.com)
    Feedburner (http://feeds.feedburner.com/blogspot/GeekSpeak)
    iTunes (http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=202319851)
    I'm trying to figure out why iTunes is pulling in my blogger posted text instead of using the metadata embedded in my audio file for the GetInfo text descriptions.
    As an example...
    If you were to look at my Episode 1. The GetInfo data displayed reads:
    Download Episode 1: iTunes Audio MP3 Audio The Road to Hellboy... We hang out with Writer/Director/Producer, Tad Stones and talk about past, present, and future, including his current project Hellboy: Sword of Storms. Lovely Copyright Stills Courtesy of Tad Stones Also... We discuss our Top News Stories. Recommended Movies. Recommended Comics. UPDATED: Podcast Notes... Transformers Cast List: Autobots Optimus Prime (MAC Truck) Bumblebee (VW Bug) Jazz - (Porsche) Ratchet - (Ambulance) Ironhide - (Fire van) Decepticons Megatron (was a Gun - Now an Alien Jet) Starscream (was an F15 Jet - Now an F22 Raptor) Brawl - (Tank) Bonecrusher - (Bulldozer) Barricade - (unconfirmed) Scorponok - (Scorpion) Frenzy - (Cassette tape) Blackout - (B1 bomber) Transcript of the Tad Stones Interview: Rich Text Format Plain Text Format
    If it were pulling the embedded data it would have read:
    Episode 1 - August 2006
    Topics:
    00:01:13 - Transformers Movie
    00:16:50 - Batman Sequel
    00:30:16 - Hellboy Sequel
    00:38:03 - Interview w/ director Tad Stones
    00:59:24 - Recommendations (Movies, Comics)
    Any idea why this is happening and what needs to be done to fix it?
    This problem does not occur if the audio files are directly downloaded and then played. Only when subscribed to in iTunes.

    You don't resubmit: you just follow the instructions in the page you mention, specifically adding the 'itunes:new-url' tag in the old feed. As you haven't published the URL for the old feed it's not possible to check it to see whether it's all correct.
    When you have done this it might well take a day or two for the iTunes Store to catch up: it won't be immediate.

  • Flex not embedding metadata in CS5 and CS5.5

    I believe we have a problem related to:
    http://blog.natebeck.net/2011/05/flex-sdk-4-5-doesnt-keep-embed-metadata/
    The project is a CS4 fla that has numerous files embedded with metadata tags:
    [Embed(source = "campaign.xml", mimeType = "application/octet-stream")] public static var campaignData:Class;
    [Embed(source="mirror.pbj", mimeType="application/octet-stream")] public static var MirrorShader:Class;
    [Embed(source="rotateCW.pbj", mimeType="application/octet-stream")] public static var RotateCWShader:Class;
    [Embed(source = "shopUpgrades.json", mimeType = "application/octet-stream")] public static var upgradesData:Class;
    [Embed(source = "help.txt", mimeType = "application/octet-stream")] public static var helpData:Class;
    None of the embedded data is being loaded in when compiled with CS5 or CS5.5
    This is a serious issue for us as it means that all of our Flash 10 projects are now uncompilable in CS5 and CS5.5 and we are unable to make money on these projects.
    What work around can we implement to solve this?

    what exactly is your requirement. I have been able to read and write using property XMPString
    this is the way to start, refer to extended toolkit documentation for XML class.
    var oXML = new XML(app.activeDocument.XMPString);

  • XML metadata conversion to embedded metadata

    For several years we have run a specific set of audio files as an rss feed. All the audio files were described in a single xml file. We are scrapping that system and moving everything to iTunes University but since all the metadata is in a single document I am not sure how I get that information connected to each audio file I am uploading to iTunesU. Is there a way to continue to use my xml file to describe my audio files or a way to take that information and convert all the xml data into embedded data?

    See my reply to your post in the iSync forum:
    http://discussions.apple.com/message.jspa?messageID=9618578#9618578

  • Metadata Confusion

    In Adobe Bridge, I made entries into the Document Title and Description fields of the metadata of an image. In Lightroom v. 3.3 for Mac OS-X, the same image has metadata fields named Title and Caption, but both are blank.
    What is going on here?
    FYI, the popular forum at flickr.com displays content of Document Title and Description fields of submitted images containing non-blank entries in those fields.

    Jack wrote: 3 -  Some editing tasks still need PS. My close-up work often requires a focus stacking application, which accepts DNG but saves in PSD. Some other operations are still (but see 1 above) better done in PS using PSD format, but instances of that are decreasing over time.
    But for most processing workflows, I'm finding LR to be clearly the best solution.
    No problem with using other tools to further enhance a photo; there are instances were you simply can't do without. What's important however is that this edit should be initiated from Lightroom (Right click and Edit In, or from the Photo menu and Edit In...then select the appropriate program to perform your changes). Once changes are done save the file with the external editor and exit the editor; the modified version will appear as a new photo alongside the original one (or stacked with the original). Don't rename the photo from the external editor as otherwise Lightroom will loose track of the file.

  • Adobe Lightroom 2.7 exporting issue (says it is exporting at 300dpi but exports at 72dpi)

    Hi,
    I have lightroom 2.7.
    I am a photographer that depends on lightroom. I do a lot of printing from images I export direct form it.
    I am trying to export images at 300dpi.  I am selecting 300dpi in the export box under image sizing.  I use mogrify plugin also if that means anything to anyone.
    However when I open up these images in photoshop and go to image size it says they are all 72dpi. My printers have also complained that this has happend as well as my wedding supplier. They all say my images are 72dpi.
    I have read all the forum responses like getting rid of the minimise embedded metadata check in the box etc and nothing is working.
    I am working hundreds of images at a time and therefore can't afford the time to set up an action in photoshop to resize every single image and sit there an hit the play button.
    Does anyone have a simple answer to this issue that has proven to have solved the problem or any other non time consuming work around.  Or even a support number for adobe I can call.
    It is causing me a huge amount of time loss and stress.
    Would be awesome if someone had an answer floating out there.

    Bella,
    I don't think you've understood my post above. When you export from Lightroom you create JPEG file, a JPEG file does NOT have a DPI measure. You cannot export a file at a certain DPI.
    The reason is DPI or Dots Per Inch is a measure of length, inches. A file does not have a length, or a width for that matter. The only meaningful measure for a JPEG file in this context is 'Image Size'. Image size is expressed as pixels wide X pixels high, in the case of your Canon 5616x3744.
    Exporting from LR, if you opt to 'Burn Full-Sized JPEG' at 100% then you will get a file of image size 5616x3744. Printed at 300dpi you'll get a print 18.7 inches wide.
    If you want a print bigger than that then you have to create more pixels. Software does this by 'making up' new pixels based on the pixels that are already there. Exporting from LR and adjusting the Image Sizing will do it. You can do it from Photoshop. For optimum quality it's best done with some knowledge of the final print size, and print device.
    From the sound of things if you supply both parties will full sized JPEG's then you are giving them as much as you can without getting into the murky world of upsizing. The metatdata tag that gives a DPI measure in the file is meaningless, don't let it fool you or the printers.
    Hover your mouse over the file (in PC, not suer about Mac) and Windows will show you the image size.
    Hope this helps.
    Pete

  • Confused Metadata after import from catalogue

    I have two catalogues on this machine. I just imported one into the other in order to merge them. The images in each catalogue have never been in the other.
    After the import, most, but not I think all, imported images have an icon either saying either:
    The metadata for this photo has been changed by both Lightroom and another application. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?
    or
    The metadata for this photo has been changed by another application. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?
    My confusion is because I can't see how either of these statements can be true for most of the photos, which have either lived in one or the other LR catalogue all their lives. Unless by "another application" it is just referring to another instance of LR in the past?
    I also don't understand whether "overwrite settings ... with those from the catalog" means using the metadata in the current catalogue, which came from the old catalogue (and which I therefore want), or whether it means overwrite the images embedded metadata with the (blank) metadata in the new catalogue after importing.
    Assuming Metadata really means literally that, and not Keywords or presence in Collections etc, then it's no biggy, as I don't use Metadata very much. But still, can someone guide me through the safest option for the 6000 imported photos?
    thanks
    Nic
    Amateur user, LR3.6, Mac OSX 10.6.8

    Ian-
    After reading your post, I did some reading, and now I get how to us LR's Paint tool!
    With only your jpeg selected in the Library module, go to grid mode displaying the other images you want to copy the keywords to. Select the Paint tool in the tool strip, and If you don't see it, select Metadata>Enable painting.
    On the right-hand panel, there is a Keywording text box with a comma-delimited list of keywords in the selected jpeg. Use your pointer to select all the list, then copy.
    Make sure the paint tool is set for Keywords, then click in the dim little text box next to the Paint: Keywords selection labels. It should turn white: copy the list into that text box.
    Now, click on each picture in the grid you want the list applied to and it happens! A message comes up. The spray paint icon changes to an eraser, so if you want to remove the keywords from an image, just click it.
    Pretty cool tool!
    Tony

  • XMP confusion

    I just can't get my head around this xmp thing. Some basic info:
    I use DNG files
    I back-up my Lightroom catalogue every time Lightroom exits
    and under catalogue settings >metadata I have ticked:
    Include develop settings in metadata inside jpeg, tiff & psd files
    + Automatically write changes into xmp
    I am about to start using Photoshop
    Some questions please:
    1) When I exit Lightroom & back-up my catalogue, does this also write the xmp into my DNG, or must this be a separate operation
    2) I've heard that auto' write changes into xmp can slow things down - is this correct for someone like myself who doesn't work with a huge number of images
    3) From what I've read it seems to me that maybe when I send LR4 images to PS for further editing I should ensure that LR4 edits are written into xmp (so even if catalogue back-up writes xmp to the dng, if I've made say develop module changes during current session I'd still need to write changes to xmp before opening with PS)
    The more I read about this the more confused I become. Can someone please answer these questions as simply as possible
    Many thanks

    Exporting Files
    LR embeds metadata from the catalog into all exported files and, if the Edit In feature is used (e.g. Edit in Photoshop), re-imports metadata from the file once editing is complete. This is entirely automated, requiring no manual operations from the photographer. This applies to all supported export formats (JPG, TIFF, PSD and DNG).
    Modifying Metadata Within LR
    If he so wishes the photographer may want to update metadata from within LR. By default, these changes remain inside the catalogue. The photographer may wish to manually update the file using Library > Metadata > Save Metadata to File or automatically using the Edit > Preferences > Catalog Settings > Editing > Automatically write changes into XMP. Same goes for Develop settings if the Include Develop settings in metadata inside JPEG, TIFF, and PSD files is selected.
    If metadata on RAW format files are modified and updated (manually or automatically) then a sidecar xxx.xmp file is generated/updated in the same folder as the original in order to avoid corrupting proprietary RAW files.
    Modifying Metadata Outside LR
    If metadata is edited independent of LR, LR prompts the photographer by displaying an arrow symbol in the top right of the image in Grid and Filmstrip previews. The photographer can either update LR from the file or re-write LR metadata to the file by clicking on the arrow or the using the features above.
    It should be noted that whilst advantageous to keep Develop and other metadata stored in image files in order to more effectively interface with other applications and protect from Catalog failure, it isn’t strictly necessary because exporting transfers the metadata anyway and your catalogue should be backed up regularly.
    Furthermore, assuming automatic update mode, constantly writing and re-writing out your master image files (not RAW) just because metadata has changed on the off-chance you might want to refer to that metadata outside of LR seems like an unnecessary overhead to me. Also, the fact that most backup programs will be compelled to re-backup your files adds to the system burden.
    Maybe it would be worth it if you planned to have two instances of LR running using shared image files – maybe a desktop and laptop with NAS?
    I don’t know, the case for turning this automatic XMP update hasn’t been made for me and my workflow. Maybe it will be for yours.
    Roy, to answer your questions specifically:
    Per advice from dj – separate operation but can be automated
    Per advice from dj, though I believe there has to be a performance impact when re-writing out master files just because you added a keyword or increased the white balance temperature by a few kelvin. Imagine adding a simple keyword to 10, 000 images...and then backing them all up.
    I disagree with dj on this, sending images to PS does involve xmp because LR automatically embeds the latest metadata from the catalogue into the exported file and updates the catalogue from the edited file on return. Nothing to do manually, though.

  • Exporting Metadata (caption information) from JPEGS to a comma separated value (CSV) file

    Here is my dilemma. I am an archivist at an arts organization and we are in the process of digitizing many of our materials to post them on the web and make them available to internet users. One of the principle components of our collection is a large trove of photographs. We have been in the process of digitizing these images and embedding metadata (in the Caption/Description, Author/Photographer and Copyright fields) via PhotoShops File Info command.
    Now I am at a crossroads. We need to extract this metadata and transfer it into a comma separated value form, like an Excel spreadsheet or a FileMakerPro database. I have been told that it is not possible to do this through PhotoShop, that I must run a script through Acrobat or Bridge. I have no clue how to do this. I have been directed to a couple of links.
    First I was directed to this (now dead) link: http://www.barredrocksoftware.com/products.html
    The BSExportMetadata script allegedly exports the metadata from files selected in Adobe's Bridge into a comma separated value (CSV) file suitable for import into Excel, Access and most database programs. It installs as a Bridge menu item making it simple to use. The the Export Metadata script provides you with an easy to use wizard allowing you to select associated information about a set of images that you can then export. This script requires Creative Suite 2 (CS2). This script sounds like it does exactly what I want to do, but unfortunately, it no longer exists.
    Then I found this:
    Arnold Dubin, "Script to Export and Import Keywords and Metadata" #13, 8 Aug 2005 7:23 am
    I tried this procedure, but nothing seemed to happen. I also tried to copy the script into the JAVASCRIPT action option in Acrobat, but I received a message that the script had an error. It also seems to me that this script does not set up a dumping point, that is, a file into which this information will be exported to.
    I am a novice, not a code writer or a programmer/developer. I need a step-by-step explanation of how to implement this filtering of information. We have about 2000 jpeg and tiff files, so I would rather not go through each file and copy and paste this information elsewhere. I need to find out how to create a batch process that will do this procedure for me. Can anyone help?

    Hello -
    Is anyone aware of a tool that will do the above that is available for mac? Everything I've found so far seems to be PC only.
    Any help is appreciated, thanks!

  • Extracting "File Properties" metadata

    After processing scanned images in Photoshop CS3, I am uploading them to a DAM solution that has the capability to extract embedded metadata using custom defined keys. I would like to know the syntax/structure of embedded metadata labels that display in the "File Properties" template of Bridge CS3 (e.g. File Size, Dimensions, Color Space) so that I can extract that metadata.
    Thank you!

    In Preferences>Metadata there are two choices for dimensions - inches and cm, check the box for your poison.

Maybe you are looking for