My Lightroom Observations

Okay, I have been going back and forth with Lightroom... I love it, I hate it, I love it... you get the point. Anyway, as I have stated in the past, I want Lightroom to work for me, and so I have decided to take a step back and try a level-headed approach to evaluating Lightroom and documenting my findings. I'll update this thread as I make new observations.
First, my system: Custom Pentium Core 2 Duo (E6300) 1.86 GHz CPU, 3GB dual-channel DDR2 PC-5300 memory (two 1GB and two 512MB), nVidia GeForce 7300 GS video card with 512MB memory, 160 GB SATA-II system drive (application and database are on this drive), 250 GB SATA-II storage drive (RAW images and sidecards are on this drive), and a 250 GB SATA-II backup drive. I am running a native resolution of 1680x1050 through DVI on a 21" widescreen monitor. I have turned on "Render Standard Previews" on import, and my Standard Preview size is 1680 pixels at medium resolution. I do not have Lightroom writing changes to sidecar files.
Lightroom Observations 03-15-07
I imported 2038 RAW images (plus sidecars). They were either CR2 files or compressed NEF files. The CR2 files appear to be quicker to import and refresh than the NEF files do, although there doesn't appear to be too much difference (could just be the compression of the NEF files). Thumbnails get the three white dots on them on first viewing, and one by one, the dots go away. Additionally, these three white dots didn't appear on the first hundred or so images that were imported.
On a side note, there appears to be a tremendous amount of work by Lightroom to draw/refresh its own GUI. I am typing these notes into Notepad on a Windows XP machine, and I noticed when I drag the non-maximized Notepad window around on the screen, there is a long "trail" of Notepad windows left behind. This "trail" goes away after a second or two. I recall this being an issue in the BETA, but I also recall Adobe reps suggesting that this was a BETA only issue and that it would be fixed. It appears that it is still an issue.
Thumbnail generation for the first pass appears to only happen on thumbnails currently in view, and even then, only if there isn't an open window such as Notepad on top of Lightroom that is not maximized. Odd thing I just noticed, however, is if I switch to Firefox, which is maximized, to browse the web as thumbnails are created, when I return to Lightroom, the visible thumbnails are finished. As I switch to the Notepad to type these notes when the Notepad window is not maximized, Lightroom stops processing the thumbnails even though they are visible on screen. If the Notepad is maximized, however, thumbnail creation continues on the visible thumbnails.
Regardless, no thumbnails get drawn for the first pass when they are not visible on the screen, even if Lightroom has the focus. I have to page down to show a new screen of thumbnails, and only then will they get drawn for the first time. Subsequent viewings of the thumbnails is faster, but not instantaneous.
Scrolling through thumbnails using the scroll bar, even at a reduced thumbnail size (third tick from the left, instead of fourth tick from the left which I believe is the default), is hit or miss on how smooth it will be. It's almost as if the thumbnail cache (is there one) is wiped out while scrolling, and when it is wiped out, the smooth scrolling comes to a halt. From then on, it is jerky and non-fluid. However, I can scroll backwards, and everything is smooth sailing again for a short while, at which point scrolling becomes jerky once again. There doesn't seem to be any rhyme or reason to when the scrolling is no longer fluid and smooth.
Thanks for reading, and I'll experiment more tomorrow.

Lightroom Observations 03-17-07
I have decided to delete the existing Lightroom database and start over. This time, I have set the thumbnail size back to what I believe is the default, the fourth tick from the left. I am going to import a smaller set of images based on a typical photography day for me, which ranges from roughly 50 images to 500 images, depending on the subject and purpose for the photography. I am doing this so that I don't start out behind the 8 ball, so to speak. I am thinking that because Lightroom seems to do so much "behind the scenes" that I need to import images in smaller, typical photography-day chunks. Let's see what happens when I do this...
I imported 64 CR2 RAW files with sidecars. The first thing I noticed is that after import I was unable to force Lightroom to render standard sized previews by selecting that option through the menus. It appears that Lightroom knows when the standard sized previews are fully rendered, and won't allow re-rendering when there is no need. Note that I did have render standard sized previews checked on import; I just wanted to see what would happen. In this case: nothing. The second thing I noticed is that metadata appears to be slow. I have my thumbnails (in compact view) set to show the following:
- Include quick collection markers
- Include pick flags
- Include thumbnail badges
- Show clickable items on mouse over only
- Tint grid cells with color labels
- Compact Cell index number: off
- Compact Cell rotation: on
- Compact cell top label: label
- Compact cell bottom label: Rating and label
When I browse my thumbnails by moving the scroll bar, the label data at the top and bottom of the thumbnails takes roughly one to two seconds to display. Additionally, all of these images do not currently have a label designation. The top label for the thumbnails shows "none" to reflect this. However, if I chose a thumbnail and select none for a label option, the "none" at the top of the thumbnail goes away and I am left with a blank top label. Obviously, Lightroom is attempting to display the title of the label, such as "Rejected", or "Needs Edit In Photoshop", etc., and on first import, when there is no label, Lightroom displays "none." However, Lightroom doesn't display "none" when I chose the none option for label; Lightroom displays nothing (a blank field).
With this small import of images, scrolling the thumbnails is fairly smooth. I say fairly, because the first time I scroll up or down, there is a slight pause. This pause is nothing like I documented in Day 2, but it is an obvious stuttering. However, scrolling after this initial stutter is smooth, as expected. Additionally, there are no three white dots on any of the thumbnails when I scroll through them.
Undoubtedly, this is directly related to the thumbnail cache, and I am no anywhere close to exhausting the cache with only 64 images to display.
When I double-click on a thumbnail, I am taken to the Loupe view, as expected. The screen draws the larger version of the image very quickly (under one second), and is similar to the observations I made on Day 2.
I am now trying to enter higher metadata into these newly imported images, specifically Location, City, State, Country, and Country Code. When I click into the Location field under the metadata panel in grid view, I can enter the text for the location name, as expected. However, when I hit tab to move to the next field (City), the focus is lost as the metadata information is updated/refreshed. This breaks my workflow for entering metadata. I am expecting the focus to shift to the next field, not disappear altogether. As it is, if I am not paying attention when the focus is lost, and I start typing, I end up hitting keystrokes that invoke functions within Lightroom, causing havoc. It seems that the metadata should only update after I either leave the metadata panel, or I hit ENTER on the keyboard. Tab should simply take me to the next metadata field, not invoke a metadata update.
So I have updated the higher metadata in my small collection of images. I then clicked on the metadata browser to see the results, and the first thing I notice is that there are no image counts for the various metadata fields listed under the browser. Then, one by one, the image counts update to reflect my metadata changes. I'm not too sure why this is so slow, and don't really have any suggestions for this one.
On a small side-note: As I was importing these 64 images, I was deleting them and starting over, testing that rendering standard sized previews on import had any effect. What I discovered was that deleting the images from the Lightroom database and from the disk (by using the delete option from within Lightroom) took approximately ten seconds. Ten seconds to delete these 64 images is entirely too long, but I am at a loss to figure out just what is going on. I assume that there is some database management taking place, but ten seconds to delete a small handful of images indicates, to me, that there is an underlying issue. Don't get me wrong... I'm not making the argument that the database concept is flawed. I, personally, don't have a problem with the database concept. I use and enjoy iView MediaPro3, and it is database driven. It just seems that there is a serious flaw with respect to database functions within Lightroom.
I'm still experimenting, so I'll likely have more later. This has also been updated at http://lr.ianfarlow.com.

