Keyframes with stereoscopy button doesn't work in animation, individual frame works #76353

Open
opened 2020-05-03 00:12:46 +02:00 by Artur · 17 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-01 14:06, hash: 60741cfe18
Worked: never, tested 2.75a (when Stereoscopy was introduced) and 2.79

Short description of error
Whole animation is render with stereoscopy ignoring on/off animation keyframes.

Exact steps for others to reproduce the error
with stereoscopy "on" insert a keyframe on it, move few frames and turn off stereoscopy and insert a keyframe. While rendering animation (my setup is FFmpeg with mp4 coding) all frames are rendered as stereoscopic. I attached an example file with render result. I was expecting to have half of this animation as stereoscopic and half normal. Originally I discovered it in a situation where I was swapping cameras (binding to video marker).

Open file, render frames 39-40-41 individually.
in viewport change set frame to 39
Render animation (5 frames)
in viewport, set frame to 41,
Render animation
notice difference in the two.
T76353Stereoscopy.blend

bug reportstereoscopy.blend0001-0250.mkv

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-01 14:06, hash: `60741cfe18` Worked: never, tested 2.75a (when Stereoscopy was introduced) and 2.79 **Short description of error** Whole animation is render with stereoscopy ignoring on/off animation keyframes. **Exact steps for others to reproduce the error** with stereoscopy "on" insert a keyframe on it, move few frames and turn off stereoscopy and insert a keyframe. While rendering animation (my setup is FFmpeg with mp4 coding) all frames are rendered as stereoscopic. I attached an example file with render result. I was expecting to have half of this animation as stereoscopic and half normal. Originally I discovered it in a situation where I was swapping cameras (binding to video marker). Open file, render frames 39-40-41 individually. in viewport change set frame to 39 Render animation (5 frames) in viewport, set frame to 41, Render animation notice difference in the two. [T76353Stereoscopy.blend](https://archive.blender.org/developer/F8508942/T76353Stereoscopy.blend) [bug reportstereoscopy.blend0001-0250.mkv](https://archive.blender.org/developer/F8508216/bug_reportstereoscopy.blend0001-0250.mkv)
Author

Added subscriber: @arturmachura

Added subscriber: @arturmachura
Author
[bug.blend](https://archive.blender.org/developer/F8508237/bug.blend)
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Ankit Meel changed title from animation of stereoscopy button doesn't work to Keyframes with stereoscopy button doesn't work in animation, individual frame works 2020-05-03 10:46:36 +02:00
Member

animation also seems to depend on the active frame in viewport. The modified steps show that.

animation also seems to depend on the active frame in viewport. The modified steps show that.

Added subscriber: @ChristopherAnderssarian

Added subscriber: @ChristopherAnderssarian

I've used this option to cut down on render times for scenes that I didn't need to see the stereo for, at the time. It was on a render farm so each .blend file was opened on the frame that needed to be rendered so animation worked.
I hope this option doesn't get removed.

I've used this option to cut down on render times for scenes that I didn't need to see the stereo for, at the time. It was on a render farm so each .blend file was opened on the frame that needed to be rendered so animation worked. I hope this option doesn't get removed.
Sybren A. Stüvel self-assigned this 2020-05-04 16:27:30 +02:00

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

This has never worked. I tested with both 2.75a, which introduced Stereoscopy under the name "Multi-Views", and 2.79 for good measure. From what I can see in the code, it also wasn't designed with animation of this property in mind. The setting affects things like the output format; after all, if you're rendering to a side-by-side image, the output is going to be twice as wide. If you turn this on and off in the middle of a video stream, FFmpeg likely won't be able to encode that video.

This has never worked. I tested with both 2.75a, which introduced Stereoscopy under the name "Multi-Views", and 2.79 for good measure. From what I can see in the code, it also wasn't designed with animation of this property in mind. The setting affects things like the output format; after all, if you're rendering to a side-by-side image, the output is going to be twice as wide. If you turn this on and off in the middle of a video stream, FFmpeg likely won't be able to encode that video.

Added subscribers: @dfelinto, @brecht

Added subscribers: @dfelinto, @brecht

@brecht @dfelinto What shall I do with this report? On one hand I want to avoid future confusion and make the Stereoscopy checkbox non-animatable. On the other hand, I don't want to break @ChristopherAnderssarian 's workflow either.

@brecht @dfelinto What shall I do with this report? On one hand I want to avoid future confusion and make the Stereoscopy checkbox non-animatable. On the other hand, I don't want to break @ChristopherAnderssarian 's workflow either.

Well, I've known about this for a while and made a point not to report it, as I know it wasn't designed with animation in mind and will probably end up getting removed.
It's probably just me who has ever used this. But, considering it's been five years and only now a report has come in, can we quietly keep this?

Whether it's using blender in the "wrong way", having functionality removed (in bcon3 of all times) or getting renders unknowingly deleted; you have to admit I'm pretty good at being screwed over in my edge-caseness.
Oh, I've just remembered, @sybren. You once asked me why I didn't like the term design. I think this task and the examples I gave illustrate the troubles I have with....er.. certain things.

Well, I've known about this for a while and made a point not to report it, as I know it *wasn't designed with animation in mind* and will probably end up getting removed. It's probably just me who has ever used this. But, considering it's been five years and only now a report has come in, can we quietly keep this? Whether it's using blender in the "wrong way", having functionality removed (in bcon3 of all times) or getting renders unknowingly deleted; you have to admit I'm pretty good at being screwed over in my edge-caseness. Oh, I've just remembered, @sybren. You once asked me why I didn't like the term *design*. I think this task and the examples I gave illustrate the troubles I have with....er.. certain things.

Are you saying you are switching between stereo and non-stereo in the middle of a shot? Or this goes along with a camera switch somehow, and what could work better is an option to enable/disable stereo per camera?

Anyway, I don't see any reason to change things in 2.83, if we remove support for animating this it would be in 2.90.

Are you saying you are switching between stereo and non-stereo in the middle of a shot? Or this goes along with a camera switch somehow, and what could work better is an option to enable/disable stereo per camera? Anyway, I don't see any reason to change things in 2.83, if we remove support for animating this it would be in 2.90.

I can also think of a scenario where the user switches camera mid-shot (using markers and cameras bind to them) that could potentially also impact multi-view render. But these are really corner cases where the user should know better.

I can also think of a scenario where the user switches camera mid-shot (using markers and cameras bind to them) that could potentially also impact multi-view render. But these are really corner cases where the user should know better.

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'

Also known issues are to be kept open so other users can find them. If it is to be closed as invalid then its subtype is to be kept as report.

Also known issues are to be kept open so other users can find them. If it is to be closed as invalid then its subtype is to be kept as report.
Sybren A. Stüvel removed their assignment 2020-10-01 12:16:17 +02:00

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:36:13 +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
6 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#76353
No description provided.