Tags: linebender/velato
Tags
Enable non-linear easing (#42) It seems to me that most of the work to get non-linear easing is already done. In order to check what is left to be done I removed the linear-only enforcement, created a simple example with 3 key frames and compared the results with lottielab.com editor:  I have found that: - only the easing curves from first two key frames seem to affect the animation as rendered in lottielab. - [Lottie spec](https://lottie.github.io/lottie-spec/latest/specs/properties/) mentions that: "_All keyframes MUST have an i and o value, unless It is the last keyframe in the sequence OR ..._" - This comment mentions that the last one is unused: airbnb/lottie-web#2620 (comment) The way I understand it is that while we are moving into position described by next key frame, we still should be using `o` and `i` parameters from the previous one. After changing the `Time::frames_and_weight` to use the easing from current key frame, positions seem to match pretty well:  What do you think? Is there anything else missing to enable non-linear easing? Thanks for creating an amazing library! --------- Co-authored-by: Spencer C. Imbleau <spencer@imbleau.com>
v0.3 (#24) ## 0.3.0 ### Added - Added `velato::Renderer::render`, which now returns a new vello scene. ### Changed - Updated to vello 0.2 - Renamed `VelatoError` to `velato::Error` - Renamed the existing `velato::Renderer::render` to `velato::Renderer::append` ### Removed - All code and related profiling (`wgpu_profiler`) used in examples.
PreviousNext