External Edit problem - always JPG instead of TIF/PSD

I would like to report my problem detaily, hope someone can help me out of it
I use LR 3.3 64 bit with PS CS5 64 bit on Windows7 64bit with CR6.3.
In the past, it happens like this:
    - I select External edit preference to TIFF file.
    - If i select the file "abc.jpg" and select "Edit a copy" (with or without LR changes), a file name "abc-edit.tif" will be created and opened by PS, after i finish editing, i click "Save" and the "abc-edit.tif" will appear as-is in the LR's catalog.
Now, it happens like this:
    - If i select the file "abc.jpg" and select "Edit a copy with LR changes", it will open the original file "abc.jpg" in PS (with the LR changes) (!!!).
    - If i select the file "abc.jpg" and select "Edit a copy without LR changes", it will create a "abc-edit.jpg" and open in PS. After i finished editing, if i save it as a tif/psd file, that file will not appear in LR catalog (but the "abc-edit.jpg" file)
I dont think this is normal and the effort i have tried one by one are:
    - Update camera raw to 6.3
    - Delete all PS preferences by delete all .psp file and Hold Ctrl-Alt-Shift when opening PS
    - Uninstall and reinstall PS CS5 and LR
    - Uninstall PS CS5 and install PS CS4
None of above way works for me and the problem still the same.
Anybody share the same problem w/ me and have any clue about this.
Thanks !
PS: I have googled one thread here discuss about the same problem but the way it solved doesnt work for me.
http://www.lightroomforums.net/showthread.php?6607-Lightroom-bypass-external-editor-settin gs&p=81191#post81191

LR changes are stored w/in metadata in the JPG header area so opening a JPG with LR adjustments and ending up with the same-named JPG in PS seems normal because ACR is used behind the scenes to open the file, just like it would RAW file that adjustments in the XMP sidecar.
I think LR catalogs the originally-named file, not the other name if you save it as something else.
I don't know as anything is wrong, or different than normal.
If LR is newer or older than PS by a major version (or sometimes in other cases) then editing must create a separate copy with a new name to contain the adjustments, but if your LR and ACR version of synchronized (like LR 3.3 and ACR 6.3 are) then the integration does not produce a differently-named file because the adjustments stored by LR in the metadata headers are completely compatible with PS and ACR so it just reads them and uses them to create an in-memory rendering of the changes w/o going through an intermediate file.

Similar Messages

When I Select "Edit in Photoshop," Lightroom sends a JPG instead of a PSD or TIFF

To get started, I'm on LR 5.2RC and Photoshop CS6. All software is up to date and both ACR's are the same at 8.2. And my source files are all JPEG's.
When I select the "Edit in Adobe Photoshop CS6" option on an image, I get the proper "What to Edit" pop-up window and have the option to edit a copy with LR adjustments, edit a copy, or edit original. My problem is that no matter what option I choose, LR will make a copy of the image as a JPG (rather than a PSD) and send that to Photoshop.
I've gone to LR preferences and tried changing the file format option to TIFF to see if that would work, but same problem...LR still makes a JPG and sends that to PS.
Any thoughts on how to fix this?

It sounds to me as if you may be selecting a user-saved external editing preset rather than the built-in Edit in PS option.
PSD / TIFF / JPG are the filetype options for the former, but the latter only allows PSD / TIFF.
If so, such a preset includes a selection of file format, bit depth and colourspace that may differ from the selection seen in the upper part of the External Editing dialog. This preset may not currently appear in the lower part of this dialog either.
The lower part of this dialog is used as a workbench for managing as many editing setup options as you like. These can be named and saved as a preset, or recalled for adjustment and re-saving (update), using the "Preset:" menu.
The "Edit in PS" context menu when used within e.g. Develop, will show any named editing presets you have made below (but only if successfully auto-configured) a built-in "Edit in PS" option which is controlled by the upper part of the dialog mentioned above. The built-in option is not dependent on any user preset. One indication that LR has not properly configured itself for the presence of your PS, is if the additional options (Panorama, HDR, as Layers) do not appear when you highlight more than one image and select Edit in...
This configuration apparently can be "broken" by uninstalling an earlier version of PS, which removes some system configuration that the later PS would be relying on for its LR partnering. Or I guess there may be other causes.
IIRC, usually the answer to that, is a "repair" reinstall of PS - which LR should then properly recognise.
One comment: if PS and LR are configured as "aligned" versions, it is normal to meanwhile see the filetype of the source image file as the document window title within your PS session - even if that source file is Raw, which is not something you can in fact edit using PS. This rather misleading IMO document title, collapses down to an actual proper filename only once the document has been Saved from PS - or if you close PS without saving, no actual file is made at all.
Only then is LR's suggestion of filetype, filename and saving location (as configured in LR's external editing options) implemented for real - though if you instead select Save As, those suggestions can all be overridden by the user, and LR should still auto-import the resulting brand new file.
OTOH, if you are using any external editing preset or if ACR+LR versions are not aligned, the file you see inside PS is always one which has already been saved (and already auto-imported to LR).

