Are you working in 16 bit bit depth? If you're working in 8 bit, it's common to run into problems with posterization, which this essentially is. It's best to start with a 16 bit depth image; if all you have is an 8 bit image, then ensure the first step you take is to scale it up to 16 bit before applying any adjustment curves.
Part of the problem is also that the curve you've applied is kind of odd; it flattens out the upper midtones very dramatically. Maybe that's an intended effect, IDK, but it does exacerbate the postrization problem since flattening out one bit of the curve means that another bit needs to have a very steep gradient.
View attachment 383834
Note flattened out bit marked in red and steep bit in blue.
If this area is truly clipped, that is 255-255-255 then there is no adjustment you can make to get it back. Is it possible you could clone similar areas over the clipped area to "rebuild" it?
Are you working in 16 bit bit depth? If you're working in 8 bit, it's common to run into problems with posterization, which this essentially is. It's best to start with a 16 bit depth image; if all you have is an 8 bit image, then ensure the first step you take is to scale it up to 16 bit before applying any adjustment curves.
Part of the problem is also that the curve you've applied is kind of odd; it flattens out the upper midtones very dramatically. Maybe that's an intended effect, IDK, but it does exacerbate the postrization problem since flattening out one bit of the curve means that another bit needs to have a very steep gradient.
View attachment 383834
Note flattened out bit marked in red and steep bit in blue.
Good that you checked it. The story behind the 16 bit may be more complex since the nominal bit depth of the RAW file may be 16 bits, but this doesn't mean that it actually contains 16 bits of real data. It's very well possible (even likely) that the actual resolution is limited to e.g. 14 bits, with the remaining bits being padded. This means that posterization can set in a little earlier than you might expect. This could induce problems when trying to work with very extreme curve shapes (very flat and/or very steep - especially the latter).
Another issue that may emerge is interference patterns when downsizing or downsampling to a lower resolution, e.g. when printing at a relatively small size. This can result in jagged edges here and there, especially if there's an already existing pattern (like pronounced digital noise or film grain) in the image data. But I'd expect that things would render a little more smoothly - and it's of course moot if you already see the problem emerge as soon as you apply the compensation curve, before any further downscaling happens.
All considered I'm not entirely sure where the problem is, but it does look much like a simple case of trying to push the limits a little further than the image data allow for.
Is it worth it to try printing the digital negative at a higher dpi?
Yeah, give it a try; it might make a bit of a difference in this particular case. BTW, when outputting negatives to my Epson printer, I either try to fix the resolution to its native 1440dpi (or 2880, although this generally doesn't yield much more usable detail), or I just send the file to the printer in whatever resolution it happens to be. I use the former for self-generated images like step tablets and test images, the latter for real photos.
As to the scan: ah, yes, I see - so this is basically a digital photo of a negative. Then it's virtually certain to be far, far less than 16 bits per pixel effective data. Most negatives have a fairly limited dynamic range (less than 2.0logD or around 7 stops, usually a bit less), while the digital camera is optimized to capture a fairly large dynamic range (10+ stops). So best case you're working with maybe 12-13 bits of actual resolution instead of the 16 bits you may be expecting. It could be worthwhile trying to scan the negative with a flatbed scanner and during scanning, ensure to scan at 16 bit/px and to set the black and white points so that the image data occupy the entire space. Coincidentally, I just wrote something about this here (although in a different context): https://www.photrio.com/forum/threads/doing-color-negative-inversions-manually.210239/post-2846671 - but feel free to skip that bit of theoretical musings and just give it a try.
It's truly clipping, but only /after/ the application of the curve. So the source image has sufficient information to produce a pleasant tonal curve, just when adjusted for printing in the process it's pushing the highlights to clip.
I hesitate to add my 2 cents here but here goes..
It kind of sounds like the OP is double profiling which can always end in disaster.
If he or she has a good original profile that is calibrated, then a second curve makes no sense to me... for all my work whether it is pt pd, gum, cyanotype , silver we use the same calibrated profile that was produced by creating a linearized 100step wedge where the input and output correspond within limitations of the process. LAB 96- LAB 100 will always clip no matter what so all highlight with detail is kept under LAB 95 for safety. I have printed thousands of images with different end process with the same custom profile, originally made for me here at my shop by Ron Reeder and in 2020 I made a new one with Greg Brophy when I changed printers.
When making negatives from digital files the old adage garbage in garbage out applies, I see many photographers get away with monster corrections to files and printing onto matt inkjet paper but when those same images get separated out posterization, glitches start. I am not sure why but probably the stripping apart the image is too much for it to handle.
So here we make the file look great in PS and then when making a neg via Print Tool we apply the appropriate bit order curve, Only once.
Koraks in post 11 kind of confirms my suspicion.
What’s double profiling?
I think he refers to the situation where you (possibly inadvertently) apply two separate adjustment curves on top of each other. However, that doesn't appear to be the problem you're running into, as it would only become apparent after the second curve is applied, for instance during printing (e.g. using QTR with Epson printers). You generally only notice it in the final print, but in your case, you see it happening immediately when doing the first (and possibly, only) adjustment.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?