Lightroom 5 Exporting and Plugin Issues

Hello Everyone ! I would like to express my gratitude in advance for any advise or solutions the adobe community might provide me with these issues.
I've been using Lightroom 4.3 for the last year with no issues. I decided it was time to try out Lightroom 5 and it's new features. So I installed a trial of 5.6 via creative cloud .  When I launched 5.6 it required me to update my catalog, which I did and didn't encounter any problems with the update.  The first problem I encountered occurred when I attempted to export an edited raw file. The export  progress bar stays at zero and never completes the export process, if it helps anyone , the files I am exporting to JPEG are Raw Nikon D600 files. If I attempt to do anything else while Lightroom is stuck in the export process , the program will become unresponsive and  I'm not even able to kill the process via windows task manager. My second problem is the Plugin manager , on Lightroom 4.3 I use the Smugmug upload plugin . On 5.6 the plugin manager crashes every time I attempt to setup the Smugmug plugin. I've tried other third party plugins and those cause Lightroom to crash as well so I don't believe it's just the Smugmug plugin. I've tried every possible solution I was able to find doing web searches but nothing has worked so far...
The following is a list of steps I took to try to resolve the issues.
-In the export screen I made sure that "Do nothing" was swtiched to "go to explorer" in post processing
- uninstalled all plugins
- Unistalled and reinstalled Lightroom 5.6
-Uninstalled Lightroom  4.3 (perhaps a conflict ?)
-Created a new catalog and imported new files to that catalog
-disabled firewall and antivirus
- Tried various JPEG re-sized dimensions
- Tried to export to various Drives ( local, and external drives)
-Ran Lightroom 5.6 as an administrator
-Deleted Preference File
Hopefully everyone can see I've tried my best to find a solution but to no avail , it's quite frustrating since I really want to upgrade to 5.6 .  I hope someone can provide a solution or point me in the right direction ! Sorry if this post is too long!
Computer Specs
-Windows 7
-Intel I7 processor
-12 gigs of Ram

I never had a problem with it in LR4. The example I gave was one of many options I tried. At the other end I asked it to produce smaller files (eg 1500pixels long edge) with a 1000k maximum and I could only get them to output at around 160k.
I have since realised that I neglected to mention that I was using LR/Mogrify2 plug in to add a text graphic to the images. I experimented with turning that option off and I was able to produce a 2500px long edge file at 996k. As soon as I turn that option on again the file ouptuts at 1600k (where I have specified at 1000k limit).
This was never a problem with LR4 so there is a conflict or a bug somewhere.
Is anyone else using a LR / Mogrify 2 plug in and experiencing unpredictable results? I have the option to use LR / Mogrify 2's version of ImageMagick checked.
Message was edited by: Shipp
So I just did further testing. It seems that LR5 cannot control the maximum file size when working with Lr / Mogrify 2. If I ask the plug in to resize the image and control the maximum file size I can produce a file with long edge 2500pix, 1000k maximum size and the text graphic with no problem at all, as I used to be able to do with LR4. I will contact the plug in developer and see if they are aware of this.

