Strip length doesn't extend in VSE when extending the according scene framerange. #102524

Closed
opened 2022-11-15 12:21:14 +01:00 by Rik Schutte · 7 comments

System Information
Operating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: AMD Radeon RX 6700 XT (navy_flounder, LLVM 13.0.1, DRM 3.44, 5.17.5-76051705-generic) AMD 4.6 (Core Profile) Mesa 22.0.1

Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-14 15:46, hash: 85bbcb32eb
Worked: (newest version of Blender that worked as expected) None

Short description of error
When using a new scene as a strip in VSE with an initial framerange of (for example) 250 frames, the strip doesn't allow extension when changing the framerange of the scene beyond 250. It shows the strip extension in a darker color and freezes the last frame instead of updating the animation according to the framerange extension.
VSE_framerange_extension_bug.png

Exact steps for others to reproduce the error

  • Open Blender in the VSE workspace.
  • Add a new Scene strip to the timeline channel.
  • Open the new scene (by default called Scene.001) and extend the framerange beyond the initial framerange. (for trouble shooting, animate something over the total framerange)
  • Go back to the VSE scene and try to extend (via press and drag) the 'Scene' strip to the updated framerange.
    It's not updating the strip to the extended framerange, and doesn't update the animation beyond the initial framerange.
    Interestingly, if you edit the Hold Offset property in {nav Sidebar > Strip > Time}, the framerate is immediately updated.

Blendfile to demonstrate the error:
bugreport_VSE_scene_framerange_update.blend

**System Information** Operating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits Graphics card: AMD Radeon RX 6700 XT (navy_flounder, LLVM 13.0.1, DRM 3.44, 5.17.5-76051705-generic) AMD 4.6 (Core Profile) Mesa 22.0.1 **Blender Version** Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-14 15:46, hash: `85bbcb32eb` Worked: (newest version of Blender that worked as expected) None **Short description of error** When using a new scene as a strip in VSE with an initial framerange of (for example) 250 frames, the strip doesn't allow extension when changing the framerange of the scene beyond 250. It shows the strip extension in a darker color and freezes the last frame instead of updating the animation according to the framerange extension. ![VSE_framerange_extension_bug.png](https://archive.blender.org/developer/F13916801/VSE_framerange_extension_bug.png) **Exact steps for others to reproduce the error** - Open Blender in the VSE workspace. - Add a new `Scene` strip to the timeline channel. - Open the new scene (by default called `Scene.001`) and extend the framerange beyond the initial framerange. (for trouble shooting, animate something over the total framerange) - Go back to the VSE scene and try to extend (via press and drag) the 'Scene' strip to the updated framerange. It's not updating the strip to the extended framerange, and doesn't update the animation beyond the initial framerange. Interestingly, if you edit the `Hold Offset` property in {nav Sidebar > Strip > Time}, the framerate is immediately updated. Blendfile to demonstrate the error: [bugreport_VSE_scene_framerange_update.blend](https://archive.blender.org/developer/F13916803/bugreport_VSE_scene_framerange_update.blend)
Author

Added subscriber: @Rikstopher

Added subscriber: @Rikstopher

Added subscriber: @mano-wii

Added subscriber: @mano-wii

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

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

Thanks for the report, I can confirm the issue.
I also edited the description to make the problem clearer.

Thanks for the report, I can confirm the issue. I also edited the description to make the problem clearer.

Added subscriber: @iss

Added subscriber: @iss

I have added operator "Update Scene Frame Range" to reslove this issue. This can't really be done automatically, because scene can be linked and it could seriously mess up timeline. There is also concern of thread safety.

Did not mention this report in commit, because this is not a bug technically. See 90e9406866

I have added operator "Update Scene Frame Range" to reslove this issue. This can't really be done automatically, because scene can be linked and it could seriously mess up timeline. There is also concern of thread safety. Did not mention this report in commit, because this is not a bug technically. See 90e9406866

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Richard Antalik self-assigned this 2023-01-30 08:08:55 +01:00
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
3 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#102524
No description provided.