I have a problem with external editing preferences where Photoshop will not launch when I choose "Edit In"...

Hi. I have a problem with external editing preferences. If I add Photoshop as an external editor, it won't launch when selected, if I add it as an additional external editor it will. Why? How can I fix this as I need to use Photoshop and another program as the additional external editor.
I use a Mac running OS X (10.8.5) and PS CS4 and LR 5.7. Any ideas on a fix? Thanks in advance.

I don't know why Photoshop won't start. However, it's possible to create external editor presets using the additional external editor tools. There are instructions on how to do this in the Lightroom help. You could assign Photoshop and create one preset, and then assign another program and create another preset.
I don't know if deleting your preferences would fix the problem or not. It can sometimes fix other problems.
Preference and other file locations in Lightroom 5

HELP - Issues with external edit in lightroom cc

Hi! I'm relatively new to lightroom and this was working but now isn't & on both of my mac computers so I'm stumped.
I have preferences set to open external edits as tiff in photoshop cc.
When I right click a jpg & choose "edit" - it doesn't matter which of the 3 options I choose lightroom creates a second jpg and opens it in photoshop... when I make changes & go to exit - it brings up a save as box.... I can either hunt for the jpg & lose my photoshop data (end photo is right obviously) or save as psd/tiff but then I have to import it back into lightroom....
I just processed a whole bunch of mixed raw/jpg photos & I swear this worked for all of them. This is a jpg not a raw but that's the only difference & I am pretty sure I had jpg's in the last bunch I edited.
So frustrated!
Attaching my external edit preference box & also a view of the file lightroom creates when I try to edit in photoshop.

I suggest trying the simplest fix first, which is to close all applications, shut down your system OS. Restart the system, reopen LR and PS, and try it again.
If the problem persists reset LR's Preferences file. Rename it 'com.adobe.Lightroom5.plist.OLD' instead of deleting the file.
How do I reset Lightroom's Preferences? - The Lightroom Queen
If still no change try resetting PS's Preferences file by renaming the same as suggested above 'Adobe Photoshop CC Prefs.psp.OLD.'
Photoshop preference
Filename
Path
General settings
Adobe Photoshop CC Prefs.psp
Users/[user name]/Library/Preferences/Adobe Photoshop CC Settings
You can easily restore both original Preferences file if the issue isn't fixed by deleting the new file and removing .OLD from the original file.

Importing jpgs instead of RAW...

I've just imported my 3rd CF card into lightroom 4. The first one had no problems but with the 2nd and third I have noticed that about 200+ photos in it starts importing the occassional jpg instead of the .CR2 file? By the end of the import it seems to be every second or thirtd file but random not consistent. I have been shooting in both RAW and JPG lately which was never a problem in LR3 - it would only ever import the RAW files in to LR - it would import the JPGs but just to the hard disk. I only noticed when editing and realising that I wasn't getting all the WB options on some of the files...
Anyone alse having this issue? any suggesitons?
Thanks

Thanks for the reply Lee
I hadn't changed the import setting at all from the default (always worked
ok in LR3). The strange thing is that it has imported all the pics in
sequence 321,322 but only some of them are JPEGs - completely random. I
checked the drive where they were imported and it has imported about 2/3
RAW and 1/3 JPEG so I checked the card to make sure something weird hadn't
happened to it and sure enough the card contains all the RAW and JPG files.
I had already started editing about a third of the files before I realised
so I did a new import using LR3 and then deleted the import from LR4 and
then did the 'find file' thingy in LR4 which still found the JPGs.. so I
moved the JPGs to another folder and did the 'find file' thingy again and
this time had to select the matching RAW file... quite time consuming but
it worked!
Just wondering if this is a bug? It didn't happen with the previous import
with all settings the same.
Thanks again

Edits to a JPG Smart Object in a layered TIFF file: DOES NOT Save to the originally placed file?

