@stu the #librem5 delivers as usual 🙂

There was a rather long while a few years ago when the cameras did not work yet. It's fun npw to look back at that now, see for example the various photo attempts in this issue: https://source.puri.sm/Librem5/linux/-/issues/43

Images like this 😄

@eliasr I will have to break out my librem 5 and check the camera status lol.

@stu do it!

@eliasr how is PureOS as a main driver ?

@eliasr I wanted to put pmOS but can't seem to get it installed.

@stu

> how is PureOS as a main driver ?

it's OK but it's still on the Byzantium version, the new one called Crimson has not been rolled out yet, I hope that will happen soon to get newer versions of things.

> I wanted to put pmOS but can't seem to get it installed.

Oh but that should be easy, it was easy when I tried it (long time ago, it should be even easier now). pmOS have that nice program "pmbootstrap" that does the installation. Maybe try again and ask for help if you get trouble?

@eliasr Ill try again .

@stu @eliasr Au contraire, the default JPEG output barely captures a fraction of quality you could get when processing the data from Librem 5's sensor properly. Currently it's kinda like if you recorded a music performance, but only ever listened to it as 48kbps MP3...

@dos @stu @eliasr I actually don't believe JPEG is Librem 5's biggest problem. There's still lot of work on Librem 5. IIRC kernel driver only passed 8-bit bayer. Plus we need to do all the lens corrections etc.

@pavel @stu @eliasr 10-bit is only going to visibly help where there's banding in shadows. It happens, but not that often in my experience.
If you grab already taken DNGs and reprocess them into JPEGs in more sophisticated ways the difference in results is staggering. Even without lens corrections it's still clearly noticeable (and with vignetting corrected it's simply obvious). You can go through your past photos and give them a huge upgrade this way.

@pavel @stu @eliasr In general what I wanted to say is that things that are the most noticeable about default photo quality (looking kinda like through a slightly fogged glass, greenish tint, massive vignette) are all caused in the postprocessing domain and you don't even have to take the photos again to fix them (unlike 8-bit banding, where you indeed do).

@dos @stu @eliasr Aha, ok, I misunderstood. So problem is not so much JPEG as quality of raw->JPEG conversion; yes, that can be case. BTW I don't have Librem 5 to work with at the moment; Megapixels should now work on that one. Would it be possible to test Megapixels and perhaps switch to that?

@pavel @stu @eliasr Does it do anything new now than it did a year ago? The code currently used in Millipixels is based on postprocessd, but even at 50% size, no interpolation and CV processing disabled it already takes seconds. I don't see anything longer as viable for online processing, and for offline there's already darktable-cli, so why reinvent the wheel...

@dos @stu @eliasr Well... Millipixels is kind of strange hybrid (Rust+C+libcamera), based on old gtk and Librem 5-only. Megapixels can do Librem + PP + PPP and more, so it is likely future, therefore worth testing and switching to. Not sure if it improves image quiality.

@pavel @stu @eliasr Well, Millipixels should just go away at some point anyway; the only part of it that I'm concerned with right now is pretty much just plain ol' libraw.