Problem external editing

I have ps elements 11 and have just bought lightroom4 updated it after install to 4.3 , files when click on photo edit in photoshop elements do not open, photoshop elements opens but no file

I have figured out what was wrong with my installation. In case anyone else has this problem and is searching for an answer I would like to explain what I did wrong:
When choosing external editor, I picked photoshop elements 11 but what I had actually selected was the shortcut programme launcher, in consequence the programme launched but not the file.
In choosing external editor what must be picked is photoshop elements 11 editor. this (on a mac) is found in - applications > Adobe photoshop 11 > support files.
inside the support files is the icon for elements11 editor which you must choose and not, as I did, the main adobe elements 11 icon in the applications folder.
Hope this saves somebody the hours I spent floundering around seaching for a solution.

Similar Messages

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

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.

Problem with Edit IN function between LR 2.3 and PS CS3

I recently upgraded my system to a Windows Vista 64 bit Core 2 Quad with 8 GB. Lightroom now works and loads images the way it should. I do have one major concern and need any help possible.
I am using LR 2.3 in 64 bit and PS CS3 ver 10.0.1 (which is 32 bit - loads slowly but otherwise works fine). The problem I am encountering is in LR Develop / Photo / Edit In... - using any of the menu items:
"Edit in Abode Photoshop CS3"
"Open as Smart Object In Photoshop"
"Merge to Panorama in Photoshop"
"Merge to HDR in Photoshop"
"Open as layers in Photoshop"
Photoshop opens but no image(s) are exported and I receive the message in LR - "The file could not be edited because Adobe Photoshop CS3 could not be launched."
Photoshop, however, was launched but no image exported and so I can't work on the image in PS. The appropriate TIFF image is created in LR for the first two menu items - nothing for the last three menu items.
I can create a partial work around by setting PS as an external editor, however, I can't use 4 of 5 of the menu items.
All the menu items work fine in Windows XPpro.
Any help is much appreciated.
PS I also tried the most recent Window 7 RC with exactly the same results.
Thanks
Bob

Don
I wasn't shouting - I just cut and paste the exact text and font in its original size and type as was shown in the message. Never had a thought that someone would be offended by cutting and pasting exactly what was in a message - it would appear that John Williams saw it for what it was.
However, sorry if I offended you.
Bob
Date: Mon, 1 Jun 2009 19:15:15 -0600
From: [email protected]
To: [email protected]
Subject: Problem with Edit IN function between LR 2.3 and PS CS3
There is no reason to shout. There are only other users here trying to help.
>

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

Problem with "Edit in Photoshop" and Lightroom 2.1 failing to import new file

I am a new user to Lightroom, so I won't be surprised if the problem is at the dull end of the keyboard...
I am working with Lightroom 2.1 (still in my 30-day free trial), Photoshop CS3 with ACR 4.6, on Windows XP (fully updated). My image files are mostly .cr2 files (canon raw).
When I "edit with photoshop" in Lightroom, it fires up Photoshop and brings the file up for edit as expected. Photoshop shows the file name as something like _MG_2326.CR2, as (I presume) expected. When I'm done editing in Photoshop, and I save the file, Lightroom brings up a message "The file could not be imported because it could not be read." and "It may be an incompatible format." on a second line.
If I synchronize the folder in Lightroom it picks up the save file without issue (though its not automatically stacked with the original).
I have tried messing around with the different options in the preferences "external editing" tab -- file format, color space and bit depth (I can't imagine resolution would matter). No joy there.
I have also tried setting photoshop up as the additional external editor and if I do that it works correctly. However, in this case, it makes a copy of the file before opening photoshop which slows things down a little.
Is this a problem that anybody else has seen before? Any solutions or work-arounds?
Thanks,
Doug

I'm back trying to sort this problem out (got distracted for a couple of days by trying to get my monitor calibrated).
Rearranging the folder structure didn't help. But I now have a better organized catalog, so that's ok :)
What I did find is that if I import files into lightroom using the "file/import photos from device", then I can edit them normally afterwards (that is, when I save the file in photoshop cs3, the new file gets picked up correctly by lightroom and gets correctly stacked with the original). This is true even if the new files get added into the same directory structure that I'm having troubles with.
So it looks like the directory structure is a red herring. It looks like the problem is in the catalog, with the way that lightroom originally imported my files. I created my original catalog by allowing lightroom to read my elements 6 catalog.
It seems that I have this edit problem with all catalog entries that were imported from elements 6, but I don't have any problem with catalog entries that lightroom brings in directly (either through "import photos from device" or by adding a new folder to the lightroom catalog).
So right now it looks like there is a problem with the elements catalog conversion.
Is this a problem that anybody else has seen? Any suggestions for getting around it?
Doug

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.

External edit (TIFF) and metadata