When placing a JPG as a Smart Object (and even multiples) into a layered TIFF file: If I open each layered Smart Object JPG, make changes as a JPG and SAVE the file, I expect the ORIGINAL SOURCE JPG file that was placed to also be saved- I thought that is the file I was editing!
This SUCKS! To capture my edits to the original individual files: I now have to open each layed TIF file, Edit each smart object JPG and SAVE AS to overwrite the original and capture my changes? Is this the way its always been- I don't think it has. How can I edit a Smart Object file in a layered document and ALSO update the SOURCE file?

You should edit the original jpg, and then replace the smart object. There is a utility that makes this easier, if you do many of these. Looks liek this
link_update.zip

Question about externally editing in Photoshop then saving but the files not showing up in catalog

When I am in Lightroom and I choose edit in Photoshop then I save the file, I would like the file to automatically show up in my Lightroom catalog. It shows up if I save as a tiff like I set up in my preferences, but not if I save as a jpeg. I would like for the jpegs to also show up in the catalog. Is this possible?
Thanks,
Jennifer

I found that if I do a <save> in Photoshop first (which saves a tiff or psd file, depending on the setting in Preferences), and THEN a <save as> to save as jpg, both files are automatically added to the catalog.
I do agree that if I just do a <save as>, without doing a <save> first, the <save as> file is not added to the catalog.
My workflow is good for me, because after developing a photo in LR, I then do further editing in PS, and then save the edited file as a tiff (or psd) at full pixel dimensions, with the edit layers. The next step is, if I need a jpg of that photo (for web or email), I flatten the file, reduce image size, convert to sRGB, etc., then save as a jpg. This way, I have the three files I always make/keep, and all three files end up in the LR catalog.
I agree that I could use the Export function in LR to generate the jpg instead, but 1) I'm too used to doing it right there in PS while I have the file open and 2) I can use all the tools in PS to do tweaks that the photo may need when converted to jpg.

External editing and saving

For some reason pictures that I have edited in photoshop are no longer being saved to aperture. Before when I finished editing and saved an image it automatically went to the place where it was filed in aperture before I edited it. I am sure I have changed no settings and suddenly it stopped saving properly. I don't know how to get it set up to save the way it used to. Can anybody help? I have a project due and I can't seem to get past this.
Thank you.

