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 ...

Similar Messages

  • Feature Request // Book Module: Export as indd file and management

    Book Module: Export as indd file and management
    I would like to request a feature to export a book module as indd file. 
    I like PDF's but .indd is nice also so we are able to to more in depth layouts.
    Having Lightoom being able to manage all your pictures and book layouts would be nice, alot of things can be done in one application.
    Another Feature:  Using Lightoom as book layout management.
    Being able to send a page(s) of the book from lightroom into InDesign to do indepth layout and editing, then being able to send it back into lightroom
    Almost similar to how you can send a photo from LR in Photoshop to do indepth editing and then send it back into lightroom.
    This could and will ease the workflow of book management and layout design.  So lightroom will not only be able to manage photos, but also indesign and book layouts.
    http://forums.adobe.com/message/4238530#4238530

    Why do repeat it here, as you have already filed a feature request for it?
    BTW AFAIK this is already implemented: you can use Adobe Illustrator or InDesign or Opensource Scribus to edit layouts.
    They are just not ready to publish how - another sign of the quality processes at Adobe.
    But you do not send from the book module.
    You create upfront layout templates, which you can import for use inside LR book module.
    This is a one-way street.
    The book module designers did not acknowledge a use case where you might want to fiddle the exact placement of really chosen images.
    It is always you first design a template, then use it.
    Love it or leave it - *change it* is not an option that Adobe seems to give to their beta testers.
    Cornelia

  • Saturation Loss When Exporting from Lightroom.

    This happens to me when exporting from Lightroom 2 or 3. It happens regardless of the color profile, file format, bit depth, image size, compression, or the method of export. I regularly profile my one-year-old iMac monitor with an Eye One Display 2. My working color space for Photoshop CS4 is ProPhoto. After exporting, I am viewing the images in Photoshop, Safari, Firefox and Apple Preview, with the same result. I have used pretty much all the available export methods in Lightroom, including exporting with Lighroom ad-ons such as SlideshowPro. And, conversely, if I edit an image to my liking ourside of Lightroom, there is a saturation increase when I import it into Lightroom.  The effect tends to be most obvious and bothersome with shots taken outside on sunny days, with lots of blues and greens.  I am shooting raw files with a Canon 5d II and I use the Adobe Standard profile in Lightroom.
    There is a section at the back of Martin Evening's Lightroom book where he talks about the Lightroom color space and Lightroom versus Photoshop curves, which seems to relate to what I am seeing, but I have the feeling that what I seeing is more pronounced than what he is talking about there.  It is a real dullng of the look, not merely a slight difference in how the colors are rendered.

    Looks like Lightroom doesn't like your display profile.
    Try removing the profile (don't know how to do it on a Mac) to leave your display uncalibrated. Are the colors still different in Lightroom and Photoshop?

  • 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.

  • Book Module Export To JPEG Does Not Apply Sharpening

    I'm running LR4.1 on Windows 7 64 bit with 5D MK ii raw images and just discovered the Book module 'Export Book to JPEG' produces files that do not have output sharpening applied.
    Book = JPEG
    Size = Standard Landscape
    Cover = Hardcover Image Wrap
    JPEG Quality = 90
    File Resolution = 300 ppi
    Sharpening = (Every setting produces the same results)
    Media Type = (Every setting produces the same results)
    When selecting 'Book = PDF' the sharpening is very obvious and is applied as expected based on the Sharpening setting:
    Glossy Low = least sharpening
    Matte High = most sharpening
    Maybe I'm doing something wrong since I can't find a single post in the LR forums where this has been raised, but maybe not!
    Can anyone help out or verify?

    Are we looking at printed or screen proofs here?
    Not that I have an answer for you but sharpening might not be visible on screen if that is what you are comparing. Sharpening for print should differ for print processes from sharpening for screen. The 'print' sharpening, presumably for inkjet although it should be for offset, will be related to final image size, so viewing on screen at a potentially different size and resolution might be obscuring what would occur in a printing process.
    I can't verify since I am still using LR3.6.

  • 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?

  • Export from Lightroom: folder not found.

    New Problem with export from Lightroom. I always have to select the folder where to save to, even if it was selected before. This means I have to click on an already activated folder at every export.  Why? This problem wasn't there before.
    I always use the option "choose folder later on" at the export dialog box.
    Error message: "Es wurde kein Zielordner für diesen Vorgang angegeben."
    Thanks for help folks!
    Best
    Bernd

    Normally when Lightroom says "not enough memory", that's exactly what the problem is, you don't have enough memory.
    A partial solution would be to make sure no other applications are running when you do this export.
    The real solution is to make sure your computer has both 8GB RAM (or more) and a 64 bit operating system. One of these by itself without the other will not improve the situation.

  • 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.

  • 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.

  • Exporting from Lightroom to Photoshop.

    I have set the necessary preferences so as to export from Lightroom to PS CC. However when i try to export a file then PS CC fails to open. However PSE 11 opens but with no file! Any help would be appreciated. thanks GM

    Ask in the LR/ PS forums and provide details about your system, your files, your develop settings, other stuff. You need to be much more specific.
    Mylenium

  • 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.

  • Issues when uploading book to Blurb from Lightroom 5

    have Lightroom 5 and a Mac computer
    About a month ago , I uploaded my book to Blurb from Lightroom - no issues.
    Today after taking out a few photos , also removing 2 page spreads , justifying the printed pages to the right instead of the middle of the page -
    The book would not upload - just hung. Contacted my ISP - internet connections have not slowed or changed.
    As an experiment I tried to upload a previous book from last year that successfully uploaded - this time it also hung.   - not error message - When I tried to exit Lightroom I receive a message that it is uploading to Blurb - but nothing happens .  No matter how many times I try.
    Also unable to create a PDF as well - also hangs  - no error message.
    This is the message I received from Blurb: when I contactd support
    Check to see if you are able to create a PDF of the book. If yes,
    If you're on a wireless connection please connect directly to your router/internet connection using a cable instead. This can often be enough to allow the upload to complete.
    Ensure your firewall and/or any security programs are temporarily disabled (Some software with known issues include Zone Alarm, Norton Internet Security and Kaspersky).
    Turn off services such as Carbonite or Little Snitch.
    If your upload fails again, please let me know at what stage it does so.
    Best regards,
    Kristin
    Blurb Technical Support
    My response:
    1.  Unable to create a PDF.
    2.  I do not have a wireless connection / I have an internet connection with a cable
    3.  Do not have firewall / Zone, Alarm Norton Internet security or Kaspersky
    4. Do not have Carbonite or Little Snitch.
    5 The uploading path has a blank with a x at the end
    This is the response I received from Blurb:
    Kristin M ( Blurb Support)
    Jul 25 16:16 (PDT)
    Hi Sue,
    Thanks for your reply.
    I am looking into this and we'll get back to you soon. Thanks for your patience.
    Best regards,
    Kristin
    Blurb Technical Support
    Kristin M ( Blurb Support)
    Jul 28 18:08 (PDT)
    Hi Sue,
    Thanks for your reply.
    It sounds like your best bet is to contact Lightroom support directly from the link below. They should have more detailed information to help you with this problem. (Blurb only handles the actual printing of your file or the conversion into a Blurb ebook).
    http://helpx.adobe.com/contact.html?product=lightroom&topic=using-my-product-or-service
    (Click on the "Need more help" button at the bottom of the screen)
    I'd be interested in hearing what you find out.
    Best regards,
    Kristin
    Please advise
    thank you
    Sue

    I had the same problen with Lightroom 5 - Prepares the files but won't Upload to Blurb. Tried numerours times. It is a Landscape size Book 132 Pages. There is a BUG in Lightroom and here is how I got it to work:
    Check each slide and make sure APPLY BACKGROUND GLOBALLY, GRAPHIC or BACKGROUND COLOR and not checked,. If so Uncheck them.
    Go to EDIT and SELECT ALL Slides in the Book.
    Select Apply Background Globally - turn it off and on several times, then leave it off
    Select GRAPHIC - turn it off and then turn it on and off several times
    Select BACKGROUND COLOR - turn it on then off then on then off
    I ended up with APPLY GLOBALLY unchecked for Every Page.
    GRAPHIC was turned on with a Graphic set at 12% Opacity on every Page
    Again check each page first for these Checkmarks or just fix exverything with SELECT ALL.
    Background Color was Turned off. 
    NOW UPLOAD THE BOOK - It took a couple hours but it uploaded without a hitch., I turned off all Firewalls and Plugged directly into the Router. I am using an IMac 27" with 32 GB of memory and this is the only way it would work. The Mac is about 7 days old and Lightroom 5 is also 7 days old. BUGGIEST piece of software I have ever used.
    Note - one of the above steps fixes the BUG - I am not sure which one but one will fix your book. It finally uploaded to BLURB today. It took a few hours though.

  • 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

  • Special characters issue with Nokia Maps on N95

    Hi there, when using Navigation in conjunction with Nokia Maps on my N95, all streets and towns which contain any special character in their name (for example: é, è, ü, ä, ö, etc-) do appear as unreadable garbage on the screen of the N95. I only noti

  • What's the diff between yahoo / google search?

    There are 2 choices...

  • Convert Binary Data into Pdf & send it as attachment in a mail from R/3

    Hi, Scenario: The interactive form saved in WebDynpro Application is sent to R/3 in binary format. It has to be converted into pdf and sent it as an attachment in mail to the respective person in workflow. Kindly help on these issues : 1. How to rece

  • Unapplied Receipts Amount as of date

    Hi All, I am actually trying to match AR Unapplied Receipt amount against TB. For this I have build a query to get unapplied amount according to receipts, but my total amount was not matching with TB. My Query: select a.* from      (select acra.recei

  • How to lock a user by using random password?

    hello, i need to lock a user from a target system by pushing in random passwords for the accounts. i am successfully able to create an adapter that can generate a random string, but the place where i am stuck is that where to use it as i just need to