Hello! New user here coming from VEGAS as I’m planning to jump ship from Windows 10 to Linux in the near future. There’s a lot to re-learn. : P
My actual problem:
I can’t seem to type decimals into values like position and rotation in effects such as Transform and Rotate.
I can type commas, which get removed when the value is entered, but pressing period or numpad dot does nothing at all.
Please tell me this is a bug that can be fixed or a setting that can be changed somewhere; integer precision is simply not good enough for the kind of video editing I do, especially for rotation where at HD resolutions a single degree can be enormous.
I am running Kdenlive Version 24.12.0 on Windows 10.
You’re probably not going to get decimal precisions for position (what exactly should an 0.1px transformation do and what sort of use would call for that?) - if for some reason you needed that, you probably need to be working to pixel resolution on an upscaled master and then downscale again for your final render …
But finer grained rotation than (the relatively arbitrary choice of) 1 degree definitely seems reasonable.
Please file a [Feature Request] for this bugs.kde.org
Sub-pixel positions can be used to better align rotated elements or align elements to ones with interpolated positions. The scale trick is good advice but ideally not necessary.
Thanks for the confirmation. I’ll make that feature request. : )
In theory maybe … but
a) who is going to be able to see the difference in an 0.1 pixel translation?
b) what’s the point of such a theoretically better alignment when the reality of interpolating an 0.1 pixel motion is just going to introduce ringing and distortion to the result?
Sub-degree rotation is definitely worthwhile to be able to get 1px resolution in rotations - but I’m not seeing what real benefit sub-pixel changes to linear transformations could have.
A 0.1 pixel translation won’t make a difference, no… but there have been rare instances where I needed a 0.5 pixel translation in my videos.
As stated before this could also be solved by doubling the project resolution, but these are the kinds of things that tend to come up unexpectedly well into a complex project.
Can I ask what sort of videos you’re doing where that kind of need is real?
Mostly because if you’ve got edges that sharp then they are also going to be the most adversely affected by the unavoidable ringing that comes with anything but trivial (non-subpixel) interpolation - so it’s a bit of a devil and the deep blue sea kind of problem.
When I say if you’re looking for that sort of precision you should be using an upscaled source, I don’t directly mean it’s a good idea to just double the size of a low-res original (though in some cases that might work ok) …
What I really mean is if you need that sort of precision, then if you’re targeting a 1080p final render, you should probably have your source material generated at 4k or 8k, work in that resolution for your project, and only downscale to your target resolution at the final step.
It’s a bit like all those crazy high audio sampling rates - they make absolutely no difference to what you can hear (if you’re not actually a bat), and are snake oil as an end-user format - but if you’re using them as digital masters and applying DSP to them to create an end-user product, then that extra resolution for working in will reduce the noise and distortion that your manipulations might otherwise (inevitably) introduce.
