The "how would you process this image?" thread

Fantastic thread, I'll keep my eyes peeled and hopefully learn a little!

We should do another one – anyone want to share a new image?

.

https://www.dropbox.com/s/mqw5betlzib688y/000023330003.jpg?dl=0

1 Attachment

https://www.dropbox.com/s/y4oysy3sglgip76/000023350010.jpg?dl=0

1 Attachment

.

1 Attachment

at least you cropped it well!

oups forgot something

#triggered
#processed
#resurrected

I know this thread descended into jokes but wouldnt mind some help with this image? Clearly quite underexposed, would be nice to be able to highlight the face a little more as currently its a bit washed out by the darkness. Is this possible or will it look a bit cack because of the light in front?

1 Attachment

If you push the shadows up in lightroom you'll get more of the face. Though I suspect there'll be quite a lot of grain showing up too.

(For some reason when I try and download it it wants to save as a .webp file even though I can see it as a jpeg. Not sure if that's a problem my end)

wants to save as a jpeg for me.

1 Attachment

It saves as a webp in Chrome and jpg in other browsers I think. @Velocio did explain why at some point but I can't really remember.

Irfanview will convert from webp to jpg.

So the first image (dark and in colour) saves as a webp in Chrome. And this is because the image is huge and benefits from webp compression. Webp compression can reduce image sizes by up to 50%, and for some of my test images was reducing a 30MB attachment to a 17mb attachment.

That first image has this header:

cf-polished: qual=85, origFmt=jpeg, origSize=179969

Yup, Cloudflare polished it and converted it from a jpeg that was 179KB to a webp that is now 156KB.

Over threads like this photography one, this process spares your browser of downloading an extra 1-2MB per page. It is significant enough not to be turned off... and brings the bandwidth bill we face down enough to fall under Linodes inclusive bandwidth (we do not pay for bandwidth even though we have so much traffic as we're just under the billing threshold thanks to this and another optimisation).

The second image... that downloads as a jpeg on Chrome. Why?

cf-polished: origSize=63077, status=webp_bigger

In the case of the second image, jpeg file is smaller than the webp... so we carry on using jpeg.

Is it possible to bypass the webp? Yes!

The jpegs are converted to webp within the Cloudflare cache, and the simple way to get the jpeg is to trigger a cache miss... and this can be done by simply opening the image in a new tab and adding a random querystring to the URI, i.e. https://lfgss.microcosm.app/api/v1/files/41b1f05b914d54e22f7df74ff6d957dbee69db2f.jpg becomes https://lfgss.microcosm.app/api/v1/files/41b1f05b914d54e22f7df74ff6d957dbee69db2f.jpg?hello=7865. That ?hello=7865 triggers a cache miss.

.

1 Attachment

This is great but I see what @malandro means about the grain. Kind of unavoidable I guess. Thanks all!

Yes... But I think the scan is really bad (auto mode on Fuji/Noritsu and with the candle it doesn't really work), with a better scan, you could have a much better pic !

Yeah I think the lesson I'm going to learn from this is fixing the composition, rather than throwing money at better scans (skint student, hobby not professional etc). Ideally one day I'll get my favourite negs high quality scanned and printed but thats a few years off

.

1 Attachment

not sure if this is any better for you but her you go

1 Attachment

pretty hard to save a pic that was shot with a potato

1 Attachment