Known Participant

Question

32-Bit Working Space Benefits?

Forum|Forum|4 years ago
January 14, 2022
3 replies
4759 views

What are the benefits of working in the Photoshop 32-bit space on either Raw Smart Object Layers, or even taking a Raw image from Lightroom/Camera Raw into Photoshop the standard non "Smart Object" way (into 16-bit) then immediately going into the 32-bit space (Image/Mode/32-bit)?

I have been doing this for many years now (generally taking images as far as possible in the 32-bit space, doing a "save as" so I can go back to the saved 32-bit space layers if I ever need to. Then once I have done all I can there, I bring the photo back into the 16-bit space after getting all I can out of the adjustments available in the 32-bit space.

I believe I see some real world, noticeable benefits. Of course this workflow comes with many quirky things that the 32-bit space entails.

One (of many) things I believe I am seeing is the ability to stretch tones further, and use/apply more radical adjustments that would result in posterization/banding (more damage) in the 16-bit space.

One example: a client recently sent me a black and white image that did not have great data (not shot bright enough) and although most of the work was done in Raw/Lightroom, once it was brought into the 16-bit space and several edits (some of the edits using masks) were applied to optimize it, banding/posterization occurred fairly quickly. I have seen this happen for years.

BUT, I then tried bringing the raw file from Lightroom into Photoshop as a raw "Smart Object", but this time I immediately converted it into the 32-bit space. Then once it was in the 32-bit space I rasterized it (flatten) and proceeded to do the same masking/adjustments. No banding/posterization occurred. After finishing the edits in 32-bit mode (and saving a copy there in case I ever need to go back to it) I brought the finished/flattened image back into the 16-bit space and there was no banding/posterization and the tones just seemed better overall. We made a huge print out of it, and the tones were noticeably improved. I have come to believe that the masks are higher quality in 32-bit as well.

Lastly, one other example (of many) I have also brought damaged banding rasterized images (that had a lot of abusive adjustments applied) including jpeg's that nothing in 8-bit or 16-bit could fix (only make it worse).

But then, instead, I brought the images straight into the 32-bit space, made a very slight Gaussian Blur adjustment to the sky (the banding area) and then converted it back to 16-bit and the banding was gone! In this latter example, there seems to be some kind of beneficial redistribution of the data happening. In fact, I recall an image that banding disappeared by only going into 32-bit, then to 16-bit without any adjustments.

All thoughts are welcome. Thank you!

This topic has been closed for replies.

rayek.elfin

Legend

Although @D Fosse already mentioned this, I feel it is important to emphasize once more that Photoshop's 16/32bit per channel workflow is severely hampered by selections only being 8-bit. High-bit depth data is immediately destroyed when selections are used by a client to create masks. Basically they are working with 8-bit data in selections that wreck a high-bit depth image more and more as more selections are created and layer masks based on those 8bit selections are introduced.

And people are surprised banding occurs...!

And of course Photoshop's so-called 16 bit mode can only handle half the data of a true 16bit image mode. Photoshop throws away 32767 values in a full-range 16bit HDR image when it is opened. And 32bit conversions to 16bit are of course also affected. (And Photoshop doesn't warn the user about this!!!)

To me this means Photoshop is ENTIRELY unsuitable for high-end 16bit image processing and HDR workflows, and the selection tool should be avoided in either 16bit or 32bit mode (unless it is unimportant to retain all image data, but then you ought to ask yourself why are you working in high bit depth mode...).

In simple terms: 32bit to 16bit conversions should be done outside of Photoshop, in an image editor that actually uses the full range of values - a real 16bit mode, rather than Photoshop's 15bit mode. That is, if you care about maintaining the full range of 65535 values per channel.

And then there is the unfortunate Photoshop "feature" that only displays an 8bit image pyramid when zooming into a 16bit image, causing banding where there is no actual banding, further confusing users.

All the result of Photoshop's legacy core code that hasn't seen an update to fix these issues since 16bit mode was introduced a long time ago.

To top it off, Photoshop's 32bit mode is still restricted in terms of functionality.

Of course, for most users it is "good enough", I suppose.

Myself, I switched to different alternatives that actually offer a fully supported 16bit and 32bit per channel image processing & compositing workflow.

TheDigitalDog

Inspiring

Are you showing is a mask or the edits of the high bit data 'under' the mask? And what edits?

And of course, there are masks in Adobe's raw processors.

There are very very few true 16-bit capture devices, and again, no matter; Photoshop is 15+1 bits, always has been. The test is to illustrate data loss and banding, editing on any high bit data.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