This is probably not going to be any help, but just in case...
Are you at any point in your Photoshop editing work saving the file with a new or revised name -- intentionally or otherwise? And then not saving to a separate Finder file from which you can subsequently import that "new" (from Aperture's perspective) image into your Aperture Library, as either a Managed or Referenced file (depending on your workflow)?
I ask only because I frequently find myself creating a whole new file from versions of images I've sent to my External Editor (i.e. Photoshop) from Aperture -- an example being when I create a Photomerge. But also sometimes I end up wanting to save two different versions of the file while still in Photoshop. For those situations, I've created a folder on my Desktop called PICS TO IMPORT, and it's to that folder that any of those new or "Saved As" PS files get sent. Then, back in Aperture, I import those new PS files, (in my case using the "Move Files" option so they are placed into the correct sub-folders in my MASTER IMAGES folder, which my Aperture Library then references).
The only thing I have to remember (and which I occasionally forget when I'm in a hurry) is to navigate to that "PICS TO IMPORT" folder in Photoshop's Save dialog BEFORE saving the new/revised file for the first time, otherwise it will be saved by Photoshop to the default location, which is deep within that MASTER IMAGES folder (wherever the files reside which Aperture used to create the original Exports for the External Editor). That means when I return to Aperture, I can't see the new PS file, since I still haven't officially imported it yet.
Whereas if I just send a jpg from Aperture to my External Editor, and simply keep saving that new .psd version "as is" in Photoshop (no changes or revisions to the file name), then every time I flip back to Aperture, all my Photoshop revisions (up to my last save in PS) are reflected in the .psd file now residing in a Stack right next to the original jpg which "gave birth" to it.
Again, I've no idea if any of this is even germane to the problem you're having, but I hope maybe it might at least spark an idea.
Good luck!
John Bertram
Toronto

Launch and edit problem from Dreamweaver to Fireworks

> This message is in MIME format. Since your mail reader
does not understand
this format, some or all of this message may not be legible.
--B_3266405159_588474
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
Hi
Not sure if this is a Fireworks or Dreamweaver problem but
here goes.
I¹ve created a graphic in Fireworks CS3 on the Mac and
Exported the HTML and
related images. I open the HTML file in Dreamweaver CS3, all
fine so far.
Then I highlight the table and click the Edit in
Fireworks¹ button and it
throws up a warning dialogue saying Cannot launch and
edit. The Fireworks
table could not be found in the HTML. Please export from
Fireworks and
re-import the HTML into Dreamweaver.¹
What?!!
I¹ve only just exported it from Fireworks! It¹s
even got the Fireworks table
code in the Code section, so what¹s going here?
Has anyone else had this?
Gaz
--B_3266405159_588474
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Launch and edit problem from Dreamweaver to
Fireworks</TITLE>
</HEAD>
<BODY>
Hi<BR=
>
Not sure if this is a Fireworks or Dreamweaver problem but
here goes. 
I’ve created a graphic in Fireworks CS3 on the Mac
and Exported the H=
TML and related images. I open the HTML file in Dreamweaver
CS3, all fine so=
far. Then I highlight the table and click the
‘Edit in Fireworks&#821=
7; button and it throws up a warning dialogue saying
‘Cannot launch an=
d edit. The Fireworks table could not be found in the HTML.
Please export fr=
om Fireworks and re-import the HTML into
Dreamweaver.’ 
What?!! 
I’ve only just exported it from Fireworks!
It’s even got the Fi=
reworks table code in the Code section, so what’s
going here? 
 
Has anyone else had this? 
 
Gaz
</BODY>
</HTML>
--B_3266405159_588474--

> This message is in MIME format. Since your mail reader
does not understand
this format, some or all of this message may not be legible.
--B_3266407908_747577
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
When you export the sliced graphics from Fireworks it places
them into a
table. In my instance the code says...

So it recognises Fireworks was the the graphics app and jumps
back to it
when you want to edit the image. Fireworks then displays (or
should) a
Done¹ button over the window. You do your alts and
press Done to update the
HTML and graphics back in Dreamweaver automatically.
That¹s the only table I was referring to Murray.
On 4/7/07 3:02 pm, in article
[email protected], "Murray
*ACE*" <[email protected]> wrote:
> Why would you be wanting to edit the table in a graphics
editor, instead of
> an HTML editor?
--B_3266407908_747577
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: Launch and edit problem from Dreamweaver to
Fireworks</TITLE>
</HEAD>
<BODY>
When =
you export the sliced graphics from Fireworks it places them
into a table. I=
n my instance the code says... 
 
 
 
So it recognises Fireworks was the the graphics app and jumps
back to it wh=
en you want to edit the image. Fireworks then displays (or
should) a ‘=
Done’ button over the window. You do your alts and
press Done to updat=
e the HTML and graphics back in Dreamweaver
automatically. 
That’s the only table I was referring to
Murray. 
 
On 4/7/07 3:02 pm, in article
[email protected], "Murr=
ay *ACE*"
<[email protected]> wrote: 
 
> Why would you be
wanting to edit the table in a =
graphics editor, instead of 
> an HTML editor? 

</BODY>
</HTML>
--B_3266407908_747577--

10.4.4 fixes EXIF in externally edited images!

After applying the 10.4.4 update, files opened in Photoshop from Aperture seem to retain all EXIF - at any rate they had key things like lens focal length and shutter speed.
Keywords now also show up in Photoshop as well.
The exif bug on exported TIFF's is still there - some EXIF data (but not all) gets removed. Now that externally editing files no longer drops metadata thugh, all JPG output has all the EXIF data included.
So I wonder what else was fixed. It's funny, we all seemed to be expecting RAW improvements but got Aperture patches instead. No complaints here as the EXIF bug fix will make a lot of people happy.

<...>
I believe he also said that
you can now export a new master to Photoshop and it
will still maintain the EXIF data you plug in while
in Aperture vis a vis Photo Mechanic.
You meant open a version for external editing, right? I just like to keep terms clear...
Anyway, it's true enough that keywords I entered in APerture show up in Phtooshop as well, very nice. One thing that would be kind of nice is for Aperture to take any EXIF updates back into itself - so if for some crazy reason I entered a new keyword in Photoshop or edited EXIF it would be nice if Aperture picked that up on return. I know it doesn't read new keywords, I had not tried altering EXIF data.
I am also pleased to hear verification that RAW updates are still coming, I figured they just were not included for some reason.

Externally edited Photoshop files are huge when saved back into Aperture 3

I start with an 8MB JPEG photo. I externally edit it in Photoshop Elements 6, and hit "Save". The edited image is saved back into Aperture, but it's now 34MB PSD. Ouch! My hard disk is big but this is over the top. The intent of me moving to Aperture from iPhoto had been to reduce file sizes (masters and versions), not to hugely increase them.
If I use "Save As" and convert it to a JPEG, the saved edited photo vanishes--it isn't in Aperture. I can't find it. If it is saved in some unknown location it is taking up hard disk space uselessly.
Can you help me do this better? I would be most grateful.
Message was edited by: shep222

shep222 wrote:>...even if I do zero Photoshop editing I still get this >3 times increase in file size.
Yup. That is how big such files are when not compressed and image data has not been discarded.
It's an Aperture vs. iPhoto thing: When I did Photoshop External Editing in iPhoto (before I switched to Aperture) the original JPEG stays a JPEG when exported to Photoshop. The file size problem does not occur in iPhoto.
That is correct, and is why few if any pros use iPhoto. iPhoto is by definition +low end,+ dumping image files into lossy JPEG by default. A RAW file imported into iPhoto is saved in JPEG unless the user takes special action to export it as TIFF or PSD.
Aperture won't allow it--it seems to insist on converting to PSD for external editing.
Also correct. Aperture is a professional app, and intentionally and repeatedly discarding image data would not be professional workflow.
My JPEG's are top-notch low-compression ones, using the least compression settings in my Olympus micro-4/3 camera (super fine, large image, with 1/2.7 compression). JPEG artefacts have not been an issue even after extensive Photoshop editing.
Agreed, top quality JPEGs can be very useful even though image information has been discarded. Back when RAW DSLR capture was unusably slow I shot many full-page magazine ads using JPEG Fine. But once the (fast) Nikon D2x came out I have always captured RAW and would no way ever again consider far inferior JPEG-only capture.
Perhaps Aperture is not for me, if we can't overcome this issue.
Perhaps. However IMO a far better approach is to shoot RAW and embrace a professional lossless workflow using Aperture. Mass storage is cheap and the benefits of RAW capture are very significant.
Already my Aperture Library is 70GB and I have barely started with it.
The issue of huge Library is due to using a Managed-Masters Library. Switch to RAW capture and a Referenced-Masters Library with the Library on an internal drive and the Masters referenced on external drives and the Library will no longer grow ridiculously large. IMO discarding image data via JPEG compression just to save hard drive space is inappropriate in 2011.
HTH
-Allen Wicks

[LR 5.5 Bug] External Editing settings

Hi,
When modifying an entry in the External Editing tab, changing the resolution or the compression mode (for TIFF files) is not always enough to mark that entry as "updated". I couldn't find a pattern. So you cannot update the entry with the new settings. And since it is not possible to save an updated entry under the same name, you're stuck.

When you say that the file type was not recognized, what file type does Windows think these photos are?
Has the drive changed letters in Windows recently? What drive letter did you normally use for this drive? Is the drive letter in Windows the same or different?
In Lightroom, go to "All Photographs" and turn off filters (Ctrl-L once or twice). Then, look in Lightroom for the photos that are on this external drive, are they shown in the grid? If you scroll up and down, can you find them?
One guess is to close Lightroom, delete your preferences file, and then restart Lightroom. See if that fixes the problem. If not, I would like to see a screen capture of your Lightroom Folders panel and also a screen capture of whne you double-click on "Computer" in Windows 7.

Aperture 3.5 + Mavericks external storage problems

Aperture 3.5 + Mavericks external storage problems
After upgrading to 3.5 and Mavericks, all my projects referencing files stored on NAS show blurry or black and not responding to edit commands. Sometimes Aperture crashes. The projects/photos were okay before upgrade. Also new projects on NAS show blurry or black or fail totally to import photos. If I move the same photos to the local drive, everything is just fine.
I am using NFS to access the NAS.
Reading through this forum I found some reports of similar behavior from people storing photos on USB external drives.
This seems to be only when referencing files located on an external drive. No problems if files are copied to the Aperture library.
Any similar experience?

Referenced files on a NAS was always an gray area. While it worked for most users most of the time it wasn;t clear that Apple supported the configuration.
The Apple documents on Aperture and non-locally attached drives can be read in a number of different ways. Of course the library definitely had to be on a local drive (and even here some users reported success with the library on a NAS) but referenced masters were never explicitly mentioned either way.
Most users had success with the originals on a NAS but even with earlier version of Aperture and the OS there were always the occasional report of problems. When push-came-to -shove if moving the referenced originals to a local drive fixed the problems there wasn;t much else that could be done.
Since the release of 3.5 and Mavericks it does appear that referenced originals on a NAS do not work at all in most cases. The best we can do here, being just users like yourself, is to suggest you contact Apple and try to get through to the Aperture team and see if you can get a definitive answer.
As for problems with referenced originals on locally connected drives, I'm not aware of any widespread problems. In the few cases I've seen it has come down to some issue with the OP's system.
Having your whole workflow and setup knocked out from under you like this is really bad, unfortunately there isn't much anyone here can do for this problem.
regards

Photos does not support external editing like iPhoto. Is there likely to be an upgrade to change this or will I abandon Photos for software that does support editing in Photoshop?

Photos does not support external editing like iPhoto. Is there likely to be an upgrade to change this or will I abandon Photos for software that does support editing in Photoshop?

iPhoto does work and there is an upgrade:
Go to the App Store and check out the Purchases List. If iPhoto is there then it will be v9.6.1
If it is there, then drag your existing iPhoto app (not the library, just the app) to the trash
Install the App from the App Store.
Sometimes iPhoto is not visible on the Purchases List. it may be hidden. See this article for details on how to unhide it.
http://support.apple.com/kb/HT4928
One question often asked: Will I lose my Photos if I reinstall?
iPhoto the application and the iPhoto Library are two different parts of the iPhoto programme. So, reinstalling the app should not affect the Library. BUT you should always have a back up before doing this kind of work. Always.

Custom Camera Profile Disables External Editing?

I'm using Lightroom 5 and Photoshop CS5. The problem is that if I apply a custom camera color profile created by X-Rite Passport Color Checker, I can no longer use an external editor, such as Photoshop, to edit my photos. Before I apply the custom profile, the external editor function works just fine. If I apply a custom profile in the Camera Calibration panel, then the ability to use external editors no longer works. There is no error message, but nothing happens when I try to edit in an external editor. If I go back and turn off the custom profile and go back to Adobe Standard, then the external editor function works again. What is going on? Is there a way to make it possible to apply a custom profile in Camera Calibration and still be able to use the external editors?

A suggestion: it sometimes happens that the main "edit in PS" function gets.. a bit confused. I agree with the other posters that it's critical which program is to render your image to an editable state (ACR, or LR)... which also means, whether PS is going to simply open up an already-saved file from disk, or be passed instructions to have ACR make it an unsaved image in memory.
Perhaps there is some issue with ACR seeing the folder where Passport is saving its special camera colour profiles via LR - the more standard ones are located in a structure shared by both programs, the same as with lens profiles. This will only be a difficulty, if it is ACR which is trying to do the job of rendering the image.
Just to clarify: normally when we say LR version such-and-such is compatible with ACR version such-and-such, we are assuming that the latest available Process Version is being used within Lightroom. For any individual image which happens to be set to an earlier Process Version, the compatibility with ACR operates, as if an earlier version of LR was being used. So (for example) one image using PV 2012 would get necessarily rendered by LR when you selected "Edit in PS" with PS CS5, because that is known not to support PV2012. But another image using PV2010 might get sent directly to CS5's ACR within the same setup (provided not earlier than 6.7), without giving the option, since that version of ACR IS known to support that generation of image adjustments.
To troubleshoot whether external editing is or is not possible, it can be helpful to set up Photoshop manually as a LR external editing preset (I find this useful anyway). This is done within the lower, "additional" part of the External editing tab in LR Preferences. By browsing direct to the Photoshop executable, you can specify whether 32-bit or 64-bit, also set up the bitdepth and colourspace, and explicity name that. When this name is then selected against an image from the "Edit in..." context menu, it is definitely Lightroom that renders the image - you can be sure that ACR is not involved.
If Lightroom cannot render an image under such an external editing preset, save it to disk / add a new imported image version, and have PS open that, when a {Passport profile is selected - but those things can happen when (say) Adobe Standard is selected, then AFAICT that narrows down on LR's ability to use the profile which Passport has made. I'd still have expected some kind of a warning message.
Even if PS was for some reason unable to open the image, but LR had definitely been the one told to render it - I would not expect to have "nothing" happen. I would expect to see a new image version in LR stacked with the original - named (by default) either [Imagename]-edit.tiff or [imagename]-edit.psd - which looked exactly the same as the current LR edits, only hard-rendered into a flat pixel file.
regards, RP

External Edit problem - always JPG instead of TIF/PSD

Similar Messages

Maybe you are looking for