Keywords missing in LR2.3 jpg exports.

My jpg exports do not contain the keywords and captions that I entered in LR2.3. What am I doing wrong?

DKramer24 wrote:
I'm checking by clicking on the exported/created jpg's properties in WinXP. Minimize metadata is unchecked. I've tried the exports with and without that box checked, same with Write keywords as Lightroom heierarchy.. no keywords or captions.
Personally, I don't trust Win Explorer to always list the metadata correctly. I always check with ExiftoolGUI. It will list all the metadata.

Similar Messages

Extremely large jpg exported files - help!

I was previously loving LR3 - used the trial for a month, decided to buy it - had really no problems. The big issue for me is now the jpg export file sizes that are being created. I run all my photos through the develop module to adjust the basics as well as draw in masks, and previously I had no trouble exporting the files as jpg, with the limit of size at 600kb and resized to 960x640 (original photos from 5Dmk2 RAW).
Then I bought the license. From then on it seems that now whenever I do the same exact export it doesn't work! I also used to use the output quality slider and set that at 100% and would get around the same file sizes, but now I'm getting files 2-3x the size of the previous exports. All of the photos have minimal metadata (10 keywords or so, that's it) and the same metadata was present in the exports in the trial version.
Playing around with more export parameters and reading around on this forum led me to try and minimize exif data - this didn't even work - files could not meet the requirements or they still ended up 2-3x the size they used to be.
The interesting part is that when I would delete all development history and set the file back to the original pre-edited RAW and export there would be no problems!
Could it be possible that LR is adding the development data into the metadata that it is attaching to the photo??
This has completely shut down my photo workflow and really is making me regret buying this otherwise wonderful tool.

What I can see in the image is that it contains about (uncompressed) 750KB of XMP data, the major part of it relating to some "PaintCorrection" as follows:
PaintCorrectionWhat             : Correction
PaintCorrectionAmount           : 1.000000
PaintCorrectionActive           : true
PaintCorrectionExposure         : 0.439246
PaintCorrectionSaturation       : 0.000000
PaintCorrectionContrast         : 0.000000
PaintCorrectionClarity          : 0.457077
PaintCorrectionSharpness        : 0.000000
PaintCorrectionBrightness       : 0.361949
PaintCorrectionHue              : 240.000000
PaintCorrectionSaturation       : 0.000000
PaintCorrectionMaskWhat         : Mask/Paint
PaintCorrectionMaskValue        : 0.689655
PaintCorrectionMaskRadius       : 0.005442
PaintCorrectionMaskFlow         : 0.000000
PaintCorrectionMaskCenterWeight : 0.843964
PaintCorrectionMaskDabs         : d 0.689505 0.619480
PaintCorrectionMaskWhat         : Mask/Paint
PaintCorrectionMaskValue        : 0.689655
PaintCorrectionMaskRadius       : 0.005444
PaintCorrectionMaskFlow         : 0.000000
PaintCorrectionMaskCenterWeight : 0.843964
PaintCorrectionMaskDabs         : d 0.689871 0.605390
PaintCorrectionMaskDabs         : r 0.005443
PaintCorrectionMaskDabs         : f 0.0813
PaintCorrectionMaskDabs         : d 0.689749 0.607832
PaintCorrectionMaskDabs         : f 0.1519
PaintCorrectionMaskDabs         : d 0.689626 0.610275
PaintCorrectionMaskDabs         : f 0.1700
PaintCorrectionMaskDabs         : d 0.689590 0.612722
PaintCorrectionMaskDabs         : r 0.005442
PaintCorrectionMaskDabs         : f 0.1759
PaintCorrectionMaskDabs         : d 0.689635 0.615026
PaintCorrectionMaskDabs         : r 0.005443
PaintCorrectionMaskDabs         : f 0.1742
PaintCorrectionMaskDabs         : d 0.689530 0.612581
PaintCorrectionMaskDabs         : f 0.1726
PaintCorrectionMaskDabs         : d 0.689425 0.610137
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1709
PaintCorrectionMaskDabs         : d 0.689320 0.607692
PaintCorrectionMaskDabs         : f 0.1692
PaintCorrectionMaskDabs         : d 0.689214 0.605248
PaintCorrectionMaskDabs         : r 0.005445
PaintCorrectionMaskDabs         : f 0.1678
PaintCorrectionMaskDabs         : d 0.689104 0.602803
PaintCorrectionMaskDabs         : f 0.1460
PaintCorrectionMaskDabs         : d 0.688982 0.602615
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1525
PaintCorrectionMaskDabs         : d 0.689069 0.605061
PaintCorrectionMaskDabs         : f 0.1569
PaintCorrectionMaskDabs         : d 0.689090 0.607511
PaintCorrectionMaskDabs         : r 0.005443
PaintCorrectionMaskDabs         : f 0.1625
PaintCorrectionMaskDabs         : d 0.689100 0.609960
PaintCorrectionMaskDabs         : f 0.1652
PaintCorrectionMaskDabs         : d 0.689195 0.612399
PaintCorrectionMaskDabs         : f 0.1863
PaintCorrectionMaskDabs         : d 0.689113 0.610052
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1845
PaintCorrectionMaskDabs         : d 0.688940 0.607617
PaintCorrectionMaskDabs         : f 0.1839
PaintCorrectionMaskDabs         : d 0.688743 0.605185
PaintCorrectionMaskDabs         : r 0.005445
PaintCorrectionMaskDabs         : f 0.1916
PaintCorrectionMaskDabs         : d 0.688549 0.602753
PaintCorrectionMaskDabs         : f 0.1748
PaintCorrectionMaskDabs         : d 0.688555 0.604775
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1839
PaintCorrectionMaskDabs         : d 0.688622 0.607222
PaintCorrectionMaskDabs         : f 0.2225
This data results from heavy use of the local adjustment brush. Choosing "Minimize Embedded Metadata" upon export really should solve this problem for you. Please try again specifying this option.
But then, by doing so, you lose any other metadata (keywords etc.) also. To have complete control on what metadata gets written into the JPEG upon export, you could use Jeffrey’s “Metadata Wrangler” Lightroom Plugin.
I noticed one strange thing within the XMP data in your JPEG:
The data seems to be formatted differently than what I see with JPEGs I export ("HasExtendedXMP"), which I don't know where it comes from.
For further investigation, would it be possible for you to upload the Raw file and the XMP file belonging to it to somewhere (e.g. www.yousendit.com) and post a link to it here?
Beat Gossweiler
Switzerland

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?

JPG export preset in InDesign?

Hi all,
Is there a way to save my JPG export selections as a preset? I have to export JPGs of the same document for two different purposes and they have different export requirements. Is there a way to save my selections as a preset the same way I can save my PDF export selections as presets?
InDesign 7.0.4
Mac 10.6.8
Cheers,
Trish

I'm pretty sure it won't be your fault, but I don't seem to be able to fix it. Try this one but it exports the number of pages squared! For example a 4 page document gives you 16 jpegs, 5 = 25 and so on.
What am I doing wrong John? I added in this line: app.jpegExportPreferences.jpegExportRange = ExportRangeOrAllPages.EXPORT_ALL;
//Display a "choose folder" dialog box.
if(app.documents.length != 0){
var myFolder = Folder.selectDialog ("Choose a Folder");
if(myFolder != null){
myExportPages(myFolder);
else{
alert("Please open a document and try again.");
function myExportPages(myFolder){
var myFilePath, myPageName, myFile;
var myDocument = app.activeDocument;
var myDocumentName = myDocument.name;
var myDialog = app.dialogs.add({name:"ExportPages"});
with(myDialog.dialogColumns.add().dialogRows.add()){
staticTexts.add({staticLabel:"Base name:"});
var myBaseNameField = textEditboxes.add({editContents:myDocumentName,
minWidth:160});
var myResult = myDialog.show();
if(myResult == true){
//The name of the exported files will be the base name +
//the page name + ".jpeg".
var myBaseName = myBaseNameField.editContents;
//Remove the dialog box from memory.
myDialog.destroy();
//Generate a file path from the folder name, the base document name,
//page name.
for(var myCounter = 0; myCounter < myDocument.pages.length;
myCounter++){
myPageName = myDocument.pages.item(myCounter).name;
app.jpegExportPreferences.jpegExportRange = ExportRangeOrAllPages.EXPORT_ALL;
//Modify the following to change the Resolution. Enter a figure instead of 300
app.jpegExportPreferences.exportResolution = 300;
//Modify the following to change the colour space. the options are:
//JpegColorSpaceEnum.RGB
//JpegColorSpaceEnum.CMYK
//JpegColorSpaceEnum.GRAY
app.jpegExportPreferences.jpegColorSpace = JpegColorSpaceEnum.CMYK;
//Modify the following to change the jpeg quality. the options are:
//JPEGOptionsQuality.LOW
//JPEGOptionsQuality.MEDIUM
//JPEGOptionsQuality.HIGH
//JPEGOptionsQuality.MAXIMUM
app.jpegExportPreferences.jpegQuality = JPEGOptionsQuality.MAXIMUM;
//Modify the following to change the Rendering Style. the options are:
//JPEGOptionsFormat.BASELINE_ENCODING
//JPEGOptionsFormat.PROGRESSIVE_ENCODING
app.jpegExportPreferences.jpegRenderingStyle = JPEGOptionsFormat.BASELINE_ENCODING;
//The name of the exported files will be the base name +
//the page name + ".jpeg".
//If the page name contains a colon (as it will if the
//document contains sections),
//then remove the colon.
var myRegExp = new RegExp(":","gi");
myPageName = myPageName.replace(myRegExp, "_");
myFilePath = myFolder + "/" + myBaseName + "_" + myPageName + ".jpeg";
myFile = new File(myFilePath);
app.activeDocument.exportFile(ExportFormat.jpg, myFile, false);
else{
myDialog.destroy();

Multi-threaded JPG export

The slowest portion of my application is the conversion from a generated INDD file to JPEG. More CPU power seems to be the only solution at this point, but because IDS is single threaded, 3 of the cores on the server sit idle during this.
Is it possible to implement a plugin or Javascript script that exports each page in a separate thread, or similar, thus using all available cores during the export process?

Hi,
I think it is possible in InDesign 5 via "asynchronousExportFile". You can also create multiple server instances and let each instance generate a jpg export.
Message was edited by: 2i_Geert

Missing X-Axis labels in exported excel sheet

Created chart in Desktop Intelligence.
Missing X-Axis labels in exported excel sheet.
Please help me on thsi

Use the Metrics Inspector.
Click on the chart to select it, then click on one labels of the labels to select only the text box containing the x axis labels.
In the Metrics Inspector, use the control or type in a value (in degrees CCW from horizontal) to Rotate the labels.
You may also need to move, or remove the Legend showing the colour(s) used for each series. This is also in a Text box.
Regards,
Barry

Another non-official fix for LR2's non-exporting keywords

Just as Zak Beck's fix, this is NOT an official fix! I'm sure Adobe's fix will be out soon, but for those who don't want to wait and are a bit adventurous, here's my fix :) You will need a copy of your old LR1 catalog and your new LR2 catalog. This utility will read each keyword from the old catalog and apply the same setting to Include On Export, Include Parents and Include Synonyms in the new catalog. FAIR WARNING!!! This is not tested rigorously!!! I did this for my own catalogs, and it works on them. It passes LR's integrity check, opens fine in LR2 and I have checked around 30 (of 9000) keywords and they all seem to be correct now. However, PLEASE MAKE A BACKUP of your LR2 catalog prior to running this. You never know... Needless to say, this comes with no warranty whatsoever, use at your own risk! For the diligent, the source code is included, so feel free to make sure it does what I say it does :) If your still interested, here's what you need to do: 1) If not already installed, install Java 1.6 or later. 2) Download LRKeywordFix.zip from here: http://www.box.net/shared/tyylegbccg 3) Unzip LRKeywordFix.zip 4a) If you are on a Mac, move the file macosx/libsqlitejdbc.jnilib one directory up 4b) If you are on Windows, move the file win\sqlitejdbc.dll one directory up 5) run the command "java -jar LRKeywordFix.jar <path to LR1 catalog> <path to LR2 catalog>" For example: "java -jar LRKeywordFix.jar c:\backups\LR1Cats\mylr1cat.lrcat c:\LR2Cats\mylr2cat.lrcat" Let me know how it goes! Regards, Kris

OK, so I've updated the tool now. This is what's different:
-Separate packages for Win32 and OSX
-Output is more informative now. Note the levels: INFO, WARNING and ERROR. INFO is just FYI, nothing went wrong. WARNING means something non-critical happened and the tool should continue to process. ERROR usually means a critical error happened and the tool will quit. Also, if a keyword from LR1 was not found in LR2, it will tell you so.
-I actually check that the LR2 keyword is the same by complete name, case sensitive. So, e.g., if LR1 keyword was 'Los Angeles^California^USA', the LR2 keyword must be exactly the same, not e.g. 'los angeles^california^usa' or 'Los Angeles^USA', etc. This may be a nuisance for some but I felt it was better to be strict here. If really needed, I can add an option to let the user choose how strict the tool will be.
Win32 package:
http://www.box.net/shared/54yyp6zuq4
OSX package:
http://www.box.net/shared/un61qc2gfg
/Kris

JPG export when file is missing?

I'm a new Lightroom user and have just transferred over from Aperture.
In Aperture when the original image was offline it was still possible to drag or export the high quality preview jpg out onto the desktop.
Is this possible in some way within Lightroom?

For LR2 and LR3 catalogs, LR/Viewer can extract your previews.
Beat

Can i change the color of copyright metadata for a jpg export

i'm using lr 2.7 and want to know if i can use another color other than white in my copyright metadata added to a photo. if someone can help it'd solve some problems with the copyright fading into the image and not readily visible on light image backgrounds.
thank you in advance.

89 red baron wrote:
i think your instructions are for v3. but i found what i needed for v2.7 under Web panel.
Sorry, I didn't catch this fact in your post.
89 red baron wrote:
do you know if one can change color just in Develop or Library mode for an image to email?
I don't think you can do that in Develop or Library, as LR2.7 does not have a explicit watermark editor, and the options in export are very limited.
Beat

Missing parameter values message when exporting report

Post Author: Gr_Pr
CA Forum: .NET
Using .NET 2005, CR XI R2, and the Crystal SDK for .NET 2005 to generate reports. Basically CR is my application's reporting tool. So, we create a report in CR XI R2, then distribute that report to our users loading it into the .NET application using the Report Document class.
We have a small problem.
Our user's have the ability to use pre-defined 'prompts' that will pass parameters to the reports. Let's say that the prompt will pass in (5) pre-defined parameter values, but the customer wants to run their own 'custom' report using our prompt, but their 'custom' report contains (6) parameters.
If I let the Report Viewer load the report, the user will be prompted for the missing parameter value that was not supplied by the 'prompt'.
If I run the report without loading it into the Viewer and try to export the report directly to PDF I receive an error message from CR stating I have 'Missing Parameter Values' then the report errors out.
Has anyone come across this? Is there something I missed?
I am not real sure as to why you would be prompted by the Viewer and not by the Export Class. This worked fine when using the RDC component, I was prompted for the missing parameter value by both options.
Any help would be greatly appreciated.

Hi,
The report has it's own ADO Datasource set in crystal reports, so I just pass the log on information to the report object before doing anything else.
this.DataSourceConnections[0].SetConnection("ServerName", "Database", "sa", "Password");
I then do a refresh before applying the parameter values (I do this because the user can preview the report more than one time by using a preview button on the parameter form without re-loading the report object)
this.Refresh();
Then I set all parameter values followed by setting the recordselection formula.

"Missing parameter values" error on Export - rehash

VS2008, CR2008, no SP.
I am getting this when trying to use the export button on the CrystalReportViewer tool bar. I am pretty sure I need to refresh the report when the export button is clicked, but I cannot find a CrystalReportViewer event for this. I created my own Export button and refresh the report when it is clicked and it works fine - no errors. So now I want to get rid of the Export button from the button bar, but it seems that this is not possible?
I guess my question is... is there an event I can trap associated with when the export button on the original CrystalReportViewer toolbar is pressed OR is there a way to get rid of the Export button on the toolbar?
Thanks,
Dave

Yikes - I can't believe I missed that! OK the button is gone and all is well.
This has been an interesting project. I usually set up my reports with BOTH the CrystalReportSource and the CrystalReportViewer and that combination seems to always work great. Its really easy to pass parameters and selection formulas with this combination. However, I have one report that I need to pass both parameters AND a selection formula to the main report AND a subreport so I have to get rid of the CrystalReportSource and instead use the CrystalReports.Engine. This gets a bit more tricky as I have found out.
Anyways all is well. Thanks for your help - you showed me something that was right in front of my face.
Dave

"Missing parameter values" error on Export

Hi,
I am getting "Missing Parameter Values" error if all required parameter values are not passed in the report through application. Same error is not coming when all the parameters are passed.
And parameter window also not displaying if all parameters are not passed to the report for export option. (Parameter window displaying on preview option if all the parameters are not supplied).
I have tried both Report Viewer's ExportReport function & ReportDocument's Export function. But both are results same.
Software details:
Crystal Report created in Version: 10.0.0.533
.Net 2005
10.2 Crystal component. Crystal Runtime Version - v2.0.50727 and DLL Version - 10.2
Please help me to resolve this issue.
Thanks,
Venkateswaran.P

Given example is not working as expected.
1) Calling of ExportReport() function invokes the file Save As window to save the exported file eventhough exported path & file name supplied in the program.
2) After accepting the output file name, "Missing parameter values" error coming instead of displaying Crystal's Parameter window.
Below is the piece of code to export the output. I am calling Export() function if all the parameters are supplied by the application otherwise i am calling Viewer's ExportReport() fuction. Please have a look and let me know if any code change is required.
 ReportDocument crRepDocument;
 String m_strExportPath;
 Boolean bUseRepViewExport = false;
 if( crRepDocument.ParameterFields.Count > 0 )
 if (m_Parameters.Count < crRepDocument.ParameterFields.Count)
 bUseRepViewExport = true ;
 ExportOptions crExportOptions;
 DiskFileDestinationOptions crDiskFileDestinationOptions;
 crDiskFileDestinationOptions = new DiskFileDestinationOptions();
 crExportOptions = crRepDocument.ExportOptions;
 if (base.m_ExportFormat == eExportFormat.RTF)
 crDiskFileDestinationOptions.DiskFileName = base.m_strExportPath + ".rtf";
 crExportOptions.ExportDestinationType = ExportDestinationType.DiskFile;
 crExportOptions.ExportFormatType = ExportFormatType.RichText;
 crExportOptions.DestinationOptions = crDiskFileDestinationOptions;
 else if (base.m_ExportFormat == eExportFormat.PDF)
 crDiskFileDestinationOptions.DiskFileName = base.m_strExportPath + ".pdf";
 crExportOptions.DestinationOptions = crDiskFileDestinationOptions;
 crExportOptions.ExportDestinationType = ExportDestinationType.DiskFile;
 crExportOptions.ExportFormatType = ExportFormatType.PortableDocFormat;
 else if (base.m_ExportFormat == eExportFormat.DOC)
 if (bUseRepViewExport) //If all the parameter are not supplied. I calling Viewer
 FormReportViewer oFormReportViewer = new FormReportViewer();
 oFormReportViewer.CrystalReportViewer.ReportSource = crRepDocument;
 oFormReportViewer.CrystalReportViewer.ExportReport();
 return true;
 else
 crRepDocument.Export(); //
 return true;

Missing Wraptor DCP Format for Export

Good morning.
I have a fresh install of Windows 7 64bit and a new install of Premiere Pro CC 2014 8.1.0 (81) Build. When opening a previous project from Premiere Pro CC I do not have the Wraptor DCP format for exporting. If I create a new project and sequence and dump a video file on the timeline and try and export it's still not there. I checked the plug-ins/common folder and I do have the Wraptor.prm file in there. I've searched and searched the web and have not seen an issue like this before. I did see something from Oct about it not being supported yet, but I have a second Windows machine (Windows 7 64bit) that I installed PPro on and it's there. I should note that in Encore (build 8.1.0.122) I'm missing the Cinema System Preset with Wraptor DCP too. Is there a prerequisite for getting the DCP option that I missed? I don't remember doing anything special on the other machine for it. Also, to note, I have uninstalled both and reinstalled to make sure it wasn't a botched install.
Anyone have any ideas?
Thanks.

Solved my own issue. Apparently in the barrage of Windows updates I had not yet grabbed SP1. Once that downloaded Wraptor DCP was now a selection in both PPro and Encore. Anyone else that comes across this in Windows 7, make sure you have SP1 installed.

Adobe Media Encoder CS4--Missing part of interface in Export Settings

Hi,
I have a Windows 7 operating system on a 32-bit dell computer. When I open Adobe Media Encoder
I click on the Add button. Then I go to Edit->Export Settings. I am missing some of the
options for instance: adding cue points, parameters, and filters. I think it has a problem with Windows 7, but I'm
not sure.
There should be more options.
I put in my installation disk, but it does not allow you to just reinstall this program.
Does anyone know why this is happening. It works on a computer running Windows XP.

I cannot guarantee that it is not a software issue. Sometimes Matrox is an easy "target." However, with several other Matrox users having similar issues, it does seem that Matrox might be the common element.
One of the issues with troubleshooting Matrox issues with PrPro is that few of the normal responders here have Matrox. Many tried the cards, and most unplugged them for various reasons. Some, like me, have never used them. That kind of limits the responses here, unless a Matrox-user, who has addressed such issues successfully, drops by with some tips.
Good luck, and please update the thread, especially if you do get a "fix." Others will benefit, and I will learn something new!
Hunt

Problems with jpg export and color profiles

I browsed the forum but I didn't find any recent thread about the issue I'm experiencing right now, I wonder if it's common or it just affects me. Mavericks, Aperture 3.5, all up-to-date.
I imported a RAW file (I tried with both a Nikon and a Sony camera), made a few adjustements and then exported the picture as a jpg. It looked good in the Finder, in Photoshop, in Preview. When I uploaded the file to flickr, everything was ok.
Then, I browsed flickr via its iOS app and - surprise - the image is completely wrong: colors are washed out, desaturated, with an awful greenish dominance. I tried a few things and discovered soon that also opening the file on my Mac with GraphicConverter has the same ugly result. Same with the iOS version of Safari.
I use ProPhoto RGB as my default color space in Aperture. I changed to sRGB: same result. I changed to AbobeRGB and te output is finally consistent through all the platforms and apps.
Too bad I managed to do this only for one photo because, even if I changed the settings, every other photo I exported is still sticking with ProPhoto RGB. The problem is surely here because I solved it changing manually the color space to AdobeRGB with Pixelmator and re-saving the images one by one. But of course this cannot be a successful workflow...
Any experience about this?
Thank you!

OK, I can reply to myself. The issue has mysteriously gone away - no idea why. Edit: The issue is gone on Desktop, with GraphicConverter. From iOS, pictures still look weird.
About the exported default, my bad: I was using presets and they choose their own settings for color space. Still, no idea why the first one was exported in Adobe RGB instead of ProPhoto RGB (the default for "JPEG - fit within 2048x2048").
Message was edited by: difool

Keywords missing in LR2.3 jpg exports.

Similar Messages

Maybe you are looking for