Startseite Erkunden Hilfe
Anmelden
kris
/
Megapixels
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki

Fork of https://gitlab.com/megapixels-org/Megapixels

Struktur: a2f57c02ac
Branches Tags
Megapixels
ZIP TAR.GZ
Kristian Vos a2f57c02ac Refactor camera control functions to use MPControl, store fd in MPControl vor 4 Monaten
config 5f270c1ef0 Remove unneeded files vor 1 Jahr
data ccf0314b62 Make the video recording button an icon vor 5 Monaten
src a2f57c02ac Refactor camera control functions to use MPControl, store fd in MPControl vor 4 Monaten
tools 38bbee0841 camera_test: add bridge support (MR 31) vor 1 Jahr
.clang-format 772db36877 Make clang-format more aggressive vor 3 Jahren
.editorconfig 101abe33cd Add editorconfig vor 4 Jahren
.gitignore db131f2cb0 Chosen project name vor 4 Jahren
.gitlab-ci.yml e524c4f885 Add libpulse-simple dependency to CI vor 8 Monaten
CMakeLists.txt ccf0314b62 Make the video recording button an icon vor 5 Monaten
LICENSE db131f2cb0 Chosen project name vor 4 Jahren
README.md df7e7e9eed Updated Matrix address, and added links to libmegapixels, libdng and postprocessd vor 8 Monaten
clang-format.sh f66fcc5a71 Update to clang-format 14 vor 2 Jahren
medianame.h fcba2b33c2 Add support files that will be used for video recording. vor 8 Monaten
meson.build 1a27c4b15b Added debayer_packed.frag to meson.build and gresource.xml vor 6 Monaten
meson_options.txt edd1de7a9e Add meson option for the tiff cfa pattern bug vor 4 Jahren
movie.sh.in 48a4b8db2a Get rid of fragile recursive rm, move cleanup to mpegize. This way vor 7 Monaten
movie_audio_rec.c 00f40b52df Audio recording fixes vor 7 Monaten
mpegize.py 8d74a7da06 rmdir can be easily done without calling the shell. vor 7 Monaten

README.md

Megapixels

A GTK4 camera application that knows how to deal with the media request api. It uses opengl to debayer the raw sensor data for the preview.

Chat: #megapixels:brixit.nl on Matrix

Building

Before building this, build and install libmegapixels, libdng and postprocessd.

$ meson build
$ cd build
$ ninja
$ sudo ninja install
$ sudo glib-compile-schemas /usr/local/share/glib-2.0/schemas

Post processing

Megapixels only captures raw frames and stores .dng files. It captures a 5 frame burst and saves it to a temporary location. Then the postprocessing script is run which will generate the final .jpg file and writes it into the pictures directory. Megapixels looks for the post processing script in the following locations:

  • ./postprocess.sh
  • $XDG_CONFIG_DIR/megapixels/postprocess.sh
  • ~/.config/megapixels/postprocess.sh
  • /etc/megapixels/postprocess.sh
  • /usr/share/megapixels/postprocess.sh

The bundled postprocess.sh script will copy the first frame of the burst into the picture directory as an DNG file. If dcraw and imagemagick are installed it will generate a JPG and also write that to the picture directory. It supports either the full dcraw or dcraw_emu from libraw.

It is possible to write your own post processing pipeline by providing your own postprocess.sh script at one of the above locations. The first argument to the script is the directory containing the temporary burst files and the second argument is the final path for the image without an extension. For more details see postprocess.sh in this repository.

Developing

Megapixels is developed at: https://gitlab.com/megapixels-org/megapixels

Source code organization

  • camera_config.c describes how cameras are configured. Contains no state.
  • main.c contains the entry point and UI portion of the application.
  • quickpreview.c implements fast preview functionality, including debayering, color correction, rotation, etc.
  • io_pipeline.c implements all IO interaction with V4L2 devices in a separate thread to prevent blocking.
  • process_pipeline.c implements all process done on captured images, including launching post-processing.
  • pipeline.c Generic threaded message passing implementation based on glib, used to implement the pipelines.
  • camera.c V4L2 abstraction layer to make working with cameras easier.
  • device.c V4L2 abstraction layer for devices.

The primary image pipeline consists of the main application, the IO pipeline and the process pipeline. The main application sends commands to the IO pipeline, which in turn talks to the process pipeline, which then talks to the main application. This way neither IO nor processing blocks the main application and races are generally avoided.

Tests are located in tests/.