Is it standard practice to work on 16 bit files?
Announcement
Collapse
No announcement yet.
16 bit files
Collapse
X
-
Re: 16 bit files
If that's your standard, yes. 8,16,32 are all widely used.
16 is the most common for published work, yes.
It's about knowing what you need, and not wasting time on 16 when noone is going to know the difference, or knowing that you need that 32bit on some composite work in order no to clip things etc.
-
Re: 16 bit files
Lot's of info and debate out there. Here are 3 from my bookmarks:
In my last column on relative gamut sizes in color spaces such as my eponymously named Bruce RGB, I promised to address the topic of large-gamut spaces in a future column. Before tackling that topic, I need to clarify another, related issue: It's a rare week that passes without someone asking me what the point
Comment
-
Re: 16 bit files
If you are working on an industrial strength Mac I would work 16bit as the larger file size won't make too much difference to your speed. 50% of the images I work on come from Maya as 32 bit RGB files; they invariably go out the door as 8bit CMYK. The differences in quality are easy to spot but that is only by comparing two images side by side - not something the end viewer will be able to do or care about. Looking at 16 and 8 side by side will show up differences in tonal integrity but it is very much case dependent. I would archive as 16bit basically to futureproof the file - could be that those subtle but significant differences will be easier to appreciate in print or digitally further down the line.
Comment
-
Re: 16 bit files
Lemme put it this way:
You're working a 20$ an image quick catalog/web retouch, you're doing it at 8bit and forgetting about it. Same for the model test, portrait for print that is quater of the page or smaller...
You're doing a campaign with plenty of DNB, you want those extra bits.
Comment
-
Re: 16 bit files
Originally posted by Repairman View PostIf you are working on an industrial strength Mac I would work 16bit as the larger file size won't make too much difference to your speed. 50% of the images I work on come from Maya as 32 bit RGB files; they invariably go out the door as 8bit CMYK. The differences in quality are easy to spot but that is only by comparing two images side by side - not something the end viewer will be able to do or care about. Looking at 16 and 8 side by side will show up differences in tonal integrity but it is very much case dependent. I would archive as 16bit basically to futureproof the file - could be that those subtle but significant differences will be easier to appreciate in print or digitally further down the line.
I've expected to see more raw converters go that way for years. I mean you do have some rounding as floating point math is different in the sense that not every number in its range is a part of its domain, but it's viable with a stable math library and 32 bit encoding. We just need more packages to support a full set of tools in that encoding, which unfortunately means a much more significant rewrite than what it took to go from 8 bits to 16.
Comment
-
Re: 16 bit files
There are probably two major differences that would be of interest to you.
The first is that each time the value doubles, the brightness doubles. The second is that you have a much much wider range of values that can be stored. Instead of 0-255, the equivalent range is 0.0 to 1.0, but it can store values in excess of 10.0 or -10.0 assuming you don't make any changes that force it to clip anything outside of the 0 to 1.0 range. I don't have a full list of actions that force that. For example you have to test profile conversions, as different color engines deal with these things differently.
When I mentioned ICC v2 vs v4, they're both ICC profile types. v2 are the older ones, which cannot be used in photoshop's 32 bit mode. Maya uses something that they refer to as linear sRGB, and I see the name come up quite a bit. I haven't been able to find a standardized representation of it. Anyway just like with other profiles, these things are converted to a form suitable for viewing on screen.
I guess the thing that's really interesting is you should have some ability to bring back blown highlights and things if you receive a 32 bit file that wasn't set to clamp anything that fell a couple stops out of range. Some color correction tools also offer a lot more flexibility, and they could design dodge/burn tools that would also offer greater flexibility. By the way clamp = clip for all practical purposes.
Some software has also started to implement or implemented linear tools for painting. There's sillouette fx, and I think Krita has some on the open source end. The OSX version is still basically alpha software, but I want to contribute to it if I get the time. I've said for years that Adobe should go this route.
Regarding raw files you could basically dump the full range of that file from lightroom into photoshop still in Adobe's linear prophoto space (prophoto isn't ideal, but it's what they use) without converting to a narrower gamut and clipping anything out of range. If you combined that with some of the newer edge finding algorithms that have surfaced in the past five years or so (ironically microsoft research has contributed to this), you could get a really nice balance of contrast and details. I don't really care for the typical cartoony HDR thing, but you just gain so much more control with such a workflow.
Comment
-
Re: 16 bit files
Or even simpler...
It's all number of combinations 8bit has 256 different lightness values for R, G and B.
16 bit has 65536.
32bit has 16777216.
Just an example, I know it's not real thing that you can see, and that it depends on the actual color profile blah blah.
But, what does this mean? Well, in reality, it means smoother transitions when you start pushing pixels.
So, a curve applied to something smooth like a sunny sky in 8 bit might leave you with a posterized looking result.
16 bit bit file, when affected by the same curve will be much smoother.
And 32 bit? Well, it won't even clip where the 16 bit clips, meaning if you blow something out, and than do an opposite adjustment, it might just bring it back. Why? Because there is more tonal differences.
Comment
-
Re: 16 bit files
Originally posted by skoobey View PostOr even simpler...
It's all number of combinations 8bit has 256 different lightness values for R, G and B.
16 bit has 65536.
32bit has 16777216.
Just an example, I know it's not real thing that you can see, and that it depends on the actual color profile blah blah.
Comment
-
Re: 16 bit files
Sometimes the conversion from 32 to 16 does zap the image creating the blown out effect. PS HDR Toning set to Exposure and Gamma (at default setting) seems to restore the image to normal - is that the best way to resolve the issue (in real world scenario rather than theoretically).
Comment
-
Re: 16 bit files
Originally posted by Repairman View PostPS HDR Toning set to Exposure and Gamma (at default setting) seems to restore the image to normal - is that the best way to resolve the issue (in real world scenario rather than theoretically).
Comment
Related Topics
Collapse
-
by DroptGood morning everyone,
As there is no small questions thread, I find myself opening up a whole new subject for a small question. Here's the deal and it's quite simple : My boss has given me a 16 bits camera file to convert in 8 bits, then retouch. So far so good. But he's also adding (quoted...-
Channel: Input/Output/Workflow
08-31-2011, 04:50 AM -
-
by Elmer BThis one has got me slightly (only slightly?
!) confused.
I have a collection of multi-layered psd files which contain on average 10 saved layer comps used for creating system icons. In total there are 66 files, looking at their thumbnails in Windows 7 the other day I noticed...-
Channel: Input/Output/Workflow
04-20-2010, 10:06 PM -
-
Hi there...
Is there any option to reduce a size of TIFF files without of loosing quality.
One 16 Bit TIFF in PROPhotoRGB converted from NEF file form 10 MP Nikon D80 has about 60 MB and when I finish retouching it has almost 1,6 GB. Of course I could flatten the image or merge...-
Channel: Photo Retouching
08-23-2008, 09:50 AM -
-
by Tony WIn another thread I posted the following about my current belief and understanding relating to converting 8 bit files to 16 bit i.e. I doubted that any real benefits would be had and further that there may be potential to make matters worse by taking this course. Quote:
When I started using...-
Channel: Software
07-24-2011, 06:02 PM -
-
by rlualhatiHello,
I'm about to venture into editing in 16-bit mode. I've been doing some research, gathering facts...and I'd like to ask a few questions to help tie it all together.
So before I got "smart" by shooting in RAW a few years ago, I captured a decent shot of...-
Channel: Photo Retouching
02-09-2012, 11:00 AM -
Comment