Video Sequence Editor cache not updating for scene strips #66891

Open
opened 2019-07-14 03:42:09 +02:00 by KiJeon · 6 comments

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: 06312c6d2d
Worked: 2.79

Short description of error
Not sure if I'm doing something wrong here, but the Video Sequence Editor is not updating scene strips when changes are made to the scene (like object/camera manipulation).
Whatever is cached before the change stays in memory. The only way to force the update I've found so far is to change the "Preview Shading".

The expected behavior is that any visual change made to the scene in the scene strip would be updated real-time without changing the Preview Shading every time.

This isn't the case in 2.79. For the most part, I found scene strips updating when I made changes to the scene. If it won't update for some reason, I'd toggle something that won't affect my scene (like "Show Grease Pencil" when I have no GP elements).
While even this wasn't ideal, at least I wasn't forced to change the strip visually to force the update, and it didn't need to be done every time.

If this isn't a bug but it's a settings issue, maybe the defaults need to be changed to make it work as expected.

Exact steps for others to reproduce the error

  1. Add a scene strip to the VSE.
  2. Playback the timeline in VSE.
  3. Do something to change the scene. (e.g. Add a new Cube, move the camera, etc.)
  4. Scrub the timeline in VSE, and you should find that wherever there is cache, the scene doesn't update.

T66891_VSE_cache_scene.blend

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: `06312c6d2d` Worked: 2.79 **Short description of error** Not sure if I'm doing something wrong here, but the Video Sequence Editor is not updating scene strips when changes are made to the scene (like object/camera manipulation). Whatever is cached before the change stays in memory. The only way to force the update I've found so far is to change the "Preview Shading". The expected behavior is that any visual change made to the scene in the scene strip would be updated real-time without changing the Preview Shading every time. This isn't the case in 2.79. For the most part, I found scene strips updating when I made changes to the scene. If it won't update for some reason, I'd toggle something that won't affect my scene (like "Show Grease Pencil" when I have no GP elements). While even this wasn't ideal, at least I wasn't forced to change the strip visually to force the update, and it didn't need to be done every time. If this isn't a bug but it's a settings issue, maybe the defaults need to be changed to make it work as expected. **Exact steps for others to reproduce the error** 1. Add a scene strip to the VSE. 2. Playback the timeline in VSE. 3. Do something to change the scene. (e.g. Add a new Cube, move the camera, etc.) 4. Scrub the timeline in VSE, and you should find that wherever there is cache, the scene doesn't update. [T66891_VSE_cache_scene.blend](https://archive.blender.org/developer/F7610901/T66891_VSE_cache_scene.blend)
Author

Added subscriber: @0o00o0oo

Added subscriber: @0o00o0oo
Richard Antalik was assigned by Germano Cavalcante 2019-07-15 16:23:53 +02:00

Not sure if this is valid request. AFAIK this is near to impossible to implement.

Is there similar cache system(physics etc) which can detect such changes?
I could hook up sequencer cache on such system. Otherwise it would have to be manually hooked up on every single action, that can result in change of rendered image.

Another possibility would be to not use cache for scene strips by default.

Not sure if this is valid request. AFAIK this is near to impossible to implement. Is there similar cache system(physics etc) which can detect such changes? I could hook up sequencer cache on such system. Otherwise it would have to be manually hooked up on every single action, that can result in change of rendered image. Another possibility would be to not use cache for scene strips by default.
Author

If nothing else, if it would result in the expected behavior of live updates like in 2.79, then I think not using cache by default makes sense.

Is that how it worked in 2.79?

If nothing else, if it would result in the expected behavior of live updates like in 2.79, then I think not using cache by default makes sense. Is that how it worked in 2.79?

In #66891#723558, @0o00o0oo wrote:
If nothing else, if it would result in the expected behavior of live updates like in 2.79, then I think not using cache by default makes sense.

Is that how it worked in 2.79?

In 2.79 the cache was there, but it wasn't "recycled", so technically the behavior would be the same in 2.79. The same goes for scene proxies in older versions - you have to manually remove old proxies to update them.

If there will be strips on top of scene strips, those would be cached though...

> In #66891#723558, @0o00o0oo wrote: > If nothing else, if it would result in the expected behavior of live updates like in 2.79, then I think not using cache by default makes sense. > > Is that how it worked in 2.79? In 2.79 the cache was there, but it wasn't "recycled", so technically the behavior would be the same in 2.79. The same goes for scene proxies in older versions - you have to manually remove old proxies to update them. If there will be strips on top of scene strips, those would be cached though...
Richard Antalik was unassigned by Dalai Felinto 2019-12-23 16:33:46 +01:00

Added subscriber: @iss

Added subscriber: @iss

Added subscriber: @yshui

Added subscriber: @yshui
Philipp Oeser removed the
Interest
VFX & Video
label 2023-02-10 09:32:12 +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
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#66891
No description provided.