hankbond

Lovely photographs as well, great composition and the bold editing.

> One prompt. > Hours of autonomous work. > A finished product.

Yeah, probabaly not.

What a wonderful space you have created. I have so much mindlessness in where I have things placed. I feel inspired to be a bit more purposeful and organize some things now.

> caches website contents via browser plugin

does it? I am running it but was under the impression that it did not cache the content I am viewing, unlike SinglePage.

Since there is some non-linear processing happening in the default renderer I'm not sure that it would work that well.

It makes sense to me if you are a mostly JPEG shooter and just keep RAWs for archiving. It also is less pleasant to look at the preview when using an EVF if its 30% blown. My photo style is often ETTL bc I like to crush shadows in a chiaroscuro kind of way. Also modern cameras look great at higher ISOs, and if you need it to be cleaner bc of large prints, AI powered de-noisers that operate on RAW files are also incredible.

One thing you can do with a raw workflow is use the EV compensation metadata to compensate the render you see. So you can shoot +1ev and then automatically reduce exposure by that much when viewing. This is a decent ETTR workflow and its never been easier to whip up a custom culling/importing tool.

That said, its basically a requirement to get proper signal-to-noise on a Merrill. The LCD-screen is dog-water anyway so its not like you can see anything of value on it other than blurry composition. So for those reasons ETTR is very natural. If you want to be extra careful you can spot meter with EV compensation , but I find the evaluative mode works pretty well enough.

Foveons don't actually de-bayer bc they use a stacked 3-layer sensor, where each layer is sensitive to different colors. The top layer is RGB, the middle is just RG, and the bottom is just R. We calculate the three values by subtracting the layers from each other.

Traditionally all processing of these X3F RAW files had to go thru software provided by Sigma, and its clunky and bakes in some processing you can't really turn off. Some folks (myself among them) are focused on creating new ways of processing and converting these X3F files to be used more flexibly. I have some links in the threads other replies to some changes I made to one processor.

I was able to significantly improve the highlight recovery. It's kind of a game changer since the sensor architecture requires a LOT of light to get the best results. To minimize noise you expose to the right at least one stop and then pull down in post. With the new processing I am able to get pleasing results closer to +1.7 and sometimes even 2ev. This sensor was not known for having great dynamic range, but with extra processing you can tease some information out into something attractive. It does leave the upper end of specular highlights flattened compared to a proper exposure but it often looks "believable" so I'm happy with it.

Very neat. I have a love-hate relationship with a unique type of digital sensor called the Foveon X3, which needs a particular (very sluggish and limited capability) software made by Sigma to convert the RAWs. Recently I have been using AI to create a converter that processes the RAWs in a similar fashion with some improvements.

This is one of those cases where its a means-to-an-end (I just want to take more photos without being bogged down) and less of a project for me to learn how to reverse-engineer and design signal processing pipelines. I am very grateful for what recent models are enabling me to do.

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.

Can someone explain the implications of this?

i guess, but to me its not so much "this is ai this is terrible" and more "i'm sick of hearing this phrase all the time". it's not that I never want to see an em-dash ever again, its just that i don't want them used every other sentence.