Does lightroom 5.3 use elements 4.0 editor

i have been running Elements 4.0 under Windows 7. Elements 4.0 stopped working. i installed a trial version of Lightroom 5.3 and when i launch LR 5.3 and attempt edit a picture the Elements 4.0 editor screen appears. Is this to be expected and does this mean LR 5.3 upon purchase will continue to use the Elements 4.0 editor?

when i launch LR 5.3 and attempt edit a picture the Elements 4.0 editor screen appears
What are the exact steps in Lightroom that you tried here? Please tell us the exact name of the menu commands or buttons pressed

Similar Messages

Does Lightroom work with Photoshop Elements

Does Lightroom work with Photoshop Elements?

When setting up the editor in the prefs choose images of 8 bits not 16 bits, either PSD or tiff. Elements works best with 8 bit images. For example you can't use layers with 16 bit images.
Once you have set up the LR prefs you are ready to make the round trip:
1) Ctrl+E in the Library to export selected image with develop settings or right-click and choose Open In Photoshop Elements Editor
2) Make your adjustments in Photoshop Elements; then Ctrl+S to replace (overwrite) Lightroom export copy
3) Ctrl+W to close in Photoshop Elements and update Lightroom thumbnail.
On Mac OSX Cmd+E; Cmd+S; Cmd+W
The important point is to overwrite the LR export copy by using File >> Save (Ctlr+S) because a tiff or PSD file has been automatically rendered by LR based upon your preference setting for External Editing. If you use “Save As” you create a new document which LR knows nothing about. It will only show in the LR Library if you save.

Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
Michael

Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings..

Why does Lightroom 4.3 use very high cpu when waiting for user to click OK?

I saved metadata for 52 photos.
Lightroom 4.3 couldn't save metadata for 2 of the photos and opened a window to tell me so. (It had no problem saving metadata on second attempt.)
While it waited for my response and wasn't doing any work, it was using over 50% of my CPU.
Why?
Windows 7 is 32-bit Professional.
Processor: Intel Core i5 750 Processor 2.66 GHz
Here's my system info as reported by Lightroom.
Lightroom version: 4.3 [865747]
Operating system: Windows 7 Business Edition
Version: 6.1 [7601]
Application architecture: x86
System architecture: x86
Logical processor count: 4
Processor speed: 2.7 GHz
Built-in memory: 3579.4 MB
Real memory available to Lightroom: 716.8 MB
Real memory used by Lightroom: 710.9 MB (99.1%)
Virtual memory used by Lightroom: 847.9 MB
Memory cache size: 2.0 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
Library Path: D:\Users\Calvin\Pictures\My Lightroom\lightroom\lightroom4\lightroom4.lrcat
Settings Folder: C:\Users\Calvin\AppData\Roaming\Adobe\Lightroom
Adapter #1: Vendor : 10de
    Device : 640
    Subsystem : c9593842
    Revision : a1
    Video Memory : 1007
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 8192
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 8192,8192
GL_RED_BITS: 8
GL_RENDERER: GeForce 9500 GT/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 3.30 NVIDIA via Cg compiler
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 3.3.0
OGLEnabled: true
OGLPresent: true
GL_EXTENSIONS: GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

I don't think so.
I have enough experience with LR to know what to expect for various activities.
Previews for all photos had been rendered long before I initiated the Save Metadata.
Metadata for 50 of the 52 files had already been written.
The high cpu had gone on for at least 5 minutes.   I switched to another app imediately after initiating the Save Metadata for the 52 files and only went back to LR when I heard my CPU fan running for a long time.
When I got back to LR, I saw the "Could not save metadata" window. I clicked "Show in Library" and OK. As soon as I did that, CPU usage went back to normal.
I've experienced the exact same scenario, where LR can't save metadata for all photos and I've never had LR get stuck consuming a very large amount of CPU.
As a test, I selected 118 other photos, changed metadata for all of them and then selected all and saved metadata. LR took about 20 seconds to save metadata for all 118 and LR CPU usage never went above 17%. The difference is that LR did not show the "Could not save metadata" window.

