As with others I can't export from Lightroom 4 to Elements 10 or any of the Nik products except HDR

As with others I can't export from Lightroom 4 to Elements 10 or any of the Nik products except HDR Efex pro. Surely this has been fixed? If not it is appalling. It has been going on for too long in a program that has supposed to have some integrity

I am able edit pictures in PSE (Photoshop elements) 10 BUT i am unable to edit videos in PRE (premiere elements) 10. I will uninstall LR 4.1 RC1 and then install RC2 and use a backup of the catalog. Lets see if that works.

Similar Messages

  • Can't export from Lightroom 4.3 -

    Tried TIF,  JPG and web gallery.  I get the message, "file could not be written".  Just upgraded to 4.3 and I can't export any files.

    Hi there,
    Have you been in touch with Adobe through a web chat?  That seems to be your best course of action.
    I upgraded about a week ago and all the setting for export that I had been using on Lightroom 2 stayed the same and contnued to work.

  • Can I export from Muse cc with out java script coding?

    How can I export from Muse CC with out Java Script Coding?
    I'm trying to create an custom email but email won't recognize Java Script, Only HTML.
    How do I export my tample from Muse CC using only HTML coding?
    Thanks in advance.

    Hello,
    It is not possible to selectively export only part of the code for the exported page(s). The pages that are exported, all the code for them is exported, and there's no way to export only the HTML and leave out the rest of it.
    Cheers
    Parikshit

  • JPGs exported from Lightroom 5.6 will not open in other applications

    Recently I have noticed that jpgs exported from Lightroom 5.6 can not be opened in Canon DPP 3.14 and can not be resized using Image Resizer plugin. Both of these I use frequently.
    I have seen mention of this issue re other applications also. Does anyone know if there is a solution?
    I am using Windows 8.1 64bit. 5D Mark ii

    This was an issue with 5.5 (the placement of some of the internal headers of the jpgs was changed and some other applications, including DPP, could not open them), but was corrected in 5.6. I just checked on it by exporting a jpg and opening it with no problem in DPP 3.14.15, Windows 7 x64. Are your jpgs old ones from LR 5.5?

  • What format of photos and videos can i export from my computer to my iphone/ipad?

    Hi,
    what format of photos and videos can i export from my computer to my iphone/ipad?
    Also i have a problem with Imessage from my Iphoe 4S and Ipad that some of my contacts althought they have activated Imessage from their product i cannot send them any Imessage.
    Kind regards.

    Regarding the supported formats for syncing from a computer to the iPhone, the following information is from http://support.apple.com/kb/ht4236
    On a Mac, these file formats will sync from your iPhoto library to your device:
    BMP
    GIF
    JPEG
    JPG
    JPG2000 or JP2
    PICT
    PNG
    PSD
    SGI
    TIFF
    On Windows, these file formats will sync to your device:
    BMP
    GIF
    JPEG
    JPG
    PNG
    SGI
    TIF
    TIFF

  • Can't log in with valid password, can't boot from disk, can't access disk utility, in single user mode can't reset password as appears locked in caps mode with '?' for forward slash, can anyone help?

    Can't log in with valid password, can't boot from disk, can't access disk utility, in single user mode can't reset password as appears locked in caps mode with '?' for forward slash, can anyone help?

    Which keyboard layout you were using? German, French ... I suppose your layout is reset to the default: US and you are unable to find the "?" or "/" ...
    Please have a look into the keyboard viewer, to see how the layout of your keyboard is actually.
    marek

  • I cannot export projects from GB in my MacBook into GB on my iPad3; nor can I export from IPad to my MacBook. I have tried going onto Apps update on the MacBook, but there were none available. I have read that this omission is to be corrected - can you co

    I cannot export projects from GB in my MacBook into GB on my iPad3; nor can I export from IPad to my MacBook. I have tried going onto Apps update on the MacBook, but there were none available. I have read that this omission is to be corrected - can you confirm this is intended to happen, or is it already in process. While awaiting for this essential development, can you please suggest any way of transferring information either way?

    spicer_the_coalman wrote:
    I cannot export projects from GB in my MacBook into GB on my iPad3
    http://www.bulletsandbones.com/GB/GBFAQ.html#exportgbxtogbi
    (Let the page FULLY load. The link to your answer is at the top of your screen)
    spicer_the_coalman wrote:
    nor can I export from IPad to my MacBook.
    http://www.bulletsandbones.com/GB/GBFAQ.html#exportgbitogbx
    (Let the page FULLY load. The link to your answer is at the top of your screen)

  • I have a problem that I can not load or even close the download in iTunes, it turns out I have hanging in the mode, and because of that I can't download from AppStore, because it turns out that the other programs I have on standby. What do I do? Thank you

    I have a problem that I can not load or even close the download in iTunes, it turns out I have hanging in the mode, and because of that I can't download from AppStore, because it turns out that the other programs I have on standby. What do I do? Thank you.

    If there are multiple apps trying to download at once, only one can download at a time and the rest say "Waiting" until it is then their turn. Try this. Double tap the icon of the Waiting app, and it should resume the download.
    If that doesn't work:
    •  Log out of your iTunes store account.  Go to Settings > Store > Sign Out Then press the Home button.
    • Then press and hold the Home and Sleep buttons simultaneously and don't release them when it brings up the Turn Off screen; keep holding them until the Apple logo appears.
    • After restart, the Waiting should be gone.
     Cheers, Tom

  • Trouble exporting from Lightroom 4

    While trying to export from Lightroom 4, I was getting the error message "An internal error has occurred:WIN32 API error 2, etc.   Others have asked about this and the solution offered was to check "Do Nothing" in the post processing box, which I have done.  Now I can export, but the image is severely downsized from being a full sized jpeg.  How do I get it to export at full size?   All was working fine with exporting until today

    Thanks...the quality slider was at 60 - moved to 100 and it solved the problem.  Simple - Thank you for suggesting - I was getting a headache trying to solve my issues today!

  • Why do my pictures become blurry after exporting from lightroom 5?

    My pictures become somewhat blurry or not as sharp after I export them from lightroom 5. PLEASE HELP!!!

    If you are looking at your exported pictures in preview.app than that is the culprit. It uses an extremely poor downscaling algorithm for displaying large images and will make every large image, no matter how sharp originally, display blurry. In preview you can hit command-0 (that's a zero) to make the image display 1:1 to see the actual detail. Make sure you have it's preferences in the images panel set to "Define 100% scale as 1 image pixel equals 1 screen pixel". I think in older Mac OS X versions, it was called something like ignore image dpi for display or so but I don't remember. You can also make sure to downscale (with correct output sharpening in the export panel) upon export from Lightroom. If the exported image is smaller than the display, Preview should display 1:1 by default upon opening.

  • Book Module: exporting from Lightroom as a 2 page spread

    Hello Lightroom people,
    I have begun to create my albums in the lightroom book module, and I am about 85% happy with it. I have one major complaint, and I'm wondering if it can be corrected:
    My album company wants me to submit my album pages as two page jepg spreads. For example, if I am making a 10" x 10" book, rather then submitting pages 1 and 2 as two 10" x 10" jpegs, they require a single, 10" x 20" jpeg that is then printed as pages 1 and 2.
    When I export from lightroom, it exports instead as single pages (to use the example from about, two 10" x 10" jpegs for pages 1 and 2). I've noticed that if I design a 2 page spread--then it will export that the way I want it, but obviously no album can have all  2 page spreads.
    My work around for this is to import the jpegs in photoshop and lay the pages together the way my album company likes, but this is somewhat time consuming.
    Is there a setting in the book module I am missing that could correct this?
    Thanks,
    Ellen

    JimHess wrote:
    The book module is designed specifically to work with Blurb.
    Which was the biggest error in decision making Adobe made in going forward with the book module ... it should have never been tied to ANY single vendor ...
    JimHess wrote:
    I just export copies of my images and use the software provided by the book company to create my books.
    Yes, there is always a workaround, though Lr was supposed to simplify the process, not create more work ... though if we were discussing having to export images ... THEN ... send them to a printer instead of printing them directly in Lr ... there would be much more discussion about the problems the Book module poses for many users ...
    If I must export images and use outside software to finish the job (InDesign or otherwise) I may as well give up Lightroom as a "workflow solution" ... I could get the same job done working with Bridge/ACR/Ps workflow ... however ... I bought into the paradigm of Lr being the answer for RAW processing to output workflow ... though Adobe seems to pick and choose which features they really care about ... If Adobe is going to include a Book module, and expect me to financially support the effort ... they could at least offer a module that is functional without being tied to a single vendor ...

  • Saving PSD files after exporting from Lightroom saves incorrectly

    I've only recently moved to Lightroom from using Photoshop/Bridge together, so I'm not 100% sure how saving files exported from Lightroom should go. But here's what I experience:
    Base edit of file within Lightroom
    In library view, right click on image -> Edit in -> Open as Smart Object in Photoshop
    Perform all my necessary edits and such
    File -> Save As, and save it to another location as a PSD file (totally different HDD)
    Perform more edits....
    Shortcut CTRL+S to save, and it saves it as the TIFF file under the location it was originally in within Lightroom
    Eh...? Am I missing something. It should just save as the original PSD I created when I went "Save As". I have seen on a few occasions, immediately after "Save As", the file name resorts back to TIFF and not as PSD.
    My settings for External Editing in Lightroom are as follows:
    File Format: TIFF
    Color Space: ProPhoto RGB
    Bit Depth: 16 bits/component
    Resolution: 300
    Compression: None
    Does anyone have any ideas what I'm doing wrong? Also, to note, that sometimes I double click on the Smart Object within Photoshop to load Camera Raw and perform some edits, but not often.

    Modesto Vega wrote:
    Replying to your last 3 posts.
    Re Camera Raw being used to pass an image to Photoshop
    a) I am assuming this is independent of the Compatibility level in Preferences\File Handling DNG creation.
    b) Does the same apply to other photo editing software made by Adobe like Elements?.
    Reply: Yes, the principle is the same. Photoshop Elements cannot read raw data either. That's why it has to be converted before it's opened.
    c) Assume that I have LR 5.7.1 and CS5. Is Camera Raw is still used to pass an image to Photoshop? If so, why is there a need to get LR to behave differently?
    Reply: Camera Raw is used IF you choose the option to open anyway. Then Camera Raw will be used to convert the image that's opened in Photoshop. But since it is older than Lightroom some of the new adjustments might not be transferred to Photoshop. That's why there is a need to let the user make the choice.
    d) Sometimes it does seem as if Adobe might be using Camera Raw updates and process version updates to get consumers to change their habits, this includes having to buy subscriptions or having to change workflow to some ideal that somebody at Adobe or working with Adobe might have in mind.
    Reply: The fact is that in the past, when a new version of Photoshop is released then all support and updates cease for the previous version. Since the introduction of the creative cloud, at least users of Photoshop CS6  get support for new cameras. They just don't get the new features. Yes, there's motivation to upgrade. Adobe is a business. What do you really expect?
    Re stacks
    I find impossible to see collapsed stacks on the film strip. Stacks are only visible on the Library module and using a grid view; I don't say clearly visible because they are only recognisable by the label at the top left corner with the image count; I don't even think it is possible to change the colour of that label or the grey colour surrounding an image. Also I cannot name stacks. If I could name stacks, see them as virtual folders underneath a library folder and make them glaringly visible I would use them extensively.
    Reply: The only reason I can think of that you are unable to see collapsed stacks on the filmstrip is if you have the filmstrip reduced in size to the point that Lightroom can't display all the icons. I'm able to see the collapsed stacks in the library grid view and on my filmstrip
    Re storing your Raw files and processed files in separate locations
    Assuming Raw files are negatives and Photoshop files are transparencies or prints, would you want negatives being handled/read on a regular basis? If anything happens to your negatives, you would never be able to produce another print or another transparency again.
    Reply: The raw files or the negatives, as you put it, are never modified by Lightroom. They always remain in their pristine state they were in when they were imported. If I have a backup of that raw file then I can do whatever I want to the one in my working folder. Resetting that raw file so that it looks unaltered is just a click away.
    I have worked extensively with databases and database systems, it is a standard feature of database systems to be able to choose where to store different database objects. I don't see why LR cannot do the same, it is a database after all. I do agree with both the OP and photo.
    Reply: Well, I won't argue that point. If that's what you really want than lobby for it. It just won't get my vote because I don't see any real advantage.
    If you read back through this quoted message you'll find that my replies are included. I don't know how to separate them out so they are highlighted properly. Read through it and think about it. But personally, I don't want to waste anymore time on this discussion because it isn't accomplishing anything in my opinion.

  • HELP- Exporting from Lightroom 5.0 to iPhoto 9.4

    What is my problem?
    After exporting from Lightroom via export menu I am only seeing certain metadata in iPhoto.   My keywords appear in iPhoto but my ratings are not showing up.  
    Current Process
    In lightroom save all metada data.  Select photos in lightroom (DNG format).  Export ensuring all metadata is sent.  Exporting in JPEG to desktop.   Drop folder into iPhoto.   Keyword are there but no ratings. 
    What should I do?
    I prefer iPhoto for apple tv, iOS devices, links with email, and using in Final Cut.   And general viewing.  
    Adobe please help make this easier for me.
    Otherwise love lighroom
    Thanks anyone who can help,
    J

    attached as 8.2, which you can open
    Attachments:
    BOP488.vi ‏19 KB
    BOP488-w.vi ‏18 KB
    Keithleytest.vi ‏8 KB

  • Prints exported from Lightroom consistantly 1 stop dark!

    I calibrate my monitors regularly and currently have my two monitors set to the absolute lowest brightness point they'll go.
    Everything's calibrated and my histograms look good yet, every time I try to send something out for printing, it comes out at least a full stop dark.
    Conversely, if I print on my own Canon Pixma printer and allow the "printer to manage colors" - things are spot on.
    I don't want to always have to print every little thing at home.  I'd like to send things out sometimes. 
    I do not have this problem with files exported from Photoshop.  Only files exported from Lightroom.   Yes, I know I can fool around with making a brightness preset but why do I have too??  What is going wrong here?
    This is making me crazy.  Help Please!

    IF you're working with an outside lab that doesn't supply an ICC profile for soft proofing, you can pretty much forget about getting a match. Further, the lab has to be using that profile (or let you use it) or again, you're dealing with a lab that has a half baked color management workflow. No wonder you are having good luck printing yourself, you're probably doing everything correctly.
    That's absolutely right. The only consumer oriented big box local lab I have found that does this correctly is costcos and then I understand you need one where the operators have a clue and not every location is good and keeps their machines consistent. The other labs I mentioned all do a great job color managing and I have never had "too dark" prints. The fact that your own printer works fine makes me think that this is indeed very likely a lab problem (not at all uncommon). I would recommend that you print to your own printer while having Lightroom color manage as you should get better quality in subtle color gradients but only do this if you understand the weird codes Canon uses for their profiles and you understand how to turn off color management in the driver.
    That said, you can do a quick sanity check of your calibration by using a printer test file. Andrew has one on his site here that will work fine: http://www.digitaldog.net/tips/  and a nice one from inkjetart can be found here: http://www.kenleegallery.com/images/tech/4800test.jpg
    Load these into Lightroom. Do not touch any develop settings and see if the images make sense on screen. Skin color should look great (not too bright), you should see nice saturated colors and no plugged up shadows. Export these files to sRGB jpegs (they are in a different color space as downloaded so you need to convert for most labs) from Lightroom and send those to your lab. If your prints from these testfiles come back dark, stop using them as they don't calibrate their machines correctly. Well-calibrated machines should give very good prints with tone and color very close to what you see in Lightroom. You can get somewhat better results if the lab provides icc profiles but in my experience, if the machines are tuned correctly you will have a hard time distinguishing profiled images from sRGB images if you don't use a good viewing station.

  • Corrupted EXIF data in photos exported from Lightroom CC

    After upgrading to Lightroom CC EXIF can't be read by some apps. "Re-saving" a file in Photoshop fixes the problem. I'm using Mac OSX 10.9.5. Are there any plans to update and fix the EXIF data generated when exported from Lightroom CC?
    Also, this command fixes the issue with Create Date part of EXIF.
    #!/bin/sh
    exiftool -AllDates="$(exiftool ${1} | grep 'Create Date' | awk '{print $(NF-1), $NF }')" -overwrite_original ${1}
    The reason I'm asking is because we run a site where "Create Date" read from JPG's EXIF is crucial and it's a matter of letting users upload the pic or deny uploading.
    So again, any plans on the fix?
    Regards,
    Pawel Kadysz

    I confirmed that the Exiftool command line:
    exiftool -m -all= -tagsfromfile @ -all:all -unsafe file.jpg
    removes the ICC Profile, which could account for significant color differences, considering that the profile is Adobe RGB.  I think this may be a bug in Exiftool, so I filed a bug report.  (But it might be that Exiftool just can't handle the non-standard layout of LR's JPEGs.)  The author is typically very responsive.
    I tried some alternate Exiftool command lines that touch as little metadata as possible, and this one seems to address both of LR 6's JPEG problems:
    exiftool -m '-exif:datetimeoriginal<exif:datetimeoriginal' -xmp-crs:all= file.jpg
    The -m option ignores minor errors and issues, in particular, when there are more than 1000 entries in the XMP metadata.
    The '-exif:datetimeoriginal<exif:datetimeoriginal'  option sets the EXIF Date Time Original Field with its current value; this tricks Exiftool into rewriting just the EXIF metadata without touching the other metadata segments (e.g. the ICC profile), addressing the first JPEG problem.   (You could use any EXIF field that's present -- I picked DateTimeOriginal since every camera adds that.)
    The -xmp-crs:all= option option deletes all of LR's develop settings from the XMP metadata, addressing the second JPEG problem.That metadata is not ready by any programs other than LR, as far as I know. 
    I've tested this new command line on a couple of pics, including the example you provided above, and it appears to work correctly.  But given that we're dealing with buggy output from LR that doesn't conform to the de facto and de jure standards, it's hard to have high confidence without testing on dozens if not hundreds of pics.

Maybe you are looking for