Login
You're viewing the techdon.dev public feed.
  • Jan 7, 2026, 11:58 AM

    @pavel Hm, why would you not use the gpuISP for taking still pictures? Sure, you can further improve quality with that in the long run - and the upcoming version of libcamera will allow you to choose between gpuISP and raw - but for starters I'd argue it's fine to just use the gpuISP.

    💬 1🔄 0⭐ 0

Replies

  • Jan 7, 2026, 12:23 PM
    @rmader Well... the thread began with "more than tuning is needed", and this is decision which will lead to redesign later. We'll likely want to use same tuning for gpuISP and then for hq-still-photo-component, and hq-still-photo-component does not exist at the moment :-).

    And "why not use gpuISP at the moment". Well, besides quality, gpuISP only has one output. We need that output for preview. And that means we have photos in BAYER.

    Being able to feed libcamera with BAYER data, and saying "Librem 5 back camera took this BAYER, please convert it to RGB in high quality" would be good.
    💬 0🔄 0⭐ 0
  • Jan 7, 2026, 1:00 PM

    @pavel Re "Well, besides quality, gpuISP only has one output. We need that output for preview" - the way how e.g. Snapshot works right now is that it uses the same buffers for preview/viewfinder as well as encoding video or still images.
    A proper multi-stream architecture will certainly be nice long-term - but I don't see why we wouldn't just implement that in the gpuISP when we get to that point (so it can have multiple outputs).

    💬 1🔄 0⭐ 0
  • Jan 7, 2026, 1:11 PM

    @pavel P.S.: encoding RGB/YUV to jpeg (or any image/video format) is something best left to the clients, IMO. Those already have plenty of options to do so, such as using #gstreamer, #ffmpeg or other libraries.

    💬 0🔄 0⭐ 0