I am an amateur, just now doing digital SLR. Have used simple Sony Cybershot editing but need better software. Recommendations please--Adobe Lightroom 5 vs Photoshop Elements 12 (or other)? Thanks!

I am an amateur, just now doing digital SLR. Have used simple Sony Cybershot editing but need better software. Recommendations please--Adobe Lightroom 5 vs Photoshop Elements 12 (or other)? Thanks!

Download the trial versions and then you will have a better idea what you need.

How can I use Elements as Edit in using a Lightroom?

How can I use Elements as Edit in in Lightroom using a Lightroom picture. I followed instructions: Photo/Add in/ and received in Elements a blanco screen instead of the picture selected in Lightroom. Please further instructions before ordering Elements 11.

Dear Andaleeb,
I have followed instructions as follows: In Lightroom I have installed Elements under extra plug inns. (on top of the screen reference is made to Photoshop and not Photoshop 11). Under photo, cmd-e does not work since Photoshop is colored gray. As I have Elements installed under extra plug-inns this is highlighted. BUT………..Clicking that, the picture selected does NOT appear in Elements. The screen remains being empty! How can I solve this?
Mr. F.K.A. de Haan
Op 4 mrt. 2013, om 14:50 heeft andaleebfatima1 <[email protected]> het volgende geschreven:
Re: How do I use Elements as a plug in for Lightroom? After plugging no picture appears in Elements!
created by andaleebfatima1 in Photoshop Elements - View the full discussion
Please ensure that you have added PSE Editor as external editor for Lightroom. See : http://www.photoshopelementsuser.com/html/integrate-lightroom-with-ele ments/
Thanks
Andaleeb
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5119785#5119785
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5119785#5119785
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5119785#5119785. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Elements by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Using Lightroom in Conjunction with Elements

I currently use Elements 10 (and love it) and am considering purchasing Lightroom 5. However it seems like the lines between some of the Adobe products is getting blurred. Photoshop Elements seems to be getting more of the capabilities of Photoshop CS. And from what I've read and looked at on Lightroom, it doesn't seem like it really can do anything that Elements cannot do, other than do some functions easier, one example being straightening.
First question: If I have both Elements and Lightroom, can someone give me one or more practical (and not overly complex) examples of using both together on a single photo? Please don't include functions that are available in both pieces of software, unless it gives superior results that can be obtained by one but not the other.
Second question: I don't use raw (yet), so if editing a jpg with both Elements and Lightroom, doesn't it have to be saved in one before editing in the other? Or is there some type of interface that is available between the two pieces of software where you can edit first in one and then in the other without saving in between? Obviously I am asking because I am aware of the loss of info due to compression when doing multiple saves and opens on a jpg. Yes, saving at level 12 might minimize it but there would still be loss of info*.
* Now that I finished the question, I think I know the answer. If editing first with Elements, save it as a psd rather than a jpg, then open the psd in Lightroom (is psd a common extension in both?), make the additional mods, and save it as a jpg. This way there is only one save of the jpg. Does that work?
Thanks.

