transformation -> origin act weird when the strip is scaled #97986

Closed
opened 2022-05-09 16:41:05 +02:00 by hamza.SMA · 12 comments

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39

Blender Version
Broken: version: 3.2.0 Beta, branch: master, commit date: 2022-05-02 20:13, hash: 62ef1c08af
Worked: (newest version of Blender that worked as expected)

Short description of error
origin of strips act inecpected when the strip is scaled .so the origin position consider the actual size( scale ) of the strip and adapt to the scale value for for keyframe purpose (to animate the origin when and where it needed ).

Exact steps for others to reproduce the error
2022-05-09 15-27-40.mp4

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39 **Blender Version** Broken: version: 3.2.0 Beta, branch: master, commit date: 2022-05-02 20:13, hash: `62ef1c08af` Worked: (newest version of Blender that worked as expected) **Short description of error** origin of strips act inecpected when the strip is scaled .so the origin position consider the actual size( scale ) of the strip and adapt to the scale value for for keyframe purpose (to animate the origin when and where it needed ). **Exact steps for others to reproduce the error** [2022-05-09 15-27-40.mp4](https://archive.blender.org/developer/F13061131/2022-05-09_15-27-40.mp4)
Author

Added subscriber: @hamza-el-barmaki

Added subscriber: @hamza-el-barmaki
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

I am not sure what is unexpected about this exactly. This is essentially analogous to scaling a plane with its origin not at the center, in this case, it might seem that it moves upon scaling, but it is actually just scaled unproportionally making the illusion of movement. For instance, if the origin is at the the far left, scaling will happen by having the far right corner points to move away from the origin, and vice versa for the far right.
Or am I missing something?

I am not sure what is unexpected about this exactly. This is essentially analogous to scaling a plane with its origin not at the center, in this case, it might seem that it moves upon scaling, but it is actually just scaled unproportionally making the illusion of movement. For instance, if the origin is at the the far left, scaling will happen by having the far right corner points to move away from the origin, and vice versa for the far right. Or am I missing something?
Author

@OmarEmaraDev what i expecting is the origin don't make the plan (the image) move . if the plan is scaled so the origin must not always take original size and make it move

eg: frame1 : i sacled image to (0.6,0.6)and the positioned an image the top right corner ...
for frame 100 : i want to make the origin in buttom left corner to rotate the image only so what happen is the position of the image also change to the buttom left corner
which is undesired 2022-05-10 08-53-10.mp4
so origin option became useless when the image is scaled because undesired inpredicted changing position happens

@OmarEmaraDev what i expecting is the origin don't make the plan (the image) move . if the plan is scaled so the origin must not always take original size and make it move eg: frame1 : i sacled image to (0.6,0.6)and the positioned an image the top right corner ... for frame 100 : i want to make the origin in buttom left corner to rotate the image only so what happen is the position of the image also change to the buttom left corner which is undesired [2022-05-10 08-53-10.mp4](https://archive.blender.org/developer/F13064382/2022-05-10_08-53-10.mp4) so origin option became useless when the image is scaled because undesired inpredicted changing position happens
Member

The origin is designed so that it affects scaling as well, not just rotation. So it is expected that the strips will move. The alternative is to disregard the origin when scaling, which will limit the usability of the origin option.

The origin is designed so that it affects scaling as well, not just rotation. So it is expected that the strips will move. The alternative is to disregard the origin when scaling, which will limit the usability of the origin option.
Author

@OmarEmaraDev i not against that is use full to have origin affect scale maybe i didn't explain it well ...... if we look to 3d modelling moving origin of a cube of a scaled object don't make the object change position unless we change xyz values ...so that the only issue i have

@OmarEmaraDev i not against that is use full to have origin affect scale maybe i didn't explain it well ...... if we look to 3d modelling moving origin of a cube of a scaled object don't make the object change position unless we change xyz values ...so that the only issue i have
Member

@hamza-el-barmaki In modeling, operators are destructive, so when you change the origin of an object, Blender moves the object implicitly to do what you want. The same does not apply for VSE because the transformation are non-destructive, they are done on the fly, and you can technically move the object to compensate for the movement caused by the scaling.

The equivalent for VSE is to use destructive operators. For instance, by setting the pivot to 2D cursor, setting the 2D cursor to one of the corners and rotating, then putting it on the other corner and rotating, leaving the transform origin always at 0.5. Does that work for your use case?

@hamza-el-barmaki In modeling, operators are destructive, so when you change the origin of an object, Blender moves the object implicitly to do what you want. The same does not apply for VSE because the transformation are non-destructive, they are done on the fly, and you can technically move the object to compensate for the movement caused by the scaling. The equivalent for VSE is to use destructive operators. For instance, by setting the pivot to 2D cursor, setting the 2D cursor to one of the corners and rotating, then putting it on the other corner and rotating, leaving the transform origin always at 0.5. Does that work for your use case?
Author

maybe to avoid problems we can create two origins (infuence points) (one dedicated to rotation (appear as tiny cercle )and the other for scalings and other things (appear as point )

maybe to avoid problems we can create two origins (infuence points) (one dedicated to rotation (appear as tiny cercle )and the other for scalings and other things (appear as point )
Author

In #97986#1355737, @OmarEmaraDev wrote:

The equivalent for VSE is to use destructive operators. For instance, by setting the pivot to 2D cursor, setting the 2D cursor to one of the corners and rotating, then putting it on the other corner and rotating, leaving the transform origin always at 0.5. Does that work for your use case?

don't work here a situation
2022-05-10 11-30-18.mp4

> In #97986#1355737, @OmarEmaraDev wrote: > > The equivalent for VSE is to use destructive operators. For instance, by setting the pivot to 2D cursor, setting the 2D cursor to one of the corners and rotating, then putting it on the other corner and rotating, leaving the transform origin always at 0.5. Does that work for your use case? don't work here a situation [2022-05-10 11-30-18.mp4](https://archive.blender.org/developer/F13064600/2022-05-10_11-30-18.mp4)
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Member

In #97986#1355738, @hamza-el-barmaki wrote:
maybe to avoid problems we can create two origins (infuence points) (one dedicated to rotation (appear as tiny cercle )and the other for scalings and other things (appear as point )

I guess you can add a proposal for this, but this should be handled outside of this bug report.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

don't work here a situation

I can replicate that. This seems like a bug indeed. But since it is different from this report, I created a new report for it in #98015. So I will archive this one and lets continue this in that report.

> In #97986#1355738, @hamza-el-barmaki wrote: > maybe to avoid problems we can create two origins (infuence points) (one dedicated to rotation (appear as tiny cercle )and the other for scalings and other things (appear as point ) I guess you can add a proposal for this, but this should be handled outside of this bug report. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests > don't work here a situation I can replicate that. This seems like a bug indeed. But since it is different from this report, I created a new report for it in #98015. So I will archive this one and lets continue this in that report.
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
2 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#97986
No description provided.