Lightroom 6.1 TIFF metadata issue

I work in Adobe Lightroom to process photos and move them to MediaBin (4.6) to catalog and metatag; this is what my company uses for its photo library. Last week Adobe creative cloud prompted me to upgrade Lightroom; I was using 5.7, and the newest version is 6.1. In doing so, the captions and copyright information that I write in Lightroom are no longer showing up when they come in to MediaBin.
At first I thought the metadata was getting stripped following being exported from Lightroom (exported as TIFFs), but when looking at the files in photoshop, I can see all of the metadata is present. I then began a series of tests to try and figure this out.
I first moved a previously exported TIFF file from the previous version of Lightroom into MediaBin, and I could see the data that was embedded. MediaBin was working as it should.
Next, I took a file exported as a TIFF from the new Lightroom and moved it into MediaBin. I could not see the metadata, as expected. Then I downloaded it from MediaBin- as I would do to fulfill a photo request- and opened it in Photoshop. I was surprised- all the metadata was there! For some reason, MediaBin just couldn’t see it.
Finally, on a lark, I exported a file from the new Lightroom, but this time made it into a JPEG. When I moved this into MediaBin, I could see the metadata! I tried this with other file formats- DNG, PSD- and only the TIFF files show up minus their metadata.
What could cause this to happen, and only in TIFF form? I am under the impression that Metadata is just simple text information attached to a file, but I am confused that only in TIFF form do we have an issue.
Thanks!

It appears that this is caused by the same problem described here: Lightroom CC: JPEG format tripping up other programs. JPEGs and TIFFs use the same layout of metadata, and I confirmed that your TIFF has the same atypical layout as LR-produced JPEGs.
The issue is not that LR has a "bug" -- the TIFFs and JPEGs it produces strictly conform to industry standards.  Rather, it's that there are many programs out there, evidently including HP MediaBin, that are buggy and don't conform to the standards and get tripped up by the atypical way that LR writes its metadata.  Of course, Adobe can't change all such non-conforming programs, so LR users would very much prefer that LR go back to using a more typical layout of metadata.
Please add your vote and opinion (with details) to the bug report linked above.  The more people complain, especially professional and commercial users, the more likely Adobe will prioritize a fix.

