Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: john beardsworth on October 18, 2017, 09:31:33 am
-
I've just published this lengthy article on Lightroom 7's (Lightroom “Classic”) new Embedded & Sidecar workflow here
http://lightroomsolutions.com/embedded-sidecar-workflow-in-lightroom-classic/
John
-
Thank you for that contribution John, I'll read with interest.
-
I'll be posting another one later mainly on what Adobe call "Lightroom CC" and the name shenanigans. A lot of us expected the embargo would be lifted slightly later today, but things started tumbling out a couple of hours early!
-
I've just published this lengthy article on Lightroom 7's (Lightroom “Classic”) new Embedded & Sidecar workflow here
http://lightroomsolutions.com/embedded-sidecar-workflow-in-lightroom-classic/
John
Finally ... it only took a decade of begging for this addition. Although camerabits appreciated all those unnecessary sales of Photo Mechanic due to Adobe's indifference.
-
Thank you John. Very helpful.
-
Finally ... it only took a decade of begging for this addition. Although camerabits appreciated all those unnecessary sales of Photo Mechanic due to Adobe's indifference.
And you know I've been one of those whispering in their ear! It works OK, but I do wish they had done something like Aperture 3 where you could switch to the embedded previews whenever you wanted, rather than being forced to set the option in Import.
-
Thanks for the scoop John. This is a real improvement but I feel LR is still missing the boat on an efficient workflow for photographers facing large imports and culling. A workflow where you still have to import ALL the images into LR before culling is DUMB. The initial cull should be made before importing in the import module by only selecting the winners or deselecting the losers. In my wildlife shoots I typically only import 10-25% of the images on the card. If LR sped up the browsing speed in the import module by prefetching previews this would solve this issue. I won't be ditching photo mechanic yet.
-
I would have preferred if they implemented a solution similar to FastRawViewer in the import module, which lets you check the images based on RAW data and very fast.
This Embedded & Sidecar workflow is useless (IMO) if you use ETTR, UniWB or "ISO less" mode during capture,
-
I would have preferred if they implemented a solution similar to FastRawViewer in the import module, which lets you check the images based on RAW data and very fast.
I agree. However, they'd have to rewrite their code that develops RAW files to optimize it for blazing fast speed and less features, which is exactly what you get with FastRawViewer. They'd then have to maintain two primary code branches: the speed optimized one, and the image quality one. Adobe is awash in cash, but it's hard to see them doing that. It's also not immediately obvious they have enough engineering talent to do it. The FastRawViewer folks are clearly super-talented and hard-working coders. How many Erics does Adobe have? It takes special skills to develop that kind of code.
-
I would have preferred if they implemented a solution similar to FastRawViewer in the import module, which lets you check the images based on RAW data and very fast.
And give us a stinking raw Histogram. No wonder they are embarrassed to call this version 7. :o
-
grazie mille, John, chiarissimo e molto utile.
-
Prego ;)
-
Thank you John. I’m away from my computer for another few days. I’m interested to see if they’ll be using all 4 cores in my i-7 effectively and if they now take advantage of the 8GB RAM video card in my new iMac. It seems like this solution is just a slight of hand trick.
-
The generate previews in parallel preference (enabled by default) makes a big difference. Make sure you do some tests with Lr6 vs "Classic" - I find standard previews generate 4 times faster, 1:1 previews about 2 1/2 times faster. That's with tests of 500 compressed RAFs, which would be more demanding than if you used the demosaiced DNGs from XT.
John
-
thanks, John!!! That's very encouraging. I'll be testing things out this week with "Classic" as I'm back at home again.
-
I hope you noticed the point about Fuji, Ron. I switched to raw + jpeg to take advantage of the changes.
-
The generate previews in parallel preference (enabled by default) makes a big difference. Make sure you do some tests with Lr6 vs "Classic" - I find standard previews generate 4 times faster, 1:1 previews about 2 1/2 times faster. That's with tests of 500 compressed RAFs, which would be more demanding than if you used the demosaiced DNGs from XT.
John
This is 'almost' making me sign up for the subscription model!!!! ;)
-
I hope you noticed the point about Fuji, Ron. I switched to raw + jpeg to take advantage of the changes.
Thanks, John, I did see that. I'm intrigued and will give it a try.
-
If you are processing the files as DNGs, Ron, I've not looked if XT provides an option to embed a full size preview. I would use it though. Sorry if that was obvious.
John
-
I hope you noticed the point about Fuji, Ron. I switched to raw + jpeg to take advantage of the changes.
When you shoot raw+JPEG, which gets the optimal exposure?
-
When you shoot raw+JPEG, which gets the optimal exposure?
Andrew, it’s always a conundrum, isn’t it.
I have decided, that for me raw+jpeg is not worth it. I go straight to 1:1 previews. Before latest, it meant going for a cup of coffee. Now, with classic and speedy system/gpu the wait is short, but worth it when reviewing later.
-
Andrew, it’s always a conundrum, isn’t it.
Only for those that continue to recommend shooting raw+JPEG, like John, but without informing the reader to the severe downside in doing so for (usually) the raw data. Not that optimal exposure isn't photography 101 and not that the concept of exposing optimally for raw wasn't originally found on this site by the founder who invented the ETTR 'term' (which by now needs to go) but more importantly, the correct idea that exposure for raw isn't the same as exposure for a JPEG. Those that care about image data quality often want optimal exposure for the media they are aiming for.
-
Andrew, John was sharing the advantage of shooting RAW+JPG for Fuji X-Trans photographers. It provides good previews quickly from which to choose RAW files that you want to process further. I'm a Fuji X-Trans photographer and once I see a file that is of interest to me I process the RAW to DNG using Iridient Developer or Iridient X-Transformer. For my tastes Iridient provides superior demosaicing and sharpening to what Lightroom offers. The JPGs are typically deleted.
-
Andrew, John was sharing the advantage of shooting RAW+JPG for Fuji X-Trans photographers.
The photographers I know (and trained with) understand the role of optimal exposure for the media they are capturing.
How does one accomplish this shooting raw+JPEG?
The JPGs are typically deleted.
So the capture exposure is optimized for the raw? And the JPEGs look like crap and get deleted.
My comment is about which of the two is optimally exposed for at least those that understand you can't optimize both at the same time; something John and his audience may or may not be aware of.
-
Andrew, shooting RAW+JPG enables Lr Classic to create high res previews MUCH faster. It's NOT about exposure. It's NOT about JPGs looking good or accurate. It's about having large previews that you can get to quickly. An example is when I photograph a day of horse racing and come away with thousands of photos to cull through this is a very real boon for me and I suspect others as well. Waiting for Lr to take an hour to create previews is painful.
Yes, I know how to expose properly and get good color.
-
Andrew, shooting RAW+JPG enables Lr Classic to create high res previews MUCH faster. It's NOT about exposure.
WHICH is exposed correctly? Which isn't? Simple questions with only one answer.
-
How can the Raw and the JPEG have different exposures? Do any cameras allow you to do that?
-
How can the Raw and the JPEG have different exposures? Do any cameras allow you to do that?
Do you suppose he’s asking the person on his ignore list to explain how a raw plus JPEG capture can’t be optimally exposed for both?
-
How can the Raw and the JPEG have different exposures? Do any cameras allow you to do that?
They don’t
What Andrew is talking about is you can optimize each of them differently. The best exposure for a jpeg will, most often, not be the exposure that allows you the best dynamic range after processing the raw file...such as ETTR. The jpeg exposed this way will be useless in reviewing the image.
White balance could be another difference. Also, in camera sharpness and contrast settings.
-
They don’t.
Thanks.
-
Do any cameras allow you to do that?
Unfortunately not
-
Thanks.
But you knew that....
-
But you knew that....
Whenever I hear anyone recommend a raw+JPEG capture, I have to ask them if they fully realize what they are giving up in terms of image data in the raw due to under exposure.
So some know, some don't but they keep recommending the workflow without the warnings.
-
I'd be happy to shoot RAW only for everything IF Adobe could create high res previews in a more expeditious manner. Do I shoot RAW+JPG for everything? No. It is a real boon though for sports. I've never encountered a person who told me that my sports photos didn't have perfect color or exposure after processing.
-
Whenever I hear anyone recommend a raw+JPEG capture, I have to ask them if they fully realize what they are giving up in terms of image data in the raw due to under exposure.
So some know, some don't but they keep recommending the workflow without the warnings.
Andrew .. the whole point of this thread and the new feature brought to Lightroom Classic is not to optimize a RAW+jpeg workflow ... it is merely a method to allow much quicker culling utilizing the embedded jpeg files for RAW image files .... and a workaround for Fuji cameras in order to use of the feature is to shoot RAW+jpeg for now to take advantage.
For the purpose of this specific feature ... the accompanying jpeg files from the Fuji cameras and their potentially incorrect exposure is inconsequential beyond the initial viewing/culling process.
I, and others have been asking for this capability for over a decade. After shooting sports, news, events and timely features for over 45 years, that must meed strict deadlines, the time it takes to render/build previews can be costly. I can evaluate an image based upon the embedded or sidecar jpeg just fine regardless if the jpeg preview has received 'optimum' exposure consideration. It isn't a real world issue in the sense that for this instance the accompanying jpeg for Fuji cameras is important at all once these initial steps are completed.
-
Andrew .. the whole point of this thread and the new feature brought to Lightroom Classic is not to optimize a RAW+jpeg workflow ... it is merely a method to allow much quicker culling utilizing the embedded jpeg files for RAW image files .... and a workaround for Fuji cameras in order to use of the feature is to shoot RAW+jpeg for now to take advantage.
Not only am I aware of that, it doesn't change the facts about raw+JPEG and exposure! One has to suffer. At least with my system, the JPEG would be a good 1.5 stops over exposed for optimal raw exposure and I think many here understand the effect on that JPEG in doing so; preview only or not.
Whenever I hear anyone recommend a raw+JPEG capture, I have to ask them if they fully realize what they are giving up in terms of image data in the raw due to under exposure.
So some know, some don't but they keep recommending the workflow without the warnings.
-
Andrew .. the whole point of this thread and the new feature brought to Lightroom Classic is not to optimize a RAW+jpeg workflow ...
For the purpose of this specific feature ... the accompanying jpeg files from the Fuji cameras and their potentially incorrect exposure is inconsequential beyond the initial viewing/culling process.
Yes, though the workaround is not just for Fuji but for Olympus and any other cameras that may embed a low res JPEG.
I do feel mirrorless cameras encourage one to expose to make the photo look right in the viewfinder, rather than the optimal exposure for raw processing. Of course, even if this is more than a theory, it has nothing to do with whether you shoot raw only, raw+jpeg, or use the embedded & sidecar option.
Monty Python (https://www.youtube.com/watch?v=kQFKtI6gn9Y), anyone?
-
Monty Python (https://www.youtube.com/watch?v=kQFKtI6gn9Y), anyone?
Perfect!
-
Not only am I aware of that, it doesn't change the facts about raw+JPEG and exposure! One has to suffer. At least with my system, the JPEG would be a good 1.5 stops over exposed for optimal raw exposure and I think many here understand the effect on that JPEG in doing so; preview only or not.
Whenever I hear anyone recommend a raw+JPEG capture, I have to ask them if they fully realize what they are giving up in terms of image data in the raw due to under exposure.
So some know, some don't but they keep recommending the workflow without the warnings.
Andrew, I think what they're trying to share with you/all the readers, is a view that it doesn't matter. They are using the JPG as a convenience for quick file viewing, so whether it's exposed properly is kind of immaterial - they use the raw file for that, and it's easy to focus on the raw because most cameras nowadays give you the live histogram where you can see in real time whether/what you are clipping in the raw file. I think it's a pointless discussion. Two different formats serving different purposes.
And John, if any one wants to fool themselves relying on a JPG or an EVF view of scene exposure when it's the raw file they intend to process, they need to go back to photography school and learn what the histogram is there for, where the histogram data comes from and how to learn whether their histogram information has a tendency of over-stating or under-stating exposure and DR relative to what comes out in the raw file as interpreted in one's raw converter. One develops a feel for it pretty quickly if one is aware there could be an issue in the first place.
-
Perfect!
+1.
-
John - that was a nice article about the embedded / sidecar image viewing in LR - thanks. However, no good deed goes unpunished apparently.
-
I do feel mirrorless cameras encourage one to expose to make the photo look right in the viewfinder, rather than the optimal exposure for raw processing.
And that idea is incorrect for those who aim is optimal exposure. The sensor and the photon's hitting that sensor don't care about mirrors.
Whenever I hear anyone recommend a raw+JPEG capture, I have to ask them if they fully realize what they are giving up in terms of image data in the raw due to under exposure. I'm not sure you do.
So some know, some don't but they keep recommending the workflow without the warnings.
-
Andrew, I think what they're trying to share with you/all the readers, is a view that it doesn't matter. They are using the JPG as a convenience for quick file viewing, so whether it's exposed properly is kind of immaterial - they use the raw file for that, and it's easy to focus on the raw because most cameras nowadays give you the live histogram where you can see in real time whether/what you are clipping in the raw file. I think it's a pointless discussion. Two different formats serving different purposes.
IT doesn't matter if the raw is optimally exposed; was that recommended? And what of the results of the JPEG by properly exposing for the raw? There's not much convenience IMHO, of viewing a jPEG that's a couple stops over exposed. There's not much convenience IMHO, of ending up with an under exposed raw if a raw has been under exposed a couple stops to view JPEGs.
-
And John, if any one wants to fool themselves relying on a JPG or an EVF view of scene exposure when it's the raw file they intend to process, they need to go back to photography school and learn what the histogram is there for, where the histogram data comes from and how to learn whether their histogram information has a tendency of over-stating or under-stating exposure and DR relative to what comes out in the raw file as interpreted in one's raw converter. One develops a feel for it pretty quickly if one is aware there could be an issue in the first place.
Begging again for a raw Histogram in LR. Not that those shooting JPEG snapshots and moving their entire 1 gig archive of snap's onto the Adobe cloud would have any idea about a Histogram (raw or otherwise) or the idea of optimally exposing for two vastly different kinds of data at the same time.
Some here appear to not fully or perhaps partially understand how to expose optimally:
The current ESP workflow is great for normally-exposed pictures (eg sports in daylight) but not when your work involves less-flat light (eg stage performance, sunsets) when you just can’t judge an underexposed image properly because it’s too dark, or you need to pull back the highlights or open the shadows to see if any worthwhile detail is present. Speed’s no use if you can’t see well enough.
Great for under exposed raws too? Only for those who don't fully care about their data quality!
-
IT doesn't matter if the raw is optimally exposed; was that recommended? And what of the results of the JPEG by properly exposing for the raw? There's not much convenience IMHO, of viewing a jPEG that's a couple stops over exposed. There's not much convenience IMHO, of ending up with an under exposed raw if a raw has been under exposed a couple stops to view JPEGs.
For clarity, the "convenience" aspect is just for a quick review and selection of the photos that one may wish to further work on. You don't need perfect exposures for this. It's mainly to quickly check for subject matter, composition, focus etc.
I don't work that way, I don't use the "raw+jpeg" option in camera, only "raw" - I'm just trying to understand the logic of those posting here who do set for both and find it useful.
-
Begging again for a raw Histogram in LR. Not that those shooting JPEG snapshots and moving their entire 1 gig archive of snap's onto the Adobe cloud would have any idea about a Histogram (raw or otherwise) or the idea of optimally exposing for two vastly different kinds of data at the same time.
Some here appear to not fully or perhaps partially understand how to expose optimally:
The current ESP workflow is great for normally-exposed pictures (eg sports in daylight) but not when your work involves less-flat light (eg stage performance, sunsets) when you just can’t judge an underexposed image properly because it’s too dark, or you need to pull back the highlights or open the shadows to see if any worthwhile detail is present. Speed’s no use if you can’t see well enough.
Great for under exposed raws too? Only for those who don't fully care about their data quality!
There is Rawdigger for - according to them - correctly seeing raw files.
I don't know what you mean by "ESP workflow" - what's that in English?
Again, I'll repeat, I believe those using JPEG renditions of photos for quick reviews aren't too bothered by JPEG exposure issues, especially if they know they've exposed the raw version correctly. You have a point under other assumptions.
-
You don't need perfect exposures for this. It's mainly to quickly check for subject matter, composition, focus etc.
You (who?) doesn't need perfect exposure for what Mark?
We are shooting raw+JPEG as John recommends. Which gets the optimal exposure? IF the raw, fine and does John's article state anything about either ideal exposure for the raw or what the JPEGs will look like IF you expose optimally for the raw? I didn't see that and instead saw text that appears to be from someone very knowledgeable about software and code for plug-in's and a rather severe misunderstanding about exposure in general! He has now actually stated here in the forums:
I do feel mirrorless cameras encourage one to expose to make the photo look right in the viewfinder, rather than the optimal exposure for raw processing.
And in the article I read:
The current ESP workflow is great for normally-exposed pictures (eg sports in daylight) but not when your work involves less-flat light (eg stage performance, sunsets) when you just can’t judge an underexposed image properly because it’s too dark, or you need to pull back the highlights or open the shadows to see if any worthwhile detail is present. Speed’s no use if you can’t see well enough.
See a disgraced for optimal exposure and raw processing based on the recommendations of that text?
See what well enough, the improperly exposed JPEG (because he actually did expose for raw) or the properly exposed JPEG and under exposed raw (because he doesn't understand how to expose for the media he's capturing)?
You shoot raw+JPEG, here are the options as I see it:
Raw is optimally exposed, JPEG isn't. Looks pretty bad.
JPEG is optimally exposed, raw isn't. You degraded your data and ignored exposure 101: back to coding, stop trying to 'teach' basic photography.
Neither is exposed optimally: don't even post!
-
There is Rawdigger for - according to them - correctly seeing raw files.
Great and massively important tool. This too:
https://www.fastrawviewer.com/raw-histogram-for-culling (https://www.fastrawviewer.com/raw-histogram-for-culling)
Too bad LR/ACR doesn't have such a simple and necessary feedback of our data.
As for your question: I don't know what you mean by "ESP workflow" - what's that in English?, neither do I, as I didn't even write that! That's all John's doing; ask him. I'm simply pasting what I saw in the URL provided. That's his quote.
Point is, no matter what he states, and what he perhaps (?)didn't appear to understand: you can't optimally capture raw+JPEG whether the camera has a mirror or not. He doesn't appear to fully understand the role of exposing for a specific type of data and/or feels exposing for raw or JPEG at the same time produces equal quality data in terms of JUST exposure. That's simply not factually correct.
-
Andrew ... all I know is I have been using the option to view the embedded jpegs in RAW image files for faster preview generation when on strict deadline in other applications like Aperture 3 and Photo Mechanic for years without any adverse effects ... even when I may choose to occasionally shoot RAW+jpeg for other reasons.
While I don't necessarily disagree with you on your points in principle ... this is a non issue for the purpose at hand.
By all means, please go on and tell us all about how this won't work ... in the mean time I'm just going to use this new capability as needed to serve my clients more efficiently.
-
By all means, please go on and tell us all about how this won't work ... in the mean time I'm just going to use this new capability as needed to serve my clients more efficiently.
Where did I say it doesn't work? I did say if you capture raw+JPEG, one isn't optimally exposed. Is that incorrect or is it correct?
You can under expose film 3 stops and push process it. It will likely appear fine. Will that be an optimal capture and quality? No. Should people recommend under exposing 3 stops either film or digital? I don't think they should without a warning. None appears in John's URL. Again, I only see these options but I'm willing to view another if someone has such a option:
Raw is optimally exposed, JPEG isn't. Looks pretty bad. By all means, use that for faster previewing if you wish.
JPEG is optimally exposed, raw isn't. You degraded your data and ignored exposure 101: back to coding, stop trying to 'teach' basic photography.
Neither is exposed optimally: don't even post!
This so called Embedded & Sidecar workflow should not ignore the basic facts surrounding exposure of our data. Yet it kind of does. :'(
-
This so called Embedded & Sidecar workflow should not ignore the basic facts surrounding exposure of our data. Yet it kind of does. :'(
A better workflow and of course one Adobe could offer us (don't hold your breath):
https://www.fastrawviewer.com/raw-histogram-for-culling (https://www.fastrawviewer.com/raw-histogram-for-culling)
FastRawViewer is the only culling tool that displays the true RAW histogram. Using FastRawViewer, you will be able to determine if the shot was exposed correctly.
FastRawViewer is extremely useful when selecting the best shot of a bracketed series.
Useful for those of us interested in shots exposed correctly!
-
Where did I say it doesn't work? I did say if you capture raw+JPEG, one isn't optimally exposed. Is that incorrect or is it correct?
You can under expose film 3 stops and push process it. It will likely appear fine. Will that be an optimal capture and quality? No. Should people recommend under exposing 3 stops either film or digital? I don't think they should without a warning. None appears in John's URL. Again, I only see these options but I'm willing to view another if someone has such a option:
Raw is optimally exposed, JPEG isn't. Looks pretty bad. By all means, use that for faster previewing if you wish.
JPEG is optimally exposed, raw isn't. You degraded your data and ignored exposure 101: back to coding, stop trying to 'teach' basic photography.
Neither is exposed optimally: don't even post!
This so called Embedded & Sidecar workflow should not ignore the basic facts surrounding exposure of our data. Yet it kind of does. :'(
With all due respect Andrew, I began my professional photographic career over 47 years ago shooting action sports on Kodachrome 25/64 ... I think I have ample understanding about exposure and how it works.
As I stated before ... in this instance, it's a non issue.
-
With all due respect Andrew, I began my professional photographic career over 47 years ago shooting action sports on Kodachrome 25/64 ... I think I have ample understanding about exposure and how it works.
As I stated before ... in this instance, it's a non issue.
With all due respect, I began my professional photo career prior to graduating from a very good photo school by shooting the 1984 Olympics, on film. As one of only 50 photographers in the world to have total access to shoot for 7 months for the LAOOC. I did attempt, as I do with all captures of film or digital, to expose optimally. That's how I was trained.
IF you are shooting your raws optimally and getting ugly JPEGs to use John's workflow, and you like it, great. I would hope you cannot dispute the answer to a question you didn't answer (I did say if you capture raw+JPEG, one isn't optimally exposed. Is that incorrect or is it correct? ) but I will assume that answer: you are optimally expose for raw, you are letting the JPEG go where it goes and then throw it away. That's fine. It's what John SHOULD recommend to his readers rather than attempt to suggest incorrectly that shooting for the JPEG doesn’t have a negative effect on the raw data. He didn't do that. That's my only point here! In fact, IF you examine my very first post about this 'workflow', I asked John which data he optimally exposes for, the raw or the jPEG. Then he asked a question that gives me the idea he doesn’t understand there IS a difference in how we expose for both. Even if he does, shouldn't his audience know the role of using a raw+JPEG workflow and exposure on both sets of data?
IF someone wants to write an article about shooting raw+JPEG and IF you agree they two demand different exposures for ideal data, should they not discuss exposure and not skirt it giving the impression one exposure for both is ideal for both? It isn't. Unless you or another wants to go on record and state that optimally exposing for the JPEG also provides optimal exposure for raw.
All one has to do is describe the workflow fully and optimally and that wasn't done. Hence my one original question which he didn't answer.
-
A better workflow and of course one Adobe could offer us (don't hold your breath):
https://www.fastrawviewer.com/raw-histogram-for-culling (https://www.fastrawviewer.com/raw-histogram-for-culling)
FastRawViewer is the only culling tool that displays the true RAW histogram. Using FastRawViewer, you will be able to determine if the shot was exposed correctly.
FastRawViewer is extremely useful when selecting the best shot of a bracketed series.
Useful for those of us interested in shots exposed correctly!
Yes, this is part of the Rawdigger software offering, purchased bundled or separately.
-
With all due respect Andrew, I began my professional photographic career over 47 years ago shooting action sports on Kodachrome 25/64 ... I think I have ample understanding about exposure and how it works.
As I stated before ... in this instance, it's a non issue.
Let me try, in my own words, say what I think Andrew is getting at.
When trying to expose for optimal quality, jpegs and raws are exposed differently.
JPEGs are exposed to, essentially, give finished results with minimal tweaks needed.
Raws are exposed to provide the minimum of noise in each sensel. This is done by maximizing the amount of light (exposure) on the sensor. The limit to the exposure is to not overload the senses for the significant highlights. In addition, raws will also not have the benefit(?) of in camera settings of sharpening, contrast, white balance, lighting optimization, whatever. Raws shot this way will require more post processing than jpegs, but CAN result in better images.
This does not mean that jpeg shooting cannot result in fine, acceptable images. Particularly in the hands of an experienced photographer. Often, in those hands, processed raw and jpeg will show little difference. However, depending on conditions, properly exposed raw images can be turned into superior finished images as well as easily corrected for improper exposures.
Where speed of turnaround is important, jpeg and an experienced hand cannot be replace. The new photogs I know only shoot raw and use Photo Mechanic for quick review and selection.
-
Let me try, in my own words, say what I think Andrew is getting at.
When trying to expose for optimal quality, jpegs and raws are exposed differently.
No kidding, really? After shooting RAW (and at times, JPEG) for over twenty years that fact must have escaped my attention. <end sarcasm>
I'm fully aware of that. I am not disputing that is the case. One again at the risk of being repetitive ... IN THIS INSTANCE IT IS NOT AN ISSUE.
-
I'm fully aware of that. I am not disputing that is the case. One again at the risk of being repetitive ... IN THIS INSTANCE IT IS NOT AN ISSUE.
So maybe you can answer the question I asked that John can't** or confirm my assumption of a massive improvement over what John doesn't suggest but should: shoot raw+JPEG, expose optimally for the raw, understand the JPEG will look pretty awful but is only used for previewing and then they will be deleted.
How hard would that be to put into an article on shooting raw+JPEG for an audience that may or may not know there is absolutely a difference in how you expose for either. I'm not sure the author does.....
** http://forum.luminous-landscape.com/index.php?topic=121085.msg1007655#msg1007655 (http://forum.luminous-landscape.com/index.php?topic=121085.msg1006195#msg1006195)
-
No kidding, really? After shooting RAW (and at times, JPEG) for over twenty years that fact must have escaped my attention. <end sarcasm>
I'm fully aware of that. I am not disputing that is the case. One again at the risk of being repetitive ... IN THIS INSTANCE IT IS NOT AN ISSUE.
Gee....thanks for your wisdom
-
How can the Raw and the JPEG have different exposures? Do any cameras allow you to do that?
If one decides on exposure based on a JPEG look/histogram, this one is a bad exposure:
(http://s3.amazonaws.com/IliahBorg/Screen%20shot%202017-10-27%20at%201.21.04%20PM.png)
Quite a different story looking at the raw histogram of the same shot:
(http://s3.amazonaws.com/IliahBorg/Screen%20shot%202017-10-27%20at%201.20.36%20PM.png)
-
By all means ... anyone who has such dire concerns about shooting RAW+jpeg in order to take advantage of the Embedded & Sidecar workflow for certain camera models ... PLEASE DON"T DO IT!
The capability isn't for you. All this wringing of hands and gnashing of teeth isn't worth your effort. Simply maintain your current workflow and let the unworthy trod along aimlessly into the abyss.
-
By all means ... anyone who has such dire concerns about shooting RAW+jpeg in order to take advantage of the Embedded & Sidecar workflow for certain camera models ... PLEASE DON"T DO IT!
The capability isn't for you. All this wringing of hands and gnashing of teeth isn't worth your effort. Simply maintain your current workflow and let the unworthy trod along aimlessly into the abyss.
What you refer to as a workflow is in fact a crunch.
-
What you refer to as a workflow is in fact a crunch.
I'll defer to your superior intellect on the matter. I apologize for reaching beyond my grasp.
However, I think it was Adobe who first referred to the implementation of capability as a 'workflow' ... perhaps you could share your concerns with them.
-
I apologize for reaching beyond my grasp.
Apology accepted.
-
However, I think it was Adobe who first referred to the implementation of capability as a 'workflow' ... perhaps you could share your concerns with them.
The topic and the peer review about exposure & workflow originate here: http://lightroomsolutions.com/embedded-sidecar-workflow-in-lightroom-classic/ (http://lightroomsolutions.com/embedded-sidecar-workflow-in-lightroom-classic/)
I'm very sorry for bringing up exposure in relationship to this workflow. My impression and training is, exposure for our data should be optimally produced as this is a basic and fundamental part of a process some call photography.
-
Iliah, exposure just isn’t the issue here - the real problem is handling the volume of pictures. But when people are snapping action at 5 or 10 or 15 frames per second, I’m sure they’ll pause between frames to contemplate your diagram.
Andrew, I suggest you re-read everyone’s comments until you understand why this workflow is welcome. Using the preview, either the embedded or the sidecar, is rather newsworthy. Not changing exposure or WB or focussing or other aspects of how you take pictures is not, and just isn’t relevant.
Enjoy the Monty Python (https://www.youtube.com/watch?v=MIaORknS1Dk&index=5&list=RDA8yjNbcKkNY).