File number is changed on export from lightroom

using lightroom 4.3...  when I edit a group of photos in lightroom, most of the files will only be edited in lightroom but a few will also be opend into PS6 (by right clicking > edit in>...) Once the PS edits are complete the image is saved & I return to Lightroom.  When I export the entire group of images - I set the file name to 'custom name - original file number'.  The images I edited in lightroom only - all are renamed as expected (ie wedding photo-1234, wedding photo-1235...).  The images I edited in both lightroom & photoshop receive the custom name but lose their file name (ie wedding photo-, wedding photo-1, wedding photo-2, etc.)  When viewing these PS edited images in lightroom - they do show the file #, it is only after export that the file # is lost..
Previous versions of lightroom / PS did not have this problem for me.
I wish to maintain the file names for all of the images, help?!?

Thanks Brett, yes - when I open the photo in PS, the file name has changed from i.e. _MG_5720.CR2 to _MG_5720-2. I save the image & go back to lightroom, the image is now called _MG_5720-edit.tiff.  When I export, (and in the export settings I rename to custom name - file name) the file now becomes wedding photo--.  In previous versions of the software - the file name would have exported as wedding photo-5720-edit.
Can you please explain how I can   check how the file names are being changed and see if I can make it so any changes to the name occur before numbers.
Many thanks, Anne

