VSE Regression: Changing dimensions are cropping instead of scaling #86301
Labels
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#86301
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30
Blender Version
Broken: version: 2.93.0 Alpha
Short description of error
Import a video and change ex. resolution.
The video will be cropped instead of scaled. It used to do that, so it's a regression.
This basically means that if you import you footage and edit it, and then realize the the project resolution is wrong or if you need to render in a different resolution, you''re in trouble.
{F9869337,size=full}
Added subscriber: @tintwotin
#89969 was marked as duplicate of this issue
#89203 was marked as duplicate of this issue
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Confirmed'
This was design decision as acceptable compromise for new functionality.
Issue is what even should be done when you increase X resolution? What if image is rotated?
Possible solution would be to set fit method flag on strip when it's added or set fit operator is used. This way changing resolution could automatically change strip scale.
When strip transform property is modified manually this flag would be removed.
This means though that when you would change resolution, some strips would re-scale, and some not. So not sure if this would be good solution.
I will confirm this as known issue for now.
It is also breaking the "Set Resolution Size" for Movie strips(Project Res: 4K, Import 2K, Set Res Size):
{F9880561,size=full}
After the project resolution has been changed, it'll crop or pad all footage which doesn't match it. So, in other words, if this design is to be kept, the options to change the project resolutions should be disabled, as they're breaking the project.
The only option users have is completely redo the entire project from scratch, because re-importing the footage manually will scale it correctly to the new project resolution(Inputs -> Reload Strips doesn't have any effect):
{F9880572,size=full}
In other words, another solution(than deactivating project resolution) could be, on project resolution change, that all strips should go through the same meta-data vs. project resolution calculation process, as it is when originally importing the strips.
VSE: Changing dimensions are cropping instead of scalingto VSE Regression: Changing dimensions are cropping instead of scalingAdded subscribers: @MFletcher, @mano-wii
Added subscriber: @costa
Changed status from 'Confirmed' to: 'Archived'
As I do not have anymore time or motivation for a continued investment in the Blender project, I'm giving up on this report for now.
Added subscriber: @lichtwerk
Changed status from 'Archived' to: 'Confirmed'
Sorry to hear (thx again reporting). In my opinion we should not sweep this under the carpet (esp. since this already been confirmed), there is still a chance to get this fixed in the future and others might be affected by this issue as well.
Feel free to unsubscribe though.
Removed subscriber: @tintwotin
Added subscriber: @ShaunKreider
In Blender 2.x I could export any video resolution I wanted and it did the business, now in 3.x a project seems to be stuck at whatever resolution it was started in. Is there a work around for this?