Convert from PSE10 to Lightroom - metadata concerns

After one too many frustrations with PSE, I've been looking for an alternative program. I don't care about editing - metadata (Organizer type features) are my focus. I looked at a few non-Adobe programs - a big problem with them is I can't import my PSE10 catalog, with 12,000 photos. On the PSE forum, the most common advice was to go to Lightroom, so I was holding out hope for that. However, I've played with the LR 5 trial for half a day now, and as far as I can tell, it doesn't make good use of the PSE catalog either! This is very disappointing for me, but I'm wondering if some of you folks can show me things I'm missing.
I'm looking into to converting from PSE10 to LR 5 on a Windows 7 machine. I have about 12,000, half TIFs from scanned images and half JPGs from digital cameras. As I said, I only care about metadata management. My focus is genealogy, so getting the original dates of scanned pictures captured is very important, and these often are only roughly known.
My main issue is that it seems to me that LR is taking the metadata from the photo files, not the catalog. I used the LR feature "Upgrade Photoshop Elements Catalog". The reason I say this is for two reasons:
(1) When PSE10 writes tags to files, it adds to any tags that are already there. So although PSE10 shows only the updated set of tags in the GUI, the photo files have both old and new tags. After doing the LR Upgrade PSE Catalog, I'm seeing old and new tags. It appears to be ignoring what is in the catalog and looking at the file. (As far as I know, the old tags are not present in the PSE catalog anymore, so it can't be looking at the converted catalog.)
(2) PSE10 allow you to tag photos with incomplete dates (e.g. no time, no day and/or no month). But if PSE10 has an incomplete date, it won't write it to the file (very annoying for working with historical photos). But LR does not show these partial dates, it only shows complete dates. In this case, I'm not sure if LR is showing the metadata in the photo files, or if it dropped the PSE10 catalog date info during the "Upgrade".
So my main question is, am I missing something with regards to the import, or am I correct in my impression that this "Upgrade PSE Catalog" isn't doing much of anything? (ExifTool shows all the metadata in the photo files -- much more complete than LR for that matter -- so what am I gaining by importing the PSE catalog into LR?)
A couple other miscellaneous questions if I may:
-- In PSE10, there is a notes field in the metadata, which goes into XMP-album in the photo files. Does LR not support this? As far as I can tell, LR supports only a few XMP namespaces, with no support for others.
-- In LR in the Folder pane, I have no scroll bar, so I can only see the first few entries. This seems to be a serious bug to me. Or am I missing something?
-- It appears in LR that one cannot show your entire catalog in the main pane sorted by folder then by file name. Is this correct? (This also seems to be a major drawback to me!)
-- When I try to change the date of a photo (Edit Capture Time in LR), it forces you to enter a complete date/time, unlike PSE10. Overall, it is much easier to manage these dates in PSE, it seems. Does LR handle incomplete dates to any level?
-- When I did my PSE import/"Upgrade", it assigned the wrong file names to some of my photos (it used file names from other photos in the catalog). Is this a known issue?
I imagine I have a very unusual vantage point, but at this point it seems that PSE is far superior to LR! And I'm not happy with PSE10!! Anyways, thanks in advance for your input. Sorry about the long post - wasn't sure if I should divide it up or not.
Bill

