a28b6ba12f* fix: adds small border around the parade to guarantee good contrast regardless of the surrounding background color (was a problem on light themes) * fix: fill area between individual color channels with this border color instead of palette background color (on light themes this looks better as there is too much contrast between parade background and palette background) * fix: consider device pixel scaling when drawing axis (fixed bug on HiDPI displays where the axis did not fully extend to the parade right border) * fix: make axis line color less distracting * change: instead of drawing current y value in the HUD scale below/above top/bottom scale values to prevent clipping let's hide the scale value instead and only show the current y value instead * change: draw current y value and horizontal line in highlight color instead of text color (think this looks better when drawing the parade only in black/white color mode) * change: use same color for gradient reference line as is used for drawing the axis lines but with higher opacity --- Most of these issues are regressions caused by my previous change to use the system palette for the surrounding area like the min/max values or the drop-down selection on top of the widget. The HiDPI bug is ancient and also present in latest release. Before: <img src="/uploads/57df01a3162714c1e720148375ccddbe/before_breeze_light.png" width=200> <img src="/uploads/5b66098b110f25ac36db9820bec38d2d/before_breeze_dark.png" width=200> After: <img src="/uploads/33243b7c868dcf748e9cc35b043f06d0/after_breeze_light.png" width=200> <img src="/uploads/70d63fd9d0b054b6c11a526ff7899895/after_breeze_dark.png" width=200> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| cmake/modules | ||
| data | ||
| deps | ||
| dev-docs | ||
| doc | ||
| fuzzer | ||
| LICENSES | ||
| packaging | ||
| plugins | ||
| po | ||
| renderer | ||
| src | ||
| testingArea | ||
| tests | ||
| thumbnailer | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .clang-tidy | ||
| .craft.ini | ||
| .flatpak-manifest.json | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .kde-ci.yml | ||
| .mailmap | ||
| .tarignore | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| config-kdenlive.h.cmake | ||
| COPYING | ||
| Messages.sh | ||
| README.md | ||
| README.md.license | ||
| REUSE.toml | ||
| rttr.CMakeLists.txt | ||
| snapcraft.yaml | ||
| suppressions.txt | ||
| tidy.sh | ||
Kdenlive
Kdenlive is a powerful, free and open-source video editor that brings professional-grade video editing capabilities to everyone. Whether you're creating a simple family video or working on a complex project, Kdenlive provides the tools you need to bring your vision to life.
For more information about Kdenlive's features, tutorials, and community, please visit our official website.
There you can also find downloads for both stable releases and experimental daily builds for Kdenlive.
Contributing to Kdenlive
Kdenlive is a community-driven project, and we welcome contributions from everyone! There are many ways to contribute beyond coding:
- Help translate Kdenlive into your language
- Report and triage bugs
- Write documentation
- Create tutorials
- Help other users on forums and bug trackers
Visit kdenlive.org to learn more about non-code contributions.
Developer Information
Technology Stack
Kdenlive is written in C++ and is using these technologies and frameworks:
- Core Framework: MLT for video editing functionality
- GUI Framework: Qt and KDE Frameworks 6
- Additional Libraries: frei0r (video effects), LADSPA (audio effects)
Getting Started
- Check out our build instructions to set up your development environment
- Familiarize yourself with the architecture and coding guidelines
- If the MLT library is new to you check out MLT Introduction
- Join our Matrix channel
#kdenlive-dev:kde.orgfor developer discussions and support
Contributing Code
Kdenlive's primary development happens on KDE Invent. While we maintain a GitHub mirror, all code contributions should be submitted through KDE's GitLab instance. For more information about KDE's development infrastructure, visit the KDE GitLab documentation.
Finding Things to Work On
- Browse open issues on KDE Invent
- Check the KDE Bug Tracker for reported issues
- Look for issues tagged with "good first issue" or "help wanted"
Need help getting started? Join our Matrix channel #kdenlive-dev:kde.org - our community is friendly and always ready to help new contributors!