Page MenuHome

Sequencer doesn't reflect source range in strip display correctly
Open, NormalPublic

Description

System Information
Windows 7

Blender Version
Broken: 2.78 Release

Short description of error
When the length of a render source is modified, the display in the strip display doesn't show it. The info 'Original frame range' is correct though.

Exact steps for others to reproduce the error

  1. From the default scene, create a 'link object data' copy (although i guess the type doesn't matter)
  2. Go back to scene 'Scene' and set the end frame to 100
  3. Go to scene 'Scene.001', open sequence editor and add scene 'Scene'. It will now show a strip of 100 frames length.
  4. Go back to scene 'Scene' and change the end frame to 50
  5. Go back to scene 'Scene.001'

The Sequence Editor will still show a green bar 100 frames long, although the info in the properties panel tells the correct info: Original frame range 1-50 (50).
More importantly, you can drag the right grabber of the strip to the right and it will still paint 100 frames green and the rest grey/transparent, although the 100 frames don't have any meaning no more - it was just the length it was created with. You can also unlink the strip from the original scene and relink it again, it will still paint 100 frames green/valid.

Maybe this is a bug, an oversight, maybe even intentional, I don't know.
I don't think a .blend file is necessary in this case, but I will upload one, if desired.

Event Timeline

I'm not sure if this is intentional or not, but it certainly bugs me. I have fixed it in the referenced diff by searching for any matching scene strips and updating their details.

N.B. I opted to leave the end of the strip where it is to avoid the pain of shuffling other strips around if you are making the scene longer, so the user will still have to do that manually.

@Andreas Halm (Tropics) are you able to build Blender with this patch in to see if the new behaviour is what you expect?

I am not able to build Blender myself, unfortunately.
Your description sounds promising, glad to see I am not the only one confused by this behavior.

Righto. I made a quick demo vid of how it behaves now:
https://www.youtube.com/watch?v=08ovpPVXatY

Here's the .blend file used within for comparison in unmodified builds:

Hopefully one of the devs will have a look at this, however I think they're all busy with BlenderConf at the moment :o)

That looks exactly as I would expect it to work. Hope to see that soon in a future blender version!

Cool. I've just spotted a bug in my patch and fixed it in the diff, doesn't affect you but thought I'd mention it here in case anyone else has tried building with it.

There may be more to this than I originally thought. I thought this was more a cosmetic feature or bug, but it indeed affects the final rendering.

I just had the case that the original strip was 495 frames long, after adjusting a camera flight it is now 505 frames long. This is reflected in the info panel (Original frame range: 500-1004 (505)). However, when rendering the scene, frame 495 is repeated 10 times.

First question: Is this behavior connected to this task?

Second: Is this behavior intentional? I can see how you don't want to "pin" the strip to the scene start and end frame settings. It provides the option to add several strips of a scene easily. However, this forces you (if you modified the length of a scene) to delete the strip and insert it anew - which also forces you to recreate all (effect) strips depending on it afaik.

If it is intentional, I would vote for either a pin/unpin to scene frames settings button, or a button to take over the current frames settings. The latter option might be more user friendly.

EDIT: I just found out the keyboard shortcut for said button: ALT-R. I feel so stupid. However, adding a button for that, or even a pin/unpin option, might be useful.

The frozen-end-frames behaviour is definitely related to this - the strip has its "endstill" value set as if the source was still the old length.

You can see the fixed behaviour in my sample vid if you look *very* closely! At 0:31 I show that the end is frozen as you do not see the yellow when I position the playhead to the right of the original end point, then when I change the length and switch back at 0:42 it is unfrozen and you see the yellow.

Aaron Carlisle (Blendify) triaged this task as Normal priority.Feb 2 2017, 6:29 AM