Get too small pictures when exporting from Lightroom

I shoot in both cr2 (23 MB) and Small-jpeg. Afterwards I upload the pictures to Lightroom and have the appear in the catalog as one picture. Here I make all the editing and when I export the picture back to my harddrive as a jpeg I can only get a file of 3-500 kb. I know I have made some croping - but not that much. It is like Lightroom is working on the jpeg picture and not my cr2 picture. Do anyone have a clue to what I am doing wrong? It may be a setting?

Lisbeth Bech wrote:
Hi
Here is a screendump of the export dialog box
https://www.dropbox.com/s/ht380sf9irk6gmt/Screenshot%202013-11-26%2019 .22.40.png
The size of the cr2 file i 21 MB (and it has a jpeg sister of 930 kb) - and the picture is cropped - but how do I read the cropped dimension? As I am shooting bird picture I normally crop a lot - but my picture are still of an ok size
I can see your screenshot, and looking at the actual pictures that were exported (thumbnails in the filmstrip at the bottom) helps understand why the jpg files are small: your pictures are mostly a smooth blue background (sky) with a tiny bird in the picture. These files are highly compressible in the jpg format, as there isn't a lot of detail in them. I would expect that the resulting file size would be rather small, even if the original files were large.

Similar Messages

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

  • Pictures all grey toned when exported from Lightroom 4.

    They look great in Lightroom and then look/print grey toned when exported, even photos that have not been edited.  Fix?

    Can't think of any ICC profile LR would allow that would produce a grayscale appearing document. Wondering if it's another of those 'corrupted' display profile issues where a grayscale treatment is being applied to the images but in LR it isn't showing? This IS a strange one.
    What if in the Print Module you Save as JPEG, Gray?

  • Receiving an error report when exporting from Lightroom - Why?

    I use Lightroom, always have. Started editing on a new computer (given to me by an associate as my computer has crashed) - the specs are sufficient to run Lightroom, and 9/10 times it gives me an error message that says it can't export photos. Every once in a while it will actually export the photo, but there's no rhyme or reason to it - Please help.
    The error message only says "Not enough memory" - no other details, no nothing.

    Hi,
    minimum requirements are from sales people, optimal ones form the working people...
    Try to close all other (backgroud) programs.
    Which camera you are using? Try to export with diffent settings. (Why only @60 when you want to print?, Why sharpen for Mate if you want to e-mail?) If you want to print, I would use TIFF.  Try to export images in smaler packages (2x 50 pictures, instead of one 100 pictures job).
    Try to disable the wateramarking.

  • Pixelated images when exporting from Lightroom

    I recently switched from A Windows PC to the MBP Retina 15". I imported photos to lightroom from my external hard drive in RAW format to lightroom, edited then exported firstly as jpeg resized to 630 x 420 at 150 dpi. The images came out pixelated so I tried exporting at 300dpi even though the images are for web use. They still came out pixelated. So I tried exporting as .tif files at 300 dpi and still they are coming out pixelated... does anyone know why this would be? The raw files don't look pixelated at all.

    [email protected] wrote:
    I resized this image to 1200 x 800 and have just cropped a section to show you.
    PART I
    Viewed at 100%, I see no "pixelation" or any other distortion of any kind whatsoever.
    Only a 100% view (1:1) shows you your true image.  At smaller percentage views, pixels have to be discarded; at greater percentages pixels have to be made up (invented) by the software.
    With the Retina screen you're bound to see very strange things, unless you're using the latest and greatest versions of Photoshop and of your video card, and utilizing the Retina features of the software.
    PART II
    JPEG is a lousy, lossy format for maintaining image quality.  Every single time you open or create and save a JPEG, the image quality deteriorates, no exceptions.  Even at the highest quality of compression.
    To take a very low resolution JPEG, like you did, and subject it to such a massive enlargement is to ask for demand trouble.  Not only are you also magnifying all the JPEG compression artifacts, but you are "inventing" an inordinate amount of pixels.
    If you have to enlarge your images often, start with an image file that has NEVER been a JPEG.
    PART III
    Photoshop performed superbly in your case.  That is a remarkably fine enlargement, especially considering the miserly JPEG you started from.  Rejoice!

  • Do I get a faulty EDL when exporting from FCP?

    I must create an EDL for a final DI to be made from film negative. When I export an EDL the Source Time Code In of each clip reads the same as the first frame in the clip, then the Source Time Code Out of each clip reads on frame higher than the last frame in that clip. E.g. if one clip ends on a frame with the timecode 02:00:15:01, the EDL out point reads 02:00:15:02.
    Is this wrong? and if so does anybody know what the promblem could be?
    the film is shot on 25 frames per second and the telecined to Pal dv tapes that run 25 frames per second, so that should not be a problem.

    No, that's not a problem, it's just a difference in the way FCP reports timecode numbers and the way EDLs expect timecode to be.

  • Colour shift when exporting from lightroom 5 into Photoshop CS6

    Hi there,
    Having a really weird problem in Lightroom/Photoshop that no amount of Googling can seem to fix.
    When I grade an image for colour in lightroom, and then use the "edit in" function to send the file to Photoshop, the file is a completely different colour.
    Here's an example:
    I'm using SRGB for both Lightroom and Photoshop, and the "preserve embedded profiles" is selected for RGB, CMYK, and gray.
    If anyone can shed some light on this, it would be great. I don't want to have to use ProPhotoRGB, because most of my work is delivered online.
    Thanks in advance
    John

    I am also having this issue with the "Merge to HDR Pro" function in both LR5.2 and PSCC. When the image is viewed at 50% image size in the HDR app everything appears fine. However, once you start to zoom in the image begins to crop out segements starting on the right hand side. See the screen shots below:
    Image at 50%
    Image at 66%
    Image at 100%
    MacBook Pro 2.7 GHz Intel Core i7 16GB RAM 512GB SSD (early 2013) NVidia GT650M Mac OS X 10.9

  • I'm losing date photo was taken when exporting from Lightroom.

    The photo taken date is being replaced with the date that I'm processing the photo with Lightroom.  The photos I'm currently working with were taken over 10 years ago with an early generation Olympus digital camera.  Does this have anything to do with my problem?  I must be doing something incorrectly, can anyone give me advice.  T

    Rob - I am working with old images from an early generation digital camera but yes the image capture date does show correctly in Lightroom for most of these images.  However, I just realized thinking about your question that some of the photos could be scanned from a film image and do not how a capture date in Lightroom.  The exif data is entirely different for these.  The photo processors I used in those days were providing a CD along with the negatives / prints so I may have just answered my own question.  Thanks for the questions and help to both.

  • Optimal photos size for Ipad when exporting from lightroom.

    anyone using lightroom. what are you setting your photos at for the ipad. what is the optimal photo resolution for the ipad?

    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?

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

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

  • I need a picture from an event that I only have video of.  Is there a way to get a jpeg/still shot exported from imovie clip?  I'm a fairly new mac user.

    I need a picture from an event that I only have video of.  Is there a way to get a jpeg/still shot exported from imovie clip?  I'm a fairly new mac user.

    John Codgell has some tips on how to use MPEG Streamclip to do this on this Discussion Thread:
    Helpful AnswerRe: can you make a still photo from clip

  • When exporting from Imovie I get the following error? OSStatus error -2009

    when exporting from Imovie I get the following error? OSStatus error -2009

    Hi
    Apple Support pages says.
    Error 2000-2009 (2001, 2002, 2005, 2006, 2009, and so on)
    If you experience this issue on a Mac, disconnect third-party devices, hubs, spare cables, displays, reset the SMC, and then try to restore. If you are using a Windows computer, remove all USB devices and spare cables other than your keyboard, mouse, and the device, restart the computer, and try to restore. If that does not resolve the issue, try the USB issue-resolution steps and articles listed for Error 1604 above. If the issue persists, it may be related to conflicting security software.
    Yours Bengt W

  • Getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

    getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

    i solve my red frame problem. originally my project was done in premiere pro cc 2014.2 & i render in Encoder cc 2014. in newer version i get lots of red frames. i complain a lot to adobe customer support . they said they know the issues but they couldn't solve. I was so tired from adobe customer support. one of the worse customer services i had. My friend got the mac pro & e got premiere pro cc 7.2 version. i convert all my footage mxf to mp4 in encoder cc 7.2 version and i succeed. i don't get any red frames.
    So i think the problem is in adobe encoder cc 2014.2 version. newer version.

  • Mac Projector Crashes When exported From Flash CS5.5

    Something strange that i noticed, when i had exported a presentation for a Mac,
    on a 64 bit windows 7 using flash cs5.5.
    the applicaton gets the paths of a few swfs from an XML file
    and loads them one after the other.. there is a small bit of interactivity.
    .. tested this projecter on various versions of MAC, it crashes often,crashes earlier if i switch applications.  what follows here is a part of a report that was generated on an  OS X 10.7.3,
    works fine if the projector is exported from flash cs5.
    i need it to work when exported from flash cs5.5.. any suggestions on what i need to change in my application so that it works when exported from flash cs5.5?
    Your help would be appreciated Thanks in Advance
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x00000000500d98eb
    VM Regions Near 0x500d98eb:
    Memory tag=240         000000000ebd0000-000000000ec90000 [  768K] ---/rwx SM=NUL 
    -->
    __TEXT 0000000070000000-0000000070142000 [ 1288K] r-x/rwx SM=COW  /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    Application Specific Information:
    objc_msgSend() selector name: orderOut:
    objc[9434]: garbage collection is OFF
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libobjc.A.dylib                 0x92115d47 objc_msgSend + 23
    1   com.macromedia.Flash Player.app 0x00467d96 main + 240950
    2   com.macromedia.Flash Player.app 0x0047efda main + 335738
    3   com.macromedia.Flash Player.app 0x002feae2 0x1000 + 3136226
    4   com.macromedia.Flash Player.app 0x0033a77b 0x1000 + 3381115
    5   com.macromedia.Flash Player.app 0x00462718 main + 218808
    6   com.macromedia.Flash Player.app 0x004628b2 main + 219218
    7   com.apple.CoreFoundation        0x98e0b3df __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
    8   com.apple.CoreFoundation        0x98e0ad96 __CFRunLoopDoSources0 + 246
    9   com.apple.CoreFoundation        0x98e34c68 __CFRunLoopRun + 1112
    10  com.apple.CoreFoundation        0x98e3447c CFRunLoopRunSpecific + 332
    11  com.apple.CoreFoundation        0x98e34328 CFRunLoopRunInMode + 120
    12  com.apple.HIToolbox             0x9289117f RunCurrentEventLoopInMode + 318
    13  com.apple.HIToolbox             0x928984e7 ReceiveNextEventCommon + 381
    14  com.apple.HIToolbox             0x92898356 BlockUntilNextEventMatchingListInMode + 88
    15  com.apple.AppKit                0x98fe8a9c _DPSNextEvent + 678
    16  com.apple.AppKit                0x98fe8306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
    17  com.apple.AppKit                0x98fe4675 -[NSApplication run] + 911
    18  com.apple.AppKit                0x99278261 NSApplicationMain + 1054
    19  com.macromedia.Flash Player.app 0x000032a2 0x1000 + 8866
    20  com.macromedia.Flash Player.app 0x000031c9 0x1000 + 8649
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib          0x97d3f90a kevent + 10
    1   libdispatch.dylib               0x99a75c58 _dispatch_mgr_invoke + 969
    2   libdispatch.dylib               0x99a746a7 _dispatch_mgr_thread + 53
    Thread 2:
    0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
    1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
    2   libsystem_c.dylib               0x9232482a pthread_cond_wait + 48
    3   com.macromedia.Flash Player.app 0x003ff62f 0x1000 + 4187695
    4   com.macromedia.Flash Player.app 0x0001a06c 0x1000 + 102508
    5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
    6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
    7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
    8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
    9   libsystem_c.dylib               0x9237c6de thread_start + 34
    Thread 3:
    0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
    1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
    2   libsystem_c.dylib               0x9232482a pthread_cond_wait + 48
    3   com.macromedia.Flash Player.app 0x003ff62f 0x1000 + 4187695
    4   com.macromedia.Flash Player.app 0x0001a06c 0x1000 + 102508
    5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
    6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
    7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
    8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
    9   libsystem_c.dylib               0x9237c6de thread_start + 34
    Thread 4:
    0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
    1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
    2   libsystem_c.dylib               0x9237cf7b pthread_cond_timedwait_relative_np + 47
    3   com.macromedia.Flash Player.app 0x003ff5f8 0x1000 + 4187640
    4   com.macromedia.Flash Player.app 0x001c58fe 0x1000 + 1853694
    5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
    6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
    7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
    8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
    9   libsystem_c.dylib               0x9237c6de thread_start + 34
    Thread 5:
    0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
    1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
    2   libsystem_c.dylib               0x9237cf7b pthread_cond_timedwait_relative_np + 47
    3   com.macromedia.Flash Player.app 0x003ff5f8 0x1000 + 4187640
    4   com.macromedia.Flash Player.app 0x00305328 0x1000 + 3162920
    5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
    6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
    7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
    8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
    9   libsystem_c.dylib               0x9237c6de thread_start + 34
    Thread 6:: com.apple.audio.IOThread.client
    0   libsystem_kernel.dylib          0x97d3cc22 mach_msg_trap + 10
    1   libsystem_kernel.dylib          0x97d3c1f6 mach_msg + 70
    2   com.apple.audio.CoreAudio       0x9cd8e9fe HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned long, unsigned long, mach_msg_header_t*, unsigned int) + 122
    3   com.apple.audio.CoreAudio       0x9cd8ea6a HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, unsigned int) + 60
    4   com.apple.audio.CoreAudio       0x9cd86e5f HALC_ProxyIOContext::IOWorkLoop() + 1145
    5   com.apple.audio.CoreAudio       0x9cd86926 HALC_ProxyIOContext::IOThreadEntry(void*) + 136
    6   com.apple.audio.CoreAudio       0x9cd86898 __HALC_ProxyIOContext_block_invoke_6 + 20
    7   com.apple.audio.CoreAudio       0x9cd8681d HALB_IOThread::Entry(void*) + 69
    8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
    9   libsystem_c.dylib               0x9237c6de thread_start + 34
    Thread 7:
    0   libsystem_kernel.dylib          0x97d3f02e __workq_kernreturn + 10
    1   libsystem_c.dylib               0x9237accf _pthread_wqthread + 773
    2   libsystem_c.dylib               0x9237c6fe start_wqthread + 30
    Thread 8:
    0   libsystem_kernel.dylib          0x97d3f02e __workq_kernreturn + 10
    1   libsystem_c.dylib               0x9237accf _pthread_wqthread + 773
    2   libsystem_c.dylib               0x9237c6fe start_wqthread + 30
    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00dbe0e0  ebx: 0x00dbe0e0  ecx: 0x99985548  edx: 0x500d98cb
    edi: 0x0000036e  esi: 0x00aad0e0  ebp: 0xbfffe4f8  esp: 0xbfffe488
    ss: 0x00000023  efl: 0x00010202  eip: 0x92115d47   cs: 0x0000001b
    ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
    cr2: 0x500d98eb
    Logical CPU: 1

    Looks like it was a memory problem with the jvm.ini file.
    Pumped it up to 256 and it works now.
    Hope this helps anyone else in the future if they come across it.
    Thanks.

Maybe you are looking for