Hacker News

Everyone has a love/hate relationship with Foveon, that's the beauty of the sensor isn't it ? Would you mind sharing your project ? That's awesome. Have you been able to compare crispness of files ? Dng compatibility from latest cameras, although it results in huge files, was pretty useful but files were not as sharp as native X3F developed in Sigma Photo Pro.

Remind us what the Foveon sensor's quirk was? Something in the subpixel layout as I recall. A non-bayer pattern since abandoned and largely unsupported, yet effective somehow. But maybe I'm imagining this.

What improvements have you made? Processing RAW sluggishness was always an issue from de-Bayering. Before RAW, my hell was DPX image sequences. This was pre-SSD, so I/O was painful opening/closing individual frames in realtime. The best improvement of processing RAW I've experienced was NVMe SSDs.

Some aspects of the process seem more like labor than a form of self-expression. I think if you are into the limitations of shooting film photos it makes sense.

When I showed my Konica Hexar to a younger colleague, he said, but how do you get the pictures into the computer. It was like a world opened for him when I said that I don't.

I agree in part, in that it is sad that this person does not have access to a darkroom. As someone who is also now shooting film and then camera scanning, I would love to have access to a darkroom. It's just a compromise film shooters have to make, and often at no fault to them. It's either too expensive (which the negatives already are), or too far away/too big to fit in modern homes, or more likely both.

We're just grateful that film is still available at all.

website is actively setting the cursor CSS style to none.

Very user-hostile.

A colorist I worked with did something similar by using reference film stock of the same film that was being scanned. This was anime 16mm film prints from the 80s that had been scanned multiple times and color set on arbitrary decisions by who ever was working with the film at the time. After using the reference stock to base decisions, the director said it was the closest he had seen to what he wanted.

To reiterate, those were legit questions. I used voice dictation to my phone, with an app that transcribed and formatted my message.

You should check out the negpy project. It in my view has the best inversion process. It claims to emulate the whole analog print chain in the inversion process. They have a fold works cited.

It also automates most of the process. It works with SANE, some other legacy scanners, and camera scanning. It can even do trichrome scans automatically.

I don't have a public writeup, but the general approach for orange mask removal is: scan a blank unexposed frame from the same roll, take its per-channel mean as your reference white, then divide each pixel by that reference per channel before doing anything else. That normalizes the mask out instead of trying to subtract a fixed color. After that, a per-roll linear stretch (black point from the darkest scanned frame, white point from the lightest) gets you a rough base. Tone curve is the hard part: NLP uses a nonlinear S-curve tuned per stock, and matching that from scratch means a lot of trial and error with reference images you know the expected look of. If you want a quick win before rewriting things, Lightroom lets you write develop settings to XMP so you're not locked into the catalog even if you cancel later; the actual RAW/TIFF processing engine is what needs a subscription, not the metadata.

Can you please not post AI-generated or AI-edited comments to HN? It's not allowed here - see https://news.ycombinator.com/newsguidelines.html#generated and https://news.ycombinator.com/item?id=47340079.

Of course, it's impossible to know for sure what was LLM processed or not, but some of your posts (like this one) have been getting classified that way.