TheDigitalDog

Inspiring

Just took this test file: https://www.dropbox.com/s/s14f4w7dq85r7oo/10-bit-test-ramp.zip?dl=0

Open in Photoshop.

Make a rectangle marquee over half.

Save Selection.

Target just that Alpha Channel, make a gradient (black to white).

Now use Load Selection which is a gradient selection of the data above.

Pull Levels (a lot).

Result: No banding in the edited data. On my high bit video path, the edited gradient looks as smooth edited as it did prior to edits through this '8-bit mask'.

I could pop a screen capture but a JPEG wouldn't look right.

Download and do the same test. I see no issues editing high bit data, designed to show banding, any issues after editing through the mask.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

TheDigitalDog

Inspiring

All high bit processing in Photoshop is actually 15+1 bits.

You will never get banding editing a high bit document. You can see banding in them IF you don't have a full, high bit display path. The banding is in the display, not the image data. And if there is banding in the display path, 32-bits does nothing more to aid in this issue.

A full high bit display path invoves the display, the video card and the OS (plus application but Photoshop supports this).

High bit editing is useful for overhead to keep from introducing banding from edits, which can result in 8-bit per color images:

http://digitaldog.net/files/TheHighBitdepthDebate.pdf

Here is a document produced to view and determine if you have a high bit display path. Open it in Photoshop, view at 100% zoom. IF you see banding, it is your display path.

https://www.dropbox.com/s/s14f4w7dq85r7oo/10-bit-test-ramp.zip?dl=0

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

Camera Raw FanAuthor

Known Participant

Thank you very much. I have a high bit display path, and the degrading that we see is in the prints.

TheDigitalDog

Inspiring

Thank you very much. I have a high bit display path, and the degrading that we see is in the prints.

By @Camera Raw Fan

Then that's a totally different issue and has nothing to do with bit depth of the data or Photoshop. Most print drivers don't even send high bit data to the driver itself. The few that are known to do so (for example, my Epson 3880 on Mac only) produces identical prints (measured) if you send a 16-bit or 8-bit per color document to that printer.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

D Fosse

Community Expert

I really can't see how you can get banding in 16 bit files, even with extreme adjustments. It shouldn't even be theoretically possible. Something else must be going on if you see that.

First of all, keep in mind that your display pipeline is 8 bit. That's where the banding you see happens - even more so if you have calibration tables loaded into the video card or a bad monitor profile. Theses can all pile on top of each other.

Secondly, Photoshop previews at less than 66.7 % zoom are always rendered at 8 bit depth. Try again at 100%.

Masks are the same bit depth as the document. However, selections are restricted to 8 bit depth, so a selection directly turned into a mask is 8 bit (until you start working on it).

And jpeg, of course, only ever supports 8 bit depth.

Camera Raw FanAuthor

Known Participant

Thank you for taking the time.

I completely understand where you are coming from, and understand all the above information and I teach it. But the banding and posterization is a well known thing doing print post-processing for a living for top end photo galleries full time over the last 15-20 years. Many clients do incredible amounts of adjusting to their files. All kinds of selections, and masks on masks on masks on masks and more. In black and whites it can happen even easier when people are doing a lot of major tonal stretching, masking, bluring, noise reduction, more stretching and so forth. So, I actually do not want to debate or defend that part of my post above.

I'm really wanting to see what kind of answers some might have in regards to the original question:

What are the benefits of working in the Photoshop 32-bit space on either Raw Smart Object Layers, or even taking a Raw image from Lightroom/Camera Raw into Photoshop the standard non "Smart Object" way (into 16-bit) then immediately going into the 32-bit space (Image/Mode/32-bit)?

Thank you.

davescm

Community Expert

"What are the benefits of working in the Photoshop 32-bit space on either Raw Smart Object Layers"

For your workflow - none at all. Starting on 16 bit then moving to 32 bit merely maps existing values into the floating point space and changes to linear gamma. 32 bit floating point linear is for HDR work which might be combining multiple exposures or 3D renders at high dynamic range. It therefore handles white and black levels way beyond those that can be displayed on monitors (hence the need for tone mapping). It has though major disadvantages in that the tools available in that mode are severely restricted and you cannot actually see the full range of tones or adjustments that you are making (you have to use the slider to select the visible parts of the range).

I sometimes use 32 bit output from 3D renders, which by their nature have extended white and black points, but I quickly tone map to 16 bit for further adjustment and processing. 16 bit is more than capable of handling extreme manipulation and gives access to all tools and most filters without any banding or posterisation.

Dave

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded