About elie_di

elie_di · ‎Feb 26, 2018

The OP has been rather unclear in describing her problem, but since she has said that the Save button is greyed out, I think that she is referring to the OS's Save dialog window that LR calls up. That is the only place where she would see a "Save" button, not the in the LR Print Module interface where the relevant button is labelled "JPG File". To Heather > I strongly advise not using the Print to JPG File function to output edited jpgs, but rather the Export function. At least until you hav learned a bit more "tech". Print To File can be tricky. For instance, it will resize your image so that it fits on the paper size you have selected at the resolution (PPI) you have selected. It will include in the new jpg any margins set for the print. Export is comparatively straight-forward.

elie_di · ‎Feb 25, 2018

The only way LR can know exactly which photos you want Auto Synch used on is that you tell it. You tell it by selecting those photos. You can only select those photos that are displayed in the Filmstrip and the Library Grid or have been designated for display in those modes when they are on-screen. Ergo, Auto Synch can only be applied to photos in the Filmstrip. Otherwise, a change to one photo would cause tens of thousands to be changed; in fact, all on-line photos. No connection to CR Cache.

elie_di · ‎Feb 22, 2018

Do you understand that LR Classic 7.x is only available on a subscription basis and that the basic Photography Package also includes Photoshop CC 2018 and 20 GB of cloud space?

elie_di · ‎Feb 21, 2018

"I'm trying to figure out the best way to get maximum detail without adding any "false" tone in the highlights." The "best" way is to learn how to expose a Raw file without clipping it although you are exposing as close to clipping as is possible. It's the proper way to get the maximum tonal range and minimum noise from your camera and the best conversion from the Raw Convertor software and it's called ETTR (Expose To The Right, Google it). Unfortunately it is a technique has to be learned because cameras don't show you a histogram of the Raw image data but rather of a processed jpg and Lightroom does essentially the same thing, displaying an image and a histogram derived from it that are predictive of what will be exported. Fortunately there are computer applications that will show you the "Raw reality" with a histogram of the Raw and you can learn to correlate between the misleading camera histo and optimum Raw exposure. The two that I use constantly are from the same authors, Fast Raw Viewer and Raw Digger. https://www.fastrawviewer.com/?utm_source=program&utm_medium=site&utm_campaign=FRV When shooting subjects that require the best possible ETTR exposure, I shoot bracketed triplets +/- a third of a stop, and pick the best ones in FRV before sending them on to LR.

elie_di · ‎Feb 14, 2018

In his book "Landscapes in Lightroom", Michael Frye writes that in P.V. 2012 the default zero positions actually represent increased exposure and contrast, above the "zeroed" values in previous PVs, and that a more truly "neutral" default would be Exposure -1.0 and Contrast -33. Also, LR (and ACR) makes an additional adjustment to exposure called the Baseline Exposure that is unique to the camera model and the used ISO setting. To see what your camera's BLE is, convert a Raw to DNG and look for it in the DNG's EXIF.

elie_di · ‎Feb 13, 2018

By me too.

elie_di · ‎Feb 11, 2018

Tensas wrote Yes, I always unzip the backup. Lightroom starts to open the catalog and then tells me the catalog is corrupt. There are a lot of people who think they have a secure backup but in truth have none. Adobe needs to get this issue resolved I have always tested my backups for numerous programs for 40 years. The only real way to know you have a secure backup is to test it as soon as you make it. D You are right. And like a jerk, despite always copying catalog backups to several different locations, I never actually tested them until after reading this thread. I can confirm that I also have this problem (LR Classic 7.1, Windows 10).

elie_di · ‎Feb 11, 2018

>"Choose embedded & sidecar method. Lightroom will use the camera preview." >"Okay. Learn something new everyday." It should be pointed out that this is a new feature introduced in LR Classic 7.0. It can indeed be a useful "speed-up" tool for the experienced or power user, but I am a bit concerned that new users may set it without understanding that what they see in the Library module will not reflect what LR intends to do to their image until some action is taken that causes a new preview to be created. On one hand that will avoid all those cries of, "Why is LR ruining my pictures?" but if exporting directly from Library the difference between Loupe view and an exported default RGB render could be significant, especially if the camera is set for strong jpg processing.

elie_di · ‎Feb 08, 2018

