Lightroom to CS2 to JPEG?

I'm experiencing trouble exporting files from Lightroom then editing them with CS2 then saving them as jpeg.  Even if the initial export from lightroom 2 was jpeg!  This is apparently a documented bug fixed in CS3 and CSS4 but not in CS2.  The solution provided here: http://www.flickr.com/groups/adobe_lightroom/discuss/72157607023379578/ works.  Is there a way to script this modification?
Todd

It might be better to try and see if exifTool will do this.
http://www.sno.phy.queensu.ca/~phil/exiftool/faq.html

Similar Messages

  • Xap rating metadata lightroom bridge cs2

    Is there anyone out there who can tell me why the xap metadata is written so differently in lightroom jpegs as compared to bridge CS2?
    I've had writtena feature on my dynamic gallery on my website that reads the xap rating in bridge-produced jpegs, but doesn't work with lightroom produced ones. When I read the metadata from the 2, the structure was totally different. I dont suppose anyone from the development team would care to tell us how lightroom and bridge CS2 read the different xap structures - it would give me a clue how to re-write the function on my website.
    Also are there plans to make the current structure standard? Does bridge CS3 for instance produce jpegs with the same structure in the metadata?
    Thanks!

    Yup, Bridge is just a Browser. ACR and Photoshop do the work.
    AFFAIK.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.10 & Win XP, Pentax *ist D
    See LR Links list at my
    Blog for related sites.

  • I've send from Lightroom 5 photos in Jpeg format to my desktop that arrive as Archive and I'm unable to do anything with the photos.  I want to put them in a folder but can't. It seems problem is in them being in 'archive'.  Any suggestions?

    I've exported photos from Lightroom 5 from my laptop to my wife's desktop.  The photos arrive as Archive and she's unable to do anything with them, such as catalog them in an IPhoto folder with other photos.  Is there an adjustment I need to make when exporting from Lightroom 5 so we can avoid this problem? Thank you.

    Sorry - this is the iPhoto for Mac support forum - Your question does not involve iPhtoo for the Mac in any way - you need to contact Adobe or use an Adobe LR support forum for LR support
    Afar as iPhoto is concerned it can import JPEGs and TIFFs - plus a few others - I have no idea what an archive format is and neither does iPhoto
    File Formats
    Native RAW import and editing of images from leading digital cameras and camera backs
    (See RAW support page for model listing.)
    .ARW, .CR2, .CRW, .MOS, .NEF, .RAF, .RAW, .SRW, .TIF, .OLY, .FFF, .3FR, .DNG1
    Compatible with all major still image formats
    JPEG, GIF, TIFF, PNG, PDF, PSD2
    LN

  • 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 4.1 exported JPEG files are not recognized by Apple Preview App

    I just started using Lightroom 4.1 Trial version (coming from Aperture). I exported JPEG versions of some images using an ICC profile. On my iMac running Lion 10.7.5 the pictures do not show a thumbnail, the file on the desktop just shows "JPEG". I could not open the file with the Preview App, but I am able to open it with DPP (Canon software)? Also the file shows that it has 0 x 0 dimentions when I click Get Info even though it is about 25 Megs in size?
    The message I get is
    "The file “Edit-739820120223Canon EOS 7D.jpg” could not be opened.
    It may be damaged or use a file format that Preview doesn’t recognize."
    Does anyone know why this is hapening?
    Is it a know issue between Adobe and Apple?
    Is there a fix for this?
    Thanks for help in advance.

    25MB is quite a large filesize for a JPG, and this might be either quite a lot of pixels saved at a very "high" quality (not very much compressed), or it may be an extremely large number of pixels saved with medium compression.
    While the technical spec of the JPG format imposes an absolute limit on maximum width and height pixel dimensions, some software employs a lower limit above which it considers the file to be invalid. Different programs, different limits, sometimes.
    I have encountered this (for example) with pano stitched images using the full resolution of a large number of component shots - where JPG output could not be made, or if made, could not even be viewed as a whole by my standard image viewer (though TIFF was still OK even at still larger sizes).
    If Lightroom has been set to a large printed size AND to a high ppi resolution, it is easy to get into very high numbers and very large output files. One should IMO at least question the utility and benefit of using very high ratios of upsampling from a standard digital photo - which may happen in some cases as a result of using the same output settings regardless, when spreading the same data across both small and large scales. If the file that was imported into LR really does provide an unusually high number of pixels expressing lots of detail, then that will better deserve such a capacious output file. Otherwise, each part of the file may merely show a very highly detailed representation, of a very blurry nothing-much-in-particular.
    If the JPG has exceeded the viewer's size limits, a reported width and height of 0 may represent an error message, in effect - not actual reality.
    regards, RP

  • Lightroom and CS2

    Sorry if this is a dumb question, but... can Lightroom 2 be used with Photoshop CS2?
    Thanks in advance!

    1. It's not a dumb question.
    2. Yes, LR2 can be used with CS2.

  • Color checker profile (in lightroom) only work for JPEG file?

    I followed all tutorials for color checker-lightroom and succeeded to sync my JPEG images into the camera profile I want.
    However, these are JPEG images from the camera. I want to work with raw file or at least PSD file.
    So my retouch pipeline was:
    - opened my raw file
    - save it as PSD
    - back to lightroom and open it there
    - and intended to sync this PSD file image with the camera profile
    But this is impossible to do, because suddenly all the camera profile  options (the ones we generated via color checker passport and the  default adobe profile) are dissapeared. The only option of camera  profile now is "embeded".
    That's it. So does it mean that I have to convert my raw file into JPEG first ?
    If yes, it's very unpractical and I can loose a lot of data bcause I  thought saving it to PSD or TIF keep the image data better than into  JPEG.
    Confused..
    Thanks for your point of views.

    In LR Preferences / External Editing you can control things about the LR-to-PS transfer:  the file format (PSD/TIFF), the color profile (sRGB, AdobeRGB, ProPhotoRGB), and the bit-depth (8 vs 16). 
    My Edit-in-Photoshop is set to use PSD, ProPhotoRGB, 16-bit.  I have chosen this because it gives me a large colorspace, with millions of distinct colors and a file-format that can contain smart-layers and other Photoshop-specific things.  LR, itself, is using a color-sapce as large as ProPhotoRGB and I don’t want to lose colors just because I’m editing in Photoshop, at least not until I’ve finished my adjustments in PS.
    A large colorspace with millions of colors gives more freedom for extreme adjustments before color banding (posterization) or color-shifting (channel clipping) at the bright end of the histogram.  The downside is that before I can save my photo as JPG for general viewing is that I need to set PS / Edit / Convert Profile to sRGB and PS / Image / Mode to 8-bit.
    It sounds like you are saving your photos as 8-bit ProProtoRGB not realizing you also need to convert to sRGB as your color profile.  For browsers and operating-systems that don’t do color-management correctly, which is most browsers and Windows-halfway, your ProPhotoRGB color numbers in the JPG are being interpreted as sRGB which makes them much duller and less saturated.   It may be that you have your External Editing set to 8-bits, which is not a good idea if you are using ProPhotoRGB as your colorspace, so set it to 16-bit.

  • New Lightroom 5.4 export jpeg error?

    I have just installed the Lightroom 5.4 upgrade (on my MacBook Pro) and attempted to export a JPEG. It complained of a "Access to undefined global: newGrainSeed   (1). Any help would be appreciated. Thanks.

    Brilliant and thanks for reporting back.... I looked at it and went "what"??????

  • Why does Adobe Bridge and Lightroom not recognise some jpeg files?

    I am trying to use Adobe Bridge and/or Lightroom to add tags to a large number of images that I have. However when adding images, almost 1000 of the 6900 images fail to import to the Lightroom gallery and the same images do not preview and will not let me edit their metadata in Bridge.
    If this has happened to anybody else I would greatly appreciate some help.
    Alternatively if anybody knows of other programs i can use to easily add tags to many many images please let me know =)
    Samples of Files that work and files that don't:
    http://files.filefront.com/FileSamplerar/;13605286;/fileinfo.html

    I downloaded same, but the folder marked "Don't work" comes up empty.

  • Lightroom Exporting V Small jpeg

    Hi,
    Hope someone can help.
    I am doing minor edits in lightroom, before exporting jpgs to Photoshop for creative edits.
    Even using the maximum export size, a 20mb RAW file turns into a 4mb jpg. Then, when further edits are done in Photoshop, and resaved (using Autoloader), the file size reduces to just 2mb.
    The image dimensions are constant throughout, 3960 × 2640. This doesn't seem right to me. I have checked setting again and agin, and from what I can see max file sizes are being used.
    I want to give clients image larger than 2mb. Can someone help?
    Thanks in advance
    Rich

    Workflow will be:
    RAWs in folder A
    Edit in Lightroom the acceptable photos, and export to Folder B as TIF
    Open Folder B images in PS and Edit accordingly, then save in Folder C
    On completion, folder B (TIF's will be deleted)
    (these are usually wedding photos, so ultimately, the RAW's will be deleted too, leaving just the jpgs as back up)
    You are just making extra work for yourself by putting these things in separate folders. They could all go in a single folder, with no confusion whatsoever.
    Furthermore, it seems that no one has discussed this yet, but EXPORT to Photoshop isn't really the best way to go. You would want to use the Lightroom command Edit In ... (right click on a photo and select Edit In), this is a better workflow since once you have saved the edits from Photoshop and close the image in Photoshop, the edited photo now appears in LR withou you having to import it.
    I don't understand why you would want to delete the RAWs and TIFs, to my mind this is a horrible practice. If you do that, you can never go back; the best you quality you will ever have is the quality of the JPGs. Now I don't know your business, but it seems to me if the clients ever ask for the photos to be re-edited in some way, you're going to have to start from the JPGs rather than the RAWs, and this will never result in as "high quality" as if you start from the RAWs.
    Lastly, "leaving just the jpgs as back up" -- no, the JPGs are not backup, they are unrelated to the concept of backup; and furthermore they are the only copy of the photo you have. If your hard disk crashes, your photos are lost. You now have ZERO copies of these photos, and I'm guessing that both you and your clients would be very unhappy about that. A true high quality backup strategy would be to save the RAWs, and save the TIFs and make backups of both on a different physical disk. Then you have originals and at least one backup on a different disk. The JPGs are what is truly expendable here.

  • How to find-" Lightroom-opening Catalog: DSC00155.jpeg.ircat" Where is it?

    I have downloaded Lightroom When I try to start the software it shows. -" Lightroom-opening Catalog: DSC0024 JPG.Ircat " Then a windows Window opens and said "Adobe Photoshop Lightroom 64-Bit has stoped working A problem caused this program to stop working correctly Windows will close the program and notify you if a solution is available." ANY Help ??? I cannot start the software.

    Did you ever successfully open Lightroom by double-clicking on the Lightroom icon? If so, we can probably advise you what to do next.
    Are you trying to open a file (DSC0024.JPG) into Lightroom via right-clicking on the file in your operating system, and selecting some command to try to open into LR? This won't work at all, you can't open JPG (or other image) files that way. Or did you try to associate JPG files with Lightroom, then try to double-click on it and open it? That won't work either. If that's what you did, please let us know, we can advise you on what to do next.
    Or, if you did something else, please let us know what you did.

  • Cannot save as jpeg in CS2 after exporting from lightroom

    I'm so frustrated. This began happening only a couple times here and there after starting to use lightroom (can't remember if it was the 1.4 version, or the beta version). I don't think it's my photoshop program, since I have completely re-installed it twice and reinstalled onto my computer.
    Anyway, now it's happening all the time. I export images from lightroom into CS2 to make final edits, sharpen for print, crop, etc and then photoshop will not let me save it as a jpeg. I can save as a psd, or a tiff, but not a jpeg. I have tried exporting in jpeg format, or tiff format, and everything is fine until I try to save either type as a jpeg. It lets me choose the quality, 10-12 etc, then when I click OK, A red box with "could not complete your request because of a program error" pops up.
    I have Vista, edit in sRGB, export in sRGB, etc..... just don't know what to do since I NEED to be able to edit and save to send to print. Please help.

    Find the solution here:
    http://www.flickr.com/groups/adobe_lightroom/discuss/72157607023379578/
    basically you delete the camera raw info put into the file that trips up CS2 (but not CS3!)

  • CS2 problem with 5D MKII RAW files from Lightroom 2.2

    Ok, this one is weird. I have tried it on two different computers with the same resulting problem. If I convert a full size RAW 5D MkII to Tiff in the new Lightroom 2.2, then bring it into CS2 and covert it to 8-bit and try to save as JPG, it always comes up with a program error. I tried an sRAW file with the same process and it worked fine.
    Just to make sure I did have something else messed up, I converted in DPP to tiff and then went to CS2 and saved as JPG just fine.
    Anyone else try this and see a problem? Looks like it's a combination of a problem with the new Lightroom, plus CS2.
    It almost seems like CS2 doesn't have enough memory to convert the file to jpeg. I have had this program error before in CS2, but with much larger files. The 5D MKII should not overrun memory.

    This is a known bug in CS2 where it trips up because of the (valid) metadata written by Lightroom. You need to delete the xmp metadata written by Lightroom from the file before saving as jpg or export from lIghtroom with minimize metadata checked.

  • I have Photoshop CS2 vsn 9.0 with the Camera Raw 3.7 update and the Digital Negative Converter.  I cannot open any RAW files. Does the fact that I've opened them in Lightroom 5.0 before make a difference?

    When I try to open the RAW file (CR2) from the Photoshop application or from the Bridge (even while holding down the shift key) I get a message saying it's not the right kind of file. When I try to convert using the converter, it won't recognize the files.

    Which operating system are you using?
    Which camera are the camera raw files from?
    Did you convert the files to dng using lightroom or the standalone dng converter?
    If using the standalone dng converter, which version?
    In the dng converter did you try setting the Compatibility for Camera Raw 2.4 and later
    (Preferences>Compatibility)
    You should also be able to send the files from lightroom to cs2 without converting to dng, either by using Photo>Edit In>Photoshop or setting cs2 as an external editor in the lightroom preferences

  • Lightroom JPEG files far larger than equivalent Photoshop files?

    I'm using Lightroom 2.3 on a Mac. If I take an image and export it from Lightroom as a JPEG at the 60 quality setting, the resulting JPEG is typically around 2-3 times larger than the same file saved from Adobe Photoshop CS3 using the High Quality setting in 'Save for Web and Devices'.
    Lightroom does not appear to be generating a preview or anything else that would account for the disparity.
    To get Lightroom to shrink files down to the sizes that Photoshop produces, I need to reduce the quality to a level at which the images contain glaring JPEG artifacts.
    I'd like to use Lightroom as part of my web workflow, but this is pretty much a showstopper. Exporting to TIFF, then using Photoshop batch actions to try to automate a conversion to JPEG runs into the problem that Photoshop's "Save for Web and Devices" command can't be fully automated (it's not possible to override the save location).
    So my questions are:
    1. Why is Lightroom's JPEG compression so poor in comparison to Photoshop's?
    2. Is there any way to get around this?
    3. Is it safe to use Photoshop's standard 'Save as ...' command in place of 'Save for Web and Devices' when preparing images for the web (I have a distant memory that 'Save As ...' used to export metadata that would choke certain browsers, but I don't know if that's still true in CS3).

    It looks as if metadata contributes about 4-8K to the image. Photoshop is stripping a large part of the metadata (even with 'include XMP' on), which contributes to the difference, but doesn't explain it completely.
    Here are some test results:
    Test Image #1: 660 x 440:
    Lightroom 2 (60, with metadata) - 170,904 bytes
    Lightroom 2 (60, without metadata) - 164,142 bytes
    Photoshop CS3 (60, no metadata) - 141,489 bytes
    Photoshop CS3 (30, no metadata) - 72,394 bytes
    Test Image #2: 660 x 440 (no metadata)
    Lightroom 2 (70) - 124,231 bytes
    Lightroom 2 (60) - 88,448 bytes
    Lightroom 2 (60) - 80,560 bytes
    Photoshop CS3 (Save for Web 70) - 94,032 bytes
    Photoshop CS3 (Save for Web 60) - 69,654 bytes
    Photoshop CS3 (Save for Web 30) - 32,287 bytes
    Photoshop CS3 (Save 8) - 93,517 bytes
    Photoshop CS3 (Save 7) - 73,067 bytes
    However, there's a quality difference to be taken into account as well. Photoshop 60 is about equivalent to Lightroom 70.
    To compare the images, I took the original image (scaled to 660 x 440 by Lightroom) and layered the JPEG over it, then set the layer to 'Difference' to reveal JPEG compression artifacts. Lightroom at quality level 60 shows visible artifacts; Photoshop Save for Web at level 60 does not. To get the artifacts to disappear, I have to take Lightroom up to about 70, by which time the Lightroom files are almost twice the size of the Photoshop files.
    Just for amusement, I tried Graphic Converter as well. GC is a great program, but its JPEG conversion turns out to be vile: even at a quality setting of 100, the artifacting on fine near-vertical lines is obvious to the naked eye.
    Using Photoshop's own 'Save' (rather than 'Save for Web') command yields similar results. quality level 8 in 'Save' appears to be fractionally poorer than quality level 60 in 'Save for Web'.

