Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • L Libcamera
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Librem5
  • Libcamera
  • Issues
  • #1

Closed
Open
Created Nov 10, 2021 by Dorota Czaplejewicz@dorota.czaplejewiczMaintainer

Do debayering

We don't want every application developer to break the open door again. Better push it to libcamera as a builtin ability.

Upstream developers unofficially confirmed that this is in scope and interesting.

Considerations:

  • fastest method depends on hardware (fragment shader, compute shader, OpenCL, Vulkan, OpenGL, CPU, IPU)
  • consumer might want to receive the raw stream in one frame but not the other (or both)
  • can get significantly simpler/faster if the output is downscaled
  • applies only to some hardware
Assignee
Assign to
Time tracking