on.raw.photography

Feel free to upload a much larger version as well. Then it would be easier to look at what can be done about the shadow noise.

Yes, lovely shot.

I like Lucc's interpretation with the warm, almost reddish tones in the fog. Maybe not accurate to the scene, but it gives a nice atmosphere.

I think you might need to not use the "inline" option. Just attach the tiff file and press submit.

I'd love to try, but you need to upload a 16bit tiff file.

Another frame with a similar problem.

It always has been that way. That is the whole point of that feature :D The selection gets heeded no matter what.

Good! Then there is a work around.



There will also be the opposite: Real frames that do not get detected and still ruin the positive image.


I just found one such image and ...

It might also make sense to disable the feature when using the "make selection and open CP while holding down the Shift key" method you suggested earlier in the thread.

In that case, the user is already explicitly defining which part of the image CP should use as the basis for its analysis, making ...

It seems to work a lot better now, based on my admittedly limited testing so far. I’ll continue to post scans if I come across any problematic cases.

I think there’s a real possibility that edge cases will always exist, given the wide variation in how people scan images and the diversity of ...

My comment was a bit unclear. What I was trying to say is that if the detection is working properly, cropping the orange mask shouldn't affect the result.

That said, I think you're probably right that the issue seems more common with images that don't have a mask or film holder, where the algorithm ...

In more general terms, I'm just trying to find images that tricks the algorithm so Christoph can use them to improve it. I imagine building a foolproof algorithm that always knows what's part of the image content and what isn't is a pretty hard problem. There are probably a lot of edge cases.

Maybe I missed something. Now the problem is when you crop the black border of the frame?
Do you mean, if we load a file with a black border into CP3, the base curve appears consistent, but when we crop the black border, the base curve goes haywire?


If you're referring to the last image I ...

Maybe this one as well. It behaves rather differently if you crop away the mask.

These two frames have some problems as well. Windows seem to be a theme.

The Fuji roll is behaving well now with last nights build. I have more similar shots on that roll.
But this image still has some problems I would say. Comparison with CP2 here:

OK, looking forward to that. I'm guessing the the detection as it is now behaves better on scans with actual film borders and masks, and the problematic images will be scans like mine, with no mask or film base in the frame.

Then some Fuji Xtra 400 frames.

Again I compared to CP2:

I fired up Rosetta to compare against CP2:

These are two scans from the same roll as the problematic scan I uploaded earlier. What's peculiar is that the first image was taken only seconds apart from the previous frame. In earlier builds, this image looked quite normal, while the other one had the issue. In the new build, the behavior seems ...

Seems to handle the uncropped scans from a Coolscan 4000 well.
But I found some other files that did cause problems. Will post them shortly.

robyferrero wrote: Sun May 31, 2026 10:41 am Here's another version that should have better color.
I'm also attaching the TIFF file.ColorNEG BP ON ZERO.png

Yes, that looks better. Though I think Christoph has now confirmed that the issue is actually in the detection code.

First:
Thank you for posting this example,
It is precisely the example that is helping me see where I need to do better still in terms of detecting a potentially harmful outside.
I won't go into it, I'll just try to fix it.

Second:
You do not need to crop anything:






I tried to track ...

This is what I get if I crop, run CP, go back to the full crop, and then use the "Exact" option. Looks kind of ok now. But why?

It woul be nice if you'd share the original file straight from the scanner.


I sort of did. The Pakon outputs a .RAW file, but Photoshop can't read that format directly. You need to run it through MakeTiff first, which makes the RGB data in the file readable to Photoshop.

(This isn't related to ...

That's how it came out for me.


Does it look like that on your side when you simply open it in CP, without making any adjustments?

On my side, it opens with a significant amount of black clipping (and white clipping as well), that I can't reduce to any sane level it by adjusting the BP tails ...

Here is an image I had problems with. At first I thought it was the light leak in the upper part throwing CP off. But then I noticed I could get CP to behave normally when cropping either the upper or the lower part of the image.

The scan is made on a Pakon f135 and converted with MakeTiff. Film ...