VSE and border render incompatable #49121

New Issue

Mike Futcher · 2016-08-20T01:26:48+02:00

Mike Futcher commented

2016-08-20 01:26:48 +02:00

Leaving border select on while using the VSE results in either a garbled mess of a render, or crashing.

Blender version: 2.77a

Windows 10,
Intel Core i5-6300HQ @ 2.30Ghz
8.00 GB

To re-create the problem:

Open Blender,
Press Keypad 0 to select camera view,
Press Shift-B and drag a box to select a border render
Change the 3D view to the VSE editor
Add a video
Press 12 to render a frame, or click Render Animation
The image is a garbled mess.

Leaving border select on while using the VSE results in either a garbled mess of a render, or crashing. Blender version: 2.77a Windows 10, Intel Core i5-6300HQ @ 2.30Ghz 8.00 GB To re-create the problem: Open Blender, Press Keypad 0 to select camera view, Press Shift-B and drag a box to select a border render Change the 3D view to the VSE editor Add a video Press 12 to render a frame, or click Render Animation The image is a garbled mess.

Mike Futcher commented

2016-08-20 01:26:48 +02:00

Changed status to: 'Open'

Mike Futcher commented

2016-08-20 01:26:48 +02:00

Added subscriber: @MikeFutcher

Mike Futcher commented

2016-08-20 01:42:02 +02:00

Ahhhh... a little more testing...

Starting from the end of the last set of instructions,

Set the video image/video output type to H.264
Pressing Render Animation now causes Blender to crash.

I think this may be due to the H.264 codec only working when it's dimensions are multiples of 8.

Ahhhh... a little more testing... Starting from the end of the last set of instructions, Set the video image/video output type to H.264 Pressing Render Animation now causes Blender to crash. I think this may be due to the H.264 codec only working when it's dimensions are multiples of 8.

Sergey Sharybin self-assigned this 2016-08-23 12:45:11 +02:00

blender-admin commented

2016-08-24 10:19:44 +02:00

This issue was referenced by 22b913a278

This issue was referenced by 22b913a27881b9bb8c4cb1738c803c8089ca0393

Sergey Sharybin commented

2016-08-24 10:23:28 +02:00

Looked into the issue.

Unfortunately, it's not that trivial to make sequencer aware of the border rendering and the way how render result is fed from sequencer to the render result adds more complexity to this..

While corrupted renders and crashes are really bad, for now i'll add a code which prevents rendering with sequencer and border enabled at the same time.

Surely, making sequencer aware of border rendering will be really cool, but that'd happen as general development. Added a note about this to our TODO list: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Tools#Sequence_Editor

Looked into the issue. Unfortunately, it's not that trivial to make sequencer aware of the border rendering and the way how render result is fed from sequencer to the render result adds more complexity to this.. While corrupted renders and crashes are really bad, for now i'll add a code which prevents rendering with sequencer and border enabled at the same time. Surely, making sequencer aware of border rendering will be really cool, but that'd happen as general development. Added a note about this to our TODO list: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Tools#Sequence_Editor

Sergey Sharybin commented

2016-08-24 10:25:04 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2016-08-24 10:25:04 +02:00

Sybren A. Stüvel referenced this issue

2023-03-30 15:30:10 +02:00

Blender development todo list -- Editors #55366

Sign in to join this conversation.