However it seems like the lines between some of the Adobe products is getting blurred.
Seems like? No, the capabilities of these two programs definitely overlap.
And from what I've read and looked at on Lightroom, it doesn't seem like it really can do anything that Elements cannot do, other than do some functions easier, one example being straightening.
Things like layers and magic extraction tool and a whole bunch of other PSE editor tools are not available in Lightroom.
First question: If I have both Elements and Lightroom, can someone give me one or more practical (and not overly complex) examples of using both together on a single photo? Please don't include functions that are available in both pieces of software, unless it gives superior results that can be obtained by one but not the other.
In my opinion, the only sensible workflow is as follows: import into Lightroom, organize in Lightroom, edit in Lightroom (do as much editing in Lightroom as possible) and then transfer the photo to PSE for additional editing that cannot be performed into Lightroom; return edited photo from PSE to Lightroom. I point out that many people find that the editing in Lightroom is powerful enough so that only a small percent of their photos need the additional editing of PSE.
Second question: I don't use raw (yet), so if editing a jpg with both Elements and Lightroom, doesn't it have to be saved in one before editing in the other?
None of the capabilities of Lightroom are limited to RAW photos. After you edit a photo In LR and want to send it to PSE, the built in LR function called "Edit In..." will make the copy for Elements to use, launch PSE (if it is not already opened) and allow you to do your edits. Then you save the edited photo (not Save As...) and Lightroom will recognize the changes made in PSE.
Obviously I am asking because I am aware of the loss of info due to compression when doing multiple saves and opens on a jpg. Yes, saving at level 12 might minimize it but there would still be loss of info*.
In the process I described, there are two such saves (one by LR and one by PSE). You could eliminate the quality loss (at the expense of much larger files) by telling LR to create a TIF instead of a JPG for editing in PSE.

How do you use Elements 10 as plugin for Lightroom 4

Have been trying to use Elements 10 as plugin for Llightroom 4.2. When I try to use prefences it can not find Elements 10. What am I doing wrong. It only shows videos of Mac not Pc

On a windows system it would better to link to the PhotoshopElementsEditor.exe in
C:\Program Files (x86)\Adobe\Photoshop Elements 10 (64 bit system)
C:\Program Files\Adobe\Photoshop Elements 10 (32 bit system)
In Lightroom: Edit>Preferences>External Editing

Question from PSE user: does Lightroom offer a better tagging workflow than Elements?

I would just like to piggyback onto this question, rather than start a new thread.
I have been a user of Elements since before it was called Elements. But I have grown increasingly dissatisfied with the product over the last couple years as it has not improved any in its organizational features.
My primary usage is for organizing. I tag all my photos so that I can search and find things easily. I have 2 main problems with the Elements workflow. #1 is simply that the application takes a long time to launch and become responsive. Sometimes it takes 30 seconds before any of the UI will respond to clicks. Yes, I have a lot of photos, (~20,000) But I don't know if Lightroom may be more powerful or more efficient in that regard.
#2 is the primary problem. Tagging takes forever. I have so many tags that there is a long list that runs off the screen. If I am tagging a series of shots that have different combinations of people in them, and those tags are spread out in my list, it takes forever to tag, select, tag more, scroll around to select and unselect tags, tag some more, repeat the process. It's excruciating. I've left feedback for Adobe several times through the years that they should add a recently used tags window where recently used tags will float to the top so that they are always available without having to scroll around to get to them. But they have not improved the tagging workflow one bit over the years.
So the question boils down to, does Lightroom do a better job in the tagging workflow? Is what I described easier in LR? I'm sure that I will download a trial to check it out, but i just wanted to know if an experienced user has thoughts on that.
Thanks

I don't have a weak machine, I'm running with 8GB of RAM and an SSD for my applications drive, although the catalog is on a regular hard drive that I use as the data drive.
This is most likely irrelevant to your Elements speed issues. Repairing or optimizing the catalog file may help
I'm not sure how a hierarchy will help with the tags, as I already have them arranged in groups of family and groups of friends. The problem is that you get events with a lot of people from different groups and there's no way to avoid having to hunt all up and down the list. You can't really predict what grouping of people will apply. That's why I've really been hoping for a recently used tag list...that would be sooo perfect.
Yes, but the ability to search for keywords and type a few letters in and see related keywords will help.
So if you have just tagged a photo with the Anderson Jones keyword (because someone in the photo was named Anderson Jones), and now you need to also tag the same photo with the William Barber keyword (because someone in the photo was named William Barber), you don't really need to scroll, you just need to type in a few letters of William and then select the proper keyword from a much shorter list.