I would like LR to take no action AT ALL on my files. .... my goal is to get raw files untouched so the LR settings called "zero" (on my version in French) is best for me. If you know what a Raw file is, you will understand that this is impossible. A Raw is data file containing a digital representation of the analog output from the camera's sensor (voltages caused by incoming light intensities). It contains a single channel, a number for each pixel, and therefore an image built directly from Raw data would be only tones of grey. The color image with three channels per pixel is created by the Raw converter, either the one in your camera or Lightroom, through a process called "Demosaicing". The Raw image would also be dark and flat because the data is linear. Another part of the processing for color involves the application of a correction curve that makes it brighter and contrastier. So some processing has to be done by every Raw converter to every Raw file even to get to the "minimum". Even when the sliders are at zero LR's processing is fairly strong, because "zero" does not mean "none". Michael Frye, in his book "Landscapes in Lightroom", says that since the introduction of Process Version 3 in 2012, minimal processing would be Exposure -1.0 and Contrast -33. An additional factor is that Lightroom does another automatic correction to Raw images that is based on the camera model and the shooting ISO, called the Baseline Exposure. For instance, for my Canon 80D the BLE is ISO 100 - 0, ISO 200 - +0.28 and ISO 400 and up - +0.32. In the photos below, on the left is the Raw image as seen in Raw Digger; the middle is a minimally processed RGB rendering by Raw Digger; and on the right is Lightroom with all sliders zeroed.

elie_di · ‎Feb 03, 2018

New Color Fringe Correction Controls CA and Fringe corrections cannot be tied to one particular lens.

elie_di · ‎Feb 03, 2018

What is the "Custom" and "Save New Lens Profile Default" for if not to customise the profile? And in fact that is exactly what they do. But your question and what you want to do have nothing to do with that or any lenses profile. IIRC, it was back in Vs. 4 (P.V. 2012) that the new CA Correction and Fringe Correction became separate and independent tools that were no longer part of the profiled lens corrections and functioned without regard for whether the profile was applied or not. Profiles now control only Vignetting and Distortion.

elie_di · ‎Jan 30, 2018

Image data is different from metadata. Lr will not change image data in the original file, but it can change metadata in a jpg, tiff or dng. Metadata is contained in a separate part of the file and a change of metadata cannot in itself cause a change in the image data. The metadata contains several subdivisions such as EXIF. Maker Notes, Color Profile, XMP, etc. At most, if the change to metadata involves the embedding of an editing xmp written by LR, other Adobe software which uses Camera Raw (as does LR) will understand that the xmp contains editing adjustments for it to use when displaying or rendering the image, but the image data in the file on your hard drive will not be itself changed until you overwrite it or write a new file.

elie_di · ‎Jan 30, 2018

Recently, any edits made in lightroom no longer show in original files despite xmp being created. Absolutely. Always has been that way. LR never changes original files. That is why the edits are saved in the catalog database and, optionally, in xmps. Only an application that can read and implement the xmp data will apply the edits, so that means primarily Adobe products. To obtain image files that have been rendered with the edits, you have to export a whole new file.

elie_di · ‎Jan 30, 2018

But what D Fosse has also said - and you haven't related to it - is that very few of your web viewers will be doing so on calibrated, profiled, and color managed HDR monitors. Just as only a minority of today's viewers have a Wide Gamut monitor (although they have been around for much longer) and therefore the current advise is to reduce the gamut of your web postings to sRGB. Will you upload "as is" photos that look great by you to Flickr and on my six year old monitor will I see blown whites and blocked up shadows? Being in the tech vanguard may sound attractive, nevertheless you will sometimes need to consider exactly where that state-of-the-art, "paradigm shift of viewing photos on a screen" is really at (to say nothing of the limitations of human vision until the day when we all have USB slots on our foreheads).

elie_di · ‎Jan 29, 2018

Also it would be nice if saturation and vibrance is not automatically applied or if I could select the settings to be applied for auto tone. Double-click on "Presence" to zero out Vibrance and Saturation. To apply Auto to individual tone values instead of all at once, hold Shift and double-click on the value's name or on the slider. Auto Settings attempts to bring your image to a standard established by the analysis of thousands of photos submitted by a panel of pros and fed into Adobe's Sensei AI. Start from a flattish, conservative profile like Camera Neutral, more "jazz" will be added; start from a contrasty and saturated profile and the changes will be less. But in both cases the result will be similar to the "pro standard". It may not suit your taste, but it's hard to see what Adobe could have done otherwise. I doubt a standard based on jpgs from cellphones would have gone over well.

elie_di · ‎Jan 29, 2018

Or mask the entire image by brushing over it with a very large hard brush (or by setting a Grad Filter that covers the entire image) and then erase the mask over the subject.

elie_di · ‎Jan 29, 2018

in m version of LR there is no checkbox to check and I have read elsewhere that the checkbox functionality was discontinued in some version of LR CC. Apparently, what you read was mistaken:

elie_di · ‎Jan 27, 2018

The size of a jpg file in MB is determined by four factors: 1. The pixel dimensions of the image - obviously cropping involves discarding pixels and thus reducing the number of pixels and the file size. Likewise downsampling in the Export dialog. 2. Jpgs are always 8 bits - hence even before compression the image data is half of what it would be when written to 16 bits. 3. The amount of compression - better quality = less compression and vice versa. 4. The amount of detail and/or noise in the image - areas of uniform color compress better.