Similar Messages

  • Standard and Non-standard exports and queries issue

    Hi,
    We have created a few STANDARD books with standard exports in them. The standard exports use standard queries.
    The ISSUE is that in the Verifications/Filters tab, where we have put in a lot of queries - ONLY the STANDARD queries show up. We would like to have all the queries show up. I am the adminsitrator and still only the standard ones show up.
    I am worried that if I "Save As" the export as a non-standard export, it does not allow me to uncheck the standard tick column and save it but I have to manually change the name of the export. Can we change this in anyway?
    Is there a system preference where I can allow all the queries to show up in the verifications/filter tab at least for the admnistrators if not for all? Thanks
    - Ad

    Thanks for your input but DRM does seem to be behaving what you said or may be I am still missing something here.
    I created a standard query.
    I have a standard export.
    Now, in the verification/filter tab of my Standard export, I am able to see my standard queries.
    But,
    I am unable to see the Non-Standard Queries.
    HOWEVER,
    If I have a Non-Standard export --> I am able to ALL the queries. This makes it a lot more flexible in doing things.
    My question is the WHY are my standard exports not able to reach the non-standard queries. What I wanted to do a twist in my export for analysis purposes for a particular use. If non-standard exports have access to Standard and Non-Standard queries --> it just makes more sense to always use a non-standard export and create non-standard queries.

  • Lightroom 3 Export to JPEG issue ( please help) (photo attached)

    Hello,
         I have been going crazy trying to solve this issue and can't find a solution. I am using Lightroom 3.4.1 on a Mac running 10.6.7. In Lightroom I am editing raw images from a Canon 7D. I tweak and adjust the images to my liking but when I export them as a JPEG at full quality using color space sRGB my jpegs do not look like my adjusted photos in Lightroom. The biggest missing factor is all my "detail" adjustments. Sharpening ect. The colors are slightly less vibrant but the huge issue is the sharpening I do that disappears. Can anyone help me with this? I will supply an example below. On the left is the jpeg and on the right is the grab from Lightroom. I am viewing the jpegs in preview and don't have photoshop. Thanks in advance for any help!

    When you export from Lightroom and you do not select the resize option, you will get the full resolution from your original image. This contains far more pixels than your screen can display as displays are very low resolution devices (typically only around 100 ppi). When you open the resultant jpeg in an image viewer, it will have to downscale from that. Usually many times. This necessarily introduces blur and the result will strongly depend on the chosen scaling algorithm. Lightroom uses a fairly good one to downscale and it shows you a preview of a properly output sharpened image at the size you are looking at. Preview uses a particularly bad one. In preview if you want the screen pixels to correspond to the image pixels, you need to hit apple-0 (or use the view menu and select "actual size"). In Safari and Firefox, you need to click on the image to zoom in to actual pixels.
    Your comment also makes me realize that you do not really understand the sharpening in Lightroom. The detail tools in Develop are meant to optimize what is called capture sharpening. These should NOT be used to optimize sharpness at the fit view level, but only at the 1:1 view level. They operate basically on the image to correct for image blur that comes from the sensor's antialias filter and for a small amount of lens blur (say when you are diffraction limited owing to use of large f-numbers). Do not zoom out and play with the detail setting. Zoom into 1:1 on certain areas and optimize the sharpening. There are many tutorials on the web that explain this. Then when you go to output your image, you need to apply another sharpening, called output sharpening, at the final size, in order to correct for blur introduced by the output medium such as a printer or a display and by rescaling the image. The print panel has this built in. In the export panel, the options are in the lower tabs. You need to rescale the image to your final size (for example, a 533x800 pixel image is typical for a good web sized image). Then also apply the correct output sharpening in the tab below it. Typical would be to sharpen for screen at a standard amount. I showed some comparisons on this around the LR 2 timeframe here: http://lagemaat.blogspot.com/2008/08/on-output-sharpening.html The output sharpening has improved by quite a bit by now from those examples, but they show the general idea.
    Hope this helps.
    Jao

  • Lightroom 2 colour difference in lightroom vs. export and print

    Hi,
    I am currently using Lightroom 2 and Windows Vista, monitor profile is Dell's E248WFP Color profile.
    The problem I have is that everything looks fine in lightroom, I was able to see the black backdrop with some defining detail on it. However, when I export the photo (export colour space: sRGB) and view it, the photo darkens, I could no longer see any detail in the black backdrop (I've tried othercolour space like the adobeRGB but results is the same). I understand that there could be difference using Windows viewer as someone has pointed out to me. I tried importing what I've just exported from lightroom back into lightroom and I could see all the original details.
    So I am guessing it's just an issue with windows viewer not able to display all the colours intended. I than send the file to "Blacks photography" (photo developing store) for printing and the same issue exists, it's darker than what is displaying in lightroom. Could someone please point me to the right direction?
    Thanks in advance for your help!
    Gi

    Hi,
    Thanks for the advice, I bought a Spyder pro 3 thinking that might solve the problem but I think the problem is what is being exported? (not sure)
    Photo looks good in LR but after exporting, open the file and looks different in windows photo gallery than what's in LR.
    So I tried looking at the exported jpg in LR and it looks good in LR. I assume that's normal as people has mentioned that LR will display more colour and do it correctly. The problem for me than is printing. I send the photos to local photo processing stores and the colour is still off. Sorry for the ramble but here are some of my questions:
    I assume it's completely ok that photos look different in LR and windows photo gallery (or even other viewer).  As look as it looks ok in LR than it's fine?
    Is the problem with a low quality monitor (Dell's E248WFP)?
    I might not be calibrating it correctly? (will try again)
    Thanks again!!
    Gi

  • Export and Import issue in Oracle 11g

    Hi All,
    I have exported data using exp command in oracle 11g by keeping deferred_segment_creation FALSE.
    Even then my zero records tables are not coming in export.
    What could be the reason or what other thing i have to do to make it work.
    Thanks in advance
    Mohsin J

    Tables that were created before you changed deferred_segment_creation to FALSE and do not have any rows would still be segment-less tables --- i.e. not exported.
    You need to issue an "ALTER TABLE tablename MOVE" for each of such tables (after having set deferred_segment_creation to FALSE) to force a rebuild of these tables with segments before the export.
    Thus, the sequence is
    1. set deferred_segment_creation to FALSE
    2. identify all tables with 0 rows
    3. issue an ALTER TABLE tablename MOVE for each of such tables from step 2
    4. Re-run your export
    alternatively use conventional export (exp) instead of datapump export.
    Hemant K Chitale

  • Exporting and YouTube Issues

    So frustrated. For 6 months I have been able to export my iMovie videos to YouTube, no problem. I have also been able to export my iMovie videos into QuickTime format so they can be viewed on PCs without having to import them into iDVD. Now all of a sudden i can do neither. What is going on...seriously?
    Anyone have a fix for either of these issues?

    What happens when you try to share to YouTube? Is there an error message?
    If you are still experiencing failures you might want to try (as a test) creating a new YouTube account and exporting one of your projects to the new account. That would help narrow down whether the problem is with iMovie or with your older/existing YouTube account.

  • PPRO CC 2014 CRASHING, EXPORTING AND RENDERING ISSUES

    So Im finally back on track and working well except for the sequence thumbnail regeneration issue.
    Once I started rendering in Software vs OPENCL including projects already rendered in OPENCL I was able to EXPORT again,
    Render without issues and a heck of allot less crashing.
    I also had to go back to Pluraleyes 3.0 vs 3.5 because it was so unreliable.

    Hi,
    Please go to following location move the Adobe folder to desktop,
    User Library >> Application support>>
    User Library>> Preferences>>
    Make sure you're in user library not in system Library.
    Access hidden user library files | Mac OS 10.7 and later
    Please rename the Adobe folder in documents to old.adobe
    Now try and launch.
    Hope that helps.
    Thanks
    Mohd Naseem.

  • Export and import issue

    I would like to copy a materialized view from one database to another with data.
    I used datapump .I did the export as follows:
    export ORACLE_HOME=/oracle/product/10.1.0/db_1
    export ORACLE_SID=orcl
    $ORACLE_HOME/bin/expdp system/orc8737 tables="PIMS_REPO".\"DW_V_SELECTION_TXN_QSIII\" directory=DATAPUMPST dumpfile=expdp_txn.dmp logfile=expdp_txn.log
    expdp_txn.sh (END)
    I did the import as follows:
    impdp import_user/twoseven27 directory=datapumpst
    dumpfile=expdp_txn.dmp logfile=impdp_txn.log
    But it got copied as table and not as materialized view. I thought datapump can transform a materialized view to a materialized view.
    Can someone tell me what is wrong with the syntax.
    Thanks in advance.

    Thanks for your reply.
    But when I use
    $ORACLE_HOME/bin/expdp system/orc8737 directory=DATAPUMPSTEVE dumpfile=expdp_txn.dmp logfile=expdp_txn.log schemas=PIMS_REPO include=DW_V_SELECTION_TXN_QSIII
    it gives
    ORA-39001: invalid argument value
    ORA-39041: Metadata filter has no selectivity.

  • Lightroom catalog export and re-import

    I am not new to Lr, and I do know how to export catalogs, or collections, etc.  However, what I am concenred about it is exporting, lets say a collection "as a catalog" and taking it to another computer for edits, then bringing it back to the origianl computer or hard drive.  My concern is in how it comes back to the original computer.  Is there a way to do this so that it goes right back exactly the way it was before I exported it?  I don't want the edited collection to come back as a new or separate collection.  Is this something that can be done?
    Thanks a lot.
    Richard

    Thanks for your response.  What I'm essentially wanting is for the new edits to go into the catalog and after that there being no indication there was ever an export/import... In other words my folder structure on the master computer to look the same.  Also, is it true that once the edits are imported back to original computer/catalog - the raw image files that were originally exported as part of the "export as catalog" can be deleted as they are now just dupes, or extraneous?
    Thanks again.
    Richard

  • Exporting and DVD issues

    Hello,
    I have been trying for over a week to find a decent way to export my 54 minute film without a loss of quality without success! I have tried exporting as a quicktime document, exporting through compressor, sharing, exporting as an avi file: no go: I always get a crappy quality! I tried burning a DVD directly throught the "share" option but also got a lousy result. DVDs that are as high quality as the original films exist!!!! How can I do this with FCP 7.0.3 ???????? I would like to send my film to destivals and people are wanting to project it in public debates, including in theaters. So I really need a high quality export/DVD. HELP!!!!!!!

    Big studio DVDs look that good because they:
    1. utilize dedicated hardware to do the conversion to mpeg2
    and
    2. have a staff of wizards running the system that understand the dark magic necessary to do good compression.
    Converting from HD to the standard definition size that is DVD is always going to look worse than the original (on the assumption that the HD was well exposed, sharply focused, etc).
    If you start with HDV, the problems become worse.
    Try this:
    If you have not editied in a ProRes codec based timeline, do so.
    Export the ProRes based file from FCP using "current settings". This will export a file at the full HD frame size and frame rate.
    Open up Compressor and convert the HD ProRes version to a standard definition ProRes version with FRAME CONTROLS set to BEST.
    Once you have the SD ProRes version, use Compressor again to create the m2v and ac3 files necessary to build and burn a DVD.
    With a less than an hour project, I'd try encoding with a constant bit rate set at 7 and see how things work.
    x

  • After Effect cs4 export and render issue

    When I tried to render or export a video, After Effect(CS4)
    become no respond and close,after that, my computer shut down too!
    My computer:
    Althon 64X 4600+
    2GB DDR2 Ram
    ATI HD5870 (500mb video Ram)
    Windows 7 32 bit
    Can anybody can slove this problem for me?

    Mylenium asked very pertinent questions.  I'll make some educated guesses, which may or may not apply.
    First thing: 2 GB may seem like a ton of memory to you, but in AE-Land, it's NOTHING.  You need to trick that machine of yours out with memory.  On a 32-bit system, that would mean bringing it up to 4 GB.
    If you're trying to use multiprocessing, turn it off and leave it off.  On a 32-bit system, you'll never have enough memory to make multiprocessing work efficiently.
    Trying to speed rendering by using Open GL acceleration?  Turn that off, too.
    Since you're on a 32-bit system, the most recent version of AE you can run is Version 9.  Make sure it's fully updated. 
    But if you shot video on a DSLR, HDV Camera, XDCam or Flip Cam, you could still have problems.  Since you can't be running AE 10, which pretty much solved the problem of long-gop footage, here's why:
    Dave's Stock Answer #1:
    If the footage you imported into AE is any  kind of the following -- footage in an HDV acquisition codec, MPEG1, MPEG2, AVCHD, mp4, mts, m2t, H.261 or H.264 -- you need to convert it to a different codec.
    These kinds of footage use temporal, or interframe compression. They have keyframes at regular intervals, containing complete frame information.  However, the frames in between do NOT have complete information.  Interframe codecs toss out duplicated information.
    In order to maintain peak rendering efficiency, AE needs complete information for each and every frame. But because these kinds of footage contain only partial information, AE freaks out, resulting in a wide variety of problems.
    I'm a Mac guy, so I like to convert to Quicktime movies in the Animation or PNG codecs; both are lossless.  I'll use Apple's Compressor, Adobe Media Encoder or Quicktime Pro to do it.

  • Lightroom PSD export inconsistencies and other quirks...

    We are  a  professional imaging organization,  photoshop and lightroom experts (well, at least to our clients we are ..LOL)     We have been battling two very troublesome problems they seem to have been present in every version of LR3 we've used and its getting to the point where its costing us a lot of time so we'de like to address  it if we can.    I suspect its in the  code,  but perhaps its something more obvious...
    For starters, here is our workflow:   1>  Import to DNG,  2 > Adjust  3>  Export as PSD ProphotoRGB    
    We then do our creative work on the images and  use layered PSD files for our intermediate archives (DNG are the originals as shot).  We use Photoshop to size, sharpen and export to final sized JPG  for agency submission.  
    That said,
    Problem #1>    When we  open the PSD files in photoshop (after exporting from LR3)   they are ALWAYS  dimmer, in fact,  we have to go into levels on each and every image and bring the far right slider over to where the  histogram curve starts so that we can recover the luminance.  In other words, if you are looking at the levels histogram in Photoshop,  there is a flat spot on the right hand side.  We end up moving the slider over to pick up the low edge of the "bell curve".      In some cases, this flat spot is severe.       NOT GOOD, we lose shadow detail doing this and quite honestly its  real PITA in terms of time wasted.   
    We notice in general, that even within the same color space, images do not look the same in Photoshop as they did in Lightroom.    That is an issue, they should at least look very close.  
    Problem #2>   When applying an Auto Tone (in develop)  to an image initially  we understand what its doing - setting white and black points -   but in just about  every case,  it applies WAY TOO MUCH contrast.   Again, we always have to slide the contrast slider over  to bring it within our tastes.    We wrote a preset to zero the contrast  but we should not have to do that ?   Is there a way of shutting the contrast off in Auto Tone ?    Its very annoying...
    So anyway, we love LR3, but those two issues are severely limiting our workflow...     any ideas, hints or other suggestions ??
    Thanks,
    Mark

    We notice in general, that even within the same color space, images do not look the same in Photoshop as they did in Lightroom. That is an issue, they should at least look very close.
    I agree with Jeff. Other forum members who have posted with this issue have had a corrupt or incompatible monitor profile. Issues that can cause this are hard drive file corruption, defective calibration puck device, and using monitor calibration software that creates ICC v4 monitor profiles. LR has issues using ICC v4 profiles and it is suggested to always use ICC v2.

  • I am currently using Lightroom 5.6 and operating on a Mac with OSX Ver 10.9.5. I am receiving an error problem when doing the following -  I am exporting selected photos from a particular Catalogue saved on Drive 1 to a folder created on another Drive whe

    Hi, I am having a little trouble with exporting images to another drive and Catalogue and need some help if anyone can give me some advice
    I am currently using Lightroom 5.6 and operating on a Mac with OSX Ver 10.9.5.
    I am receiving an error problem when doing the following -
    I am exporting selected photos from a particular Catalogue saved on Drive 1 to a folder created on another Drive where a Lightroom Catalogue has been created. In this Catalogue I have arranged for the images once exported to be moved to a different folder - I used the Auto Import process under the File dialogue box.
    When processing the Export I receive an error message for each of the images being exported indicating the following -
    Heading Import Results
    Some import operations were not performed
    Could not move a file to requested location. (1)
    then a description of the image with file name
    Box Save As                                  Box  OK
    If I click the OK button to each image I can then go to the other Catalogue and all images are then transferred to the file as required.
    To click the OK button each time is time consuming, possibly I have missed an action or maybe you can advise an alternative method to save the time in actioning this process.
    Thanks if you can can help out.

    Thank You, but this is a gong show. Why is something that is so important to us all so very, very difficult to do?

  • I have Lightroom 4.4 and a Nikon d800 with firmware upgrade 2.005. raw files are now since upgrade, unreadable. any plugins or advice? Thanks

    I have Lightroom 4.4 and a Nikon d800 with firmware upgrade 2.005. raw files are now since upgrade, unreadable. any plugins or advice? Thanks

    I select the images I want uploaded, NEF files, click the "IMPORT" button, process bar comes up and shows work in progress, but no progress. after about 2 minutes, dialogue box appears with message: "unable to import because the following files are unreadable: NEFxxxx, etc."

  • Lightroom export and copyright symbol

    Why copyright symbol ©  from my metadata preset looks like (c) in the  properties menu of the file after exporting photo? ( I can see this (c)  in the properties menu- summary of the file)
    I'm using Lightroom 3.2. and Windows XP.
    Thanks.

    EXIF only allows for ASCII-encoded 7-bit NULL-terminated strings, so the © symbol cannot be represented.  So LR needs to change it  to *something*. It is debatable if the (c) is the right thing to change to, as the US Copyright office only seems to recognize the symbol © or the English word "Copyright". Other countries may vary.
    Beat Gossweiler
    Switzerland

Maybe you are looking for