Kezdőlap Felfedezés Súgó
Bejelentkezés
kris
/
Megapixels
1
0
Másolás 0
Fájlok Problémák 0 Beolvasztási kérések 0 Wiki

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

Branch: master
Branch-ok Tag-ek
Megapixels
ZIP TAR.GZ
Pavel Machek 8d74a7da06 rmdir can be easily done without calling the shell. 6 hónapja
config 5f270c1ef0 Remove unneeded files 1 éve
data c9dceb170b Hack: we have data from debayer -- square -- but yuv uses block of 7 hónapja
src 4a124688d1 mkv is better extension for the video, as we are using mkv envelope. 7 hónapja
tools 38bbee0841 camera_test: add bridge support (MR 31) 1 éve
.clang-format 772db36877 Make clang-format more aggressive 3 éve
.editorconfig 101abe33cd Add editorconfig 4 éve
.gitignore db131f2cb0 Chosen project name 4 éve
.gitlab-ci.yml e524c4f885 Add libpulse-simple dependency to CI 7 hónapja
CMakeLists.txt dbacf8a005 Write YUV frames to jpeg directly instead of DNG 10 hónapja
LICENSE db131f2cb0 Chosen project name 4 éve
README.md df7e7e9eed Updated Matrix address, and added links to libmegapixels, libdng and postprocessd 7 hónapja
clang-format.sh f66fcc5a71 Update to clang-format 14 2 éve
medianame.h fcba2b33c2 Add support files that will be used for video recording. 7 hónapja
meson.build fcba2b33c2 Add support files that will be used for video recording. 7 hónapja
meson_options.txt edd1de7a9e Add meson option for the tiff cfa pattern bug 4 éve
movie.sh.in 48a4b8db2a Get rid of fragile recursive rm, move cleanup to mpegize. This way 6 hónapja
movie_audio_rec.c 00f40b52df Audio recording fixes 7 hónapja
mpegize.py 8d74a7da06 rmdir can be easily done without calling the shell. 6 hónapja

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/.