The new version of Millipixels, now in crimson-updates-proposed, significantly improves the way photos are developed by default. No need to develop the RAWs on your own to get rid of that greenish retro look anymore. Time to update and show off your cats on the fedi 😺
#shotonlibrem5 #librem5 #shotonmainline #pureos #gnu #linux #linuxmobile #linuxphone #linuxsmartphone #mobilelinux #catsofmastodon #cats #camera
Here's a before-and-after example. There's much more (done with an early version of this code) in my old thread: https://social.librem.one/@dos/115091388610379313
Here's a few cat-less examples too for some variety.
The processing is still pretty basic, you can easily get better results out of Darktable etc. but it should nevertheless be a big improvement for what you get by a simple point-and-shoot.
Millipixels has really overstayed its welcome, it was meant to be a temporary pile of hacks to facilitate driver development, but - perhaps inevitably, as makeshift does - it stayed there much longer than anticipated. I have spent a few hours polishing some of its roughest edges, finishing up past WIP work and hacking some desperately needed quality-of-life improvements in.
Along with e.g. rotation sensing and better QR code detection, it can now also adjust frame rate to extend exposure time.
The way it does video recording is still... uhm, not great 🤪 so it's only usable for short clips, but it also benefits from the processing improvements, so these short clips should at least look prettier now. Audio should be a bit less desynced now too.
If you want to record for as long as your storage lets you to with perfect audio sync, check out the video recorder at https://source.puri.sm/-/snippets/1223
Last but not least, last kernel update is also lowering the FPS you can get in various modes - from 120/60/60/20/15 to 83.3/40/30/20/8. Why?
It was the easiest way to reduce the MIPI CSI-2 clock freq, which turns out to effectively resolve the issue of camera locking up until a reboot under DRAM load due to ERR050384 erratum! The driver could be made to configure the clocks dynamically to unlock the full FPS range again, but that's left for later.
Kernels are hard to show, so have more cats 😸