Page MenuHome
Create Task
Maniphest T43799

VSE Scene Bug
Closed, ArchivedPublic
Actions

Description

System Information
Windows 8.0
INtel HD 4600

Blender Version
Broken: 2.73.8

Short description of error
VSE Scene Bug when updating scene

Exact steps for others to reproduce the error

  1. open blender

2.Select every object and delete them

  1. Go to VSE and add a scene strip
  2. Go back to 3d view port and add a object and a camera
  3. go back to vse look at the scene strip- nothing changes
  4. reload the strips (Alt R)
  5. some frames are better some are still messed up

Event Timeline

Aaron Carlisle (Blendify) created this task.Feb 24 2015, 9:47 PM
Aaron Carlisle (Blendify) raised the priority of this task from to 90.
Aaron Carlisle (Blendify) updated the task description. (Show Details)
Aaron Carlisle (Blendify) added projects: BF Blender, Video Sequencer.
Aaron Carlisle (Blendify) edited a custom field.
Aaron Carlisle (Blendify) added a subscriber: Aaron Carlisle (Blendify).
Julian Eisel (Severin) lowered the priority of this task from 90 to 30.Feb 24 2015, 9:50 PM
Julian Eisel (Severin) added a subscriber: Julian Eisel (Severin).

I can't really recreate that here, .blend?

Aaron Carlisle (Blendify) added a comment.Feb 25 2015, 9:23 PM

Bug.blend493 KBDownload

Bastien Montagne (mont29) raised the priority of this task from 30 to Normal.Feb 27 2015, 12:36 PM
Bastien Montagne (mont29) added subscribers: Sergey Sharybin (sergey), Antonis Ryakiotakis (psy-fi).
Bastien Montagne (mont29) added a subscriber: Bastien Montagne (mont29).

Think @Aaron Carlisle (Blendify) is referring to caching issue here…

Not sure how to solve that though, pretty much any change in a scene may alter its render or not, we cannot invalidate cache on each and every NC_SCENE notification :/

Sergey, Antony, maybe you have idea here?

Antonis Ryakiotakis (psy-fi) added a comment.Feb 27 2015, 1:20 PM

That works as expected - if you know how it works of course, which is not what the users might expect. The refresh button is there for that reason.

To solve this through notifications we'd basically have to add new notifications in a gazillion places in blender, or we'd have to have a dependency system somehow, but again there are so many places that would invalidate the sequencer.

I am tempted to reject as working as expected, but I'd like some more opinions on this first.

Sergey Sharybin (sergey) changed the task status from Unknown Status to Unknown Status.Feb 27 2015, 1:34 PM
Sergey Sharybin (sergey) claimed this task.

You can't reliably invalidate sequencer cache with just notification system. Some sort of depsgraph is needed for that, but even then it's not totally trivial to avoid unneeded cache freeing.

For now just use manual cache update button.