This is a reply to the post from John R. Ellis...
You mentioned "Adobe has never bothered to fix...". Note that the last post by Michel B in this thread
http://www.elementsvillage.com/forums/showthread.php?t=78779&page=2
indicates that PSE11 can handle this.
You say "After importing.... I used ExifTool to append..." Did you do this file by file, or with a script? A Perl script? (The reason I ask is that I would have to learn Perl, so I would have to decide how much this means to me...)
Regarding your suggestion to use fake dates
"(e.g. "1970" => "1/1/1970 00:00:00")"
I've been aware of this since I read it in your psedbtool material a year or two ago, but I've resisted making such changes. When dealing with historical photos, you want the ambiguity. In fact, you'd like to use things like "About 1970" and such. I wish the photo metadata community would get on board with that.
Regarding your point about catalog conversion, for me it sounds like it would be just as good to import the photo files directly. (Better for me, I think, since converting the catalog seems to lose the folder hierarchy in the LR Folder view for some reason. However, if I'm going to import the photo files directly, then LR has no advantage for me over any other program that I can see. The ExifTool GUI utility does a much better job with the metadata in general - the key drawback for me being the fact that you have to type out the keywords each time you want to add one to photo. Looking at the ACDSee Pro trial, that appears to handle metadata better than any of the Adobe products - the critical drawback being that it uses its proprietary XMP namespaces, meaning interoperability issues. LR has drawbacks for me, such as not being able to sort by folder than filename in the main view pane and the lack of support for other XMP namespaces (and the Folder pane scrollbar thing). So at this point I'm in a state of depression. As far as I can tell, I only have a partial solution to my problems - upgrade from PSE10 to PSE11. Truly a depressing notion!!

Similar Messages

Convert from Aperture to Lightroom

I have a "managed" Aperture library with 18,000 Pics. The library is located in my pictures folder on my main HD. I want to convert my collection of pics into lightroom while retaining the keywords that I have assigned. I want to create a "bucket" file structure that will reside on an external HD. The pics are an assortment of file types consisting of NEF raw, Tiff, jpeg & DNG.
I have tested a few pics to get a feel for exactly the best way to do this. I tried exporting a master with a sidecar file and when I import into lightroom I cannot see the keywords. When I view the file with iView the keywords show up and I cannot figure out why LR doesn't see them.
Thanks,
Kevin

Annoture was the answer.... Here is how I was able to do it
1. In Aperture export each project as a separate folder w/xmp to final desired drive location rename files to master filename (the file name is important later when running Annoture)
2. Drag the new folder into iView
3. Use Annoture to copy metadata from Aperture to iView (it will look for matching filenames)
4. In iView Sync Annotations- (export to original file)
5. Import into LR at current location and ratings & keywords are now visable
The only thing that I don't understand is what to now do with the XMP sidecar files?? Do you need a sidecar file with a DNG or do you only need them with JPEG & RAW files? I notice that if I remove them when I go into LR all of the information is unaffected. Does this mean that I have altered the original file or is LR keeping track of this somewhere else? Should I remove all of them?
Thanks,
Kevin

Questions about converting from Photoshop to Lightroom

Hi! I have been a Photoshop user for many years now, but after a lot of thought, reading many reviews and much reccommendation, I have decided I would like to buy Lightroom! However, I have absolutely no idea how I go about doing it. I thought it would be simple but after looking into it, people have made it seem much more complicated than I thought. SO, here are a few qustions which I hope somebody can answer!
1. Do I already need a version of Lightroom before I can buy Lightroom 4 or 5?
2. Do I buy it on a disk, or do I download it off the Adobe website? Which is the better option?
3. I'm currently on windows 7, however I'm going to be buying an iMac next year. Will I have to buy another version of Lightroom next year? Or can I install it on multiple devices?
4. Why is Lightroom 5 so much cheaper than Lightroom 4 on Amazon? (not the update versions)

The Upgrade from a previous version is a lower price, but the upgrade price should clearly say UPGRADE.
If it says FULL version, you won't need to own previous versions of LR
Looks like Adobe is offering LR 5 for $40 off on the FULL version right now

Converting from PSE to Lightroom 3

If you're thinking of migrating your PSE catalog to Lightroom 3, see my (last) FAQ:
http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm#_Converting_to_Lightroom

Not correct at all - please see my previous response to a similar post.
Although you may want to check my work - I don't know a thing about iPhoto - I'm assuming the iPhoto directory structure is also a disk directory structure, like Aperture can be - is that correct? Or is it a figment of iPhoto's imagination, so to speak - if so, disregard everything I said in this post and the other one too.
Rob

Moving from Bridge to Lightroom, when adding existing files on hard drive, will metadata transfer? Should I choose embed sidecar in file handling or will it automatically happen if I choose standard?

Moving from Bridge to Lightroom. Will metadata in existing files be recognized by Lightroom, and should I select embed+sidecar when adding files to library for the first time.

Thanks guys, appreciate the feedback.
CHRIS - you are exactly right about my FUTURE workflow. What I'm trying to figure out now is how to best handle images already processed. My import should be OK based on the way I have duplicates in separate directories, BUT I'm wondering how to avoid seeing all of these duplicates in LR when I search by keyword, etc.? I guess I can somehow flag the RAW files and only get them in my results.
One question though - Stacks, etc. sounds great for the LR processed images. But what about variations based on processing in Photoshop after the LR Develop stage? I guess in this case I will just have to keep duplicate images if I have multiple versions from my PS work?
ISAAC - Thanks for clarifying that LR will recognize my XMP files from Bridge. What about the opposite direction . . . if I edit something in LR and capture this via XMP, it won't prohibit Bridge from recognizing XMP info if I access a file via Bridge, will it?
ALSO - Do you know where I can find info about tracking via XMP vs. the central database? You mentioned a couple of valid points, but I'm not sure I have a full handle on the pros/cons of these options.
Thanks!
Mark

Convert from free trail version to CC download version of Lightroom

I tried the trail version of lightroom and liked it. I signed up for the special Photoshop CC and Lightroom cloud version for 9.99 a month. When I use the download for Lightroom it says it is up to date because I have the download from the trail on the machine. If I click the link to convert from trial to purchased version it drives me to enter a license number which I do not have for the Cloud based monthly subscription. How to I get converted from the trail (which has 23 days remaining ) to the version I am paying for? Thanks for the help

According to Adobe if you already have a trial or purchased version of Lightroom installed, you don't have to uninstall it. Choose the option to install the Lightroom through either the Creative Cloud app or through the Creative Cloud Download Center. It upgrades your trial or purchased installation to the fully licensed version that is part of your membership. You can’t even use the serial number from previous version of Lightroom when you install the Creative Cloud version of Lightroom. Creative Cloud products license with your Adobe ID. Even though a Lightroom Creative Cloud installation includes a serial number, it's only used for registration, not installation.
After you have purchased a Creative Cloud Individual membership, Lightroom is available for installation within the Creative Cloud desktop app. If you have already installed the trial version of Lightroom, you can license it by running the Lightroom installer from the Creative Cloud desktop app.
http://www.suzannemathiaphotography.com/learning.htm

System or program crashes when converting from NEF to DNG

Hello Adobe.
First off, I love your software.
Second, this is my concern. You guys are pushing DNG as the go to raw format. That would be great if it worked good, but it doesn't.
First, when I convert from my Nikon NEF format (Nikon D7100) it chugs along just fine, then suddenly crashes either the program or my system after converting 50-100 or so images.
I have tried everything from downloading your software again, to turning off everything other then what is needed to do the conversion.
Of course I have the latest DNG utility/plug in/drivers from your website.
Second, the DNG images open much slower then my NEF images. Plus when I view them in Windoze file system view and want to see the photos in extra large icons, it renders the images very slowly.
My system is Windoze 8.1 updated always, Photoshop CC latest and greatest (I'm in the rental program), Bridge and Lightroom.
I have tried to use bridge and lightroom to do the conversion, even a separate utility and the crashing still happens. All these are up to date.
My system has an i7 Intel processor, 16 gb of Kingston ram, an ASUS P8Z77 MPRO mother board and a good stable power supply.
No other software crashes my system like converting from NEF to DNG.
What I do notice is my CPU fan goes into high RPM's and I am wondering if the CPU is overheating causing this.
If that is the case, then it would seem to me the conversion software is taxing the system far more then it should since my system is no slouch and while it isn't the latest and greatest, I would consider it to be in the top 20%,
it should be able to handle the conversion with no problem.
Are you aware of problems with the DNG software and or file format?
Is their any information I could forward to you to help solve the problem?

Photoshop Help | Digital Negative (DNG) - Adobe
helpx.adobe.com/photoshop/digital-negative.html
DNG is a publicly available archival format for storing camera raw files. Adobe provides Adobe DNG Converter, a free utility that converts files from more than ...
That is off the net, therefore, Adobe looks at DNG as part of Adobe Photoshop, which it is if a person chooses to convert.
My issue has to do with it crashing, both my system and software.
I assume if people here are using it, then they can advise me if they are having similar problems.
I have also written Adobe directly several times over the last month and have yet to receive a response.
I apologize that I posted here, but since I consider DNG an integral part of Photoshop, then I think it is appropriate here.
I was also not aware of a DNG forum, if one exists.
Thank you for your assistance.
Jim

What are all the locations where lightroom metadata is written?

Hi, I have a question about the location of any metadata (IPTC, keywords, etc.) written in Lightroom 5 to my raw files. I understand that this data is written (embedded) into jpg files but as a .xmp file next to the raw files. My question is, if I purge the jpgs and do NOT continuously copy the updated .xmp files to my backup drives, and if I were to lose my Lightroom catalog, will all my Lightroom metadata that I added be lost? Or, does Lightroom keep all my metadata in the catalog file? Is the Lightroom catalog the "source" location of the data that's added to the jpgs and .xmp file?
Thanks for any help explaining this arrangement to me!
DLMST

By default, your metadata is NOT written to the JPG or RAW sidecar XMP files.
By default, all metadata is written to the Lightroom catalog. Furthermore, there is no way to turn this off, your metadata always is stored in the Lightroom catalog. Thus, if you are concerned about making backups, and restoring from backups, you need to backup/restore the photo files and the Lightroom catalog file. In fact, I consider making backups (on a different physical disk) of photo files and Lightroom catalog to be mandatory.
You can optionally write SOME metadata to the JPG or sidecar XMP files, but this method never gives you a complete backup of all of your metadata. It can be valuable additional insurance.
My question is, if I purge the jpgs
This is not a good idea, I can't imagine why you'd want to "purge" your original photos, especially if you are concerned about restoring them at a later time

"Share to Flickr" stopped transferring tags and descriptions from PSE10.

The "Share to Flickr" function suddenly stopped transferring tags and descriptions when uploading photos from PSE10. The only event that preceded this error was a prompt to "authorize" my Flickr account (when this prompt happens on occasion, I simply re-authorize my Flickr account and everything usually returns to normal).
Here is what I've tried so far, with various ordering of steps:
Preferences-Adobe Partner Services-Reset Accounts
Preferences-Adobe Partner Services-Clear Online Service Data
Preferences-Adobe Partner Services- Refresh
Deleting the cache folder found at: C:\Users\<username>\AppData\Roaming\Adobe\Online Services\Photoshop Elements 10.0.0\cache
Any other suggestions? My photos continue to upload and appear on Flickr, but the hours of time consuming effort I put into tagging and captioning my photos is no longer displayed on my Flickr page.
Thanks,
Garth

Hi,
I have tried using PSE 9 & PSE 10 - they both omit the tags when uploading the images to Flickr.
If I upload the same image directly to the Flickr page then the tags are copied.
I am beginning to think that the problem may lie in the Adobe uploader service. When you use PSE to share to Flickr, the images are sent to the Adobe uploader service which then passes them to Flickr. The same Adobe service is used by Lightroom and I believe that has an option to minimize the metadata. I'm wondering if the service has been changed to minimize the metadata by default but we don't have a way of changing the default.
I would be interested to hear if Jon can get it to work correctly on PSE - then I know whether to carry on looking or not. I'm sure that it will work on Lightroom.
I have downloaded the Flickr uploader tool and use drag & drop from PSE to the uploader. If you write the tags to the photos first, they are copied to Flickr.
Brian

Applescript to convert from AW6 spreadsheets to Excel

I have an iMac (iMac12,2) running OS 10.9.1 with applications of Pages’09 (4.3), Pages (5.0.1), Numbers’09 (2.3) and Numbers (3.0.1) available.
One of my laptops is a MBA (MacBookAir1,1) that I have kept at 10.6.8 with applications Appleworks (6.2.2) and Appleworks (6.6.9) available.
Recently, I converted many CWWP documents from AW6 into Pages. This was done on the iMac with an Applescript that copied a file (AnyDocumentCWWP) to the desktop as a file named AWV6, opened AWV6 with Pages’09, saved the result as AWV6.Pages, applied the creation date and modify dates of the original to AWV6.Pages, moved the new AWV6.Pages to the original directory and moved the original file to the trash, renamed AWV6.Pages to the original filename (excluding extension). The Pages version of the original document does not preserve the formatting of the CWWP, but the content was now discoverable with Spotlight. Since I was primarily concerned with the content, I would consider the conversion effort successful enough.
I performed the same sort of process on the iMac with CWSS documents converting from AW6 into Numbers. Here the results were less successful. I discovered that many of the converted spreadsheets had cells where the cell contained the last calculated value in substitute for the formula originally present -or- Numbers was unable to open the CWSS spreadsheet due to size limitations. Neither problem occurs when the file is converted on the MBA by Appleworks into an Excel format. For those CWSS files that did not properly convert to Numbers, I would like to perform a conversion to Excel.
When a given spreadsheet is manually opened on the MBA with either version of Appleworks, one can “Save as” using several formats of Excel. That operation will preserve the formula which cannot be recognized in Numbers’09. An example of this issue is when a spreadsheet has a cell that contains a formula with the function “ISNUMBER”. When I manually open a CWSS in Appleworks (either 6.2 version), I can Save As Excel Win 97 … or Excel Mac 98 … creating an XLS file that preserves the formula.
I have attempted two techniques with Applescript to be able to convert my CWSS documents into XLS format. Neither seem to work.
The first technique is very similar to a few lines extracted from a canned script found on http://macscripter.net/viewtopic.php?id=8296 the relevant code is:
set theSprTranslator to "Excel Win 97, 2000, XP 2002 spr"
tell application "System Events" to set mfpath to get path of disk item ("~/desktop/" as string)
set newfile to (mfpath & "AWV6" as string)
set NewFilename to AWV6XLS
tell application "AppleWorks 6"
    activate
    open newFile -- alias reference is ok
    save using translator theSprTranslator with NewFilename and replace
    close front document without saving
end tell
When this did not work, I attempted a scripted GUI solution as a second option. The GUI code I had found at http://stackoverflow.com/questions/17348326/applescript-to-save-an-appleworks-do cument-wont-compile-end-tell-vs-end-easy is:
tell application "System Events"
         tell process "AppleWorks"
                 click menu item "Save As…" of menu "File" of menu bar 1
                 click menu button "File Format" of window "Save : AppleWorks 6"
                 click menu item "Excel Mac 5 spreadsheet" of menu 1 of menu button "File Format" of window "Save : AppleWorks 6"
                 keystroke return
         end tell
end tell
Unfortunately there is no “File Format” menu button, after a bit of further research, I discovered UI Browser and wrote my own Applescript equivalent:
set mytempwork1 to AWV6
set theSprTranslator to “Excel Win 97, 2000, XP 2002 spr”
tell application "Finder" to open file (mytempwork1 as string) of the desktop
tell application "System Events"
    tell process "AppleWorks"
        click menu item "Save As…" of menu "File" of menu bar 1
        tell text field 1 of window "Save : AppleWorks 6"
            set value to "XX" & mytempwork1
        end tell
        click pop up button 1 of group 1 of window "Save : AppleWorks 6"
        click menu item theSprTranslator
        —click radio button 2 of group 1 of window "Save : AppleWorks 6"
        —delay 3
        —click radio button 1 of group 1 of window "Save : AppleWorks 6"
    end tell
end tell
tell application "System Events"
    tell process "AppleWorks"
        delay 10 — <<<<<IF YOU CLICK ON THE BUTTON WHILE IN THIS DELAY, THE SCRIPT WILL BEHAVE PROPERLY
        click button "Save" of window "Save : AppleWorks 6"
        delay 1
    end tell
end tell
This GUI script behaves almost as I would like. It seems to ignore the setting of the “pop up button 1” unless I actually intervene while the script is running and I click on the button. When I do so, the script runs as intended.
Is there a way to force Appleworks to recognize the Applescripted value of the “clicked” menu item?

Hello
As far as I know, there's no need to resort to GUI scripting. The problem in exporting in AppleScript is that AppleWorks 6 only accepts typeChar (TEXT) data as translator name while AppleScript string has become always being represented as typeUnicodeText (utxt) since OS X 10.5. This makes passing translator name to save command difficult but there's a workaround method as shown in the sample code below. The |TEXT|() handler does the job. Tested with AppleWorks 6.2.4 under 10.6.8.
main()
on main()
    set export_translator to "Excel Mac 98, 2001 spreadsheet"
        "Excel Mac 5 spreadsheet"
        "Excel Mac 98, 2001 spreadsheet"
        "Excel Win 5 spreadsheet"
        "Excel Win 97, 2000, XP 2002 spr"
    set export_translator_TEXT to my |TEXT|(export_translator)
    set src to (path to desktop)'s POSIX path & "in.cwk"
    set dst to (path to desktop)'s POSIX path & "out.xls"
    set srca to src as POSIX file as alias
    set dsta to touch(dst) as POSIX file as alias
    tell application "AppleWorks 6"
        --return export translators
        open srca
        tell document 1
            if document kind = spreadsheet document then
                save in dsta using translator export_translator_TEXT
            end if
            close saving no
        end tell
    end tell
end main
on touch(f)
    do shell script "touch " & f's quoted form
    return f
end touch
on |TEXT|(u)
        string u : source text
        return data : «data TEXT...» representing u converted to MACROMAN encoding
    do shell script "u=" & u's quoted form & "; printf '%s' \"$u\" | iconv -f UTF-8 -t MACROMAN | xxd -p"
    run (run script "
script
    «data TEXT" & result & "»
end script")
end |TEXT|
Hope this helps,
H

Are there problems converting from Adobe Bridge to Organizer?

HI,
I've searched for information on this and haven't found anything so maybe there aren't any problems :} but...Murphy and I are good friends so I have to ask if there are problems.
I currnetly run Elements 8 on a MacBook and have about 2000 pictures in Bridge and some in Iphoto. I use bridge for pictures for web design and Iphoto for family stuff. I 'help out' with the computer stuff at a cat shelter in town and they have just bought Elements 10 and run the PC version. I am thinking of upgrading to 10 so I will be familiar with their version but am worried about converting from bridge to organizer. Are there any known problems? Is there a tutorial some place about the conversion from bridge to organizer.
Thanks for any ideas

You have no pictures in Bridge. Bridge is just a browser; it just shows the current state of any folder to which you point it, so that's no problem. If you really want to use organizer, it will pick up your metadata keywords when you import the photos. Photos from iphoto will be duplicated on import to the organizer (normally it just makes a dbase pointer to the existing photo) to avoid inadvertently writing into the iphoto library, which can corrupt it and cause loss of the photos it contains.
You will lose any stacks in bridge when you import the photos into organizer.

Lightroom Metadata editing and workflow is tedious nightmare!

I'm new to Lightroom in just the past month, but have used it enough to see that a serious interface problem makes Lightroom version 1x virtually unusable in a deadline-oriented publishing workflow. Lightroom's Metadata editing and workflow is just a terrible nightmare, and far too tedious and slow. It appears to be an afterthought implemented by good-hearted souls who've never had to edit this sort of information under serious deadline pressures. I know Lightroom is marketed as an image database and not a file browser, but we're all looking to simplify our workflow here and with just a few subtle enhancements, Lightroom could be an excellent file browser and file import manager too.
As it is now, the Lightroom v1x handling of File Naming and Renaming, Metadata Editing and Keyword Editing is poorly implemented and in need of an immediate overhaul to help professional photographers expedite this crucial and time-consuming first step in the archiving workflow. While Lightroom is very good at many other tasks, I give it a big fat "F" of a failing grade for these tasks.
First, the Lightroom Library Module needs an even more simple, linear interface that steps users through a precise procedures (and helps them remember them). Arguably, to accomplish this, the Import function may need to become a separate Module that can be selected and used separately before entering the Library. As File Naming and Renaming, Metadata Editing and Keyword Editing currently are implemented, I, for one, am always forgetting to fill out one of these critical sections and can't even seem to remember that some may need to be done before importing while others appear to be conceived to be done after importing. My point is, all these related steps really need to be done together, but the Interface spreads out the functions too much, and it is nearly impossible to build a logical and linear Import workflow, especially when you are first learning Lightroom.
I'd like to see a workflow that walks me through applying and editing (in order), File Naming, Basic and IPTC Metadata, Captioning and Keywords, so that I don't always forget some obscure step in the process (which I keep doing). Here are some specific suggestions, some of which may prove to be valid, some of which may be problems due to my lack of experience with thye software.
1. As currently implemented, Metadata editing requires too much thought, and does not have enough intelligent automation. Eliminate as much typing as possible (See Photo Mechanic!)
2. Lightroom needs better Metadata Presets. A "Quick Edit" view to simplify interface for editing minimal metadata info (File Name, Basic Info, Keywords, Headline, Limited Copyright Info).
3. Separating Keyword Tags, Metadata Browser, Keywording Presets and Metadata Presets confuses the workflow. They should all appear together under one selectable module that organizes a suggested, linear workflowfor these tasks, but allows it to be customized. This is the sort of tasks that need to be learned by rote memory, and having all these panes floating around on both sides of the photo make it impossible to quickly step through these tasks.
- Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import or...
- Import, Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import
4. Rename should offer the option of renaming the master file names on the disk, not just file names in the database (which I think is what Lightroom does, but again, this is very confusing for new users)! So, it is my belief that this feature needs a checkbox option to rename one, the other or both. But you need to be able to quickly find this dialog box every time you do an import, and it should not be hidden away out of view under the Library menu. Ideally and logically (for workflow), File Renaming should be handled when starting the Import into Lightroom.
This is critically important because many user

Lightroom metadata editing Part 2 (see Part 1 at top of thread)...
...This is critically important because many users just do not want to trust their images solely to any database and we want the ability to go look for master files with identical names should something go wrong with the software or we decide to edit the file in Photoshop outside of Lightroom or even switch to another library software program.
My own habit is to rename every file with the date followed by a unique, three-digit file number, as in 20070717_001, 20070717_002...up to 999 etc. (I have never shot more than 999 files in a single day, but this could be a four-digit number). To file these on disk, a folder with a similar naming scheme is created for each day's shoot, although a keyword slug is added to the end instead of file numbers.
5. Metadata Presets (Basic Info, IPTC metadata, EXIF metadata), Keywords need to be able to toggled on or off (promote/demote-expand/contract). Turning Off/On one section at a time via the Metadata Presets popup menu is too tedious...and you can't display IPTC and Large Caption together or leave Large Caption turned on. It also is difficult to remember where the Large Caption default (Preferences) setting is...
6. Please get the EXIF data out of the way entirely when editing captions and visa-versa...And the EXIF data should not separate Basic Info and IPTC Info fields. Please relocate the EXIF to the bottom of the Metadata pane...
7. IPTC Content, IPTC Copyright, IPTC Creator, IPTC Image expand/collapse sections need more automation:
- The Presets fields need Preset lists of entry choices for cities, states, countries, etc.!
- ISO Country Code automatically should be filled in when a country is entered.
- Date created automatically should be filled in from camera EXIF data
- Metadata Presets "Save As" should fill in old name, and allow you to rename it; (When it appears, the new name field should not be empty. This would aid in consistent, alphabetical naming
- Metadata Presets naming should support job names, with actual Presets saved under each job name...
8. IPTC Status EXIF, Contact, etc.
- Caption field MUST display more than one line...(6-8 lines)!
- Caption field MUST support Shift/Return!
- Headline (IPTC Content) should be displayed with (and above) caption. Please present information logically!
- Yellow popups should describe what each field name is for...some are real brain teasers...

Artifacts in DNG files converted from NEF

On two occasions, I've encountered artifacts in my photos that I've converted from NEF (using Nikon D7000) to DNG format in Lightroom 3.6. Is there a "fix" for this?

Yes, you're correct. It sounds perfectly feasible to keep a checksum in the database for other file types. I voted for your idea.
Here's an interesting article: http://dpbestflow.org/data-validation/dng-validation
Currently, the only way to check a large number of DNGs is to run the free DNG converter on them, which can take a long time and requires disk space for the second copies. The Adobe SDK has a function for checking the checksums, so it sounds like a relatively easy task to write a small app that would validate an entire directory tree containing DNGs. That could be quite fast and would be a good thing to run periodically.
Hal

How to import photos from iPhoto to Lightroom?

Hey Guys, How do I export photos from iPhoto to Lightroom? I deleted them from the SD Card so I cannot import them directly to Lightroom. Im using a mac so its all very confusing for me. Please help me., Hey Guys, How do I export photos from iPhoto to Lightroom? I deleted them from the SD Card so I cannot import them directly to Lightroom. Im using a mac so its all very confusing for me. Please help me.

To simply import the original files is quite a simple process.
Locate the iPhoto Library (default is your Pictures Folder). Right click on it and select "Show Package Contents".
Locate the Masters folder and drag it onto the Lightroom icon or an open Library window. This will invoke the Import command.
Be sure "Include Subfolders" is checked.
Now you can import all the original files.
If your goal is to maintain structure of the Events it gets a little more tedious. Drag the event onto the Lightroom icon or the Library window. Once imported you can group them into a Collection Name that mimics the Event.
Repeat with other events.
With the impending demise of iPhoto and Aperture, I suspect Apple may be working with Adobe to develop an automated process that will also maintain metadata that was added in those programs. If you can wait a while, it may be worth it.

How do I import GPS information for all of my images from Bridge into Lightroom 5.3?

After importing my images into Lightroom 5.3, I discovered that the GPS location data was imported for some images, but not for others. When I checked the metadata files for the same images in Bridge, the location data was present for all of my recently downloaded images.
Why would Lightroom import the GPS data for some images and not others?
Is there any way to import the location data from the Bridge metadata files into Lightroom?

Tony,
Thank you for your suggestion. I had already tried several approaches along those lines without success. In the end, the GPS data was still present in Bridge metadata file for each image, but not in the Lightroom metadata files for the same images.
So, I went back to Lightroom, and did some further exploring on the internet for solutions. Just as I was wondering whether or not the problem might be rooted in my download presets (i.e., setting copyright into, etc.), I stumbled across a reference by a Pentax owner that identified the same problem. Here's the link:
http://www.pentaxforums.com/forums/115-pentax-k-5/203274-gps-data-not-importing-into-light room-4-2-a.html
In a nutshell, I can download all of the metadata, including the GPS location information, but only if I do NOT use any metadata presets. If I use a metadata preset when downloading my images, no GPS data can be seen in the Lightroom metadata files, but it does import into Bridge's metadata files. I've now tried this both ways, several times now, and have verified this result.
I also tried re-downloading images with no presets, and replacing (copying over) the image from my original download. This did not solve the missing GPS data in the Lightroom metadata. From this point, all that I could think of doing was removing all of my recent downloads from Lightroom, and starting over. However, I'd already started editing my images, and I didn't want to lose that time.
So, I re-downloaded all of my recent images from my memory cards as a copy into each file without any metadata presets. Then, after selecting the copy first, followed by selecting the original (order is important), I toggled 'Sync Metadata' under the Metadata tab in Lightroom. Voila, the GPS data appeared in the original metadata. When this is done for all of my images, I will delete the second copies in my files. Once I am satisfied that everything is okay, and my images are backed up satisfactorily, and only then, will I reformat my memory cards.
This whole experience has surfaced an interesting quirk in Lightroom, or in my Lightroom settings that I don't understand. It may be something that Adobe might want to look into further, if others are finding a similar problem.

Convert from PSE10 to Lightroom - metadata concerns

Similar Messages

Maybe you are looking for