gerardo2068
TPF Noob!
- Joined
- Sep 30, 2011
- Messages
- 331
- Reaction score
- 12
- Website
- 500px.com
- Can others edit my Photos
- Photos NOT OK to edit
Peano said:Why would you flatten the image?
I meant to say export it as jpeg. In that context
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
Peano said:Why would you flatten the image?
There's basically no point in shooting in Raw 16bit (65,536 values) and converting to (usually jpeg) 8 bit (250 values). Might as well shoot in Jpeg.
If you don't use any plug ins that you might have an issue with, why are you exporting to 8bit? If you find one random one thats not compatable, wouldn't it make more sense to just change the mode on that single one to 8 bit rather than compress them all on the off chance you'll use a 3rd party plug in that might not work?
This statement is kind of like saying that ALL jpegs of the same image would always be the same. That's not true. You are adjusting the output from the raw in lightroom What you export from that post processing will look VERY different than what the camera would have processed-which is the beauty if shooting raw. You control what that output into your jpeg is.
I do not keep my raws or dng's. Along this line of thinking it was silly for me to shoot in raw to begin with. I can tell you that what the camera puts out in jpeg mode is VASTLY different than what I put out in a jpeg for editing. I have no NEED to have that 16bit in photoshop... the only reason I don't change it is because I don't need to. However what I am putting out at the end of my PS action is an 8-bit, sRGB, jpeg for both print and internet use.
I'm talking about what the OP is doing, pulling files straight from the camera into Lightroom and converting there, then working on 8 bit files. I'd be surprised if there was that big of a difference between a camera compression and a LR compression. We're not talking about post processing at this point.
We're talking about the same thing, just different stages.
One thing that hasn't been mentioned is the relationship with colour space. sRGB may be OK to work on in 8-bit, and Adobe RGB might be marginal, but any colour space larger than those two should be used with 16-bit.
Yes, of course.When you make those changes on a 16 bit image, the gaps are smaller...and when you make those changes to an 8 bit image, the gaps are larger.
This assumes that you're starting with a raw file and exporting it to PS in 16-bit mode. If you start with a jpeg (which is 8-bit, of course), converting to 16-bit for editing won't have any effect.
A compressed 8 bit JPEG typically contains less than 20% of the data in a RAW file and less than 10% of the data in the original scene.
I'd be interested to know how you arrived at these figures. I tested a raw file that is 7.74 MB. When saved as a jpeg directly from ACR with no editing, the file size is 4.25 MB. That's 54 percent of the raw file -- a big loss, to be sure, but considerably less than 80+ percent.
As I understand it. If you are going to be making edit/changes, it's best to be working in the larger color space. If you're just going to be making a few tweaks, resize, sharpen etc., then you don't risk much by choosing the smaller space earlier in the workflow.Helen, I would appreciate your further thoughts and expertise on this topic. We use color spaces (ProPhoto) that can't be realized on our hardware -- so an issue of practice versus theory. Most of us really can't afford a 24 inch ColorEdge display and even that can't handle the ProPhoto space. The theory is telling me that I want to keep the RAW converter working space ProPhoto and the 16 bit RGB image ProPhoto so that if I make adjustments I won't mangle my data trying to twist and bend it inside a container that's too small to process my changes. I think I get the theory, but I struggle with doing anything in photography that I can't directly SEE! It bothers the #$*&%& out of me to think that I'm working with a photo and my window on that photo is partially obscured while I'm trying to adjust the image characteristics. I've had the horrible experience of trying to edit a photo on a laptop for example and the even more horrible experience of later viewing the result of that effort on a good display. I personally don't use LR but if I had a nickle for every photographer who's asked me about why their photo looks different after they've exported it from LR, well, I am retired. So I have this gut response that makes me want to RAW convert straight to an 8 bit sRGB and view the image using a good sRGB display (that I can afford) so I can SEE what I've done. When I'm working on the photo in the RAW converter again the same practical issue applies; my viewing window is limited! And so my gut again wants to set the working space in the converter to sRGB and convert straight to 8 bit sRGB -- no surprises! When I'm working with a 16 bit photo in the ProPhoto color space on a display that barely manages 95% of sRGB, I can't shake this uneasy feeling that something is going to jump up and bite me in the butt. I'm basically happy with my end result but I do get an occasional surprise as I make the ProPhoto to sRGB reduction and then I find myself tweaking the photo yet again. My confidence is subtly shaken by this nagging thought that if I adjust my photo while in the ProPhoto color space (including in the RAW converter), something is happening that I can't SEE and wouldn't I be better off preventing that earlier on in the process.
Thanks,
Joe
I'd argue if anything the loss is more extreme than my rough suggests.
I'm a confirmed raw shooter, so I'm not defending jpeg over raw. But your "rough" estimate is a long way from that of Bruce Fraser and Jeff Schewe in their book Real World Camera Raw. They say that when shooting jpeg, "you trust the camera to throw away one-third of your data ...."
Well clearly they're wrong then. 16 bit to 8 bit is 1/2 not 1/3 -- 16/8 = 2.........
So are you all saving your files as 16 bit TIF or PSD? How could you possible store all those files? Personally, when I up-sample from camera RAW 14 Bit to PSD I have a 500MB file out of my FF cameras (D700 and D3S). I see what everyone here is saying and agree that the output is much better but how big are you guys actually printing too see this difference?
Please don't take this wrong but it sounds like allot of pixel peeping to me. Do you really need 16 Bit files? Seriously? I may just be missing the point here...