Add to the KDEnLive:
Horizontal “Median” direction;
Vertical “Pixs0r” direction or fully implemented “Pixel Sort”;
“Displacement” effect;
“RSMB (Real Smart Motion Blur)” or him’s analog which looks similar to “Teknos Blur”;
“Datamosh” effect, you can simply scrap something like this from Akascape’s Datamosh tool;
“Lens Flare” effect;
“DOF (Depth of Field, or Distant Blur)” effect;
“Solarize” effect;
“Parallax” deformation effect in “Transform”;
Simplified “Velocity (Time Remapping)”, with the same keyframe interpolation as in every configurable effect.
Fix in the KDEnLive:
“Gradfun” effect (he is not working absolutely);
“Dither” effect on a 270p preview scalling (it shows wrong video picture depends on a highest preview scale);
Nervous frame blending in “HQD3D”;
Broken “Rotate” effect, which sometimes bounces up the picture when it rotates to 180 degrees;
“NTSC’s” picture cropping.
Real bugs, especially (and if you’re unsure, preferably) after they’ve been triaged and independently confirmed here, definitely should be reported and tracked until fixed there. And any supporting example files (like a minimal test project that shows the problem) can be attached there to be preserved with the report too.
But please do remember that if you’re requesting pie in the sky things, that you haven’t actually researched the feasibility of implementing or are planning to implement yourself, then filing those into that tracker without any prior discussion confirming that they might be a viable work item is really just taking developer time away from fixing bugs and implementing new features from the roadmap - because someone who could be doing those things has to spend the time to triage and close them, even if they are completely impractical or impossible or just out of scope for being directly part of Kdenlive.
So it’s good to get past at least that question, and refine an idea of what might really be possible, before opening a specific and targeted feature request there. And bug reports to that tracker should always and only be for a single actionable item, not a long list of many things that you’d like to see, which clearly can’t all be done as one job.
For raw brainstorming, and discussion of things that you think might really benefit your personal workflow, here is a good place to start - as are the regular Kdenlive Cafés we hold for users to engage directly with the developers to discuss and question these sort of things.