Similar Messages

  • Color change on exporting from lightroom and saving in Photoshop CS5

    I have been having issues with my pictures with color management.    I have Lightroom 4 and Photoshop CS5.  I thought over the last 2 years that it was just me.   I have bought a Eizo monitor with a hood, calibrate with a i1display pro, painted my walls gray, updated my strobes from alien bees to elinchrome bxri's.   Updated my sekonic meter to a L 758.   Have done custom white balance with gray card, expodisc, xrite kits.   The problem has been over the years when I work on a picture in lightroom and export it as jpeg or adobe rgb it gets saved to my external hardrive and the colors are really bad !!   You can go back and compare the picture in lightroom to the picture on my iomega external drive and there is a significant difference.   I do some animal photography and I had a dog that had brown fur and when I export it out of lightroom the dogs fur is actually a bright very orange color.  Same thing happens with skin tones.     When I import the photos into lightroom the pictures look ok.       The same thing is happening when I go from lightroom to photoshop the picture color looks good but when I go to File-save as - tiff or jpeg the colors are changing.   It does not matter what color space I am in I have tried them all it is still happening.    If anyone has any insight that would be great.  
    Teresa

             Thanks everyone for the help.   I have only been doing photography for about 2 years and the color managment part has been my hardest thing to get right.   My monitor ColorEdge CG243W LCD.   Wide color gamut of 98%.  Has a sensor on front of monitor that detects ambient brightness but this will only work if you are in a custom color mode.  Modes are: custom,  sRGB,DCI,EBU, Cal1.   I use the Cal 1 to be able to use the Colornavigator software that came with the monitor.  You also have to be in custom color mode to be able to manually adjust brightness, contrast, temperature on the monitr itself which I do not use because I use the Cal 1 mode.   I was not sure about the digital input signals.   I am on the DVI-I in which this allows digital signal input and analog signal input.    There is a DVI-D mode that allows only digital input only.    Also did not know if I needed to be concerned about setting the frequency that corresponds to the grahic board in the monitor ?    My bandwith was set to normal and now is on wide.   My digital input is for 1920x1200 resolution.   Appicable signal is Vesa CVT RB.  Frequency is 60 Hz.   Yes I did call Eizo twice last year when I got my monitor and did not get very far.     I have also called and spoke to a color specialist at my lab and told him the problems I have been having and he just told me to leave everything in sRGB.   Well I would like to get the most from my monitor's color gamut and when working on my pictures so that is why I am still determined to get this figured out.  
    I use the i1 Dislpay Pro hardware to calibrate with and the ColorNavigator software.     When calibrating.   I go to create a new target---select enter manually--Gamut ( monitor native--states recommended)--Brightness 100cd---White point (6500k)--set black level (recommemded states mininum 0.2)---gamma 2.20---priority (set automatically to standard, this adjusts gray balance while maintaining the contrast)---then I hit calibrate and it goes through the process.   The results I get are:                                            Target                                               Result
                          Brightness                                        100cd                                              99.9cd
                           Black Level                                    minimum                                       0.15cd
                          contrast ratio                                                                                            647:1
                          White Point                                    6500k                                              6501k
                           Gamma                                           2.20                                             R   0.6774,0.3136
                                                                                                                                            G   0.2031,0.6992
                                                                                                                                            B    0.1498,0.0499
    Thanks again for your help I know this is alot of information but I thought it might help ?
    Teresa

  • Color change after exporting from Lightroom

    I noticed a drastic color change after exporting a file from Lightroom to a JPEG file today. I have been using Lightroom for a while, and it never happened before. I am assuming that I changed the setting somehow and I cannot find how to fix it.
    Here is the original.
    After exporting to a JPEG. The color is so drastically different. I tried both sRGB and AdobeRGB and they turn out to have the same problem.
    It is not as clear as JPEG files, but edited files with Photoshop CS5 also looks slightly different viewed on Lightroom.
    I would appreciate it if anyone could help me.  Thank you so much for your help!

    Thanks everyone for looking into my problem!
    >Can you upload a sample of each
    >* Raw File
    >* XMP Sidecar
    >* Exported JPEG
    I somehow can't find XMP sidecar files in my folders.... So instead, I exported the JPEG file to the 2nd JPEG file, hoping you can compare those two JPEG files.
    The colors get lighter and lighter every time I export the files. I uploaded those files (RAW, 1st JPEG, 2nd JPEG) on line. I also changed the file samples from the original post because I can't add watermarks.
    I checked my flles, but there is no preset applied to the JPEGs.
    I am thinking of unistallng Lightroom and reinstalling it and see what happens.
    Thanks!
    1. The data of the RAW file: http://yuko-hirao-photo.hechtmail.com/others/DSC00530.ARW
    2. Data of the GPEG exported from the RAW: http://yuko-hirao-photo.hechtmail.com/others/DSC00530test_upload_01.jpg
    3. Data of the JPEG exported from above JPEG: http://yuko-hirao-photo.hechtmail.com/others/DSC00530test_upload_01test_upload_01.jpg

  • Saving PSD files after exporting from Lightroom saves incorrectly

    I've only recently moved to Lightroom from using Photoshop/Bridge together, so I'm not 100% sure how saving files exported from Lightroom should go. But here's what I experience:
    Base edit of file within Lightroom
    In library view, right click on image -> Edit in -> Open as Smart Object in Photoshop
    Perform all my necessary edits and such
    File -> Save As, and save it to another location as a PSD file (totally different HDD)
    Perform more edits....
    Shortcut CTRL+S to save, and it saves it as the TIFF file under the location it was originally in within Lightroom
    Eh...? Am I missing something. It should just save as the original PSD I created when I went "Save As". I have seen on a few occasions, immediately after "Save As", the file name resorts back to TIFF and not as PSD.
    My settings for External Editing in Lightroom are as follows:
    File Format: TIFF
    Color Space: ProPhoto RGB
    Bit Depth: 16 bits/component
    Resolution: 300
    Compression: None
    Does anyone have any ideas what I'm doing wrong? Also, to note, that sometimes I double click on the Smart Object within Photoshop to load Camera Raw and perform some edits, but not often.

    Modesto Vega wrote:
    Replying to your last 3 posts.
    Re Camera Raw being used to pass an image to Photoshop
    a) I am assuming this is independent of the Compatibility level in Preferences\File Handling DNG creation.
    b) Does the same apply to other photo editing software made by Adobe like Elements?.
    Reply: Yes, the principle is the same. Photoshop Elements cannot read raw data either. That's why it has to be converted before it's opened.
    c) Assume that I have LR 5.7.1 and CS5. Is Camera Raw is still used to pass an image to Photoshop? If so, why is there a need to get LR to behave differently?
    Reply: Camera Raw is used IF you choose the option to open anyway. Then Camera Raw will be used to convert the image that's opened in Photoshop. But since it is older than Lightroom some of the new adjustments might not be transferred to Photoshop. That's why there is a need to let the user make the choice.
    d) Sometimes it does seem as if Adobe might be using Camera Raw updates and process version updates to get consumers to change their habits, this includes having to buy subscriptions or having to change workflow to some ideal that somebody at Adobe or working with Adobe might have in mind.
    Reply: The fact is that in the past, when a new version of Photoshop is released then all support and updates cease for the previous version. Since the introduction of the creative cloud, at least users of Photoshop CS6  get support for new cameras. They just don't get the new features. Yes, there's motivation to upgrade. Adobe is a business. What do you really expect?
    Re stacks
    I find impossible to see collapsed stacks on the film strip. Stacks are only visible on the Library module and using a grid view; I don't say clearly visible because they are only recognisable by the label at the top left corner with the image count; I don't even think it is possible to change the colour of that label or the grey colour surrounding an image. Also I cannot name stacks. If I could name stacks, see them as virtual folders underneath a library folder and make them glaringly visible I would use them extensively.
    Reply: The only reason I can think of that you are unable to see collapsed stacks on the filmstrip is if you have the filmstrip reduced in size to the point that Lightroom can't display all the icons. I'm able to see the collapsed stacks in the library grid view and on my filmstrip
    Re storing your Raw files and processed files in separate locations
    Assuming Raw files are negatives and Photoshop files are transparencies or prints, would you want negatives being handled/read on a regular basis? If anything happens to your negatives, you would never be able to produce another print or another transparency again.
    Reply: The raw files or the negatives, as you put it, are never modified by Lightroom. They always remain in their pristine state they were in when they were imported. If I have a backup of that raw file then I can do whatever I want to the one in my working folder. Resetting that raw file so that it looks unaltered is just a click away.
    I have worked extensively with databases and database systems, it is a standard feature of database systems to be able to choose where to store different database objects. I don't see why LR cannot do the same, it is a database after all. I do agree with both the OP and photo.
    Reply: Well, I won't argue that point. If that's what you really want than lobby for it. It just won't get my vote because I don't see any real advantage.
    If you read back through this quoted message you'll find that my replies are included. I don't know how to separate them out so they are highlighted properly. Read through it and think about it. But personally, I don't want to waste anymore time on this discussion because it isn't accomplishing anything in my opinion.

  • Why won't .MOV files export from Lightroom?

    Why won't .MOV files export from Lightroom?

    The will.
    Or at least they can, and do, sometimes, if you have good MOV karma..
    Why not supply a little more info, like:
    * Which OS
    * Which version of Lightroom
    * History of MOV files.
    * Export format.
    * Do other video types export OK
    * How many different MOV files have you tried - all with the same history?
    and of course:
    * What, exactly, happens, when you try?
    Rob.

  • JPGs exported from Lightroom 5.6 will not open in other applications

    Recently I have noticed that jpgs exported from Lightroom 5.6 can not be opened in Canon DPP 3.14 and can not be resized using Image Resizer plugin. Both of these I use frequently.
    I have seen mention of this issue re other applications also. Does anyone know if there is a solution?
    I am using Windows 8.1 64bit. 5D Mark ii

    This was an issue with 5.5 (the placement of some of the internal headers of the jpgs was changed and some other applications, including DPP, could not open them), but was corrected in 5.6. I just checked on it by exporting a jpg and opening it with no problem in DPP 3.14.15, Windows 7 x64. Are your jpgs old ones from LR 5.5?

  • Exporting from Lightroom to Photoshop.

    I have set the necessary preferences so as to export from Lightroom to PS CC. However when i try to export a file then PS CC fails to open. However PSE 11 opens but with no file! Any help would be appreciated. thanks GM

    Ask in the LR/ PS forums and provide details about your system, your files, your develop settings, other stuff. You need to be much more specific.
    Mylenium

  • Saturation Loss When Exporting from Lightroom.

    This happens to me when exporting from Lightroom 2 or 3. It happens regardless of the color profile, file format, bit depth, image size, compression, or the method of export. I regularly profile my one-year-old iMac monitor with an Eye One Display 2. My working color space for Photoshop CS4 is ProPhoto. After exporting, I am viewing the images in Photoshop, Safari, Firefox and Apple Preview, with the same result. I have used pretty much all the available export methods in Lightroom, including exporting with Lighroom ad-ons such as SlideshowPro. And, conversely, if I edit an image to my liking ourside of Lightroom, there is a saturation increase when I import it into Lightroom.  The effect tends to be most obvious and bothersome with shots taken outside on sunny days, with lots of blues and greens.  I am shooting raw files with a Canon 5d II and I use the Adobe Standard profile in Lightroom.
    There is a section at the back of Martin Evening's Lightroom book where he talks about the Lightroom color space and Lightroom versus Photoshop curves, which seems to relate to what I am seeing, but I have the feeling that what I seeing is more pronounced than what he is talking about there.  It is a real dullng of the look, not merely a slight difference in how the colors are rendered.

    Looks like Lightroom doesn't like your display profile.
    Try removing the profile (don't know how to do it on a Mac) to leave your display uncalibrated. Are the colors still different in Lightroom and Photoshop?

  • Prints exported from Lightroom consistantly 1 stop dark!

    I calibrate my monitors regularly and currently have my two monitors set to the absolute lowest brightness point they'll go.
    Everything's calibrated and my histograms look good yet, every time I try to send something out for printing, it comes out at least a full stop dark.
    Conversely, if I print on my own Canon Pixma printer and allow the "printer to manage colors" - things are spot on.
    I don't want to always have to print every little thing at home.  I'd like to send things out sometimes. 
    I do not have this problem with files exported from Photoshop.  Only files exported from Lightroom.   Yes, I know I can fool around with making a brightness preset but why do I have too??  What is going wrong here?
    This is making me crazy.  Help Please!

    IF you're working with an outside lab that doesn't supply an ICC profile for soft proofing, you can pretty much forget about getting a match. Further, the lab has to be using that profile (or let you use it) or again, you're dealing with a lab that has a half baked color management workflow. No wonder you are having good luck printing yourself, you're probably doing everything correctly.
    That's absolutely right. The only consumer oriented big box local lab I have found that does this correctly is costcos and then I understand you need one where the operators have a clue and not every location is good and keeps their machines consistent. The other labs I mentioned all do a great job color managing and I have never had "too dark" prints. The fact that your own printer works fine makes me think that this is indeed very likely a lab problem (not at all uncommon). I would recommend that you print to your own printer while having Lightroom color manage as you should get better quality in subtle color gradients but only do this if you understand the weird codes Canon uses for their profiles and you understand how to turn off color management in the driver.
    That said, you can do a quick sanity check of your calibration by using a printer test file. Andrew has one on his site here that will work fine: http://www.digitaldog.net/tips/  and a nice one from inkjetart can be found here: http://www.kenleegallery.com/images/tech/4800test.jpg
    Load these into Lightroom. Do not touch any develop settings and see if the images make sense on screen. Skin color should look great (not too bright), you should see nice saturated colors and no plugged up shadows. Export these files to sRGB jpegs (they are in a different color space as downloaded so you need to convert for most labs) from Lightroom and send those to your lab. If your prints from these testfiles come back dark, stop using them as they don't calibrate their machines correctly. Well-calibrated machines should give very good prints with tone and color very close to what you see in Lightroom. You can get somewhat better results if the lab provides icc profiles but in my experience, if the machines are tuned correctly you will have a hard time distinguishing profiled images from sRGB images if you don't use a good viewing station.

  • Corrupted EXIF data in photos exported from Lightroom CC

    After upgrading to Lightroom CC EXIF can't be read by some apps. "Re-saving" a file in Photoshop fixes the problem. I'm using Mac OSX 10.9.5. Are there any plans to update and fix the EXIF data generated when exported from Lightroom CC?
    Also, this command fixes the issue with Create Date part of EXIF.
    #!/bin/sh
    exiftool -AllDates="$(exiftool ${1} | grep 'Create Date' | awk '{print $(NF-1), $NF }')" -overwrite_original ${1}
    The reason I'm asking is because we run a site where "Create Date" read from JPG's EXIF is crucial and it's a matter of letting users upload the pic or deny uploading.
    So again, any plans on the fix?
    Regards,
    Pawel Kadysz

    I confirmed that the Exiftool command line:
    exiftool -m -all= -tagsfromfile @ -all:all -unsafe file.jpg
    removes the ICC Profile, which could account for significant color differences, considering that the profile is Adobe RGB.  I think this may be a bug in Exiftool, so I filed a bug report.  (But it might be that Exiftool just can't handle the non-standard layout of LR's JPEGs.)  The author is typically very responsive.
    I tried some alternate Exiftool command lines that touch as little metadata as possible, and this one seems to address both of LR 6's JPEG problems:
    exiftool -m '-exif:datetimeoriginal<exif:datetimeoriginal' -xmp-crs:all= file.jpg
    The -m option ignores minor errors and issues, in particular, when there are more than 1000 entries in the XMP metadata.
    The '-exif:datetimeoriginal<exif:datetimeoriginal'  option sets the EXIF Date Time Original Field with its current value; this tricks Exiftool into rewriting just the EXIF metadata without touching the other metadata segments (e.g. the ICC profile), addressing the first JPEG problem.   (You could use any EXIF field that's present -- I picked DateTimeOriginal since every camera adds that.)
    The -xmp-crs:all= option option deletes all of LR's develop settings from the XMP metadata, addressing the second JPEG problem.That metadata is not ready by any programs other than LR, as far as I know. 
    I've tested this new command line on a couple of pics, including the example you provided above, and it appears to work correctly.  But given that we're dealing with buggy output from LR that doesn't conform to the de facto and de jure standards, it's hard to have high confidence without testing on dozens if not hundreds of pics.

  • Exporting from Lightroom 1.3: Different sort order than defined in Grid view

    Just did an export from Lightroom 1.3 and ended up with a the wrong export order.
    Here is what I did.
    1. Create a collection
    2. Drag the pictures I want to export into that collection
    3. Select: Sort: Import order (In lightroom grid view - the sort order was correct)
    4. Export from Lightroom with "Userdefined name - sequence"
    The result is a total different sort order than I can see in the Lightroom Grid view.
    Very annoying.
    Any ideas?
    Also - in the new export dialog there seems to be no option anymore to CHANGE a user-defined export like in the previous version. What do you do if you want to change something?
    Overwrite with the same name?
    Remove old export and add the new one changed?
    greetings
    gfisch

    Are you seeing this only in Lightroom? They are not 'still in the parent, Germany folder.' only visible their if you have 'Include Photos from Subitems' checked in the Menu/Library of Library.
    Uncheck that you you will only see them in their correct folders.
    Don
    Don Ricklin, MacBook 2Ghz Duo 2 Core running 10.5.1 & Win XP, Pentax *ist D
    See LR Links list at my
    Blog for related sites.

  • Export from Lightroom: folder not found.

    New Problem with export from Lightroom. I always have to select the folder where to save to, even if it was selected before. This means I have to click on an already activated folder at every export.  Why? This problem wasn't there before.
    I always use the option "choose folder later on" at the export dialog box.
    Error message: "Es wurde kein Zielordner für diesen Vorgang angegeben."
    Thanks for help folks!
    Best
    Bernd

    Normally when Lightroom says "not enough memory", that's exactly what the problem is, you don't have enough memory.
    A partial solution would be to make sure no other applications are running when you do this export.
    The real solution is to make sure your computer has both 8GB RAM (or more) and a 64 bit operating system. One of these by itself without the other will not improve the situation.

  • As with others I can't export from Lightroom 4 to Elements 10 or any of the Nik products except HDR

    As with others I can't export from Lightroom 4 to Elements 10 or any of the Nik products except HDR Efex pro. Surely this has been fixed? If not it is appalling. It has been going on for too long in a program that has supposed to have some integrity

    I am able edit pictures in PSE (Photoshop elements) 10 BUT i am unable to edit videos in PRE (premiere elements) 10. I will uninstall LR 4.1 RC1 and then install RC2 and use a backup of the catalog. Lets see if that works.

  • Trouble exporting from Lightroom 4

    While trying to export from Lightroom 4, I was getting the error message "An internal error has occurred:WIN32 API error 2, etc.   Others have asked about this and the solution offered was to check "Do Nothing" in the post processing box, which I have done.  Now I can export, but the image is severely downsized from being a full sized jpeg.  How do I get it to export at full size?   All was working fine with exporting until today

    Thanks...the quality slider was at 60 - moved to 100 and it solved the problem.  Simple - Thank you for suggesting - I was getting a headache trying to solve my issues today!

  • Why do my pictures become blurry after exporting from lightroom 5?

    My pictures become somewhat blurry or not as sharp after I export them from lightroom 5. PLEASE HELP!!!

    If you are looking at your exported pictures in preview.app than that is the culprit. It uses an extremely poor downscaling algorithm for displaying large images and will make every large image, no matter how sharp originally, display blurry. In preview you can hit command-0 (that's a zero) to make the image display 1:1 to see the actual detail. Make sure you have it's preferences in the images panel set to "Define 100% scale as 1 image pixel equals 1 screen pixel". I think in older Mac OS X versions, it was called something like ignore image dpi for display or so but I don't remember. You can also make sure to downscale (with correct output sharpening in the export panel) upon export from Lightroom. If the exported image is smaller than the display, Preview should display 1:1 by default upon opening.

Maybe you are looking for

  • I have itunes 10.5.2  Can I download and update directly to the latest version of itunes without any issues?

    I have itunes 10.5.2   Can i download and update directly to the latest version of itunes without any issues?

  • Restrict some document numbers in f-44 tcode

    Hello Experts, My client requirement is to restrict some document numbers when we run f-44 , here I am entering account and company code as input and after pressing enter here it displays some records. here among the list of displayed records, I want

  • War an ear deployment problem

    hi, I got a war and ear that share common classes. I would like to deploy both of them on the same application server. I started with weblogic and it worked fine. Now I am running it on Websphere - the problem is the ear application failed to start -

  • Event Handling when EditText has been filled

    I'd like to call some code after an EditText has been filled.  But I'm having a little trouble figuring out which events I need to watch. The tricky part (it seems) is that I need to catch the event any time data is added to or changed in the EditTex

  • Central Numbering

    Hi all We have CMDM scenario with central harmonised numbering where this number must be distributed to multiple downstream instances of ECC and BW in out landscape We can achieve central numbering by configuration Key Generation on a single remote s