VSE: Inserted keyframes under the Transform panel 'Position X' or 'Position Y' are always set to linear interpolation #87222

Closed
opened 2021-04-05 22:10:13 +02:00 by hudson barkley · 13 comments

System Information
Operating system: Windows 10

Blender Version
Broken: 2.92
Worked: (this is a new feature in 2.92)

Short description of error
Inserting keyframes under the VSE 'Transform' panel for Position X or Position Y will result in animation curves using linear interpolation, regardless of what the preferences are set for the default interpolation mode (in my case, it should be bezier). Also note that this does not happen for other values in this panel.

I am including an example gif showing the issue (also including my default value settings for the animation curves):
keyframes.gif

Exact steps for others to reproduce the error
Add an image or movie strip to the VSE, in the transform panel
Add two keyframes animating the position value
Check the animation curve in the graph editor

**System Information** Operating system: Windows 10 **Blender Version** Broken: 2.92 Worked: (this is a new feature in 2.92) **Short description of error** Inserting keyframes under the VSE 'Transform' panel for Position X or Position Y will result in animation curves using linear interpolation, regardless of what the preferences are set for the default interpolation mode (in my case, it should be bezier). Also note that this does not happen for other values in this panel. I am including an example gif showing the issue (also including my default value settings for the animation curves): ![keyframes.gif](https://archive.blender.org/developer/F9920904/keyframes.gif) **Exact steps for others to reproduce the error** Add an image or movie strip to the VSE, in the transform panel Add two keyframes animating the position value Check the animation curve in the graph editor
Author

Added subscriber: @snuq

Added subscriber: @snuq
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Member

This seems to be intended behavior (since this is an integer property), see #29073 (Keyframing int properties defaults to bezier), 1768a96774

This might be debatable, but since code is working as expected, I would say this issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

This seems to be intended behavior (since this is an integer property), see #29073 (Keyframing int properties defaults to bezier), 1768a96774 This might be debatable, but since code is working as expected, I would say this issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Author

Considering that the previous method for animating the strip positions that this panel is replacing (the transform strip) behaves entirely differently (its values are floats), I would not consider this to be working as expected.

Maybe I'm missing it... but there seems to be no indication ANYWHERE in the interface that this behavior arbitrarily happens for certain variables and not others... nor is there any way to change this behavior. If this is not a bug, it is definitely an unexpected behavior for anyone animating these values.

Considering that the previous method for animating the strip positions that this panel is replacing (the transform strip) behaves entirely differently (its values are floats), I would not consider this to be working as expected. Maybe I'm missing it... but there seems to be no indication ANYWHERE in the interface that this behavior arbitrarily happens for certain variables and not others... nor is there any way to change this behavior. If this is not a bug, it is definitely an unexpected behavior for anyone animating these values.
Member

Changed status from 'Archived' to: 'Needs Developer To Reproduce'

Changed status from 'Archived' to: 'Needs Developer To Reproduce'
Member

Added subscribers: @iss, @dr.sybren, @brecht

Added subscribers: @iss, @dr.sybren, @brecht
Member

I would have thought that this stirs debate :)

Will let the (module) devs decide here...

CC @brecht
CC @dr.sybren
CC @iss

I would have thought that this stirs debate :) Will let the (module) devs decide here... CC @brecht CC @dr.sybren CC @iss

Hmm looking at commit above this seems to be quite hard-coded.
I wouldn't mind using bezier interpolation, integer seemed to be more natural for pixel values in screen space. Float with step of 1 and rounded to whole number would be probably usable here as well.

Question is, @snuq what is scope of your bugreport? Because I can change variable type for transform position, but does this apply to crop? And possibly other integer properties in Blender?

Hmm looking at commit above this seems to be quite hard-coded. I wouldn't mind using bezier interpolation, integer seemed to be more natural for pixel values in screen space. Float with step of 1 and rounded to whole number would be probably usable here as well. Question is, @snuq what is scope of your bugreport? Because I can change variable type for transform position, but does this apply to crop? And possibly other integer properties in Blender?
Author

Frankly, it seems odd to me that any values would be animated linearly instead of by the default mode set by the user, but this is more of an opinion and apparently that is the intended behavior.

I just know that in the case of this panel, it was rather strange behavior that seemed out-of-the-blue and was confusing to a new user of the vse (and to myself as well). Since these variables are commonly animated along with the scale or rotation variables, it seems unexpected for them to behave in a different way.

Maybe the confusion stems from the panel mixing percentages (for the scale) and straight values (the position and cropping as well). Honestly, I don't know what the best solution would be, just that I imagine most people would expect the values to behave in a similar way.

Frankly, it seems odd to me that any values would be animated linearly instead of by the default mode set by the user, but this is more of an opinion and apparently that is the intended behavior. I just know that in the case of this panel, it was rather strange behavior that seemed out-of-the-blue and was confusing to a new user of the vse (and to myself as well). Since these variables are commonly animated along with the scale or rotation variables, it seems unexpected for them to behave in a different way. Maybe the confusion stems from the panel mixing percentages (for the scale) and straight values (the position and cropping as well). Honestly, I don't know what the best solution would be, just that I imagine most people would expect the values to behave in a similar way.

Even though it may not be working as expected by new users, this seems to be working as designed. This is thus not a bug in Blender.

Even though it may not be working as expected by new users, this seems to be working as designed. This is thus not a bug in Blender.

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Noticed this report in backlog still open, Closing since this is not a bug.

Noticed this report in backlog still open, Closing since this is not a bug.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#87222
No description provided.