![]() ![]() This can also be included within an export preset. Its disadvantages are that all metadata is stripped (not a concern in my situation) and there is a quirky pop-up every time the plug-in runs. This requires installing only one piece of code, the plugin itself. On the plus side, this can be easily added to an export preset so it's very set-it-and-forget-it.Ĥ. This works but requires installing two pieces of software (exiftool and Run Any Command), plus having some expertise with scripting. Would eliminate this unnecessary duplicate file, leaving only the LR-5.7-compliant jpg. The first command line I used created a duplicate copy of the original jpg with a ".original_jpg" suffix, but I am advised that using the command lineĮxiftool -m -all= -tagsfromfile -all:all -icc_profile -unsafe -overwrite_original "" ![]() Use the Run Any Command plug-in to execute an exiftool command line to edit the metadata back to classic style. The disadvantage to this is that a multitude of unnecessary files are also created every time the jpg is exported.ģ. The jpgs created this way do not have the problem with mis-interpretation by my client's web reporting system. Use the Lightroom Web module to export, thereby producing classic jpgs in the "Large" folder. For my user reports, these worked fine but of course were much larger than the JPEG files I had been using.Ģ. This is a high-volume client with multiple uploads daily and hundreds of photos every month, so a reliable, clerically simple solution that required minimal additional labor was needed.ĭue to the assistance of the LR/PS/CC community, I can report four workarounds:ġ. This produced a low-resolution image that appeared out of focus. Apparently the client's report software that worked fine with my LR-5.7 jpgs was ignoring the full uploaded resolution from LR-CC jpgs, and instead magnifying the embedded thumbnail. When I switched from LR-5.7 to LR-CC, my jpgs began showing up very blurry after being uploaded into my client's reporting software. I'm the user who had the problem John R Ellis is reporting on May 13, 2015. Windows 8.1: File Explorer Preview, Irfanview, Paint, Windows Photo ViewerĮven though LR's JPEGs may be strictly conforming, if it wrote the JPEGs without the unused header bytes and it put IFD0 immediately after the TIFF header, as Photoshop does, then there would be fewer problems with other programs choking on LR's JPEGs. Mac: Preview, Photoshop CC 2014, ColorSync Utility, Firefox, Chrome, Lattice, Paintbrush, Safari, Word I've tested LR JPEGs with 12 Mac and Windows programs and 2 online services, all of which read them just fine: Here's an Exiftool dump of the beginning of a LR JPEG:Īnd here's a dump of the beginning of a Photoshop JPEG: Whereas Photoshop CC uses a more traditional layout: TIFF header, no unused bytes, IFD0, ExifIFD, IFD1. LR writes the APP1 header as: TIFF header, 114 unused bytes, ExifIFD, IFD1, IFD0. While they appear to be strictly conforming to industry standards, the unusual layout has caused problems for at least two users: one who had problems uploading photos to real-estate services, and another whose own software tripped over the layout. See ExifTool FAQ #26 for more details on reading from a csv file.Lightroom CC writes JPEGs in an atypical layout that trips up other programs. Exiftool's biggest performance hit is in its startup and running it in a loop will be very slow, especially on a large amount of files (see Common Mistake #3). This has an advantage over a script looping over the file contents and running exiftool once for each line. The -sep option is needed to make sure the keywords are treated as separate keywords rather than a single, long keyword. The result would look like this: SourceFile,KeywordsĮxiftool -csv=/path/to/file.csv -sep ", " /path/to/files The whole keywords string need to be enclosed in quotes so they aren't read as a separate columns. If the filenames don't include the path to the files, then command would have to be run from the same directory as the files. The first row would have to have the header of "SourceFile" above the filenames and "Keywords" above the keywords. You would have to reformat it in this way. If you can change the format to a CSV file, then exiftool can directly read it with the -csv option. ![]()
0 Comments
Leave a Reply. |