Animating sequencer speed affects itself #48095

Closed
opened 2016-04-09 20:33:44 +02:00 by Bloody Rain · 7 comments

System Information
Win7 Pro x64, 32gb, i5 6600, 2x 970 GTX 2gb

Blender Version
2.77 22a2853

Short description of error
I was trying out to do a dynamic slowmotion effect by making a cube bounce drop over frame 1-60 (2 sec at 30fps) and have the time slow down to 10% short before the first bounce.
But the result I got from animating the 'Speed factor' in the sequencer made the slowdown affect it's own F-Curve as it seems since the 10% point should have been reached 1 frame before the bounce but was actually reached several frames before.
The slowdown was also supposed to revert after this bounce reached it's peak and went over into the 2nd bounce, but this point was reached before the 1st bounce even touched the ground.

It seems to very counterintuitive to me that this is going as it does and I can't figure out where to place the curve points due to having to refresh the sequencer after every single change since they are being mapped to the resulting timeline instead of the original one.

https://dl.dropboxusercontent.com/u/59546146/SlowMotionIssue.blend

**System Information** Win7 Pro x64, 32gb, i5 6600, 2x 970 GTX 2gb **Blender Version** 2.77 22a2853 **Short description of error** I was trying out to do a dynamic slowmotion effect by making a cube bounce drop over frame 1-60 (2 sec at 30fps) and have the time slow down to 10% short before the first bounce. But the result I got from animating the 'Speed factor' in the sequencer made the slowdown affect it's own F-Curve as it seems since the 10% point should have been reached 1 frame before the bounce but was actually reached several frames before. The slowdown was also supposed to revert after this bounce reached it's peak and went over into the 2nd bounce, but this point was reached before the 1st bounce even touched the ground. It seems to very counterintuitive to me that this is going as it does and I can't figure out where to place the curve points due to having to refresh the sequencer after every single change since they are being mapped to the resulting timeline instead of the original one. https://dl.dropboxusercontent.com/u/59546146/SlowMotionIssue.blend
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @BloodyRain

Added subscriber: @BloodyRain
Author

Something I forgot to also mention: clicking the little lock icon in the F-Curve editor to make the speed curve not affect the result does actually not stop it from affecting the result, it does either way for some reason.
It works for the cube's location though.

Something I forgot to also mention: clicking the little lock icon in the F-Curve editor to make the speed curve not affect the result does actually **not** stop it from affecting the result, it does either way for some reason. It works for the cube's location though.
Member

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Joshua Leung self-assigned this 2016-04-10 01:34:12 +02:00
Member

You really need to be using two different scenes if you're going to be playing around with speed/time.

  1. The scene with the cube motion - That should not have any sequencer stuff in it at all
  2. The "sequencer scene" - This one is the one which contains the scene strip referencing #1, and is where you do any time animation.
You really need to be using two different scenes if you're going to be playing around with speed/time. 1) The scene with the cube motion - That should not have any sequencer stuff in it at all 2) The "sequencer scene" - This one is the one which contains the scene strip referencing #1, and is where you do any time animation.
Author

That doesn't work either. I've created a 2nd scene called "Time", removed all sequencer stuff from "Scene", referenced "Scene" in "Time" and set the speed curve again, and it desynced exactly the same way : (
I have updated the blend file which this approach.

That doesn't work either. I've created a 2nd scene called "Time", removed all sequencer stuff from "Scene", referenced "Scene" in "Time" and set the speed curve again, and it desynced exactly the same way : ( I have updated the blend file which this approach.
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
2 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#48095
No description provided.