Lens Correction Transform Issue

I've noted in LR3 that lens distortion corrections will export, however , they are not performed on the image when opened in PS directly from LR3. Is that a bug or is this by design?

Ahhhh! Yes, that works. Thank you so much, I totally bone-headed that. So, essentially the primary editor should work with the distortion correction when CR gets a future update? Also, I would love to see an automated setting for the 17-35 Nikon
Aside: the email message I received said "Are you using the Cmd-Shift-E shortcut for the secondary editor?"  not  Cmd-Opt-E

Similar Messages

  • Odd Issue Editing in Photoshop with color and lens corrections

    First off, I'm on LR 4.4 and PS CS6 (Camera Raw 7.4.0.137) using ProPhoto RGB as my LR colorspace and have my PS color settings as Working Space: ProPhoto RGB and my color management policies to preserve embedded profiles.
    When I right click on a DNG in LR and choose "Edit in Photoshop", LR sends it to PS and PS does its "Reading in Camera Raw Format" and opens the image.  However, the colors are off (very muted) and any lens corrections I've applied in LR are missing.  My monitor (iMac on OSX 10.8) is calibrated with a Spyder.  I've also noticed that if I choose to edit in another application, it renders the tiff fine and the color and lens corrections are correct in the tiff. 
    Anyone have any ideas what my issue is?
    Thanks,
    Matt
    ETA: After some experimenting, it seems that the "Adobe Standard" profile is what gets sent to Photoshop.  The rest (Camera Landscape, Portrait, etc.) are ignored. What's going on here?

    Sounds like you need to reset your warning dialog. Preferences>General>Prompts [Reset all warning dialogs]
    Then try it again and make certain of the three choices you are Editing a Copy with Lightroom Adjustments.

  • PS CS2 lens correction causes "Maximize Compatibility" issue in LR

    Question: why does PS CS2/3 convert the layer "Background" to "Layer 0"?
    This is the problem (and solution):
    I encountered the widely discussed "Maximize Compatiblity" issue with a bunch of PSD files (slide scans) that contained only one layer. Puzzled as I was that the layer thing apparently could not cause the problem, I reopened some of those files in PS CS3 and I noticed that each of them had had a lens correction. Just to make sure I was on the right track I applied a lens correction to a file that had been already imported into LR successfully and used the SaveAs command and unchecked the Maximize Compatibility option. The new file could not be imported into LR. So no more lens corrections? - I thought.
    A closer look on the troublesome files made me learn the (only) layer had been renamed from "Background" to "Layer 0" after the lens correction was made. I used the "Flatten Image" command and this turned it back into "Background". After this, the file could be imported into LR without a problem.
    I can now apply this trick to all troublesome files that have had lens corrections and thus avoid the huge increase in file size (130MB is a lot already).
    Now I write this for those of you who have the same problem and are still puzzled (to help out) but I also would like to have some insight into why PS CS2/3 lens corrections mess with the layers.
    Thanks.

    >My conclusion would be that LR can only import PSD files that meet the following requirements:
    >1. must contain only one layer
    >2. that layer must be called "Background"
    Your conclusion is only partially correct.
    Lightroom will import multi-layered PSD files that have been saved with the preference for "Maximize PSD and PSB File Compatibility" set to On. This is clearly stated in the Release Notes and Help documents:
    >Photoshop format (PSD)
    >Photoshop format (PSD) is the standard Photoshop file format. To import and work with a multi-layered PSD file in Lightroom, the file must have been saved in Photoshop with the Maximize PSD and PSB File Compatibility preference turned on. Youll find the option in the Photoshop file handling preferences. Lightroom saves PSD files with a bit depth or 8 bits or 16 bits per channel.
    As to the original point -
    PS CS2 lens correction causes "Maximize Compatibility" issue in LR.
    Photoshop renaming Background Layer to Layer 0 is a Photoshop issue, not Lightroom. When it occurs the files effectively becomes a multi-layered file, even if there is only one layer (i.e layer 0). Why using the Lens Correction filter causes the background layer to be renamed is currently unclear, but I have raised it in the "appropriate" place. In the meantime, I recommend that you set the Maximise Compatibility preference to
    Always. Doing so will save non layered files as normal and multi-layered will have the
    necessary* composite preview. You can continue to use the flatten command to fix the errant files.
    *Enabling the Maximise Compatibility preference ensures that Photoshop creates a composite preview of multi-layered images. It is intended to enable applications that can't read layers to preview the images. Lightroom cannot read multi-layered files, therefore the composite preview MUST be present in such files.
    >Has anyone noticed different behaviour with the Lr v2 beta? I'd hate to double the size of all my multilayer PSDs just so they can load into Lr(?)
    Lr 2.0 will function as per Lr1.x; i.e. not using Maximize Compatibility when saving multi-layered files will mean that they are not compatible with Lr2.0.

  • Use Lens Correction or Transform/Skew for Vertical Perspective??

    I recently visited the Redwoods in California and took many photos of trees with a wide angle lens, which as you know causes the trees to bend inwards. I have tried using both Filter/Distort/Lens Correction and Transform/Skew to attempt to correct the problem. It is my observation that Lens Correction reduces the number of pixels by producing a trapezoid shaped image with the sides slanting inwards. Skewing does the opposite: increases the pixels by creating a trapezoid with the sides slanting outwards.
    What are the pros and cons of using each method to correct vertical perspective? How will the image quality differ with each method? Thanks!!

    Anthony,
    Click on the link to see this short QT video tutorial:
    http://photoshopnews.com/wp-content/uploads/2009/05/psn-perspectiveacr-low.mov

  • LR 4.3 lens corrections issue (bug?)

    Hello,
    I'm having trouble with LR 4.3 lens corrections panel, that I didn't have with LR 4.2.
    I'm running LR 64bit  on Windows 7 Ultimate. Camera is Pentax K5.
    This is what the lens corrections panel looks like after import in LR 4.2. I did setup the "Enable Profile Corrections" as default for my camera, so everytime I import photo's this is autmatically checked.
    Opening the same photo in the same catalog with LR 4.3 this is what I get:
    Notice "Setup" has changed to "Custom" and Lens Profile says None.
    Changing Setup to Default again, Make and Model display the correct information, but Profile says None.
    Clicking on the Profile arrows gives me the correct lens profile but...
    ... selecting that profile turns everything back off and setup is changed to Custom again.
    Now setting Setup to Default makes no difference! Lens Profile displays None but...
    ... selecting Auto gives me the right Make and Model!!
    And finally, when I leave the image with settings as here above, go the another photo and change the lens corrections, and then go back to the initial image, everything's gone again!!!
    As far as I'm concerned, this is a serious bug, unless I'm missing something obvious.
    Did anyone have this same problem?
    I've downgraded to LR 4.2 again, and everything is back to normal.
    Regards,
    Peter

    No, that's not it either. Lens Corrections appears in the right panel, between "Detail" and "Effects".
    It's just that when I click on the "make" under the Lens profile, all I get is Nikon and Sony (and not the other brands I used to see) and under model there is only one lens if I remember correctly...
    This is frustrating, and it will be more so if it turns out that I did something silly!!
    thanks
    christos

  • Lightroom 5 and Lens Correction-issue

    Hi, sometimes in LR4 I used the lens correction. Most pictures nowadays I take with an old NIkon 24-85:2.8-4 lens. When I tick lens correction and choose as manufacturer Nikon it automatically gave me the Nikon 24-85:3.5-4.5 (as the 2.8-4-version is not present), but usable. In LR5 it always gives me a Nikon Coolpix-lens and I have to manually change it. Quite annoying.

    LR has not automatically assigned that lens profile, since it does not exactly correspond.
    But it's no biggie...after manually selecting a particular lens profile, you can set that as a user default to be used in future (for any other pictures that report the same lens data as the current active image does).
    It's an option in the drop-down menu within the lens profile panel.
    Your LR default settings or import preset affecting these future imported images, will just need to ensure that Profile is active, and that the selection of profile is set to Default (instead of Manual) within this same drop-down menu.
    Hereafter, LR will adopt whatever profile is the factory default or (as an override) is the user selected default, or (failing both) no profile at all, for each image imported.

  • Erratic behaviour of Manual Lens Correction in Develop Module

    64 bit Windows 7
    Sometimes - not always - using the manual lens correction, with Constrain Crop activated, leads to the image jumping around very quickly and erractically and it being impossible to achieve fine control using the mouse: tiny movements of the slider by dragging with the mouse result in large jerky movements of the image.  I have only used this for correcting converging verticals and cannot comment on the other adjustments.
    Moreover, on a subsequent crop when this has happened, it may be impossible to crop as you would like using the crop tool - the top edge of the image jumps above the intended crop outline.  The only way to get the crop you want when this happens is to adjust each edge individually, rather than by dragging the corner.
    Apologies if I have not explained this well.  In short, it seems to be a bug whereby proper mouse control of the lens correction is lost.  I often correct converging verticals in buildings and have never seem the same behaviour in version 3.  I cannot always replicate it in version 4, but it happens a lot.
    Hope this feedback helps.  I cannot see that it has been reported elsewhere in this forum.

    Hmmm, this is going to be tricky.  I just tried to replicate it on two photos on which I know I had the problem, by going back to the original import setting, but both behaved fine this time!  Both, as it happens, were portait format, having been rotated 90 degrees counter-clockwise from the original.  I cannot recall, I am afraid, whether or not other ones with which I had an issue had been rotated first.  I will try to replicate and keep more detailed notes.  In at least these two instances, I had not applied a lens correction profile first.  The vertical transformation slider would be set to somewhere between -25 to -35.
    Having played about with this for a while now without full replication, I have one idea which may or may not be correct.  When I reset the Develop settings and started on the Lens Corrections first, absolutely nothing untoward happened.  Now I have gone back and done a number of other adjustments first (as I would often do, before correcting the perspective).  In this case, the vertical adjustment slider seems more sensitive to small mouse movements - definitely discernible, but not nearly as bad as the examples I have seen previously when I was not looking for them, nor is there yet any sign of the cropping problem.  Maybe the effect becomes more pronounced as the number of edits accumulates before applying the manual Lens Corrections.  If this is correct, I do not know whther the effect is cumulative across all edits to all images (as if memory is not being released - but that should not be a problem, since I have 12GB of RAM and nothing else running) or whether it is a per image phenomenon, since I have only recently re-opened Lightroom.  You will know better than I whether this is a possiblity, but it is just a thought as I play with this without so far being able fully to replicate the issue.  I have some work to do on a number of images and if I get time, I will come back to these images to see if the problem manifests itself more clearly after a larger number of edits across multiple images in a single session without closing Lightroom.
    I am very sorry this is so vague and quite speculative.  I hope I will be able to give you more accurate feedback later.

  • Lens Correction and Cropped Pixels

    I'm starting out as an architectural photographer, and as I don't yet have a perspective correcting lens to adjust images in-camera, I need to use the Lens Correction tools in Photoshop and ACR.  I prefer to use them over the Free Transform tool for the sake of accuracy (and convenience), but I do have an issue with the tools.  When I correct the perspective of an image and then process, whatever extends beyond the boundary of the canvas winds up being automatically deleted, and it seems as if there's no setting to prevent this from happening.  As there is sometimes a piece of a photo that I would like to be able to retain (i.e. extra sky, the top of a building, etc.), I understand that I can scale down the image in the Lens Correction tool and then re-crop after processing.  Of course then this causes the image to still be smaller than I would like it to be (in certain cases where the distortion correction is more extreme, an original 21MP photo might become a 12 or 13MP photo after processing in the Lens Correction due to scale-down).
    Is there any way that the Lens Correction tool will allow for pixels extending beyond the boundaries of the canvas to remain uncropped, thus allowing me to expand the canvas in order to reclaim the extra information?

    Yammer P, yes the list is shorter because it's a jpeg rather than raw, and we have more profiles for raw than for jpeg.
    For the set of lenses supported in CS5's initial release, we created profiles for both raw and jpeg. Since then, we have been concentrating on raw-based lens profiles, for a number of reasons (one of which is that we feel we can consistently deliver the highest quality results this way). This is why you see some lenses supported with raw & jpeg profiles, but many more supported with raw only.
    CS5's Lens Correction plug-in does indeed let you choose raw-based lens profiles even though it is processing a rendered file (e.g., jpeg, tiff). This will work in many (but not all) cases for distortion correction, but will often work poorly for chromatic aberration and vignette correction. I don't recommend this workflow and it is a key reason we don't let users mix/match in ACR & LR.
    Eric

  • Manual Lens Correction in Lightroom 4

    The Manual Lens Correction sliders in Lightroom 4 seem completely useless. They aren't working the same as they do in Lightroom 3. Instead of being able to fix keystoning of images, now the horizontal and vertical sliders just stretch or distort photos. Is this a bug? If not, is it possible to go back to the functionality from LR3? If this isn't possible, I'm probably going to switch back to Lightroom 3, since this is one of the program's most useful features.

    Lee Jay wrote:
    ... This functionality hasn't changed at all for me - it works exactly as before.
    I think so, too.
    See my example in the feedback forum demonstrating the different effect of the manual transformation sliders depending on the angle of view: http://feedback.photoshop.com/photoshop_family/topics/i_would_love_automation_in_the_lens_ correction_manual_panel : There is an automatic aspect ratio correction, and for photos taken with a rather small angle of view, this is mostly a stretch/distort. Which is totally correct IMHO (and hasn't changed since LR3).
    P.S. I don't know which angle of view LR assumes for photos w/o information about focal length and sensor size (probably 50mm focal length and 35 mm film format ("full format") sensor.

  • Lens Corrections unavailable in Adobe Camera Raw 8.3

    hello,
    since i switched to photoshop CC (mac version), i am having constant problems with lens corrections in ACR 8.3. i am a professional photographer and i use various canon pro lenses that all exist as unique lens profiles already in photoshop and ACR's lens profile archives. when i open canon .CR2 files in adobe ACR 8.3, i encounter the message "unable to load lens profile" at the bottom right of dialog box and even though the correct lenses are identified, ACR cannot apply corrections (please see the attached visual). furthermore, this behavior happens to be sort of erratic, since it may sometimes decide to apply corrections without displaying the "unable to load lens profile" error message.
    when i open the files into photoshop CC without being able to apply corrections, i try the "lens correction" menu within photoshop and it works. it is very cumbersome not to be able to do this at the ACR stage.
    the ACR that came with photoshop CS 6 never had such problems and it corrected all the lenses that i had.
    can you please help me to fix this issue ASAP, since this error makes me lose a lot of time in my workflow.
    i also have photoshop CS6 installed in the same disk, could this have any effect?
    best regards,
    murat germen

    Presumably you're shooting raw for everything, right, otherwise the issue can be that most raw-capable-camera's JPGs don't have lens profiles whereas raw files do, so profiles are found for raw images but not JPGs.  The reverse is sometimes true, too, where a camera used to only have JPG output but now produces raw files.  I believe the DJI Phantom Vision FC200 quadcopter camera is an example of such.  The screenshot doesn't have enough of the ACR interface to see the name of the file.
    Are the profiles that aren't found consistently the same lens or are they from various lenses that also have photos that work in ACR 8.3 at other times?  And do the same photos that fail to have lens profiles load in ACR 8.3 at one point then work if you open them again, later?  In other words does the intermittency seem to be tied to either the specific photos or the specific lenses or not?  Specific photos could mean there is something corrupted in the photo.  Specific lenses could mean that the lens profiles are missing, somehow, or inaccessible due to permission problems.
    Is CS6 updated to the same ACR 8.3 version or is it older?  If it is older then install the ACR 8.3 update for CS6.  This will re-install the lens and camera profiles, again.
    If CS6 is already updated to ACR 8.3, too, then install the DNG Converter 8.3, which also will install the profiles, again.
    The DNG Converter can be found, here:
    http://www.adobe.com/downloads/updates
    If you can't figure it out, then uninstall PS-CC, log out of the CC Desktop app, log back in--so it sees that CC is missing, then re-download and install CC.  This should reset ACR back to 8.0 or 8.1 after which you can install the ACR 8.3 update, again.

  • Adobe Camera Raw - lens correction profiles not found

    I use Photoshop CC as part of the photography program of Creative Cloud. My platform is a Mac Book Pro (2013) with the latest Mac OS-X operating system. I have also installed Bridge CC and Lightroom 5.
    Since about three weeks (maybe after an update but I'm not sure on that) Adobe Camera Raw's lens correction feature fails permanently. With older pictures (taken long before the error occured for the first time) as well as with new photos and with dng files as well as with cr2 files the ACR dialog always shows the error message (lens correction profile can't be found - since I have the German version of Photoshop this is how I would translate the error message). I didn't install or uninstall any programs, plugins etc. around the time of the first occurance of the error.
    I already uninstalled Photoshop CC completely (using the uninstall function in the programs folder) and reinstalled it via Creative Cloud but it still shows the same error.
    What can I do?

    Hello, you can make sure the latest version is installed by going to help-updates.
    Also, make sure that you are running the latest version of the creative cloud application, as it fixes a permission problem that might cause the issue you are facing. Just go to the creative cloud application on your menu bar, and restart it.

  • Lens correction help needed: Nikon 14-24 used in model shoot...

    Hello,
    I just finished a model shoot with 9 models standing in a horizontal line relative to the camera.  Because of the very short working distance I had to use a Nikon 14-24mm lens to fit everyone in, resulting in the end girls being noticeably distorted (unpleasantly "wide").  They certainly won't like that!
    I've opened the raw file in CR, but have not found settings for lens correction that fix this.  CR has the correct lens profile, but no matter how I play with the settings manually or automatically, things just don't look right.  Similarly, if I open corresponding TIFF in Filter -> Lens correction, I still run into the same issue.
    I've enclosed a sample out-of-the-camera image so you can what I'm talking about.  Hoping there's a way to correct the twp outermost girls w/o sacrificing those in the middle...  They are much slimmer than in the shot.
    Running PS CS 5.5 on Win7/64
    Thanks!
    Jerry

    Hi Toasted
    I've seen the adds for the DxO Viewpoint and thought they had a great idea on their hands providing it as a Plug-in. However, I've been using the full DxO Optics Pro as my Raw file editor for a couple of years now, and ran your shot through that, and not the plug-in. 
    Judging my my results, I think the full version is a more powerful tool; the "Volume Anamorphosis" correction in the full version is a semi-automated tool. Simply applying the correction at the initial automated setting still left me with some distortion in the models at either end, which was especially noticeable in the girl on the extreme right. However, I then manually tweaked the setting to the maximum available, to get the result above.
    Now, there's no such thing as a free lunch, and you can't get something for nothing, and the same applies here. What's actually happening is that the Volume Anamorphosis is being "corrected" by re-introducing a set amount of Barrel Distortion into the image, oh, and the image has also been cropped, which is most noticeable in the bodywork of the cars on the left and right, but this is unavoidable. It isn't too obvious here, but if you were to have strong horizontals or verticals in the image, you'd see the curvature in them very easily.
    Take a look at my own example below.
    This was taken with a Tokina 11-16mm f2.8, and in the original the guitarist on the left, and the keyboardist on the right, both had the dreaded "squished head" effect! As you can see that's been fixed, but if you look at the pipes above the lights at the back, the line of the monitor cabinet at the lead singers feet, and the microphone stands, you can plainly see the curves... which is still infinitely preferable to distorted heads!
    Good luck
    Paul

  • BPM - two FORKS and a Transformation issue

    my scenario is File - BPM - Proxy
    input file has multiple records and each record has 1 field that we put a validation logic in.  There will be one message created for each record, so this is a 1:N Integration Process
    I used two Forks:
    Fork #2 has two branches: Branch 1 --> Transformation Step 3;     Branch 2 ---> Fork #1.
    Validation#1 = if the validation field has null value then it will go to Transformation Step3 along Fork#2 (end receiver is Proxy-C)
    validation#2 = if the field has value then it will go inside Fork#1 which has 2 branches: Transformation Step 1 (goes to Proxy-A) and Transformation Step 2 (goes to Proxy-B)
    I am testing a file with only the null value, so I am doing validation#1 only.
    I can see the message in BPE engine  (Outbound status = Processed successfully) but the message is stucked in the BPE
    I checked on the workflow log and here is what i see:
    1) Transformation Step 3 is executed (all mapping steps 1-4 completed so this is successful)
    2) Transformation Step 2 is executed (but mapping encounters an exception so this is not successful)
    3) Transformation Step 1 is not executed already because of the exception, and therefore Send Alert is triggered.
    It seems that all records of the file passes through all the branches, which is not intended.
    My intention is that when the validation field has null value that record will only pass thru Transformation Step 3,   if it is not null then record will pass thru Transformation Step 2 & 1.
    I already created a mapping for this validation, and when I test the Interface Mapping for Transformation Step 3 (consisting of 4 mapping steps) using an actual payload  it is successfuly generating the message.  - so no problem in this Interface Mapping.
    But on Runtime, BPM triggers exception due to validation#2 failing which again is because all records of file seem to pass on both Forks.  I want that when Validation#1 is true that specific record only passes in Fork#2   and not in Fork#1 also.
    I am using ParForEach.
    Can you kindly advise how to correct this issue?

    that was a very detailed explanation!
    But on Runtime, BPM triggers exception due to validation#2 failing which again is because all records of file seem to
    pass on both Forks. I want that when Validation#1 is true that specific record only passes in Fork#2 and not in Fork#1 also
    problem with your design...Fork seems to be working fine....you need to have a Switch block which will perform the validation and then route the message accordingly.
    I already created a mapping for this validation, and when I test the Interface Mapping for Transformation Step 3
    (consisting of 4 mapping steps) using an actual payload it is successfuly generating the message. - so no problem in this
    Interface Mapping.
    Mapping success does not mean that the BPM processing will be success.

  • LX7 Lens Correction in LR4

    I see that my Lumix LX-7 is supported by LR 4.3 (Camera Raw 7.3), but when in the Lens Correction portion of the Develop module, I can't find any reference to Panasonic or Lumix.  Leica lenses are listed, but I can't find any that are equivalent to the LX-7's lens. 
    Can you suggest which Leica lens I should choose?
    Is there a reason that the lens is not automatically selected the same way my other lenses (Canon, Sigma, Tokina) are for my 7-D?

    I was running into the same issue with the correct lens not being shown.  I have a Nikon D7000 with a Sigma 17-50 F2.8 lens.  When I went into the Lens Corrction Panel my specific model wasn't showing up.  Normally when I import my photos I "Copy to DNG" to keep the files organized better.  So I imported a photo as a .NEF and what do you know, the lens auto detected without any issues.  From this I found a workaround so I can keep using the .DNG format and have the correct lens adjustments.
    *** Work Around ***
    Import a photo as a RAW .NEF (or whatever your camera creates)
    Open the "Lens Correction" in the Develop Panel and ensure the lens you use is selected
    Save the settings as a "User Preset" under the Develop Panel
    Open the Import Window and select "Apply During Import"
    Select the "User Preset" that was created
    Select "Copy to DNG" as the import type
    Once the preset has been set on import it will apply the setting and then convert the file to a .DNG with the settings applied.  So at that point if you go to the Develop Panel and choose Lens Correction, the correct lens will show up in the list with it's adjustments.

  • DNG Conversion Of Sony ARW Not Carrying Over In Camera Lens Corrections

    One of the great features of the Sony NEX-7 is that the NEX-7 makes automatic lens corrections for vignetting, chromatic aberration and distortion problems. These corrections are written to the file and the preview. However, when converting these images from ARW to DNG the correction data seems to be lost, and the images revert to their uncorrected state. This requires all images to then be re corrected with the Adobe lens profiles, which is both tedious, an extra step, and also seems to produce results that are somewhat less optimal than the original corrections made by the camera.
    Should not the ACR Converter and Lightroom retain the lens corrections made by the camera?

    A Tonal wrote:
    This is one of those confusing issues where the way Sony describes the feature makes it sound as though it's part of the ARW format, and the way Adobe describe ACR and DNG makes it sound like this would be one of those manufacturer specific details that DNG is supposed to convert into a the Adobe format.
    Yes, that might be so. It's similar with the manual of my Nikon D600. Nowhere does it say explicitly that all these adjustments (including lens correction, Active D-Lighting, etc) work only for the JPGs. And it cannot be otherwise.
    A Raw image is not defined yet, not written in pixels yet, heck it is not even an image.
    The Raw image is only affected by the exposure, that's pretty much the only thing. Even White Balance is nothing but a metadata tag that - luckily - is read by Lr.
    A DNG is Adobe's answer to the various Raw formats. But it is designed to behave like a Raw image. Therefore you cannot expect that camera settings that affect JPGs only carry over to DNGs.
    A Tonal wrote:
    There are so many features on cameras that are only supported with JPG output that it almost makes it not wroth bothering with RAW, as by the time you get to the end of the process, with all the extra steps and work involved in handling RAW, you pretty much wind up with something that looks like a JPG anyway, and you had to give up using some of the camera's features to use RAW.
    This shows that you don't understand what Raw is and what its advantages over JPG are.
    I would recommend that you educate yourself about the advantages of Raw. Your photography would benefit from this, believe me.
    Google "Why should I shot Raw?" and you will find lots of good webpages.
    Finally, Raw shooting is much simpler than shooting JPGs where you always have to fiddle with the virtual 100s of different settings for JPGs.
    What do you have Lr for? In Lr you can adjust your Raw image by looking at it on a large calibrated monitor, whereas for the settings in your camera you have to rely on a 3" monitor - at best.
    Make your life simpler and your photography better: Shoot Raw.

Maybe you are looking for

  • How do I install iphoto for my mac with my start up discs for my mac?

    I have an mac OSx which was bought in may 2005. Mac gave any new mac users the iphoto program into the mac installed discs. ( I have 2 I dont know which one its on) My iphoto needs to be reinstalled as its not importing photos anymore. I need to inst

  • Sending Mail to all E-Mail Accounts for a Contact

    Hi all, When I'm sending mail to someone in Address Book, is there a way I can send the mail to all of their email accounts? Thanks

  • Dynamic Implicit Structure Creation Question

    Hello, I was curious if it was possible to dynamically create an implicit structure where you might occasionally want to omit some keys from being added to the structure? I played around with using ternary operators in the structure creation with no

  • I have cs6 and getting error. waiting for bridge cs6.can any one help?

    I have photoshop cs6. Getting error message waiting for bridge CS6. tried contacting adobe and they don't seem to be able to resolve the problem. they say they will ring back but don't. Is their any one who can help please. i have a macbook pro runni

  • Where to find Invoice Detail Condition Value

    Hi Folks! I'm working on a report where I need a column that brings me a total of shipping(condition value) where its value is entered manually when creating the invoice. I know that the table KONV is the table that contains the information of the co