Natron

Natron is a free, open-source (GPLv2 license) video compositor, similar in functionality to Adobe After Effects, Foundry's Nuke, or Blackmagic Fusion. It is portable and cross-platform (GNU/Linux, macOS, and Microsoft Windows). Website: Source code: Forum: Discord: User documentation: Natron is looking for developers and maintainers! You can help develop and maintain Natron if you have the following skills: Git and GitHub C++ (Natron source is still C++98, but switching to C++11 or C++14 should be straightforward if needed) Design patterns Qt (Natron builds with Qt4 or Qt5, but does not yet support Qt6) Basic knowledge of OpenGL Basic knowledge of Python If you are willing to help, please contact the development team on the pixls.us Natron forum. A machine running one of the supported operating systems (GNU/Linux, macOS, Microsoft Windows), and a 32-bits x86 or 64-bits x86-64 processor. An OpenGL 2.0 compatible graphics card is needed to run Natron (2.1+) with hardware-accelerated rendering. Other graphics cards work with software-only rendering (see below). On Windows and Linux you can enable software rendering. On Linux, enable the environment variable LIBGL ALWAYS SOFTWARE=1 before running Natron. On Windows, enable the legacy hardware package in the installer. Standalone binary distributions of Natron are available for GNU/Linux, Windows, and macOS on GitHub, or from the Natron web site. These distributions contain Natron and four included sets of OpenFX plugins: openfx-io openfx-misc openfx-arena openfx-gmic For each architecture / operating system, you can either download a stable release, a release candidate (if available), or one of the latest snapshots. Note that snapshots contain the latest features and bug fixes, but may be unstable. This documentation may be slightly outdated, so do not hesitate to submit updated build instructions, especially for the various GNU/Linux distributions. These scripts run on virtual machines running a specific operating system, setting these up is more complicated than the basic build process linked above. You should start contributing to the Natron project by first picking an easy task, and then gradually taking more difficult tasks. Here are a few sample tasks, by order of difficulty (from 0 to 10): 2: Pyplugs, Shadertoy scripts (there are still developers for these, see ) 4: Write an OpenFX plugin, starting from an example in openfx-misc or from the official OpenFX examples, for example try to make an OpenFX plugin from a widely-used PyPlug. There are a few OFX plugin developers in the community. 5: Build Natron locally (on any system) 7: Compile a redistributable Natron binary (Linux is easier since we build and ship most dependencies using the build scripts) 9: Fix a simple Natron bug 10: Add new functionality to Natron (see issues) The main development branch is called "master". The stable version is on branch RB-2.5. Additionally, each stable release supported has a branch on its own. For example, the stable release of the v1.0. and all its bug fixes should go into that branch. At some point, a version that is no longer supported will get removed from GitHub's branches and only a release tag will be available to get the source code at that point. Feel free to report bugs, discuss tasks, or pick up work there. If you want to make changes, please fork, edit, and send us a pull request, preferably on the "RB-2.5" branch. There's a .git-hooks directory in the root. This contains a pre-commit hook that verifies code styling before accepting changes. You can add this to your local repository's .git/hooks/ directory by doing the following: Pull requests that don't match the project code style are still likely to be accepted after manually formatting and amending your changeset. The formatting tool ( astyle ) is completely automated; please try to use it.