Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Interaction with Lightroom

Kommentare

14 Kommentare

  • johnbeardy
    Jim

    I assume in LR you Ctrl S to save out the metadata to a sidecar? Then in MP, Sync and Import the annotations?

    The rating should come across, and I've not noticed a problem there, but the label won't. LR/Bridge and MP record the label in slightly incompatible ways. It's possible to convert them with a script but it's a pain.

    John

    PS Some LR users like my OpenDirectly plug-in for opening raw files directly in C1 (or in any other app) directly from LR. You can also use it to send files to the active MP catalogue
    0
  • Jim MSP
    [quote="johnbeardy" wrote:
    Jim

    I assume in LR you Ctrl S to save out the metadata to a sidecar? Then in MP, Sync and Import the annotations?

    The rating should come across, and I've not noticed a problem there, but the label won't. LR/Bridge and MP record the label in slightly incompatible ways. It's possible to convert them with a script but it's a pain.

    John
    ......


    John - thanks much for the explanation.
    We can blame this one on pilot error. Not being a LR expert by any means, I had just assumed it saved the sidecar when as it saved the catalog.
    I tried it - and it works just fine for the rating.
    0
  • johnbeardy
    Good, I thought it would be something straightforward.

    In LR's Edit > Catalog Settings | Metadata, there is a preference for automatically writing to XMP. However, whenever you use two DAM apps you have to be careful about which is the master. A one way flow is easy enough to manage, but if you are wanting to exchange metadata repeatedly....

    For instance, if you entered keywords in MP and then read ratings and other metadata from LR, it would probably overwrite MP's keywords with those entered in LR. In theory you should be able to avoid this by saving the MP keywords back to the images with the Sync command, and then in LR using its Read Metadata command to bring MP data into LR, so it is in sync with MP. This works well with DNGs and other files where the metadata is embedded in the file, but with raw files MP's Sync command creates a new sidecar, destroying the Lightroom/ACR adjustments which were in any existing sidecar - oops.

    I mention all this to alert you to the need to be careful about the detail and to be cautious, and in the hope that P1 will understand the shortfalls in how they've implemented the Sync to xmp sidecar command.

    John
    0
  • Jim MSP
    [quote="johnbeardy" wrote:
    Good, I thought it would be something straightforward.

    In LR's Edit > Catalog Settings | Metadata, there is a preference for automatically writing to XMP. However, whenever you use two DAM apps you have to be careful about which is the master. A one way flow is easy enough to manage, but if you are wanting to exchange metadata repeatedly....

    For instance, if you entered keywords in MP and then read ratings and other metadata from LR, it would probably overwrite MP's keywords with those entered in LR. In theory you should be able to avoid this by saving the MP keywords back to the images with the Sync command, and then in LR using its Read Metadata command to bring MP data into LR, so it is in sync with MP. This works well with DNGs and other files where the metadata is embedded in the file, but with raw files MP's Sync command creates a new sidecar, destroying the Lightroom/ACR adjustments which were in any existing sidecar - oops.

    I mention all this to alert you to the need to be careful about the detail and to be cautious, and in the hope that P1 will understand the shortfalls in how they've implemented the Sync to xmp sidecar command.

    John


    John,
    Thanks for the additional thoughts. At this point, I only intend to use MP as the master file for keywords, etc. I was simply starting with LR, as the current MP light table is so painfully slow. I also use LR for my 1st cut at high iso shots, as its noise reduction is better, imo, than CO. When I print, however, I'll use Topaz deNoise.

    I'll have to play a bit on a small set of files with the MP <--> LR exchange. It would be nice, in the long run, to have them in sync .

    However, your warning on losing LR adjustments for raw files is very worrisome. I'll test this as well.
    I may have already screwed up some that I wanted to keep.
    0
  • johnbeardy
    Jim

    To see what I mean, try this with a single (copy) raw file:

    1. In LR make some adjustments and add a rating
    2. Ctrl S to save them to xmp sidecar - look at its file size in Explorer
    3. Add raw file to MP and add some keywords
    4. Action > Sync - Export and choose the Create XMP sidecar files options "Always" or "Only when ..."
    5. In Explorer, notice how the sidecar is a new file
    6. In LR, Metadata > Read Metadata from File and watch your adjustments vanish.

    It's only those who use raw files who experience this problem. I use DNG and MediaPro (as it always has) updates the fields it needs to, without destroying data in other fields.

    John
    0
  • Jim MSP
    [quote="johnbeardy" wrote:
    Jim

    To see what I mean, try this with a single (copy) raw file:

    ...
    6. In LR, Metadata > Read Metadata from File and watch your adjustments vanish.

    It's only those who use raw files who experience this problem. I use DNG and MediaPro (as it always has) updates the fields it needs to, without destroying data in other fields.

    John


    I tried this a bit ago - and yes, my LR adjustments vanished from my raw. UGH.
    Fortunately, I had used EM2 as my primary DAM. I was hoping just to use LR for what it was best at.

    So much for flexibility; I'll continue to be careful. But I'll probably not import metadata into LR.
    0
  • johnbeardy
    The solution is to tell P1 that you need Sync to be done properly by updating rather than overwriting the sidecars.
    0
  • Jim MSP
    I'll probably tell them -- but they seem to have a list of other major problems to fix first.

    My experience with writing code (and managing it) is that the more custom code that is written, the more potential problems down the line when you try to expand its use.
    0
  • johnbeardy
    This isn't that wacky. I suspect they copied the code from the old Extract Metadata command (which creates new sidecars) and put it in Sync. Instead they could have taken the existing Sync command code that updates DNGs JPEGs etc and made it apply to sidecars.
    0
  • Paul Silk
    [quote="johnbeardy" wrote:
    Jim

    It's only those who use raw files who experience this problem. I use DNG and MediaPro (as it always has) updates the fields it needs to, without destroying data in other fields.

    John


    Hi John, like you I have always used DNG and I have to ask, are you having problems getting Media Pro1 to build previews from DNG files for off line use, or is it just me? This was never a problem with EM2 and was one of it's good points as you could rebuild the previews to reflect any changes made in PS/LR to the DNG file.
    0
  • johnbeardy
    Seems to work, Paul, though occasionally I've had to select all and Ctrl B (Cmd B on Mac) to rebuild the thumbnails.

    John
    0
  • Paul Silk
    Thanks John, must be a Windows problem, there are no previews or thumbnails using windows imaging componant for rendering and just thumbnails using PhaseOne rendering.

    Still works fine for me on EM2 though, I just wish I had not upgraded as without that ability MP1 is unusable for me! 😡
    0
  • johnbeardy
    I'm on Windows 7 / 64 bit with Adobe's DNG Codec installed, using embedded preview. I'm not saying everything is OK though!

    For example, in the preview mode the image is shown as a large thumbnail. I can't get it bigger than about 160x250 pixels.
    0
  • Paul Silk
    John strangely enough I'm on W7 64bit and I used the Adobe DNG codec to get thumbnails in MPI but then DNG previews in EM2 would not build until I uninstalled the codec...go figure!
    0

Post ist für Kommentare geschlossen.