Showstopper: 2nd keyframe for image sequences can't be set in compositing #73932
Labels
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#73932
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash:
77d23b0bd7, type: Releasebuild date: 2020-02-13, 01:56:46
platform: Windows
Worked: 2.81
Short description of error
This is a heavy issue for me, because I'm using the compositing every day and must go back to v 2.81 because of this one.
It's impossible to set a second fac keyframe for all nodes, where fac is implemented.
Exact steps for others to reproduce the error
Attached an example scene.
Open it and try to change the fac value for the mixer node.
blender_compositing_bug01.blend
Added subscriber: @ChristophWerner
#73991 was marked as duplicate of this issue
Added subscriber: @Blendify
I can confirm
Seems to be related to Image sequences, single images work fine.
Changed status from 'Needs Triage' to: 'Confirmed'
That's right. Forgot to mention it.
A bisect shows that this was caused by
5d36a2e587, which fixed #72143. @brecht would you mind taking a look at this?Added subscriber: @brecht
Added subscriber: @dr.sybren
Added subscriber: @antoniov
Removed subscriber: @antoniov
Added subscriber: @Sigmund_Fraud
I hereby remove Antonio Vazquez as assigned.
Added subscriber: @antoniov
Whoops. I hereby re-assign Brecht as assigned.
Thought that assigning again = removing from assignment, so I "assigned" Antonio again to undo my initial assigning. Darn, El_Fraudo, quite a newbie aren't you :)
@Sigmund_Fraud please leave the task assignment to the developers '-)
Added subscriber: @MD.FahadHassan
Added subscriber: @EAW
Note @ChristophWerner & @MD.FahadHassan : As a non-optimal work around in the meantime, you can keyframe the second frame with the same value, and adjust it to the desired value using the sliders in the dopesheet and the sliders and sidebar in the graph editor. That is if you really want to still use 2.82 or 2.83 before this is fixed.
Thank you. Good workaround, but I stay in 2.81 until the next update.
The problem exists with all fac related nodes in the compositor and this is "uncomfortable" when creating complex node systems.
This issue was referenced by
9070bb122dThis issue was referenced by
f0a22f5dd0Changed status from 'Confirmed' to: 'Resolved'