Adding a scene strip to VSE in the same scene makes results vary depending on scene start frame #50139

New Issue

Jason schleifer · 2016-11-29T23:01:15+01:00

Jason schleifer commented

2016-11-29 23:01:15 +01:00

Original report:

I have a scene where my VSE contains a scene strip of the current scene. When rendering interactively, I get what I expect.. a full frame. When I render in batch mode, I get a zoomed in view of my image.

I've attached a copy of the file. Just render a single frame interactively, then render the same frame in batch mode and compare.

Easy way to see the bug:

https://developer.blender.org/T50139#413098

**Original report:** I have a scene where my VSE contains a scene strip of the current scene. When rendering interactively, I get what I expect.. a full frame. When I render in batch mode, I get a zoomed in view of my image. I've attached a copy of the file. Just render a single frame interactively, then render the same frame in batch mode and compare. **Easy way to see the bug:** https://developer.blender.org/T50139#413098

Jason schleifer commented

2016-11-29 23:01:15 +01:00

Changed status to: 'Open'

Jason schleifer commented

2016-11-29 23:01:15 +01:00

Added subscriber: @JasonSchleifer

Sergey Sharybin commented

2016-11-30 18:53:11 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2016-11-30 18:53:11 +01:00

The file is missing.

Please also explain what is interactive and batch rendering.

The file is missing. Please also explain what is interactive and batch rendering.

Jason schleifer commented

2016-11-30 18:54:51 +01:00

sequenceEditorScalesRender.blend

Hi Sergey, I've uploaded the file (not sure why it didn't attach before).

Interactive rendering is hitting F12

Batch is running from the commandline.

[sequenceEditorScalesRender.blend](https://archive.blender.org/developer/F412157/sequenceEditorScalesRender.blend) Hi Sergey, I've uploaded the file (not sure why it didn't attach before). Interactive rendering is hitting F12 Batch is running from the commandline.

Olly Funkster commented

2016-12-01 10:54:23 +01:00

Added subscriber: @Funkster-3

Olly Funkster commented

2016-12-01 10:54:23 +01:00

I've tried a few variations, but always get the same size image as the one generated in interactive rendering.

Tried at 100% and 25%, and with released 2.78 and my current local build. Linux x64.

I didn't run the scripts in the .blend.

I've tried a few variations, but always get the same size image as the one generated in interactive rendering. Tried at 100% and 25%, and with released 2.78 and my current local build. Linux x64. I didn't run the scripts in the .blend.

Jason schleifer commented

2016-12-01 17:47:46 +01:00

That's so strange - I get it zoomed in running from command line.. here's my command:

blender --enable-new-depsgraph -b ./sequenceEditorScalesRender.blend -t 0 -s 600 -e 600 -a -x 1 -y

That's so strange - I get it zoomed in running from command line.. here's my command: blender --enable-new-depsgraph -b ./sequenceEditorScalesRender.blend -t 0 -s 600 -e 600 -a -x 1 -y

Olly Funkster commented

2016-12-01 18:02:43 +01:00

Huh. Confirmed using your command - I was using -f to render one frame rather than start and end frames.

This command doesn't scale:
blender --enable-new-depsgraph -b ./sequenceEditorScalesRender.blend -t 0 -f 250 -x 1 -y

Huh. Confirmed using your command - I was using -f to render one frame rather than start and end frames. This command doesn't scale: blender --enable-new-depsgraph -b ./sequenceEditorScalesRender.blend -t 0 -f 250 -x 1 -y

Jason schleifer commented

2016-12-01 18:23:37 +01:00

Interesting.. the plot thickens! so if you try and render a frame range, you'll get the zooming in as well!

Carlo Andreacchio commented

2016-12-02 02:27:29 +01:00

Added subscriber: @candreacchio

Carlo Andreacchio commented

2016-12-02 02:27:29 +01:00

enable-new-depsgraph seems to be the issue for me, but not with size

blender --enable-new-depsgraph -b C:\Users\user\Downloads\sequenceEditorScalesRender.blend -s 3 -e 4 -o C:\scaletest.####.jpg -a

and ignored -o entirely for me, and rendered (but didnt save) the images.

im on win7 x64... both with and without new depsgraph the size was fine.

- enable-new-depsgraph seems to be the issue for me, but not with size blender --enable-new-depsgraph -b C:\Users\user\Downloads\sequenceEditorScalesRender.blend -s 3 -e 4 -o C:\scaletest.####.jpg -a and ignored -o entirely for me, and rendered (but didnt save) the images. im on win7 x64... both with and without new depsgraph the size was fine.

Nikos Priniotakis commented

2017-01-14 15:04:38 +01:00

Added subscriber: @NikosPriniotakis

Dalai Felinto commented

2017-01-20 12:06:58 +01:00

Added subscriber: @dfelinto

Dalai Felinto commented

2017-01-20 12:06:58 +01:00

Changed status from 'Open' to: 'Archived'

Dalai Felinto closed this issue

2017-01-20 12:06:58 +01:00

Dalai Felinto self-assigned this 2017-01-20 12:06:58 +01:00

Dalai Felinto commented

2017-01-20 12:06:58 +01:00

This is a tricky one. Technically it's not a bug. In your case you are rendering frame 1200, not 600.

How to reproduce your issue in a simpler file:

Open: sequencer.blend
Render the frame 6, you will get the frame 6 (see sequencer on top):

Now change your scene frame start to 10 and re-render frame 6, you will get frame 15:

So what's happening?
When you add a Scene strip, the strip frames are relative to the scene range. The moment you change the frame start, the frame that will be used will change as well.

Why does it matter? Well in your case when you do blender -b -s 600 e 601 -a you are effectively changing the scene range before rendering the animation. Which leads to the problem above.

How to fix this? From the user point of view, a solution is to use a different scene to animate.

I will archive this and move to the TODO: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Editors#Video_Sequencer

This is a tricky one. Technically it's not a bug. In your case you are rendering frame 1200, not 600. How to reproduce your issue in a simpler file: * Open: [sequencer.blend](https://archive.blender.org/developer/F437318/sequencer.blend) * Render the frame 6, you will get the frame 6 (see sequencer on top): ![seq_fine.png](https://archive.blender.org/developer/F437319/seq_fine.png) * Now change your scene frame start to 10 and re-render frame 6, you will get frame 15: ![seq_start_10.png](https://archive.blender.org/developer/F437321/seq_start_10.png) So what's happening? When you add a Scene strip, the strip frames are relative to the scene range. The moment you change the frame start, the frame that will be used will change as well. Why does it matter? Well in your case when you do `blender -b -s 600 e 601 -a` you are effectively changing the scene range before rendering the animation. Which leads to the problem above. How to fix this? From the user point of view, a solution is to use a different scene to animate. I will archive this and move to the TODO: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Editors#Video_Sequencer

Dalai Felinto changed title from ~~Adding a scene strip to the VSE in the scene you're in causes the image to be zoomed in batch render~~ to Adding a scene strip to VSE in the same scene makes results vary depending on scene start frame

2017-01-20 12:09:14 +01:00

Alberto Mardegan commented

2017-03-11 21:50:21 +01:00

Added subscriber: @mardy