@fizzo (although many other devices have a dedicated piece of hardware to do this and more for you)
@fizzo Nothing sensor-specific there (except calibration data of course), just doing very basic stuff that you need to do in order to get a proper image from any Bayer sensor (unless it does parts of it for you already). See the description at https://source.puri.sm/-/snippets/1223 for details.
All this ADHD productivity advice accomplishes one thing first and foremost, and that's imitating the markers of neurotypical productivity.
You're masking. You're pretending to be normal when you just aren't. And that takes a shitton of energy.
You're at your best when you just randomly bump into tasks and do them. And that doesn't need to involve any of the trappings of what we traditionally think of as productivity.
You will eventually figure out what you need and what works for you. And when it eventually inevitably stops working, because it has become boring, then you will naturally figure out something else.
@hoolis @sos You may want to grab the version from https://github.com/TheSos/allegrojs/pull/25 which fixes some crashes and lets you use raf-based mainloop
@rozie A operator był ten sam co w drugim slocie czy nie? (przy czym Orange i T-Mobile liczą się jako ten sam)
@pavel How comfortable does one need to be to replace a single line that calls a function called "debayer"? 🤔
@pavel I'd rather give the shader RGB values than rebayer debayered data so it can debayer it again if I wanted "easy", but that's just me.
@pavel Just take a step back and think a bit about what you just wrote and you won't need any code 😜
@pavel That's not how it works. A 4-channel 13Mpix image remains a 13Mpix image and still fits within limits.
@pavel ??? Full 13MP is still well within GL texture limits. The code just works as-is.
FWIW, don't mind the stripes on the bottom or right edge on some of these photos. It was just me poorly rotating and noticing too late 😛
And the great thing is that you can take your past photos and re-develop them again with whatever code you have available now. No need to be picky, it's fast enough to just go through them all.
There are still some crucial things missing, such as profiled denoising or proper highlight recovery, but since the performance budget for a still photo is much higher than for a 30 FPS video, there's plenty of room to add more stuff - and most of these 2 seconds are spent reading DNG and saving JPG anyway.
Unlike Glowup, which takes about 30 seconds and lots of RAM to process, this is still just as fast - the photo is developed within 2 seconds from shooting.
To pass some time in a train yesterday, I've copy'n'pasted my recent GPU ISP into Millipixels' postprocessing code to see how it compares with what was already there. Before/after:
It's a pitch deck season. Finally I have 2 personal projects in the making, that I deeply believe in ❤️
and I'm searching for funding.
Keep the faith (for me) 😊
Hi, I'm dos. Silly FLOSS games, open smartphones, terrible music and more. 50% of @holypangolin; 100% of dosowisko.net. he/him/any. I don't receive DMs.