Lightroom does not open photoshop using "Edit in adobe photoshop CC-" command.

I updated lightroom and photoshop using the CC desktop. (LR V5.3 x64, PS V14.6.2 x64) This broke the “Edit in adobe photoshop CC…” command.
Based on advice from this forum, I unistalled both programs completely and reinstalled them. The
“Edit in adobe photoshop CC…” command is still broken.
Is there a way to fix this? I use this feature frequently.

In reply to DdeGannes:
What’s broken? -- The “Edit in adobe photoshop CC…” command does not open photoshop and the file as it did before the upgrade.
Is the "edit in function" not available? -- It is visible in the edit it menu.
Was it working before? Yes.
What happens if you click? - Nothing.
Do you get an error message? - No.

What is best for me. I have been using Elements for many years (since Elements 2) and now want to but either 13 or Lightroom. Can anyone help me decide

I have been using Elements for many years (since elements 2) and now want to upgrade. I am reasonably old and at this stage do not understand Creative Cloud. Am I best to upgrade to Elements 13 or try Light room 5?

Do you want to make a one time purchase (Photoshop Elements) or pay monthly rent ($9.99 per month for Photoshop and Lightroom)
Do be aware that the subscription model is just like rent... stop paying and the programs stop working... but you get the full Photoshop

I'm switching from PC to Mac. I'm using my one time switch for Lightroom. I have elements 7. Can I upgrade or do I née to just buy outright?

I'm switching from PC to Mac. I'm using my one time switch for Lightroom. I have elements 7. Can I upgrade or do I née to just buy outright?

If you use the organizer, you need to buy the boxed version of PSE 12. You can usually find it at big box stores and online retailers for less than adobe's upgrade price, if you shop around. You need the boxed version because you get a serial number that works on both platforms, and you will need to install PSE 12 in windows first, upgrade your catalog, then make a full backup to a removable drive and restore from that to the mac, after installing PSE 12 there.
If you don't use organizer, it doesn't matter.

I use "element 12" and want like in the old PS version due Automating and Contact II upload multiple filesand print them with any columns and rows on the same page . How does it work?

I use "element 12" and want like in the old PS version due Automating and Contact II upload multiple filesand print them with any columns and rows on the same page . How does it work?

Can you supply a link?

I don't know what to order. I want PS for photo editing and some composting. I don't do any website work or sharing yet. I have been using elements for a few years and also have Lightroom 5 on my desktop. I don't want to spend $1000s for a bunch of stuff

I don't know what to order. I want PS for photo editing and some composting. I don't do any website work or sharing yet. I have been using elements for a few years and also have Lightroom 5 on my desktop. I don't want to spend $1000s for a bunch of stuff I don't use. Any advice on what to buy?

Well, there is a whole world of free or affordable software out there like GIMP, PDPaint and similar. Otherwise if you want to stick with Adobe stuff signing up for the CC photography program would be the most cost-efficient way...
Mylenium

When I try to print a 4X6 photo using Elements 12 it prints out 2X3. Does anyone know how you can get hold a live person at Adobe?

When attempting to print a 4X6 photo using Elements 12 it prints out 2X3. Does anyone know how you can get hold of a live person at Adobe?

I've never done a forum and am not exactly sure what to do from here.   I
know how to do a screen shot on my phone, but not on my computer.
I'm about ready to throw every adobe product I have out the window!   If
you purchase a product you should be able to get support from the company.
In a message dated 4/6/2015 3:04:02 P.M. US Mountain Standard Time,
[email protected] writes:
When I try to print a 4X6 photo using Elements 12 it prints out 2X3.
Does anyone know how you can get hold a live person at Adobe?
created by Peru Bob (https://forums.adobe.com/people/Peru+Bob) in
Photoshop Elements - View the full discussion
(https://forums.adobe.com/message/7412463#7412463)

Does lightroom 5.3 use elements 4.0 editor

Similar Messages

Maybe you are looking for