Similar Messages

  • Lightroom Upgrade at a client - sucess? - keyword problem deal breaker

    Hi
    Just a small report, on how upgrading a client's LR 2 catalog went.
    Background: The client is a professional photographer specialized on garden photography. Her customers are gardening and lifestyle magazines who publish her photos regularly as illustrations to various articles. She has a professional Canon EOS 1Ds MK III equipment and shoots exclusively raw. In a shoot around 300 to 1000 images are shot. The Lightroom catalog has around 20,000 images currently.
    In Lightroom she uses mostly DAM and some basic development features, images are delivered either as raw of as JPEG images to the clients. Keywording is especially important. She has an extensive hierarchical list of plants most of them multiword keywords with spaces, and lots of other keywords indicating if images were sent to clients and other stuff.
    The upgrade went just very well. I exported the catalog to a new intermediate catalog without previews, installed LR3 and imported this intermediate catalog into LR3 generating new previews from scratch. The hardware is modest, and some functional tests (especially switching images in develop, spot tool, and adjustment brushes) revealed that everything performs well enough.
    Then she asked me where she would have benefits from using the new version. And then I told the whole benefit story, which can be read everywhere.
    - New process version, better details and noise reduction. She asked where she can see it? Hmm, I switched to 1:1 view changing the process versions, not really much to see on Canon 1Ds Mk III files. Even with noisier files, it was hard to tell, what has actually changed. So only a 4:1 view very tiny changes were visible. The impact on her business? Near to nothing as she does not print large. The differences would hardly be seen in the magazine prints.
    - Lens corrections and perspective control: does not really matter in garden photography, but she could see some occasional usefullness.
    - Publish services: no real need for it
    - Print packages: nope
    - Slightshow improvements: no use for it
    - Performance improvements: nothing visible
    - Effects: completely superfluous
    - New import dialog: at first glance a hindereance, as she has to get used to it
    Then she asked: did they correct the keyword handling, when entering keywords witrh spaces? (You know the nasty bug, where keyword completion is broken at keywords with spaces). We checked (I knew it wasn't fixed), and of course she was heavily disappointed. Thus, after 2 years of development nothing new for her, keyword bug not fixed? Of course she said, that I should tell her, when keyword completion works, then and only then would she consider an upgrade.
    So, despite all the bells and whistles about the new version, I doubt that for many photographers the benefits are really so overwhelming in the real world. It is a pitty that Adobe continues to neglect the DAM features (some fresh ideas for client management would be great), that existing features aren't consequently implemented (esp. the possibilities to query the catalog, and keywording), and that existing bugs are constantly ignored and not fixed.
    So, please Adobe, get keyword completion fixed for keywords with spaces immediately !!! This is what professionals need. A catalog without reliable DAM features, renders the catalog concept to a great extend useless. Please listen!
    Disclaimer: As I am not a professional for me the situation is not the same. I just report my experience I had, with a photgrapher, who needs a proper asset management. I recommended Lightroom to her because of the overall package (she moved from Cumulus), so I feel a little obliged to help her in this issue. In my case, as a user of a modest Lumix G camera system, I would consider the IQ benefits more signifcant. I don't know, if this is a general observation.
    Kind regards
    Thomas

    W.W. Webster wrote:
    tgutgu wrote:
    Just a small report, on how upgrading a client's LR 2 catalog went ...
    So, please Adobe, get keyword completion fixed for keywords with spaces immediately !!! This is what professionals need. A catalog without reliable DAM features, renders the catalog concept to a great extend (sic) useless. Please listen!
    I just report my experience I had, with a photgrapher (sic), who needs a (sic) proper asset management.
    So the over-riding conclusion from your experience with just one photographer is that Lightroom is 'useless', and this compels you to demand, in bold type, that Adobe must listen?
    That Lightroom has issues and areas for ongoing development is obvious, and Adobe won't dispute this.  But rants like yours add nothing and are unhelpful.  Julie's response is extremely tactful and far more moderate than your post deserves.
    Dear Mr. Webster
    I think when you post, you should definitely change your tone. Julie simply answered my original post by acknowledging the problem, your accusation that I did not use appropriate "netiquette" is ridiculous. Posts like yours are a real problem of this forum.
    I simply gave a user story example to show that not for everybody the shiny advertised new features provide real benefits and that paying attention to a thorough implementation of features can be equally important. I think Julie has recognized this. And the issue is nothing for ongoing developments. Lightroom supports keywords with spaces, so it has to be done consequently. Keywording is essential for DAM. If keywording gets too tedious or leads to wrong keyword assignments, then DAM is really pointless.
    The intention of my post was to point Adobe to an apparently small problem, which has quite a big impact to people, who depend on good DAM features. The issue is nothing new, existed since the first release of Lightroom, but nothing was done about it, unfortunately. Now that Lightroom addressed keywords with spaces even with a new preference setting, it was fair to assume, that they had done something about it with care. This isn't so obviously. The issue was discussed in previous threads, but did not get any visible notice from Adobe. I am glad that this has changed now with Julie's post.
    In no way did I say that Lightroom is useless or even that I regard it to be so. I merely said that the catalog concept is to a great extend (not completely) useless, if its implementation is sloppy. DAM starts with data entry and only after doing this, you can use it to your benefit. Therefore it has to be efficient, which currently is not. Lightroom is criticized by a large number of users that it is forcing them into a catalog system instead of just providing access to the file system. Long existing bugs like this, likely proves them right in their view.
    The competition (I mean complete workflow solutions) is not really better than Lightroom with respect to DAM features, however, my take is, that the developers should be equally ambitious with the quality of the catalog system as they are with IQ, especially if the achievements in IQ are apparently less relevant to owners of high end camera systems. (I could be wrong with the last statement, but it would be interesting to hear if others have similar observations).
    Kind regards
    Thomas
    Thomas

  • Lightroom 5.6 crashing, not able to import or back up changes

    I have been having issues with Lightroom 5.6 for few days now. I have been working from this Lightroom install for a year now problem free. The problem seems to happen when I try to import pictures. At first I thought it was my SD card but I copied the pictures to my desktop and was not able to import from the file on my desktop. It will start to download a few out of 400 and stop at 2 or 3 pictures then freeze. A message pops up that says "Lightroom encountered a problem and needs to quit" When i try to open Lightroom again I will get a message that says "The last time Lightroom ran, it shut down prematurely due to a problem reading the catalog. Lightroom must now check the catalog before proceeding." It will proceed to check integrity of the catalog then another message pops up saying it was repaired successfully. When I try to open, same stuff happens all over again.
    I have not moved any files around through the external hard drive and there are no images in the catalog that are "missing." So I'm a little confused as to why Lightroom suddenly keeps crashing.
    I am able to export images from the same catalog, I am able to edit pictures as I normally would,but I am unable to Back up the changes or import new files. I tried working from a different external hard drive and the same thing happens.
    Please help!!

    Are you able to import 450D raw files into LR5.5via USB connection and are you on Windows 7/8?
    I agree with your observations concerning SD vs CF card fragility, but they also have a limited number of insertions before failure.
    http://en.wikipedia.org/wiki/USB#Durability
    The newer Micro-USB receptacles are designed for up to 10,000 cycles of insertion and removal between the receptacle and plug, compared to 1,500 for the standard USB and 5,000 for the Mini-USB receptacle. This is accomplished by adding a locking device and by moving the leaf-spring connector from the jack to the plug, so that the most-stressed part is on the cable side of the connection. This change was made so that the connector on the less expensive cable would bear the most wear instead of the more expensive micro-USB device.
    All my Canon cameras have micro-USB connectors. With one (1) insertion and removal per day that equals 10,000 days, or about 27 years before end-of-life! SD and CF cards are also rated at ~10,000 insertion and removals, but more prone to damage from static electricity and handling due to the exposed contacts and fragility of CF card sockets.
    So there's no real advantage from the camera wear perspective to using a card reader. I'd say use whatever method is easiest for your workflow, but handle memory cards with care and avoid exposing them to static discharge.  Ground yourself to something metal before removing memory cards and inserting them into the card reader, especially in cold Winter months.
    BTW- I helped design one of the first semiconductor DRAM memory systems back in 1970. We killed more memory chips than I care to count before we discovered they were easily damaged by static electricity. Today's ICs have built-in protection, but you can still damage them with a big enough static ZAP!

  • How do I transfer Lightroom 4 license from one computer to another?

    Hi Adobe Community,
    Recently I have purchased a new Windows laptop to replace an older one; in my attempt to transition all files and programs to the new one I found some difficulty in the transferring of lightroom 4.
    I know that in order to transfer the license over I would need the serial number (of my purchase) as well as to deactivate lightroom on my old laptop (because I have only 2 codes, one is being used on a home computer and one on the laptop that I am attempting to transition away from, this might be the case for photoshop too). Normally, I would just go into lightroom and follow steps that other users have posted on this forum (going to Help--->System Info to get the serial number) but here is my problem:my laptop can't open light room and I can't seem to find the box of my purchase.
    Is adobe able to email me the serial number that I have used or am I able to access lightroom files which could either: a) Allow lightroom to function on my older computer   OR   b) transfer files that could avoid the serial number process    OR C) Have my serial number available for observation.
    If anyone is able to help, it would be GREAT!

    This is a user-to-user forum so nobody here is going to be able to retrieve your serial number for you. However, if you registered Lightroom with Adobe then the serial number should be available from your account profile. Otherwise I think you need to contact customer "support".

  • Lightroom 4 runs too slowly

    I have spent weeks trawling forums now and implementing as much as I can from people's suggestions as to how to try and get Lightroom to run better.
    As an example, alway leave the Details section til last, as it makes a significant impact on slowing Lightroom down.
    I flush the cache before starting any work, I bought a  new 1tb drive, and downloaded a brand new, up to date nVidia driver for my card.
    I've spent some considerable time ensuring that all meta data has been written to xmp and none is outstanding, and all 1:1 previews have been rendered for every image in the catalog. Standard previews are set at their lowest level, and I have set all LR locations including the cache, catalog and preview locations as 'excluded" from MSE, which is the only anti-virus type program I run.
    I have tried using process 2010, then changing to process 2012 when the work is complete and implementing the changes, the same problems occur. Using process 2010 in LR 4.3 does not seem to be any qucker than using process 2012.
    I've been through all Windows services to see which ones I can turn off and which I can't. All those not necessary for the operation of the computer are turned off.
    The cache has been set at everything from 10gig to 150 gig, that doesn't seem to have any effect but it is at present on 100 gig. I flush it regularly when working. I also have tried deleting history from each file I work on, although this doesn't seem to have any positive impact either.
    Now, the issues.
    When using Lightroom, there is a 'hang' or 'lag' of a fraction of a second before any command is carried out. So, if I zoom into full size, grab the small selection box from the view on the left to move it around my image, it is a half a second before it responds.  Often on any task, the cursor doesn't change, as if there is still something going on.
    If I click using the healing brush to get rid of dust bunnies, it is 1-3 seconds before it appears and is editable, then I can move onto another. When using the spot healing tool, after 2 -3 photos have been completed, each time I click on the image the 'target' for the tool appears, but it is in the top corner of a very large black square, which does not disappear for 3-5 seconds.
    I can do an image with maybe 20 of those then it begins to get real slow. If I then use the sliders, it can be up to 4-6 seconds before they respond. During this period, at random times on the top bar of Lightroom I see the message "Lightroom not responding" flash on and off, sometimes for minutes before it clears. If I then go to export the file as a jpg, it can take as much as 3 minutes to export one full size image from a RAW file. During that whole period the processor is toiling away at 100% and LR is using the max amount of memory, which for some reason is only just over 700mb. (I will paste the system info from LR at the end of this.) Once this begins, LR pretty much thrashes away at 100% of processor power for many minutes even when doing nothing, and trying the slghtest thing starts it off again.
    Once I've exported 3-4 images, everything slows down to the point it's really unusable. If I try to export an image at that point, I get a 'not enough memory' message. I can try 5-6 times to export and I always get the same message. My only option then is to shut LR down, and start it up again after a minute or so, flush the cache and start again. Obviously this is an unacceptable workflow.
    So,  I know that LR works fine for some people, so please don't say "It works for me", I know it does. It doesn't work for me though, and I am trying to establish why. If your car breaks down I don't point and say "It must be you cos I have the same car and mine is fine." What I would like is for anyone who has useful suggestions to help. Perhaps someone who it didn't work for and they solved the problem?
    Lightroom version: 4.3 [865747]
    Operating system: Windows 7 Home Premium Edition
    Version: 6.1 [7600]
    Application architecture: x86
    System architecture: x86
    Logical processor count: 2
    Processor speed: 1.9 GHz
    Built-in memory: 3068.9 MB
    Real memory available to Lightroom: 716.8 MB
    Real memory used by Lightroom: 504.9 MB (70.4%)
    Virtual memory used by Lightroom: 506.6 MB
    Memory cache size: 3.8 MB
    Maximum thread count used by Camera Raw: 2
    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: J:\Lightroom 4\Master\Master.lrcat
    Settings Folder: C:\Users\G\AppData\Roaming\Adobe\Lightroom
    Adapter #1: Vendor : 10de
    Device : 649
    Subsystem : 1451025
    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 9600M 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 think the "Available Memory" figure is pretty standard for a 32bit system, which is what I think the OP is running.
    @howmanyetc: A couple of observations: the systems specs would seem to be not much higher than the minimum requirements for LR4, so blazing fast it ain't ever going to be. Also is the J drive the new external drive that you bought? If so I'm guessing that it may be USB2 connected? If so having the catalog on a "relatively slow" external drive is probably not the best idea from a performance perspective. The "red lining" of the CPU during exports is entirely likely, the processor is simply not sufficiently powerful to do the work quickly. As a comparison, exports which take maybe 3-4 seconds on my desktop would take upwards of 30 seconds on my old Thinkpad laptop (similar specs to yours) with both cores at 100% with no deviation (and that was back in LR3, so I can't imagine how slow it would be using LR4). The "getting real slow" after a while is more than likely due to your RAM limitations, especially on a 32 bit system.
    I'm not saying that you should rush out and buy a brand new powerful system, though I do think you might struggle to make significant improvements given your specs. It sounds as though you are doing everything you can to improve things, however as I said, if the catalog is on a USB2 external drive, trying it back on an internal drive would be the first place that I would start. Having the images on the external is probably OK, your bottleneck for things such as Exports is CPU, not I/O.
    Do you need to be writing XMP for all your files? Do you have the "Auto write XMP" setting enabled? If so, turning that off and using Ctrl+S to manually write the XMP at the end of a session may help a little.
    Sorry I can't be of more help.

  • Lightroom crash in Develop module with RAW files with sidecar files from ver 3

    The issue probably has to do with the differences in settings between the two versions but I figured I would document what I am experiencing. 
    I am using the 64 bit version of Windows 7.
    I imported a group of pictures with the XMP sidecar files generated with Lightroom v3.  All the image files, a mixture of Canon Mark 5D II RAW and jpg files from my point & shoot UFO camera, imported without issue picking up all my tagging and GPS settings. When importing you are put into the Library module and from the Library module I could click on any RAW or jpg file, look at the meta data and view full screen.
    I then entered the Develop module with a jpg picture selected and none of my settings made it across. The process was set to 2012.  I was able to try out the new adjustments and all worked very well. 
    I then selected a RAW file while still in the Develop module and all hell broke loose.
    I got a tip window pop up, the film strip went orange, the rest of the app screen then became greyed out and then behind tip pop up a crash window containing this information appeared:
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: lightroom.exe
    Application Version: 4.0.0.1
    Application Timestamp: 4ef2621d
    Fault Module Name: MSVCR100.dll
    Fault Module Version: 10.0.40219.1
    Fault Module Timestamp: 4d5f034a
    Exception Code: c000041d
    Exception Offset: 000000000003c1be
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: cc7e
    Additional Information 2: cc7e9ac0f4374c9d4c9f2c948a85a235
    Additional Information 3: 41e7
    Additional Information 4: 41e779def86567567ae94271de75e4e9
    There was no other path but to have the app close after that.  Now since Lightroom has left off with the RAW file in the develop module when I restart the app it starts in the develop module with that same RAW image selected and I crash before I can change to a jpg.   I am probably going to have to delete and recreated the data file to use the app again
    After the all this I went back and checked to see how I had the catalog settings in LR 3 set because there were no sidecar files for the jpg images.  I did not have the option to write settings to jpg and tif files but did have write settings to sidecar set.  So I have a bit of a mystery why I have no sidecar files for jpg files when I should have based on the way the settings were.  This probably explains why I had no issues at all with them in LR 4.
    I am going to get LR 4 working again and then import the same batch of pictures without any sidecar files and see if I have any issues.  I will report back soon.
    When I imported the files without the sidecar files I had no issues at all but the RAW images came under older process not the 2012 process. There were no settings without the sidecar files so why would the app not start the images at the most recent process level? I updated then to 2012 and some of the setting sliders changed.  I tried all the adjustment might use with both RAW and jpg files and no issues were observed.
    The new develop module does seem to light darker areas without impacting other lighter areas better.  The brush toll does work better and I see some additional settings were added along with presets.
    As I posted elsewhere, I am disappointed content aware fill and healing were not included.  This is the functionality that would save me from going to Photoshop when I have some undesirable reality in an image.
    I tried out the new geo coding functionality and I really like it as it beats using Google maps on the web (painfully slow these days), dropping latitude / longitude markers, copying and pasting the data from the markers into a Lightroom plug-in and then going through a time consuming three step process.

    Idem for me on Mac:
    No problem to developp a RAW file from a D300 never develop before in LR 3 but when I enter a RAW file develop in LR3 into the develop module of LR4, Lightroom Crash. The report on Mac:
    Process:         Adobe Photoshop Lightroom 4 [412]
    Path:            /Applications/Adobe Photoshop Lightroom 4.app/Contents/MacOS/Adobe Photoshop Lightroom 4
    Identifier:      com.adobe.Lightroom4
    Version:         Adobe Photoshop Lightroom 4.0 Beta [800002] (4.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [295]
    Date/Time:       2012-01-13 18:46:19.729 +1100
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          24816 sec
    Crashes Since Last Report:           11
    Per-App Interval Since Last Report:  3225 sec
    Per-App Crashes Since Last Report:   11
    Anonymous UUID:                      B2BF54C2-46B7-4994-A520-D74AD1B91289
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000126c5f000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.adobe.ag.AgImageIO                  0x0000000116f384f4 private_load_AgColorProfile + 386306
    1   com.adobe.ag.AgImageIO                  0x0000000116f2e7e7 private_load_AgColorProfile + 346101
    2   com.adobe.ag.AgImageIO                  0x0000000116f2ccdc private_load_AgColorProfile + 339178
    3   com.adobe.ag.AgImageIO                  0x0000000116f2c5e4 private_load_AgColorProfile + 337394
    4   com.adobe.ag.AgImageIO                  0x0000000116f2cb7c private_load_AgColorProfile + 338826
    5   com.adobe.ag.AgImageIO                  0x000000011702773b private_load_AgColorProfile + 1365833
    6   com.adobe.ag.AgImageIO                  0x0000000117029937 private_load_AgColorProfile + 1374533
    7   com.adobe.ag.AgImageIO                  0x0000000116f3f3eb private_load_AgColorProfile + 414713
    8   com.adobe.ag.AgImageIO                  0x0000000116f3f4cd private_load_AgColorProfile + 414939
    9   com.adobe.ag.AgImageIO                  0x0000000116fb8e70 private_load_AgColorProfile + 913022
    10  com.adobe.ag.AgImageIO                  0x0000000117147175 private_load_AgColorProfile + 2544003
    11  com.adobe.ag.AgImageIO                  0x00000001171482d6 private_load_AgColorProfile + 2548452
    12  com.adobe.ag.AgImageIO                  0x0000000116eb7d71 0x116eae000 + 40305
    13  com.adobe.ag.AgImageIO                  0x0000000116ecc4fc AgDevelopSupport_load + 27921
    14  com.adobe.ag.AgImageIO                  0x0000000116ecc6d5 AgDevelopSupport_load + 28394
    15  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    16  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    17  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    18  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    19  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    20  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    21  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    22  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    23  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    24  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    25  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    26  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    27  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    28  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    29  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    30  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    31  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    32  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    33  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    34  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    35  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    36  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    37  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    38  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    39  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    40  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    41  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    42  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    43  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    44  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    45  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    46  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    47  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    48  com.adobe.ag.ui                         0x000000010009b4a5 AgUI_fontFullNameL + 36981
    49  com.apple.AppKit                        0x00007fff884d5d75 -[NSView _drawRect:clip:] + 3566
    50  com.apple.AppKit                        0x00007fff884d354b -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 2112
    51  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    52  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    53  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    54  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    55  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    56  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    57  com.apple.AppKit                        0x00007fff885f19c4 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 276
    58  com.apple.AppKit                        0x00007fff884cf3de -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2683
    59  com.apple.AppKit                        0x00007fff88448c0e -[NSView displayIfNeeded] + 969
    60  com.apple.AppKit                        0x00007fff883fe5a4 -[NSNextStepFrame displayIfNeeded] + 76
    61  com.apple.AppKit                        0x00007fff88443aba _handleWindowNeedsDisplay + 678
    62  com.apple.CoreFoundation                0x00007fff82f75b07 __CFRunLoopDoObservers + 519
    63  com.apple.CoreFoundation                0x00007fff82f51434 __CFRunLoopRun + 468
    64  com.apple.CoreFoundation                0x00007fff82f50d8f CFRunLoopRunSpecific + 575
    65  com.apple.HIToolbox                     0x00007fff896db7ee RunCurrentEventLoopInMode + 333
    66  com.apple.HIToolbox                     0x00007fff896db5f3 ReceiveNextEventCommon + 310
    67  com.apple.HIToolbox                     0x00007fff896db4ac BlockUntilNextEventMatchingListInMode + 59
    68  com.apple.AppKit                        0x00007fff88418eb2 _DPSNextEvent + 708
    69  com.apple.AppKit                        0x00007fff88418801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
    70  com.apple.AppKit                        0x00007fff883de68f -[NSApplication run] + 395
    71  com.apple.AppKit                        0x00007fff883d73b0 NSApplicationMain + 364
    72  com.adobe.Lightroom4                    0x0000000100001c35 main + 1073
    73  com.adobe.Lightroom4                    0x00000001000017fc start + 52
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                       0x00007fff88de9c0a kevent + 10
    1   libSystem.B.dylib                       0x00007fff88debadd _dispatch_mgr_invoke + 154
    2   libSystem.B.dylib                       0x00007fff88deb7b4 _dispatch_queue_invoke + 185
    3   libSystem.B.dylib                       0x00007fff88deb2de _dispatch_worker_thread2 + 252
    4   libSystem.B.dylib                       0x00007fff88deac08 _pthread_wqthread + 353
    5   libSystem.B.dylib                       0x00007fff88deaaa5 start_wqthread + 13
    Thread 2:  Worker Thread Dispatcher
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 3:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 4:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 5:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 6:  cr_scratch
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.AgImageIO                  0x0000000116fe717e private_load_AgColorProfile + 1102220
    3   com.adobe.ag.AgImageIO                  0x000000011718f99b private_load_AgColorProfile + 2841001
    4   com.adobe.ag.AgImageIO                  0x0000000116fb7fb9 private_load_AgColorProfile + 909255
    5   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    6   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 7:  AsyncDataServer
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x00000001000415af AgConditionLock_wait + 171
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 8:  Queue Processor - AgPhotoAvailability
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 9:  Preview Server
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x00000001000415af AgConditionLock_wait + 171
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 10:  Queue Processor - PreviewFileStore
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 11:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 12:  Queue Processor - NegativeQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 13:  Queue Processor - HistogramQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 14:  Queue Processor - RenderQueue_Render
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 15:  Queue Processor - RenderQueue_ReadPreview
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 16:  Queue Processor - RenderQueue_Video
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 17:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 18:
    0   libSystem.B.dylib                       0x00007fff88dd0d7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff88dd13ed mach_msg + 59
    2   com.apple.CoreFoundation                0x00007fff82f51902 __CFRunLoopRun + 1698
    3   com.apple.CoreFoundation                0x00007fff82f50d8f CFRunLoopRunSpecific + 575
    4   com.apple.Foundation                    0x00007fff87ebb14f +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 297
    5   com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    6   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    7   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 19:  com.apple.CFSocket.private
    0   libSystem.B.dylib                       0x00007fff88e14932 select$DARWIN_EXTSN + 10
    1   com.apple.CoreFoundation                0x00007fff82f73468 __CFSocketManager + 824
    2   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    3   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 20:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 21:
    0   libSystem.B.dylib                       0x00007fff88deaa2a __workq_kernreturn + 10
    1   libSystem.B.dylib                       0x00007fff88deae3c _pthread_wqthread + 917
    2   libSystem.B.dylib                       0x00007fff88deaaa5 start_wqthread + 13
    Thread 22:  Queue Processor - renderPixmapWorkerThreadQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.AgImageIO                  0x0000000116fe71de private_load_AgColorProfile + 1102316
    3   com.adobe.ag.AgImageIO                  0x0000000116fb8110 private_load_AgColorProfile + 909598
    4   com.adobe.ag.AgImageIO                  0x0000000116fb8d53 private_load_AgColorProfile + 912737
    5   com.adobe.ag.AgImageIO                  0x0000000117147175 private_load_AgColorProfile + 2544003
    6   com.adobe.ag.AgImageIO                  0x00000001171482d6 private_load_AgColorProfile + 2548452
    7   com.adobe.ag.AgImageIO                  0x0000000116eb7d71 0x116eae000 + 40305
    8   com.adobe.ag.AgImageIO                  0x0000000116ecc4fc AgDevelopSupport_load + 27921
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    11  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    12  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    13  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    14  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    15  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    16  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    17  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    18  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    19  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    20  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    21  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    22  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    23  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    24  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    25  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    26  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    27  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    28  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    29  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    30  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    31  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    32  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    33  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    34  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    35  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    36  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    37  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    38  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    39  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    40  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    41  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    42  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 23:  cr_area_task
    0   com.adobe.ag.AgImageIO      

  • Crash in develop module RAW files with sidecar files from Lightroom 3

    The issue probably has to do with the differences in settings between the two versions but I figured I would document what I am experiencing. 
    I am using the 64 bit version of Windows 7.
    I imported a group of pictures with the XMP sidecar files generated with Lightroom v3.  All the image files, a mixture of Canon Mark 5D II RAW and jpg files from my point & shoot UFO camera, imported without issue picking up all my tagging and GPS settings. When importing you are put into the Library module and from the Library module I could click on any RAW or jpg file, look at the meta data and view full screen.
    I then entered the Develop module with a jpg picture selected and none of my settings made it across. The process was set to 2012.  I was able to try out the new adjustments and all worked very well. 
    I then selected a RAW file while still in the Develop module and all hell broke loose.
    I got a tip window pop up, the film strip went orange, the rest of the app screen then became greyed out and then behind tip pop up a crash window containing this information appeared:
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: lightroom.exe
    Application Version: 4.0.0.1
    Application Timestamp: 4ef2621d
    Fault Module Name: MSVCR100.dll
    Fault Module Version: 10.0.40219.1
    Fault Module Timestamp: 4d5f034a
    Exception Code: c000041d
    Exception Offset: 000000000003c1be
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: cc7e
    Additional Information 2: cc7e9ac0f4374c9d4c9f2c948a85a235
    Additional Information 3: 41e7
    Additional Information 4: 41e779def86567567ae94271de75e4e9
    There was no other path but to have the app close after that.  Now since Lightroom has left off with the RAW file in the develop module when I restart the app it starts in the develop module with that same RAW image selected and I crash before I can change to a jpg.   I am probably going to have to delete and recreated the data file to use the app again
    After the all this I went back and checked to see how I had the catalog settings in LR 3 set because there were no sidecar files for the jpg images.  I did not have the option to write settings to jpg and tif files but did have write settings to sidecar set.  So I have a bit of a mystery why I have no sidecar files for jpg files when I should have based on the way the settings were.  This probably explains why I had no issues at all with them in LR 4.
    I am going to get LR 4 working again and then import the same batch of pictures without any sidecar files and see if I have any issues.  I will report back soon.

    When I imported the files without the sidecar files I had no issues at all but the RAW images came under older process not the 2012 process. There were no settings without the sidecar files so why would the app not start the images at the most recent process level? I updated then to 2012 and some of the setting sliders changed.  I tried all the adjustment might use with both RAW and jpg files and no issues were observed.
    The new develop module does seem to light darker areas without impacting other lighter areas better.  The brush toll does work better and I see some additional settings were added along with presets.
    As I posted elsewhere, I am disappointed content aware fill and healing were not included.  This is the functionality that would save me from going to Photoshop when I have some undesirable reality in an image.
    I tried out the new geo coding functionality and I really like it as it beats using Google maps on the web (painfully slow these days), dropping latitude / longitude markers, copying and pasting the data from the markers into a Lightroom plug-in and then going through a time consuming three step process.

  • Lightroom = Overrated, misdesigned and buggy.

    So I have been using the V1.0 version of Lightroom, and all I can say is that it is overrated and most of it is just plain junk.
    Don't get me wrong, the DEVELOP module is extraordinarily good, really really good, but the DEVELOP module has been surrounded by such copious crap that the overall program itself becomes a burden to use in any productive way.
    Let's start with the library... what a joke. You have to import everything, a time consuming process that is utterly unnecessary if you just want to look through your files. It is buggy, slow and utterly network unfriendly. You can't copy, you can only move. It is completely unfriendly to network storage, taking 1.5 hours to do the same batch rename that a piece of shareware does in 7 minutes. The DAM capabilities are second rate at best. All for what? So I can search for keywords????
    The Slideshow... useless. What good is a slideshow that doesn't let you do image ranking during a client presentation. I guess that we are expected to use pencil and paper.
    Web galleries... the provided versions are amateurish at best... and the whole thing in written in some Klingon variant of XML which requires a PHD in programming just to create (or even change) a simple template.
    Printing... nice but useless to me, since I send everything to a commercial printer, and the stupid module won't generate a JPEG that I can upload to the lab. And no, a simple export doesn't do it... tell me how to add a 1/4 inch margin to an 8x10x300 print file using export... can't be done.
    Like I said, the DEVELOP module is fabulous. Give the Library a standard file browser capability (using just XMP sidecars), give the HTML generator a token based design so mere mortals can code for it, allow export from the print module, and make the slideshow actually useful for something and then the full program will be worth the effort.

    I have been using Adobe Lightroom 1.0 for the last 3 weeks or so. I keep reading rave reviews but Im having difficulty seeing what others see. Here are some observations regarding Lightroom as a photo organizer specifically the Library module from someone (me) who is already familiar with ACDSee as an organization tool
    1. Lightroom, like other Adobe products, eats an enormous amount of resources on my PC. Loading the program with even a moderate-sized database is slow especially if I am backing up the database frequently. Navigating around can be very sluggish. (I have 1GB of memory. Maybe more would help...?)
    2. Lightroom can only see folders and photos that have already been imported into the Lightroom database. If you temporarily leave the program to process some RAW files somewhere else, for example, the JPEG or TIF files created will be invisible in Lightroom, until you import them. I think this is a stupid concept. In ACDSee, you can see everything from within the program even files that have been added using 3rd party software outside of ACDSee. Simply browsing adds stuff automatically to the database.
    3. It is not possible to drag and drop photo files from Lightroom into another program one of the drawbacks of non-destructive file editing, I suppose. I drag & drop all the time with ACDSee and actually, it is a pretty important tool if you make use of a virtual system (categories, ratings, keywords, etc.) to organize your pictures. I print with Qimage, for example, and I have trouble finding photos based on the hard drive folder structure. But if ACDSee is open in category view, I can drag and drop the photos I want to process into Qimage. This is impossible with Lightroom.
    4. It seems that Lightroom will only handle 2 external editors and one of them is Photoshop by default! Sometimes I want to send a photo to Qimage (for printing) or to DxO Optics Pro or NX (for RAW processing), or PTGui (for panorama processing). Every time I try to do this, I must change the External Editor preferences and hunt down the EXE file required to launch the program I want to use. Pretty cumbersome, I think. ACDSee allows setting up these programs so they appear as choices in the Edit menu, and it allows full use of drag and drop.
    6. I think the Lightroom Loupe view screen is too small unless you close up all the sidebars. But if you are editing, you need to keep at least the develop sidebar (on the right) open. This leaves the full-size view rather inadequate, I think.
    7. The small font is not very small. In the Library, I cannot see many of my Folders or Collections on the left without a lot of scrolling. And there is no way to distinguish between the Folder list and the Collection list they look the same and they both scroll in the same list! A different color or font option would help. The headings for these groupings (Folders, Collections, etc.) disappear from view when scrolling, making it even more difficult to figure out where I am! Poor design!
    8. What is the point of the filmstrip? There is already a grid view. Isnt the filmstrip a little redundant? Granted you can make it disappear, but whats the point of having it there in the first place? It just eats up valuable real estate on a screen that is already way too cluttered.
    8. I like the Lightroom develop module okay, but it is not as good as Photoshop CS2 for photo editing, or Capture NX for raw conversion both of which I can easily access from within ACDSee.
    9. I do like the Lightroom renaming template. It facilitates a variety of renaming options and is more flexible than the offering in ACDSee. But right now, this is about the only thing I have found to be more usable in Lightroom.
    I have decided that Lightroom is sort of like one of those do everything printer/fax/scanner machines. While it can be handy, it doesnt do any of one those functions particularly well. Better to have 3 separate devices each dedicated to one of those functions exclusively.

  • Problem with Exporting/Stacking in Lightroom 5.2

    I have used stacks in Lightroom for a long time but I am now having a problem. My typical workflow is to process RAW images in the Develop Module then Export them as JPG files. I choose "export to same folder as original" and I check "add to this catalogue" and "add to stack above original". Until recently this has worked well - the RAW and JPG files appeared as a stack in the catalogue. Now, when I go back to Library I do not see the JPG files in the catalogue and there are no stacks being created. (I can see that the JPG files are appearing in the same folder as the original RAW files as I intend them to do.)
    An additional observation is that stacks that were previouly created are not behaving normally. When I split a stack, the stack status is compleley lost - the number in the upper left corners are gone.
    How can I fix these problems?

    If you're a beginner this might be helpful.
    Capture Sharpening
    Make sure you are using LR's 1:1 Zoom view when adjusting Sharpening and Noise Reduction. A Sharpening Amount in the range of 25 to 50 with the default 1.0 Radius and 25 Detail works well with most "normal" images. Adobe increased the Sharpening Amount from 100 to 150 to provide additional sharpening when using high Mask settings. You shouldn't need to set the Amount higher than 100 when Masking = 0. Even with Masking I've never required Sharpening Amount higher than about 75.
    Noise Reduction
    If you have visible noise in the image after sharpening, increase the Luminance NR from the 0 default. If color noise is visible increase Color NR as well. You may then need to go back and increase Sharpening slightly–It's a trade-off of low-noise vs sharpness. This procedure is normally only required with images shot at high ISO settings. Images shot at ISO 100-400  should have minimal visible noise at 1:1 view and require very little more than the default LR settings.
    Output Sharpening & Resizing
    With today's high-megapixel cameras full-size Exports are not required for most purposes and simply create larger file sizes. When resizing images during Export it is important to add 'Output Sharpening' to match the target usage (prints or screen viewing). This has much more effect on the resized file's image sharpness than LR 'Capture Sharpening' used alone. If you do Export images full-size for use in other applications Output Sharpening is normally not required.
    Cheers,
    Todd

  • Lightroom Workflow & Avoiding Photoshop

    There are still basic colour adjustments that I'm performing in Photoshop for which I suspect Lightroom would be able to handle just as well. But I'm still too addicted to Adjustment Layers to see an efficient way of accomplishing the same thing.
    For example, a typical case:
    I open a photo in Photoshop, and decide to do a B&W conversion. I use a Channel Mixer adjustment layer, and quickly cycle through Yellow/Orange/Red filters. I settle on Red.
    After looking at the result, I decide that the image would be a bit punchier if I increased the saturation before the B&W conversion. So I slip in a Hue/Sat adjustment layer underneath the Channel Mixer, and ramp up the Saturation.
    Hmmm. Better. Now for a little contrast adjustment with a Curves layer: I go back and forth as to whether I like the result of the Curves adjustment when it is placed above or below the other adjustment layers, and I settle on above.
    This workflow should be possible entirely in Lightroom, as LR is a non-destructive editor. However, it seems to me that in order to get the same results as above, I am prevented from experimenting as I described, as LR doesn't stack adjustments -- it just has a history.
    Any thoughts?

    Jim
    I do most of my b&w work in Lightroom, but plenty in Photoshop too, and while you've obviously got good advice from Ian, I'll add a few other thoughts for you:
    1. Create a few presets of your b&w treatments so you can preview the results of the conversions. So instead of your initial run through of the channels in PS, you simply move the mouse over these b&w preset in Develop's left panel and observe the results in the Navigator.
    2. For judging alternatives, play a bit with virtual copies as an alternative to snapshots. Ctrl ' on PC, Cmd ' on Mac is all it takes to create a VC. You can view all the variations side by side in Library, Print too, and eventually make your preferred VC the master and remove the rest (if you want).
    3. Eventually you may well decide that you do actually need to do the conversion in Photoshop. I find this is especially where you want to convert one part of the image differently from the rest - ie not because of deficiencies in LR's decision-making process.
    John

  • Lightroom 2.0 will not export to Photoshop CS3

    OK,
    So I downloaded and installed lightroom 2.0 this morning and things are not working well.
    System: Macpro 2.8, 8 gb ram, os x 10.5.4, nikon d300 raw files
    The problem...
    It started with Lightroom not exporting any images to photoshop. Doesn't matter if I try to send 1 or 20, I get a spinning beach ball, then nothing. if photoshop is closed it will open it, but nothing gets loaded into it. Plain export, merge to panoramic, edit as smart object, nothing does anything.
    Tried in both 32 and 64 bit modes, tried re-installing Lightroom 2.0 from scratch. still nothing. I sent a sample raw file into adobe and am waiting to hear back, but figured I'd see what everyone else thinks as well.

    @jc:
    >However.....that being said, if I 'Edit in CS3' a raw file-it now opens and I can make changes to it in CS3. When I save it, the resultant saved file is not stacked beside the original. All my folders are on my L: drive, in a hierarchal structure. After saving, I have a second occurrence of L: in the volume list, with a repeat of the original folder name ... and it contains 1 file (the one I saved). I have to manually synchronize the 'real' folder to pick up the file saved from CS3. Then I can delete the 'phantom' folder.
    Replace the 'L:' with an 'E:' and you accurately describe what I observe.
    crh
    System Info:
    Lightroom version: 2.0 [481478]
    Operating system: Windows Vista Service Pack 1 (Build 6001)
    Version: 6.0 [6001]
    Application architecture: x64
    System architecture: x64
    Physical processor count: 4
    Processor speed: 2.4 GHz
    Built-in memory: 8124.8 MB
    Real memory available to Lightroom: 8124.8 MB
    Real memory used by Lightroom: 2565.8 MB (31.5%)
    Virtual memory used by Lightroom: 2563.3 MB
    Memory cache size: 1553.2 MB

  • Lightroom has a hard time with local adjustments:

    Local adjustments: Spotting / Cloning / Healing Brush, Adjustmenst Brush, Graduated filter
    I posted  the piece below as a response to thaehn’s post “Lightroom freezes on Dust Spot Removal” but I thought the topic is important enough to warrant its own post.
    This in advance: I'm running WIN XP SP4 with all available patches; have 4 GB of RAM; have a dual-core processor at 3 GB.
    Apart from my drive C, I have two internal hard drives in Raid 0 configuration (thus they show up as one drive). I also have an external hard drive that's in Raid 1 ( "mirroring') and is connected by fire-wire 400.
    Yes, LR "freezes" when using the dust spot tool and also when using the adjustment brush or - but to a lesser degree - when using the grad filter.
    My observation though is that it's not a true "freezing", because if I wait long enough LR starts working again. So when using these tools, LR gets extremely busy und just doesn't have enough resources left to respond to further commands right away - but it "stores" the comands and acts on them eventually.
    If I turn on my task manager I observe the following when using these tools: the CPU gets extremely busy (i.e. the green bar is at 100%)  while the RAM usage is high but not to the max. The "freezes" occur when and as long the CPU works at 100%. If the CPU is below 100% LR responds sluggish and the response is normal again when eventually the CPU usage is at 0%.
    Also, in my observation, this behaviour of LR is compounding, i.e. the wait-times for my CPU to get back to 0 are increasing, the longer I work with these tools or the more photos I work on. Re-starting LR does not bring change: the behaviour establishes itself when using the tools again. It is as if LR needs to do some work in the background and that this background work piles up the longer I work in LR.
    I am not a software or hardware specialist, so the following observations are somewhat subjective and not really quantifiable.
    In Photoshop I observed a similar behaviour (although never as bad) when working on files of 500 MB and above. It was particularly bad when working on photos residing on my external RAID 1 hard drive. I had a hunch that it might have to do with the reading and writing from a drive that a)  is external and b)  is  in RAID 1. It is known that RAID 1 has slower writing (and also reading) speeds than RAID 0 (or no RAID at all). So in Photoshop I managed to cut down on the unresponsiveness by moving large files to my internal RAID 0 hard drive and working from there.
    From this experience I come to the assumption that some of the "busy-ness" in LR (or of the CPU) is due to reading/writing to/from the hard drive.
    To test this assumption for LR, I moved some photos from my external (RAID 1) to my internal (RAID 0) hard drive and did some "intensive" work: first some "fancy" lens correction, then a few grad filters, and a "final touch" with the adjustment brush. I thought that LR could handle these tasks somewhat better when the photos were on the internal drive - so some of the "sluggishness" or " freezing" is due to the reading/writing from/to the hard drive.
    Acually I cannot explain why this should be so: In my naivete I thought LR writes everything only into the catalog (?), that - by the way - is on my internal RAID 0 drive.
    I think it would be good if Adobe could look into this and maybe give us some recommendations, just as they do for Photoshop by saying that the scratch disk should be on a different drive than Photoshop.
    But it seems also that local adjustments - spotting, adj. brush. etc - are a very high "number-crunching" business for LR - independent of where the photo is located on the drive. (Interestingly the grad filter is not as bad as the adjustment brush). The clone-tool in Photoshop hardly registers on my CPU and if at all only with a very short spike, while the clone tool in LR sends the CPU through the roof for 10 to 30 seconds- even when the photo in question is on the internal drive.
    I'm sure loots of people will now tell me that this is due to the difference between pixel-based adjustment and non-pixel-based ones. OK, I acknowledge that. But still ...
    It seems some guys are still in denial about this (or maybe they have two quad processors and 16 GB of RAM):
    But it's a fact: LR has a hard time with localized adjustments. There must be by now 100's of complaints to that respect, and that can't be dismissed by blaming it on the hardware specs alone.
    I just hope Adobe is working on that.
    LR3 is a fantastic program that I would not want to work without. Often I have to work on a lot of photos with a very tight deadline. Without LR it would be impossible.
    Thank you,
    ErnstK

    You are right Samoreen.
    I posted my above message in July 2010 and this topic has been re-opened by Adobe under the thread Lightroom 3.3 Performance Feedback
    I think it would be best if everybody would post their concerns only under this thread.
    Otherwise we'd have two different threads for the same issue.
    So let's close this one here.
    WW

  • [FIX] Darker prints and color shifts when printing from Lightroom 2

    Hi,
    The problem :
    When printing RAW or TIFF files from LR2, you get a printer output that
    is much darker than it should be and that presents various color shifts.
    I'm using an Epson Stylus Pro 3800 with the latest Windows driver
    (6.50 - which is rather old by the way). The workaround described below
    works for me under Windows XP SP3. It should also probably work with
    other systems/printers/drivers. Use at your own (minor) risk.
    The "official" procedure for printing from LR is as follows:
    1. Do not let the printer manage colors and select "Other..." from the
    profile dropdown list and select the ICC/ICM paper/printer profile that
    you want to use.
    2. Click on Print... in LR which opens the Print Settings dialog.
    3. Select the options you need and the paper you're using.
    4. **Disable the color management from the driver's side** (in Epson's
    drivers, "Mode | Custom | No Color Adjustments").
    5. Print
    Unfortunately, **this doesn't work** for many of us and this produces a
    print that is dark and has color shifts as mentioned above. Note that
    the same image prints correctly from QImage or Photoshop CS3 (that is,
    the printer output corresponds to what you see on your calibrated
    display).
    Apparently, although color management has been (allegedly) disabled in
    the driver, there's something wrong between LR and the driver which
    makes that *both* LR and the driver are still trying to manage colors.
    In other words, the "No Color Adjustements" option of the driver doesn't
    seem to work with LR.
    The workaround (found after hours of hair pulling and paper and
    expensive ink wasting):
    In step #4,
    1. Instead of selecting "No Color Adjustments", set Mode to "Custom |
    ICM
    2. Click Advanced...
    3. Check "Show all profiles".
    4. Select Driver ICM (Advanced)"
    5. Set **both** the "Input profile" and the "Printer profile" fields to
    the very same profile that you specified in LR.
    That is, if you specified Pro38 PGPP (Premium Glossy Photo Paper) in LR,
    then also select Pro38 PGPP in both "Input Profile" and "Printer
    Profile". This has actually the same effect has disabling color
    management in the driver (what "No Color Adjustements" should normally
    take care of).
    That's it. When printing, you'll get exactly the same color results as
    when printing from QImage or Photoshop. No more dark prints. No more
    color shifts.
    One might think that the bug is in the Epson driver but in that case,
    QImage would have the very same problem. So I tend to think that the bug
    is on the Lightroom side.
    Note: Although Photoshop CS3 produces a correct printer output, it
    demonstrates the same problem as LR when using the "Match Print Color"
    option for soft proofing. But in that case, only the preview colors are
    wrong. The printer output is ok. Which also tends to demonstrate that
    Adobe has the problem, not Epson. Or maybe both... :-) .
    Don't ask me why some users have the problem and other don't.
    Hope this helps.
    Patrick Philippot
    MainSoft Consulting Services
    www.mainsoft.fr

    A sincere thank you for your reply, Michael. Sorry about the "it just doesn't make sense" shortcut. I have been trying to solve this issue since LR 1.1, spending dozens of hours on different trials and digesting everything written on this forum and the B9180 forum about color management and double profiling. My shortcut was a summation of my experience (and my frustration) but doesn't really advance the conversation. Here are some data that should be more useful in diagnosing the problem.
    I am running Windows XP SP2. I calibrate my monitor monthly with the Spyder. The reason I suspect this may be an issue of double profiling is because the results (moderately strong magenta overlay plus an increase in contrast) match what more knowledgeable people than I on this forum describe when double profiling occurs. Perhaps I shouldn't presume it is double profiling, and follow Patrick Philippot's lead in naming the problem "color shifts." Patrick does refer in post #2 of this thread, however, to obvious double profiling.
    I certainly do have a successful and consistent print method. With PS CS3, and either my Epson 1280 or my HP B9180, the output is almost always dead on. Here is how I do it. In PS from the print dialog box, under color handling I always choose "Photoshop manages colors." Then under printer profile I select the profile designated by the manufacturer for a particular paper/printer combination. Then in the printer driver I disable printer control of color. With the Epson I check the box "Off (No Color Adjustment)." With the B9180 I choose the option "Application Managed Colors." While I sometimes may tweak the final output, these procedures have served me well with PS for several years.
    Contrasted with my positive PS experience, my experience with LR printing has been inconsistent. I regret having to be so imprecise but truly sometimes LR produces accurate results that match the calibrated monitor, but most of the time it does not. I use standard procedures with LR that parallel the PS ones described above. In LR's printing panel, under color management, I specify the correct profile, just as I did for PS. Then in the printer driver I use the same procedures I use with PS. Most of the time the prints have the magenta overlay and too much contrast.
    BTW, the inconsistent LR printing only takes place with my HP B9180. I have never had any problem with off-color LR prints with my Epson 1280. Again, I emphasize that I have standard procedures that always work with PS (no matter which printer) and LR (but only with the Epson).
    Unfortunately the LR printing problems are intermittent. Some of the time (perhaps 20%) LR produces fine prints in the B9180, indistinguishable from PS prints. When LR is printing well, it will continue to print fine until "something happens" and the output shows the color shift. This means I do not get a random sequence of good-bad-good-bad prints, but rather good-good-x factor-bad-bad-bad. Ths problem is that I do not know what this "x factor" is. Once, when LR was giving me accurate output, I simply changed the default printer (Control Panel-Printers and Faxes) from the B9180 to my Samsung 1430 laser; immediately afterwards the LR output colors shifted. Did LR react to this change in default printers? Another time I had good LR printing success with version 1.2 but ran into the problems described above when I upgraded to version 1.3.
    Sorry for the long post. I am hoping that someone will see something that I am missing and provide a hint. I think, though, that Patrick is correct when he states, "I tend to think that the problem is with LR. After all, similar issues (obvious double profiling) are observed only in LR but with various printers."

  • Why isn't ratings information set in lightroom showing up in windows explorer file properties?

    I am using Lightroom 3.4 64 bit on Windows7 64 bit.  When I apply keywords and set a rating in lightroom, only the keywords show up in the file properties in windows explorer, and FastStone viewer.  The ratings information is not shown.  Is this a known problem, or is there a way to fix it?

    I am using Lightroom 3.4 64 bit on Windows7 64 bit. When I apply keywords and set a rating in lightroom, only the keywords show up in the file properties in windows explorer, and FastStone viewer. The ratings information is not shown.
    Hmm, are you remembering to do Metadata > Save Metadata To File after you change the rating in LR?
    LR and Windows 7, Vista, and even XP (if you install Windows Live Photo Gallery) share metadata using industry-standard fields, and Windows' manipulation of the metadata is pretty robust.  In particular, they'll share the rating via the metadata field XMP:Rating.  I just verified this with LR 3.4 and Windows 7, but I'm pretty sure it also applies to earlier versions of LR 3:
    1. In LR 3.4, change the rating of an image.
    2. Metadata > Save Metadata To File
    3. In Windows Explorer, right-click the image file and select Properties.
    4. Observe the new rating on the Details tab.
    5. Change the rating on the Details tab.
    6. In LR, do Metadata > Read Metadata From File.  Observe the new rating in LR.

  • "Lightroom has encountered problems reading this photo."

    ***** UPDATE July 17, 2013 @ 9:16 am Central Time (UTC -06:00)*****
    After Creating a fresh catalog I have been able to clarify the issue a bit. This error appears to only show up in Folders exported as Catalogs. Particularly when I try and open that exported catalog.
    I suspect there is a problem with the way Lightroom 5 is exporting these catalogs. I didn't have this issue with LR4.4, but it shows up any time I export a folder as a catalog within LR5, regardless of whether or not it is exported from an upgraded catalog or a fressly created catalog.
    It looks like fixing the problem is going to be time consuming, but not impossible. So far I have confirmed that these files - reported as throwing this error by Lightroom 5 ("Lightroom has encountered problems reading this photo .... You will not be able to make adjustment to this photo.") - can be imported into a new/existing catalog by multiple methods without carrying over the errors displayed in the exported catalog.
    This is frustrating and adds additional steps to my workflow, but isn't undoable. Of course it would be nice if LR5 worked as correctly and exported folders as catalogs without throwing errors when those new catalogs were opened...
    Is anyone else seeing this problem when they open catalogs created by "exporting a folder as a catalog"?
    ***** Original Post *****
    I'm really confused. I am consistently getting this message on certain exports, but not others...
    When it happens:
    1) "Export this Folder as a Catalog" from a specific folder within my Working Catalog
         Select the location
         Select "Export negative files"
    When I open the NEW Catalog - ALL the photos reflect this error message: "Lightroom has encountered problems reading this photo .... You will not be able to make adjustment to this photo."
    When I go to the Develop tab it displays "There was an error working with the photo" over the photo, but I can edit it... When I close the catalog and re-open it, the changes don't reflect UNTIL I go back to the Develop tab, then the thumbnail will reflect the change. But the system still insists that it has a problem with the file...
    2) The same thing happens when I export the file from my Working Catalog as an image of the same format - be it tif, dng, or psd, or RAW files. Not sure what I was refering to here (can't duplicate today - July 17).
    When it doesn't happen:
    When I export the file to the auto import folder for my Portfolio catalog (original format). This seems to work...
    Why am I so confused? Because all of these catalogs are located on the same drive (which is different than the drive my Working Catalog is on). When they are auto imported to my Portfolio catalog they seem to work, but everything else throws an error sinse I upgraded to LR5!
    My System:
    Windows 7 Pro SP1 (fully up to date) 64-bit
    Intel Core i7 CPU 950 @ 3.07GHz
    Installed RAM: 12.0 GB
    My Lightroom 5 Working Catalog doesn't seem to be having any problems...
    This problem is frustrating enough that I may go back to LR4. I can't have my archived files compromised...

    Suggestion to all who encounter problems like this: if you've installed 3rd party memory cards (ram), go back to your original ram, or at least the brand of ram that your computuer came with.
    Long story, short:
    I had the same error message in LR5.  It only happened with several images in a given import.  If I deleted all of the images from the import and reimported the images, a different set of images would have the error message.  The images that originally had the message would no longer have the problem.  I deleted and reimported several times while observing the same behavior. 
    Not only did lightroom give me issues, but Bridge had problems reading the files, and the previews of the problem images would not show up in Finder (Mac speak).  This ruled out, to me at least, that it was a software issue.  I went out and purchased a new card reader and had the same problems.  I tried a different card with different images and got the same problems. 
    After I contacted Adobe, they had me upload two files with the error, and they said the files were corrupted due to faulty hardware.  I took my mac book pro (13in early 2011 w/ 10.7.5) to the apple store and they ran a diagnostic test amoung other test and we came up with nothing.  Everything seemed to be good on the hardware side.  After some research the Rep. asked me about my ram (memory cards).  I had in the past installed two 3rd party cards to boost my ram from 4GB to 8GB. The rep. suggested that I go home and test the issue with the original ram my computer came with before we go any farther.  So far, I haven't had any issues. 
    I hope this helps,
    Josef

Maybe you are looking for