Our short term roadmap has been updated and it looks like this:
* Command Line Interface Rendering
* Improve AVFilter support
* Qt6 and KF6 migration
* Easing modes for keyframes (fundraiser)
* Performance Boost (fundraiser)
* Efficient Effects Workflow (fundraiser)
@kdenlive What’s meant with “Command Line Interface Rendering”? We already can export scripts that can be run on command line. We also have #ffmpeg to do all the fancy things on command line if we really want to.
What about better #Wayland support? (Unusable on my machine with #Hyprland and #labwc). Maybe hopefully Q 6 migration will fix this automatically? … We’ll see
And what’s with backwards scrolling the timeline that only runs runs between 0.1 to 3.0 FPS or not working at all when using a jog-dial?
What about compiling marker lines as chapter marks in video containers that support chapters?
What about simple video scaling/cropping/resizing instead of having to change the project parameters or manually applying weird settings before rendering?
What about helping out?
https://community.kde.org/Get_Involved)
Some of the stuff you mention will be easier to do with hands-on contributions rather than just yelling from the stands.
@dirk CLI rendering will be used for automated tests to catch bugs or regressions. Bonus, users can use it to set up a server render node.
@kdenlive Will the render node help with backwards scrolling or Wayland compatibility? SCNR You're all doing a great job but those are the issues I face in reality.