Compositor: Add Scene Time node #94603

Closed
opened 2022-01-03 15:22:22 +01:00 by Jeroen Bakker · 14 comments
Member

Implement a Scene Time node similar to the one of geometry nodes.

image.png

Implement a Scene Time node similar to the one of geometry nodes. ![image.png](https://archive.blender.org/developer/F12786796/image.png)
Author
Member

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

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

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker

Added subscriber: @GeorgiaPacific

Added subscriber: @GeorgiaPacific

Added subscriber: @super_jo_nathan

Added subscriber: @super_jo_nathan

I would like to start contributing to Blender and this seems like a great place to start. If I have any questions I'll be sure to let you guys know!

I would like to start contributing to Blender and this seems like a great place to start. If I have any questions I'll be sure to let you guys know!
Author
Member

Great!

Great!

I've done some looking around and I've been able to build blender and I've found where I should be working in. But I've also found the time node already available in the compositor. If I add the scene time node there will be two very similar nodes. Should the functionality of the scene time node be added into the already existing time node? Because I'm afraid that two similar nodes might cause confusion.

I've done some looking around and I've been able to build blender and I've found where I should be working in. But I've also found the time node already available in the compositor. If I add the scene time node there will be two very similar nodes. Should the functionality of the scene time node be added into the already existing time node? Because I'm afraid that two similar nodes might cause confusion.

Managed to get it working as a separate node, will check my code and make a commit tomorrow if that's the route we're going with.

Managed to get it working as a separate node, will check my code and make a commit tomorrow if that's the route we're going with.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

The current time node should be renamed to the "time curve" node and its purpose is to create custom transitions between any set of frames.

So in some sense its not needed if you use keyframes but it is also nice to create simple transitions without needing the animation editors.

The current time node should be renamed to the "time curve" node and its purpose is to create custom transitions between any set of frames. So in some sense its not needed if you use keyframes but it is also nice to create simple transitions without needing the animation editors.

Sounds like a good idea to me, should this change be made in a new diff or added to the one already up? And should everything in the code base be renamed (class names etc) or just the ui related elements?

Sounds like a good idea to me, should this change be made in a new diff or added to the one already up? And should everything in the code base be renamed (class names etc) or just the ui related elements?
Author
Member

@super_jo_nathan Thanks for your work. Any changes should be done inside the same patch.

@super_jo_nathan Thanks for your work. Any changes should be done inside the same patch.

This issue was referenced by b2ccd8546c

This issue was referenced by b2ccd8546c7249a5ce279210d45ddbb5e90cd10d
Author
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Jeroen Bakker self-assigned this 2022-01-12 12:30:06 +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
5 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#94603
No description provided.