Compositor: Continously add/remove for cryptomatte. #97907
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#97907
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?
Source: https://devtalk.blender.org/t/continuous-add-and-remove-for-cryptomatte/24223
PROBLEM
Sometimes when using Cryptomatte the objects to isolate and divide into various passes can be a lot, and the process becomes tedious because you can only Add or Remove one object per time, then go back to the Cryptomatte node and click the + or - icon again, slowing a lot the process. Instead, it would be way more handy being able to select multiple specific objects.
SOLUTION
Have Add and Remove to work with multiple clicks, and then press Esc to go out of the selection mode when needed.
NOTE: although categorized as good first issue, it might require more changes than expected as UI code is shared with color picker. Of course the color picker workflow should not change.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @Jeroen-Bakker
Added subscriber: @Slowwkidd
Added subscriber: @AlexeyAdamitsky
Added subscriber: @Max-49
Added subscribers: @pablovazquez, @JulianEisel
@pablovazquez and I looked at the design of this today. Here are the points we agreed on (already checked with Jeroen, who seemed to agree too).
Also, additional changes we could/should do:
Now, implementation wise this may make things a bit more difficult. The cryptomatte eyedropper would have to be split off from the normal color eyedropper. IMHO this should be done either way. Then the cryptomatte eyedropper can have its own modal keymap, e.g. see
eyedropper_colorband_modal_keymap()
. So there will be more work involved, but I think this can still be done by a new developer, if that person can follow C code well enough.To ease the development we could split this task into two.
This would keep the changes smaller and would be easier to handle.
Added subscriber: @big-nacho
Hey, new to blender devs here and was hoping to make this my first issue. Not sure about how to proceed regarding splitting tasks or claiming them. Any help on that and any other formalities is welcome :)
Hello, can we hope for gathering interest again in this QoL improvement?