Similar Messages

  • Lightroom TIFF metadata issue

    Very shortly after Lightroom 2 was released I used it to convert all the photos in our archive from JPEG to TIFF.
    These were all the digital camera photos we had shot before we started shooting as Camera Raw. We use Lightroom
    for creating files but not for cataloging. For cataloging we use Cumulus as we have to provide access to people
    on both coasts. What I have recently discovered is that when I add keywords in Cumulus and write those changes
    back to an asset the keywords disappear from the file's metadata. If I take a sample file and resave it as a TIFF in
    Photoshop then write to it from Cumulus the keywords are all there in the metadata.
    My question now is, does anyone on this forum know what is different about the metadata structure between a PS TIFF
    and a LR TIFF. I'm hoping to get some insight into this so the Cumulus engineers in Germany can help me with a workaround.
    I'm trying to avoid having to convert 100-150,000 files.
    Thanks,
                Jeffrey

    Okay, using exiftool I took snapshots of the same photo's metadata in 4  different states.
    1- I took a tiff created in Photoshop and wrote  keywords to it from Cumulus.
    2- I then imported that photo into  Lightroom and exported a tiff copy.
    3- I reimported The PS tiff into  Cumulus and added a keyword so we could
    see specifically where  Cumulus writes.
    4- I brought the LR-tiff back into LR, added a keyword, saved to the file and
    then imported that into Cumulus. I added a keyword in Cumulus, saved to
    the file and, pow, all the IPTC data is gone.
    So, there are only a few thousand that we have written keywords to from Lightroom.
    I will stop that practice and only write from Cumulus but, I still wonder if I should convert
    all of those tiffs to PS tiffs.  hmm...

  • Metadata issues in A3 - This is a real concern

    Metadata issues in A3. This is a real concern if your images go to third parties from A3.
    http://www.controlledvocabulary.com/imagedatabases/aperture3.html

    Thanks, dzedward,
    I posted a reply with quite some effort in it, but it is
    dissapeared after pressing the reply button. what I as explaining
    was that I use an attached sound and so streaming is not an issue.
    Please look at the few lines of code I use in my demo (please use
    the link above for the fla with the WAV):
    audioClock=new Sound(createEmptyMovieClip("sound1",1));
    audioClock.attachSound("theSync");
    audioClock.setVolume(90);
    stop();
    //When playing a swf (in most cases) the audio clock is on
    every 46.4399093 ms.
    //A onSoundComplete function only starts ON a clock puls!
    That explains "gaps"
    //when people complain working with audio loops in Flash.
    //The audio sample used in this test has a 200 ms duration.
    It can't be shorter.
    //So it is started 25 ms from the end. When the sample is at
    the end, the flash player
    //pauses for 46.4399093 minus 25 ms, and starts the audio
    sample from the same point
    //again ( that is at the next clock puls). That's fine for
    hearing audio clock and
    //this test:
    audioClock.start(0.175,1);
    audioClock.onSoundComplete = function() {
    audioClock.start(0.175,1);

  • Lightroom is not saving metadata. I have done several things to save and I still get the tag that states is is not saved. I have also created 2 smart collections. One showing metadata has been changed and one showing metadata is not up to date. No matter

    Lightroom is not saving metadata. I have done several things to save and I still get the tag that states is is not saved. I have also created 2 smart collections. One showing metadata has been changed and one showing metadata is not up to date. No matter what I do it is not showing in LR that it is saved. I spent 2 days with Seth Resnick trying to correct this and we re created my catalog. It was ok, until I imported new images and same problem. Now I have a new problem, when I bring image to PS it saves it but does not bring back to LR. Am I the only one out there who has this problem?

    See:
    How to use multiple iPods, iPads, or iPhones with one computer
    What is the best way to manage multiple...: Apple Support Communities

  • Cannot write exif and tiff metadata in image file

    Hi,
    I have a public XMP text file containing exif and tiff metadata: http://ns.adobe.com/exif/1.0/ and http://ns.adobe.com/tiff/1.0/.
    I want to write these XMP data in an image file and it doesn't work. I don't get any exceptions, just the metadata are missing in the image file.
    C#
    using (var xmpFiles = new XmpFiles())
          if (!xmpFiles.OpenFile("test.jpg", handler.FileFormat, OpenFlags.OpenForUpdate))
              xmpFiles.OpenFile("test.jpg", FileFormat.Unknown, OpenFlags.OpenUsePacketScanning | OpenFlags.OpenForUpdate);
         using (var xmpCore = new XmpCore())
              xmpCore.ParseFromBuffer(xmpPublic.ToString(), ParseFlags.None);
              if (xmpFiles.CanPutXmp(xmpCore))
                   xmpFiles.PutXmp(xmpCore);
         xmpFiles.CloseFile(CloseFlags.None);
    Public XMP:
    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description xmlns:_ns_2="http://ns.adobe.com/tiff/1.0/" rdf:about="">
        <_ns_2:ImageLength>4252</_ns_2:ImageLength>
      </rdf:Description>
      <rdf:Description xmlns:_ns_3="http://ns.adobe.com/exif/1.0/" rdf:about="">
        <_ns_3:ApertureValue>8/1</_ns_3:ApertureValue>
      </rdf:Description>
    </rdf:RDF>
    Result XMP in image file:
    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""/>
    </rdf:RDF>
    Does anyone can help with that problem?
    Thanks,
    Alexandra

    I found the answer by myself.
    According to the last guidelines from metadata working group, exif and tiff data should not be saved as XMP data in jpeg images anylonger because jpeg natively supports exif data.
    "The most recent (as of mid-2010) XMP specification describes the usage of Exif/TIFF properties within XMP itself. Both Exif ( http://ns.adobe.com/exif/1.0/) and TIFF ( http://ns.adobe.com/tiff/1.0/) namespaces have been defined so that corresponding Exif properties can be stored. This is particularly useful if Exif properties need to be stored but the file format does not support native Exif (e.g. PNG). [...]However, this document changes this earlier XMP guidance and recommends that Exif and Tiff device properties only be mapped into XMP in the case the file format does not support Exif natively."
    See http://www.metadataworkinggroup.org/specs

  • I cannot select radial filter points after I create them in Lightroom.  Anyone experience this issue before and what might be the solution?

    I cannot select radial filter points after I create them in Lightroom.  Anyone experience this issue before and what might be the solution?

    Press H to hide/show control points.

  • 4.2.1 Does Not Fix" Crash-on-screen saver" bug or metadata issues

    ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
    You have to set screen saver to "Never" to prevent crashing.
    No one checks these things?
    Message was edited by: Mike Kwiatkowski

    Mike Kwiatkowski wrote:
    ATV2 crashes as soon as it goes to screen saver. 4.2.1 does not fix this. WTC?
    Metadata issues still hosed.
    Not seen the screensaver issue.
    Personally I think this update was a patch to fix the DVI flickering issues that rendered the device unusable for many people - other annoyances can be fixed later but we better keep reminding them:
    http://www.apple.com/feedback/appletv.html

  • Is it true that Lightroom 4,4 has an issue importing RAW files from Nikon D610 ?

    Is it true that Lightroom 4,4 has an issue importing RAW files from Nikon D610 ?

    Hi Kenneth L,
    Please use the below link to convert your raw files to DNG files then you would be able to import the files in Lightroom 4.4
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.6 For Mac
    Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.6 For Windows
    Thanks

  • Metadata Issue iBooks

    We recently submitted an Algebra 1 iBook created with iBooks author.  Received the message that there was a metadata issue.  Was wondering if anyone knew:
    1. What is the metadata they are referring to
    2. How do you edit it
    3. Once fixed, do you have to completely resubmit and start over with the submission process, or can you edit what has already been submitted.
    Much thanks

    Meta data is the details you entered when you acted to submit your book using iTunes Producer.
    Check for red flags for that book in iTunes Producer....could be any number of things - we can't tell without more info
    Just edit the stuff for that book using iTP for whatever needs fixing and try again.

  • Metadata Issue?

    I submitted my book Friday morning. Checking yestderday, I see this.
    "Metadata Issue. There is an issue with the metadata. Contact us after you have verified and redelivered the metadata."
    Trouble is, I can't see anything wrong with the metadata. The blanks are all filled in. Has anyone else seen this? I did a search here and it seems to indicate that Apple won't be able to tell me what the problem is. Any hints or pointers would be greatly appreciated.

    It would be easy to verify for iTunes Producer whether the title in the metadata matches the title in the book. Sadly, it doesn't do that.
    "Metadata Issue. There is an issue with the metadata. Contact us after you have verified and redelivered the metadata."
    Singularly useful error message. The author gets to play the guessing game. Why not just say "The title in the metadata doesn't match the title of the book"?
    I have the same problem with many of my submitted ebooks.
    All I can suggest is to diligently go through each field of metadata, checking that it meets the requirements set up in the publisher guide and that the metadata is consistent with the book you submitted.
    Michi.

  • Lightroom removes the camera metadata on import.

    Lightroom removes the camera metadata on import. It started I think when I turned on the option for finding locations through GPS data. I have since turned it off but it still wipes camera data on import. Please help.

    So I don't know what happen but my photos were being put into an auto-upload folder when synced before I sorted them out. Occasionally I would start editing the photos here. At some point during that process Lightroom had asked me about auto looking up location data off the gps data. So now under metadata right where I found the camera, lens and all that information I was to find empty gps data listed. I tried removing and re adding that folder and resyncing the metadata but nothing worked. I turned off the gps setting which I thought was causing the problem but it didnt fix it. So I reloaded the photos onto my pc and put them in the proper folders and loaded them into lightroom that way. Bingo! Camera data! I dont know what really happened but I think when I changed that setting permanently caused a problem with my auto-upload folder. I will try again to load photos into Lightroom via the auto-upload folder and see if it is missing data. I will respond when I have tried that.  Thanks for all the responses.

  • EXIF: and TIFF: metadata is missing from XMP block in Lightroom 4

    I've recently purchased Lightroom 4 and on the whole I'm very happy with it, but I have run into a problem.  I have a few scripts which grab information from the XML-based XMP metadata block that's embedded in the DNG and JPG files that I use.  I've found that images processed with Lightroom 4 no longer export the exif: and tiff: data.
    To illustrate, a photo I exported with a previous version of Lightroom has the following data in the XMP block
       tiff:Make="Canon"
       tiff:Model="Canon EOS 40D"
       tiff:ImageWidth="850"
       tiff:ImageLength="567"
       tiff:XResolution="240/1"
       tiff:YResolution="240/1"
       tiff:ResolutionUnit="2"
       exif:ExifVersion="0221"
       exif:ExposureTime="1/800"
       exif:ShutterSpeedValue="9643856/1000000"
       exif:FNumber="71/10"
       exif:ApertureValue="5655638/1000000"
       exif:ExposureProgram="3"
       exif:DateTimeOriginal="2010-08-22T10:52:07.58+01:00"
       exif:DateTimeDigitized="2010-08-22T10:52:07.58+01:00"
       exif:ExposureBiasValue="0/1"
       exif:MaxApertureValue="4625/1000"
       exif:SubjectDistance="428/100"
       exif:MeteringMode="5"
       exif:FocalLength="80/1"
       exif:CustomRendered="0"
       exif:ExposureMode="0"
       exif:WhiteBalance="0"
       exif:SceneCaptureType="0"
       exif:FocalPlaneXResolution="3888000/876"
       exif:FocalPlaneYResolution="2592000/583"
       exif:FocalPlaneResolutionUnit="2"
       exif:PixelXDimension="850"
       exif:PixelYDimension="567"
    There is, of course, a lot more information in the XMP block, but in a file exported using Lightroom 4 there is nothing in the XMP block with the exif: or tiff: namespaces so none of this information is available to any script which queries the XMP metadata.  I'm pretty sure that the metadata is still there, embedded in the original EXIF data, as I can view it using the metadata panel in the Library module, but that's not accessible to my scripts as it's not in the XMP block.  I've made doubly sure that the metadata has been saved and also double-checked all my settings and even tried to export the files multiple times with every different setting that I can think of (even though my current settings worked fine in previous versions) but the files never get the exif: or tiff: data.
    I have called Adobe, but the best help they could give me so far was to post here and hope someone can help!

    I just compared two JPEGs exported with LR 3.6 and LR 4.1RC. The tags you mentioned are exported neither by 4.1 nor by 3.6. These tags are only present in the normal Exif metadata, but not in XMP. Which version of LR 3.x did you use before? Perhaps Adobe changed something already in the later versions of LR 3.x. If this is the case, you have to use a script or tool that is able to read the Exif metadata directly.
    In the XMP metadata in the file exported by LR 3.6, I see only crs (camera raw), aux (e.g. serial no.) and some other XMP namespaces, but no exif or tiff.
    P.S. I viewed the metadata of the exported files with exiftool. File format was JPEG (with "quality" setting, not with "limit file size", because apparently there are still some XMP differences between these two modes).

  • Migrated from Lightroom to Aperture: TIFF's in LAB mode don't work

    I migrated from Lightroom to Aperture and I noticed many TIFF's were black, or strangely colored (reddish, greenish). I couldn't figure it out, but I think I know what is the problem. I used to work in LAB-mode in Photoshop for quite some time, and I see that those files cause the problems.
    Not only can't I see the previews correctly, Ican't do anything with these files (not even open them in Photoshop). What can I do? Because these files are my portfolio (the material I sell, exhibit, etc.). They're extremely important for me. What can I do? I'm willing to convert them to RGB if necessary.

    There have been some issues with greenish previews lately. Browse this forum for threads with the tags "green" and "Previews". If that is the problem, then only your previews look strange and your original images might still be o.k.
    So I recommend to check if the images or only the previews are faulty.
    If you have a referenced Library reveal the masters in the Finder and look at the master with Preview or another Photo Browser.
    If your library is managed, you can reveal the masters inside your Aperture Library by opening the package (in Aperture 3.2.1), select the Library in the Finder and click "Show package contents". You will see folders "Masters" and "Previews". Compare the Masters and the Previews.
    If only the Previews are faulty, then select the the images in question in the Aperture Browser, ctrl-click them and select "Update Preview". If that does not help ...
    What can I do? Because these files are my portfolio (the material I sell, exhibit, etc.). They're extremely important for me. What can I do? I'm willing to convert them to RGB if necessary.
    I assume you have a backup or can access the originals you imported into Aperture.
    Convert a copy of one of pictures to TIFF in RGB mode and see if Aperture can handle that properly.
    If you are satisfied with the quality do that with all your important pictures.

  • Lightroom 5 Export TIFF tonal change, even without making changes in Photoshop

         Hi there,
    I seem to experience a mysterious issue when Lightroom creates an Edit Tiff for external editing. I have this issue only with one picture it seems. I tried to replicate it with another, but it doessn't happen.
    So here's what happens. I already had an Edit.tif of a DNG. Then I noticed I wanted to do some final retouching in Photoshop with the healing brush, but I also did some minor adjustments in Lightroom on the Edit.tiff, so I decided to create an Edit-Edit.tif.
    Then when I went back to Lightroom, I noticed the Edit-Edit.tif was all of a sudden lighter in the shadows than my Edit.tif.
    I tried some trial and error investigation myself, to replicate the issue. I couldn't replicate it with other pictures. But when I tried to do the same thing again, except this time no Photoshop editing to the Edit-Edit.tif (so Photoshop didn't ask me to save), same thing happened. So at least I found out it doesn't have anything to do with Photoshop.
    Anyone any idea what this could be? I would greatly appreciate any help! Thanks in advance!
    Kind regards,
    Dennis

    Problem is solved. It turns out, it probably has to do with the interpolation mechanism of Lightroom displaying dark area's with color noise a litte different.
    Thanks anyway for reading!

  • Metadata issues / problems...

    Using LR 4.1, on Windows 7 Professional...
    I am updating lots of photos and their metadata, all from within Lightroom.  Most every time, it tells me there was an error writing metadata and I have a majority of my photos with:
    - Metadata: Has been changed
    1.) Why is this happening?
    2.) Is there an easy way to force the write again (currently I have to select a few hundred at a time and hit "Save metadata to file".  But that's extremely memory intensive...
    Thanks,
    John

    Geoff,
    I see the same message... Not to hijack the thread but add to the discussion for kk -- I have been working to move my catalog and images to a new computer so had to Update Folder location to make it see the drive. (more on this below in case  it helps us figure out the permissions issue...) The badge with the exclamation point cascades through any folder I look at.
    As part of figuring out why I was having trouble seeing the drive and folder in LR4.1 I looked at the permissions for the drive and Lightroom folder specifically. This top-level folder, which holds pretty much all my images, was set for "Everybody" to read and write. The whole drive is set to "Share" in Win7 Pro 64-bit.
    Someone else brought up the idea that although the OS sees the drive, Lightroom might have a permission problem that keeps it from "seeing" or writing to the files. An ACL problem? I seemed to have made LR see the images but not connect the metadata consistently.
    I always held my 60,000 images on a HD assigned "E:" so as part of the move to the new machine I copied EVERYTHING (under the control of the OS) from the old "E:" to a new hard drive. I then disconnected the old "E:" HD; I started LR for the first time I made sure that this new HD was assigned "E:", although that was a re-assignment. That's why I as hunting the permissions.
    Forum user "Jasonized" brought up this Permissions issue  with reference to ACLs so perhaps I will post this issue there, too.
    Jonathan7007

Maybe you are looking for