For some weeks (I guess since I'm using Max OS X Lion or since I'm using LR 3.6) I got a problem with all external edited photos after the external changes are imported into Lightroom.
If I make any changes on metadata (or editing the photo in develop module) after I've edited a photo in an external editor (in this case it is Nik Silver Efex Pro 2) Lightroom can't write metadata anymore.
The original files are DNGs created from Leica M9 DNGs (uncompressed) by Lightroom 3.6 on import and I use TIFF-copies for external editing in SEP2.
To be completely clear, here's my workflow:
import as DNG
basic edits in LR develop module
right-click > edit in > SEP2
use copy with LR-changes: TIFF, 240dpi, ProPhoto RGB, ZIP-compession
convert to black and white in SEP2
save and go back to LR
change metadata or sometimes make some further adjustments in LR develop module
>>> warning sign on photo (grid view)!
If I then re-import the metadata from the file all changes in Lightroom after the external editing are gone. Saving the metadata again doesn't work and changes nothing.
Does anybody know if that's a bug (in LR, Lion or SEP2) or if I can do anything to prevent that problem in future?

Sorry I should have been clear - I am referring to IPTC metadata.

How to change in External Editing from Edit in CS4 to CS5?

In LR 3.2 (was also in 3.0) Preferences/External Editing it says in the top position "Edit in Adobe Photoshop CS4" even after reinstalling LR 3.2.
Originally I had installed CS4 and LR 2.7, then I installed CS5 and LR 3.0 but the top position remained with edit in PS CS4. Then I added CS5 as an additional external editor in the Preferences/External Editor, so far ok.
The problem: If I want to "Merge to HDR in PS" it goes to CS4 and not to CS5. I assume that it would go to CS5 if CS5 would be in the top position but I can't find out how I could change the top position from CS4 to CS5. Any hint would be appreciated as long as it does not say to reinstall CS5 and LR3.

It's a common problem. You'll need to reinstall CS5 as the Lr is getting the wrong key.

External editing with Elements 6

When attempting to externally edit from Lightroom 2.3 to Elements 6 for Mac, the file does not automatically open in Elements as it used to do when I edited in CS2. I find that I have to export the file from Lightroom, open the file in Elements and then import the file back into Lightroom once the edit is complete. This seems extremely long winded and I feel I am missing something.
Can anyone help please.
Dave

I have almost the same problem. I have been externally editing in PSE5 as my primary. A few days ago, I installed the PSE7 trial. Since you can't run two PSEs at the same time, LR defaulted to opening in PSE7. PSE7 was causing me too many problems, so I uninstalled it thinking it would just default back to PSE5. Now the PS (not found) showed up in my primary external editor. Even after uninstalling PSE7 I checked under the the Adobe folder, and it still showed it there. Had to manually delete it from there. Still didn't work. So I tried doing a system restore back prior to PSE7 being downloaded. Still shows the Photoshop (not found) in the primary editor spot. I, too, can edit in PSE5 independently, save, and then import back into LR for further work, but that defeats the whole purpose of being able to externally edit in PSE from within LR.
Has anyone found the solution to this yet? I'm desperate! This all happened in the middle of trying to finish processing a wedding. Can use all the help I can get right now.
Thanks!

External editing does not work in LR4 (??)

external editing does not work in LR4 (updated from LR3 a few days ago)
has anyone an idea to solve this problem?
Thank you.
Regards
Priska

priskaleutenegger wrote:
no ..
when I send the RAW Document for external editing (Elements 10) nothing happens at all ... zero :-(
a friend of mine has the same problem - also updated from LR3 to LR4, external editor: elements 10
Which process version is the image you're trying to edit externally?
You right-click (I'm assuming PC, can't help Macs), there should be a context menu option "Edit in". You choose that, and there's an option for Elements 10 or not?
If so, what happens when you select it? Do you get any further message?
If not, you may have to go to Edit menu, preferences, External Editing tab and create a preset for Elements. In the "Additional External Editor" area, click "Choose" and navigate to wherever Elements is on your machine and you can create a new external editor.

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.

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.

Problem with 'Edit Locally' command -- Due to IISProxy?

Hi,
We have a problem with 'Edit Locally' command since we are using Windows Authentication. Our architecture is:
SAP EP 6.0 SP2 Patch 28 (Solaris)
IIS Proxy (Windows 2003)
The situation is:
If we access to SAP Portal using old url (directly to Solaris) using form-based authentication we do not have any problem with 'edit locally' command.
However, if we access to SAP Portal using IISProxy and Windows Authentication we get an 'Operation failed' error message.
     Java plug-in console shows the following message:
cargar: clase com/sapportals/wcm/app/docapplet/DocApplet.class no encontrada.
java.lang.ClassNotFoundException: com.sapportals.wcm.app.docapplet.DocApplet.class
     at sun.applet.AppletClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.applet.AppletClassLoader.loadCode(Unknown Source)
     at sun.applet.AppletPanel.createApplet(Unknown Source)
     at sun.plugin.AppletViewer.createApplet(Unknown Source)
     at sun.applet.AppletPanel.runLoader(Unknown Source)
     at sun.applet.AppletPanel.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed.
     at sun.applet.AppletClassLoader.getBytes(Unknown Source)
     at sun.applet.AppletClassLoader.access$100(Unknown Source)
     at sun.applet.AppletClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     ... 10 more
Where is the problem? Is due to authentication method? SAP Portal or IISProxy configuration?
Thanks,

Thanks for your comment,
Now, we have tested with version 1.5.0_01 plugin version but the result is the same: 'Operation failed'
This is a very important topic to solve before installing Windows Authentication in a productive environment.
Has anybody any solution?
Damiá

Problem external editing

Similar Messages

Maybe you are looking for