Maybe you are looking for

  • What is the best way to extend a Virgin wifi network in a thick walled house?

    I have a Virgin Netgear wifi router in a downstairs room at home and get a relatively poor signal in adjacent rooms and none in non-adjacent rooms (i.e. at least one intervening room); it is an old (deep) victorian house with many small rooms! If I w

  • Firefox won't play sound on youtube video's but sound works in other applications

    i can play sound as usual on other applications such as media player, vlc, itunes etc... but firefox and internet explorer do not work, google chrome doesnt even work. i have re-downloaded flash player and the pluggins many times trying to fix it, cl

  • Sony HDR-SR1 AVCHD Compatibility

    Greetings friends and users- In addition to the workaround of playing the video back through some other device like a DV camera or Pyro AV Link has anybody found any other way to get video out of this bad boy and into the Mac? Thanks in advance for a

  • Reference date of last data load in query

    Is it possible to referece the date of the data load in a query via user exit / formula variable or some other way? We have a requirement to display data in a query based on when the data was last loaded. If the data load has not occured this month,

  • EJB access from C++ client / Failover+LoadBalancing

    We are accessing an EJB from VisiBroker for C++. The EJB is deployed in a WLS cluster. Trying to achieve something like 'failover', we discovered that VisiBroker supports multiloc addresses, so we are able to start our client as follows: ./client -OR