MIX NODE: Doesn't handle associated alpha correctly #47117
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#47117
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?
Mix doesn't correctly mix the results.
Test file attached.
Changed status to: 'Open'
Added subscriber: @troy_s
While I was working on a patch for this, it strikes me that there is a zero percent chance that the "Use second image's alpha" works correctly either.
By default, I'm guessing that if an image has an alpha that the Mix node should use it?
Ok so my other bug report appeared to be correct to the best of my knowledge; the mix node in default "Mix" mode ignores the colour in the node socket if it is unattached.
In addition to this, whilst working on a patch for this node, I noticed that the "Use Alpha of Background" toggle next to the mix mode seems awfully suspect.
If we mix image A with alpha over image B with alpha, shouldn't the default behaviour be to honour both alphas? What would the logical outcome be if that were not the default? To mix and ignore one of the image's alpha? Default to the background image's alpha? Foreground's?
I'm somewhat lost here and seeking guidance as I cannot for the life of me, as an imager, see what a reasonable outcome would be other than honouring the alpha of both images by default.
Thanks for anyone's input.
Added subscriber: @Sergey
Changed status from 'Open' to: 'Archived'
Mix node with the mix blend type does not equal to alpha over. You're just doing blending with the following formula: https://developer.blender.org/diffusion/B/browse/master/source/blender/compositor/operations/COM_MixOperation.cpp;4c37d910deb5a6e202cb9e166755780e5d0c89b1$155
If you want to do alpha over use node with that name.
Thanks for the report, but don't see issues here, it is all working as it was designed to.