Summary: | Shots with a transform filter are not rendered on rescaled export | ||
---|---|---|---|
Product: | [Applications] kdenlive | Reporter: | François <ftechene> |
Component: | Rendering & Export | Assignee: | Jean-Baptiste Mardelle <jb> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fritzibaby, rafael.linux.user |
Priority: | NOR | Flags: | fritzibaby:
Brainstorm+
|
Version First Reported In: | 19.04.1 | ||
Target Milestone: | --- | ||
Platform: | Flatpak | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
François
2019-05-18 08:32:33 UTC
Please try with the current Kdenlive AppImage version 19.04.1c to see if there are any packaging issues https://files.kde.org/kdenlive/release/ If the problem/issue doesn't occur when using the AppImage, then it's your configuration or packaging. I have tested the latest appimage and the problem is still there I also have the same issue when rendering a preview zone with a clip that has some transform filter. The clip is just ignored from the preview render. The rest is rendered just fine. Confirmed. Black output with and without parallel processing. Openend issue: https://invent.kde.org/kde/kdenlive/issues/205 Thanks for the report. I have identified the problem (embeded consumer in melt does not correctly handle rescale). A fix will be required in mlt, I am working on it. MLT pull request proposed here: https://github.com/mltframework/mlt/pull/453 Git commit 6c6f31468519e4aabd407be9f0a6b81e811f51a1 by Jean-Baptiste Mardelle. Committed on 05/06/2019 at 06:09. Pushed by mardelle into branch 'Applications/19.04'. Workaround MLT consumer scaling issue #453 by using multi consumer Enforce in/out that were not correctly passed with movit or multi consumer M +16 -10 renderer/kdenlive_render.cpp M +2 -2 renderer/renderjob.cpp https://invent.kde.org/kde/kdenlive/commit/6c6f31468519e4aabd407be9f0a6b81e811f51a1 Tested with nigtly build AppImage. Fixed with: https://invent.kde.org/kde/kdenlive/commit/6c6f31468519e4aabd407be9f0a6b81e811f51a1 *** Bug 408363 has been marked as a duplicate of this bug. *** |