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?

Similar Messages

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

  • 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

  • Issues with black psd files on black backgrounds when exported to PDF.

    Hello there,
    I'm having an issue since I upgraded to leopard and moved all my stuff from my old macbook pro (running OSX 10.4) to my new macbook pro (running OSX 10.5). CS3 didn't seem to have any problems before but now when I export an Indesign file with a black background containing a photoshop layered tif with a black background to pdf, the appears to be a big difference between the blacks - the Indesign file's black appears to be a mid grey.
    Any help would be appreciated!
    Here's how it all looks in InDesign: http://aycu14.webshots.com/image/48613/2005862333507831436_rs.jpg
    But this happens when exported and viewed in Acrobat (or preview etc.): http://aycu02.webshots.com/image/49801/2005871851784365159_rs.jpg

    In ID prefs go to Appearance of Blacks
    and set both instances to display Blacks Accurately.
    You will need to measure the rich black in the Tiff and make a rich black swatch in ID and use that for your book cover. now the blacks will match.

  • 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

  • Some missing and corrupt IPTC metadata on export

    As a Lightroom user I'm trying Aperture 3, I may be missing something or failing somewhere...
    I've imported some RAW files which already have IPTC metadata, captions, copyright, keywords etc. On export the copyright field has corrupted, the symbol © becomes ¬© and a few fields are missing. I don't have a date, rights usage and the image is marked as unknown copyright status.
    All of that data (except copyright status) appears in Aperture so I'd expect to see it in an exported JPEG. Everything appears as I expect when making a JPEG from Lightroom.
    Thanks for any comments or advice.
    DG

    Novak Yo wrote:
    As a matter of fact, it doesn't export costum filds at all.
    By definition, custom fields are non-standard, and therefore aren't included in the exported file as they won't mean anything to other software. This has been the case since Aperture 1.0 and has absolutely nothing to do with other metadata problems.
    Your website will likely be reading IPTC tags so if you want the information to be readable you'll have to find some appropriate IPTC tags to store the information in.
    Ian

  • File I/O error when exporting a report

    Post Author: Beth
    CA Forum: Exporting
    Hi,I have a program that runs as a scheduled task daily that runs four reports and exports them to rtf format.  This process has been running fine for a long time (several years).  However I've noticed now that I occasionally get an exception with the message "File I/O error", and the stacktrace doesn't give a much more useful information (see below): 5/4/2007 7:47:29 PM exception caught - Message:File I/O error.  5/4/2007 8:36:25 PM    at  . F(Int16   , Int32   )   at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)   at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export()   at CrystalDecisions.CrystalReports.Engine.ReportDocument.Export()   at EmailReport.Form1.ExportReport(TableLogOnInfo crTableLogOnInfo, String exportFilePath, String reportLocation)   at EmailReport.Form1.crystalReportViewer1_Load(Object sender, EventArgs e)As mentioned, this exception message and stack trace don't give me any information as to what the problem might be, and a search on the web hasn't yielded anything to help either.  Is there anyway to find more information as to the root cause of the exception?  Does anyone know what the File I/O Error means?As I said, this is not a new report, but something that has been in Production a long time.  My best guess is some upper limit on the report has been reached, and at this particular time the number of records being processed for this report is too big.  But I don't know how to prove this - the report was written by someone who has long left the company, so I don't know too much about the details of the report (as I don't know much about Crystal Reports to begin with).System Info:The machine exporting the report is a W2K machine.The executable was build using VS2003 with .NET 1.1 framework and CR8.5 and C#.The program itself contains a Form with a CrystalReportViewer object. Then creates a ReportDocument object, sets the appropriate parameters, then calls Export().Does anyone have any insight into what this exception means?Thanks,Beth  

    Chapter markers are not relevant to this. How long's the movie? What drive are you exporting to? How much space is on the drive? Did you render everything (Opt-R) before exporting? Did you mixdown the audio (Cmd-Opt-R) before exporting?

  • HELP! QT file deteriorates around halfway when exporting for web

    I have an iMovie project that I have regularly exported to DVDs or other quicktime files: only when I export "for the web" this file (a 1G file that gets compressed to about 18MB for the web) deteriorates, starts to blur as if losing sync with the codec. When I work in iMovie the file is perfect, when I tried to export it into one (or two) small .mov it deteriorates. I tried everything, including re-exporting to a new original and re-importing, splitting the file in shorter segments etc. At a specific point in the movie, it just falls apart.
    I was wondering if any of you had some suggestion.

    You could try duplicating the iMovie project, replacing the video clip which plays at the point that the movie deteriorates with -anything else- and then export again to see if the problem is related specifically to that one video clip.
    If not, then perhaps trying the export from another user account or on another computer would help determine if settings or software versions are an issue.
    If it is the one particular clip, try converting that clip to some other format prior to importing to iMovie and then exporting again ?

  • File size or resolution when exporting to PDF file.

    Post Author: Esio Nunes
    CA Forum: Deployment
    Hello,
    I'm using the following code to export my reports to PDF format, by an ASP.NET page:
    CType(crReportClientDoc, CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocument).PrintOutputController.Export(CrReportExportFormatEnum.crReportExportFormatPDF)
    But I need to produce files with sizes lower than now. Making some tests in Adobe, I note if I reduce the pdf resolution, the files became with a reduced size. Does anyone know if is it possible to configure the resolution when generating PDF files by Crystal? I looked to ExportEx method and PDFExportFormatOptionsClass, but I didn't find any about it.
    Thanks to all
    Ésio

    Post Author: Argan
    CA Forum: Deployment
    Nope. Crystal uses an old version of pdf (1.x I believe) for backward compatibility reasons.
    There is no way to reduce the size of the pdf that you export other than changing what is on the report itself.

  • Mp4 file does not play when exported to swf?

    I am putting together an interactive flash file that I have created in inDesign (CS4).
    I have had no problems creating and exporting links, buttons etc, but when it comes to embedding video I am experiencing trouble..I have a video which I have converted to mp4 H.264 format, and there appears to be no problems when uploading but when I export, the video does not play, and there is just a black box in its place with no controls. I have tried converting the file into various other formats, all with no luck. I hope you can tell me where the problem lies!
    Thank you

    Support for placed videos in exported SWF was introduced in InDesign CS5 so it does not suppose to work with CS4...

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

  • Video and Audio Files are different lengths when exporting

    I'm just trying to get comforatable with a much faster Windows workstation on PPro and AE.
    I just exported my first project from PPro to burn to Blu-ray like I've done dozens of times on our older Mac Pro w/o problems.
    My Ppro file is 7:04:18 in length.  I export the video as an mp2 Blu-ray video and import it into Encore and it shows up at that same length.
    I export the audio as an aif and import it into Encore and it shows up as 7:06:19 in length--2 seconds and 1 frame longer.
    Everything is CS6.  File is 1920 x 1080, sq pixels, 29.97.
    Any suggestions as to why this is happening?

    Thanks for the feedback.  I exported to aif as I was going to burn the Blu-ray on our Mac Pro in Encore, since we don't yet have a Blu-ray burner installed in our new Windows workstation. 
    Upon seeing your note, I re-exported the project as you described and placed the wav and mp2 in Windows Encore and they are both the same time length.
    It seems the aif should be the same too... but I assume wav is likely the preferred format on Windows so will be using that as the new workflow.
    Thanks for your help!

  • Crystal Reports 2008 Missing Page Headers and Footers when Exporting Excel

    After upgrading from Crystal Reports 9 to Crystal Reports 2008 we have noticed that when we export to Excel the document no longer retains the page headers and footers.  After doing some reading I see that there is a property called ExportPageHeadersAndFooters that we can tap into.  However, I am unable to get this to work for me.  Below is my code, do you have any suggestions?
                    ReportDocument rdReport =  new ReportDocument();
                    rdReport.Load(sReportFilePath);
                    ExportFormatType exType = ExportFormatType.Excel;
                    // create an instance of excel formatting options
                    ExcelFormatOptions foFormat = new ExcelFormatOptions();
                    foFormat.UsePageRange = false;
                    foFormat.ExcelUseConstantColumnWidth = true;
                    foFormat.ExcelTabHasColumnHeadings = true;
                    foFormat.ExportPageBreaksForEachPage = true;
                    foFormat.ExportPageHeadersAndFooters = ExportPageAreaKind.OnEachPage;
                    // set up more exporting options
                    rdReport.ExportOptions.ExportFormatType = ExportFormatType.Excel;
                    rdReport.ExportOptions.ExportDestinationType = ExportDestinationType.DiskFile;
                    rdReport.ExportOptions.FormatOptions = foFormat;
                    rdReport.ExportToStream(exType);

    I was able to get it to work but I had to do this.
    ExportRequestContext expReqCntxt = new ExportRequestContext();
    expReqCntxt.ExportInfo = rdReport.ExportOptions;
    sExported = ((CrystalDecisions.CrystalReports.Engine.ReportDocument)rdReport).FormatEngine.ExportToStream(expReqCntxt);

  • No file-type extensions appear when exporting files to a different format

    Hello.
    I have been having this issue for a while on both Pages and Numbers.
    Whenever I export a file to another format (e.g., pdf, txt, doc, or xls) the file appears WITHOUT any extension at all. I have to go to the file, click on the file name and type in the proper extension at the end of the filename.
    Frankly, I'm tired of doing this.
    Does anyone know of some way to fix this?
    Thanks for your help.

    Try to run Pages from an other user account.
    If it behaves flawlessly, we will know that the culprit is in your original user account.
    In such case, most of the time, the wrongdoer is the preferences file :
    <startupVolume>:Users:<yourAccount>:Library:Preferences:com.apple.iWork.Pages.pl ist
    Quit Pages,
    move the file on the Desktop
    restart Pages.
    If it behaves well, you will know the culprit. Move it to the trash and work … until the next corruption.
    Yvan KOENIG (VALLAURIS, France) mercredi 17 novembre 2010 16:47:56

  • File sizes increase steadily when exporting to Quicktime movies

    I have a series of short (90 seconds or so) little segments in a sequence that are very similar to each other that I've just created one after another in the timeline. There are about 50 of these. They are each made up of still frames (a .PSD Photoshop graphic), overlayed text (Premiere text) and audio - no video. As I create each little segment, I'm exporting them to a Quicktime movie (H.264, 50% compression) and the Range set to Work Area Bar to control what gets exported. Although the resulting Quicktime movies play just fine, the problem is that as I get further and further down the timeline creating these movies the resulting Quicktime movie files get larger and larger. The first movie is around 12MB, the second around 16MB, the third around 21MB, and so on until the 50th one is over 400MB. Again, the movies play just fine, but there's no reason I can see that the 50th one is so gigantic (over 400MB in size) compared to the first one (at around 12MB).
    This is a Windows XP Pro machine with 4GB RAM using Premiere Pro CS3 3.2.0.

    Silly question:
    Are you sliding the Work Area Bar down the timeline to cover the new segments, or are you just extending it?

Maybe you are looking for