• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.

Odd Change to External Editor Process

dbvirago

Member
Joined
Oct 19, 2013
Messages
33
Lightroom Version
Lightroom Version
11.0
Operating System
  1. Windows 10
Been using LR and PS for over 10 years. Ctrl-E to send something from LR to PS, like always and it asks me if I want to Edit a Copy with Lightroom Adjustments. I click Ok and the image loads in PS with none of my adjustments. Never seen this before. I've looked through the settings and can't figure out what got changed. Any ideas? Right now, I'm exporting it as a Tiff and then loading it into PS.
 
Joined
Nov 27, 2013
Messages
1,660
Location
Queensland
Lightroom Experience
Intermediate
Lightroom Version
Classic
I vaguely recall reading of a recent 'Bug' that causes this result. One answer was to [Save Metadata] to the file with [Ctrl+S] before you send to Ps by [Edit In].
 
Joined
Jul 2, 2015
Messages
11,475
Location
Netherlands
Lightroom Experience
Power User
Lightroom Version
The first thing to do would always be to make sure your applications are up to date. The bug Rob is talking about is a recent one, however. I am not even sure it has even been solved yet. So if you are still using 10.0 then I doubt this bug is what causes your problem and I am not sure if updating to 10.4 will solve it. By the way, version 11 has not been released yet…
 
Top