elie_di · ‎Jan 24, 2018

Don't confuse jpg compression and image resolution. The server has to decompress the jpg before reading it into memory and a 57 MB uncompressed size indicates that it is a high resolution 20 Megapixel image (around 3600x5400), probably still at the camera's native resolution and enough to choke the server. Moreover, even on a 4K monitor any browser would have to downscale it. Do the job yourself in LR; downsizing to something more web-friendly, like 2000x3000, and applying Output Sharpening when exporting the jpg (which will then be of better quality because it won't have to be compressed so much).

elie_di · ‎Jan 22, 2018

Poor show from Adobe and Apple, particularly Adobe as I only bought it 14 months ago. You may have bought it 14 months ago, but the wisdom of that purchase is questionable because LR 5 became obsolete and unsupported 33 months ago when it was replaced by LR 6. Perhaps the price reduction justified it. So what blame attaches to Adobe if software developed and tested more than 53 months ago does not work well with an OS released 4 months ago? Does any software maker/vendor resurrect and revise unsupported past versions to accommodate new Operating Systems? Caveat Emptor.

elie_di · ‎Jan 21, 2018

alang63882204 wrote Yesterday, taking a close look at the Creative Cloud master apps panel on the iMac, I finally discovered what my real problem was. Apparently the LR Classic I had been using after Creative Cloud installation, accessed at the same icon as my old LR 6, was not current 7.1 Classic at all but an interim version of Classic called LR 2015 ! Confusingly, this 2015 version is titled Lightroom CC, because the name change of the installed version to Lightroom Classic toook place after that release. That explains why I had never seen the Catalog update process that was supposed to take place when using Classic on an LR 6 catalog for the first time, and why so many dialogs and tabs cited in other posts were missing in my new LR..... When I upgraded to Creative Cloud, I knew that I wanted the installed version currently called Lightroom Classic, and I thought that was what I was getting after the installation. What I didn't realize, and what I think will trap quite a few people, is that I was actually getting an intermediate version with features above LR 6, but not the latest LR 7.1 . It happens that t he only new editing feature I have used so far is Dehaze Filter, which was in the intermediate version. This is not really accurate and demonstrates your misunderstanding. Lightroom CC 2015 was the subscription version of LR that ran parallel to LR 6. It was first released (together with LR 6) in April 2015 - hence the name - and had a two and a half years lifespan until it was replaced by LR Classic 7.0 in Oct. 2017. Hardly an "interim" or "intermediate" version. During its life it received, by virtue of its being the subscription version, new features that LR 6 did not receive. Apparently you did not investigate enough to reveal that what you had installed was not the latest available version to which your subscription entitled you; a fact that could have easily be seen by simply opening Help/About ( a recommended practice after the installation of any software) or Help/System Info. Undoubtedly your confusion was compounded by Adobe's unfortunate naming policy, but a little more consumer-awareness research when signing up for the subscription package could have prevented it.

elie_di · ‎Jan 20, 2018

I think Richard has put his finger on it. And I admit that the My Catalog caption could be misunderstood unless you are aware that photo files, whether Raw or rendered, can never be "in" LR or "in" the catalog because the catalog is a single database file, a place where information about the photos is stored. All that is being sent to the catalog when "Add" is highlighted is that information.

elie_di · ‎Jan 20, 2018

"As soon as I click add it directs to my C drive rather than my external NTFS formatted hard drive." That's not what your second screen shot above shows. "Add" is selected and you are still importing the same files from My Passport (E:)/..../2915_09_19_stair, but without any destination being indicated on the right side, normal behavior for the "Add" option which means "Leave In Place, Do Not Move Or Copy". So what is being directed to the C: drive? Do you mean that when you click on the "Import" button at the bottom right, a new folder is being created on C: and the files are moved or copied to it? This would indeed be a bug and a bad one, but otherwise I don't see an LR bug. Please clarify.

elie_di · ‎Jan 20, 2018

The current version of LR Classic, version 7.1, was released on Dec. 12, which was less than a month after the lens was available in mid-November. Apparently Adobe did not obtain a production copy for profiling in time to support it. It may be supported in the next update. "Dot" updates are usually about three months apart.

elie_di · ‎Jan 19, 2018

Only problem might be if the 'same' colors exist on the subject that should not change. Many have asked Abode to make HSL available in the Tool options as well as 'Global'. In many ways the new Color Range Masking in Local Adjustments fulfills the desire for local HSL settings. And in regard to controlling the tonality it is better than the rather clumsy Luminance in HSL, since there are five tonality tools available. Less precise control over Hue, but I suppose the selected color's hue can be changed with a blended color overlay or by fiddling with WB Temp and Tint.

elie_di · ‎Jan 19, 2018

If you use "Copy as DNG" and also tick the box for "Make a second copy to:" in the right side File Handling panel, the second copy will be a copy of the original Raw on the memory card; so you can have it both ways, both a NEF and a cataloged DNG.

elie_di · ‎Jan 18, 2018

Two important facts apply here: 1. A Raw file is what its name implies; raw, unprocessed data from the sensor. The only operation that was done on it by the camera firmware was the digitizing of the sensor's analog output (voltages). A Raw doesn't even have color data, because sensor voltages are caused by the intensity of the light hitting it, not its color. The color is interpolated in by Lightroom along with a lot of other image adjustments, including WB. So when LR applies that processing it is the first time, like a flower being grown from virgin soil. A Jpg is the product of such processing, whether done by a Raw conversion application or by the camera firmware. The image data has been "baked in", it is a grown flower. You can do some tweaking - prune some branches, paint the petals with paint (a' la Alice in Wonderland), but you can't convincingly change a dandelion to a rose. 2. Nowadays cameras write Raw data with 14 bit precision, or at least 12 bits. LR does its calculations to 16 bit precision. Jpgs contain only 8 bit data. In the conversion to 8 bits a lot of the original data is lost to rounding off, like my telling you I have 5 dollars when I really have 542 cents. Also, Jpgs are always compressed files; the first thing any app does when opening them is to decompress it. In these two operations more data is lost. High bit depth and abundant data gives flexibility in processing Raws that Jpgs can't have.

elie_di · ‎Jan 18, 2018

https://forums.adobe.com/people/Per+Berntsen wrote If you have Acrobat Pro (not Acrobat Reader), you can open images from the pdf in Photoshop to check the ppi. With Acrobat Reader DC installed PSCC 2018 can open pdf image.

elie_di · ‎Jan 17, 2018

The RX 10 III was first supported in Lightroom 6.5.1/CC 2015.5.1 so LR 5 will not open its Raw files. Moreover, the .ARW files contain an embedded profile for the built-in lens which LR will apply automatically in all versions that support the camera (6.5.1 and higher). Jpg files will already have had the lens profile applied by the camera.

elie_di · ‎Jan 16, 2018

46232 wrote . This file now opens in Camera Raw, and not in Photoshop, for files processed prior to the 3rd of October, they open in Photoshop (this is true for both Bridge and Photoshop). My conclusion is that something in Lightroom has changed and the impact is that a file now opens in Camera RAW and not Photoshop. Again, any advice on this would be gratefully received. Charlie Except that your time-line doesn't fit the schedule of Lightroom updates and upgrades: LR 6.12/CC 2015.12 - July 18, LR Classic 7.0 - October 18, LR 6.13 - October 26. So unless you delayed updating from 6.10.1/2015.10/1 to 6.12/2015.12 until two and a half months after its release, it's hard to understand why LR would have changed on October 3. However, I still think that changing Camera Raw Preferences to "Disable Jpg Support" will solve your current problem. BTW, you haven't actually said what versions of LR and PS/ACR you are using.

About elie_di

Re: ? print to file greyed out

Re: Develop Module: Auto Synch only works on photo...

Re: From Lightroom 5 to Lightroom CC Classic ??? 5...

Re: Does highlight recovery add neutral density?

Re: Defaults add too much contrast in raw files

Re: Lightroom Classic CC Backup Catalog Corrupted

Re: Lightroom Classic CC Backup Catalog Corrupted

Re: Turn off Smart Previews on Import

Re: Import parameters to zero

Re: Lr6 custom Lens Corrections Q:

Re: Lr6 custom Lens Corrections Q:

Re: Edits in lightroom not showing in original fil...

Re: Edits in lightroom not showing in original fil...

Re: Lightroom on MacBook Pro with 4K HDR monitor

Re: New Auto Tone of 7.1 dependent of Camera Profi...

Re: Is there a way to invert an Adjustment Brush m...

Re: Unwanted subfolder appears on import

Re: After cropping the resultant photo is much sma...

Re: File size misreading

Re: Lightroom 5.7 Crashes Trying to Import

Re: WARNING for new Creative Cloud users!

Re: Why can't I no longer import photos into my ex...

Re: Why can't I no longer import photos into my ex...

Re: Canon EF 85mm f/1.4 IS USM - Profile Correctio...

Re: Color grading questions

Re: RAW to DNG on import

Re: White Balance

Re: "Export to pdf" creates file with incorrect re...

Re: Lightroom 5 LCP for Sony RX10 III

Re: Lightroom turns on the Development Adjustment ...