https://bugs.kde.org/show_bug.cgi?id=418243
Tymond <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Severity|normal |wishlist --- Comment #1 from Tymond <[email protected]> --- Setting to wishlist because it's a wish. I'm half-sure it was already reported... but maybe I just wanted it reported. My additions: 1. it should allow both increasing and decreasing fps. 2. both "how many times should it decrease/increase" (2x - put hold frames between every frame; 0.5x - delete every other frame and squish together on the timeline) and just putting the resulting fps. 3. it should support some weird conversions too, like between 24fps and 25fps, or from 24fps to 8fps, or from 3fps to 7fps - then the algorithm will choose which frame to delete or how to set up frames to follow the new fps. It will change the animation a bit, but it's better to have this option than not. For example in case of 3fps to 7fps, algorithm could put frames like this: 0th -> 0th, 1th -> 2th, 2th -> 4th, 3th -> 7th. Note the bigger gap between the last two mentioned frames. 4. if it's nx or (1/n)x, it should be consistent throughout the whole timeline (user will know exactly which frames will be deleted and pulled or how many frames will be added between which frames), but for all other cases, it can be whatever the algorithm thinks it's fine. 5. for the non-nx or non-(1/n)x cases, there should be a warning since it will change the animation and needs to be checked manually by the user, maybe even tweaked after conversion. 6. it should expect OK button to be clicked by the user, not something that the user can do by mistake/ -- You are receiving this mail because: You are watching all bug changes.
