Compositor: Alternate sharpen kernel for filter node. #95275

Closed
opened 2022-01-28 08:14:17 +01:00 by Jeroen Bakker · 15 comments
Member

Add a new kernel to the filter node.

Api name of the kernel is: "SHARPEN_DIAMOND"
Display name: "Diamond". The description could mention that this is a softer version of sharpen.

Kernel should look like

0  -1  0
-1  5 -1
0  -1  0

See COM_FilterNode and def_cmp_filter

Original request: https://blender.community/c/rightclickselect/57Kq

Add a new kernel to the filter node. Api name of the kernel is: "SHARPEN_DIAMOND" Display name: "Diamond". The description could mention that this is a softer version of sharpen. Kernel should look like ``` 0 -1 0 -1 5 -1 0 -1 0 ``` See `COM_FilterNode` and `def_cmp_filter` Original request: https://blender.community/c/rightclickselect/57Kq
Author
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Author
Member

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

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

Added subscriber: @cmbasnett

Added subscriber: @cmbasnett
Author
Member

Hi colin saw you were working on this task. If so please assign yourself to it.

Btw I would just add the new kernel to the kernel list. Adding a new option would add some complexity and confusion.

There are ways to display the items in the list as subitems.

Hi colin saw you were working on this task. If so please assign yourself to it. Btw I would just add the new kernel to the kernel list. Adding a new option would add some complexity and confusion. There are ways to display the items in the list as subitems.
Colin Basnett self-assigned this 2022-01-29 23:49:59 +01:00
Member

Sounds good. The question then becomes what to name these things. Photoshop has two filters "Sharpen" and "Sharpen More". Perhaps the existing sharpen kernel could be renamed to "Sharpen More" and the new one be named "Sharpen"? Inversely, we could leave the existing Sharpen as-is and call the new one "Sharpen Less".

Sounds good. The question then becomes what to name these things. Photoshop has two filters "Sharpen" and "Sharpen More". Perhaps the existing sharpen kernel could be renamed to "Sharpen More" and the new one be named "Sharpen"? Inversely, we could leave the existing Sharpen as-is and call the new one "Sharpen Less".
Member

I've implemented this in the simpler way described, simply as another option in the kernel list.

I've named it "Sharpen Less" in the interface, since "Diamond" seemed needlessly opaque. In my opinion, calling it "Sharpen Less" gets the functionality across to the user more directly without needing a mouse-over description.

I will post up a PR over the weekend!

image.png

I've implemented this in the simpler way described, simply as another option in the kernel list. I've named it "Sharpen Less" in the interface, since "Diamond" seemed needlessly opaque. In my opinion, calling it "Sharpen Less" gets the functionality across to the user more directly without needing a mouse-over description. I will post up a PR over the weekend! ![image.png](https://archive.blender.org/developer/F12845385/image.png)
Contributor

Added subscriber: @Rawalanche

Added subscriber: @Rawalanche
Contributor

I'd suggest perhaps adding also Sharpen Even Less, Sharpen Slightly More and Sharpen More filters.

No, seriously. Shouldn't this go through some UX sanity check filter before being committed? It's quite obvious that if there's a need for "Sharpen Less" mode, what's really needed is a Sharpen filter with some sort of amount slider/multiplier, like in pretty much any other common sense software out there. The idea of user having a choice between two "Sharpen" and "Sharpen Less" modes, expecting that one or the other will be the exact amount of sharpening they desire is just wrong.

In other words, the sharpening matrix should be parametric, instead of having two hardcoded options.

I'd suggest perhaps adding also Sharpen Even Less, Sharpen Slightly More and Sharpen More filters. No, seriously. Shouldn't this go through some UX sanity check filter before being committed? It's quite obvious that if there's a need for "Sharpen Less" mode, what's really needed is a Sharpen filter with some sort of amount slider/multiplier, like in pretty much any other common sense software out there. The idea of user having a choice between two "Sharpen" and "Sharpen Less" modes, expecting that one or the other will be the exact amount of sharpening they desire is just wrong. In other words, the sharpening matrix should be parametric, instead of having two hardcoded options.
Contributor

Added subscriber: @MysteryPancake

Added subscriber: @MysteryPancake
Contributor

In #95275#1304556, @Rawalanche wrote:
I'd suggest perhaps adding also Sharpen Even Less, Sharpen Slightly More and Sharpen More filters.

No, seriously. Shouldn't this go through some UX sanity check filter before being committed? It's quite obvious that if there's a need for "Sharpen Less" mode, what's really needed is a Sharpen filter with some sort of amount slider/multiplier, like in pretty much any other common sense software out there. The idea of user having a choice between two "Sharpen" and "Sharpen Less" modes, expecting that one or the other will be the exact amount of sharpening they desire is just wrong.

In other words, the sharpening matrix should be parametric, instead of having two hardcoded options.

The Filter node has a "factor" slider for this purpose (it can go above 1 when the text is edited). I believe the idea with this kernel was to provide a different shaped kernel, a diamond shape rather than a box shape.

It is currently named "Box Sharpen" and "Diamond Sharpen" in the UI for this reason.

image.png

> In #95275#1304556, @Rawalanche wrote: > I'd suggest perhaps adding also Sharpen Even Less, Sharpen Slightly More and Sharpen More filters. > > No, seriously. Shouldn't this go through some UX sanity check filter before being committed? It's quite obvious that if there's a need for "Sharpen Less" mode, what's really needed is a Sharpen filter with some sort of amount slider/multiplier, like in pretty much any other common sense software out there. The idea of user having a choice between two "Sharpen" and "Sharpen Less" modes, expecting that one or the other will be the exact amount of sharpening they desire is just wrong. > > In other words, the sharpening matrix should be parametric, instead of having two hardcoded options. The Filter node has a "factor" slider for this purpose (it can go above 1 when the text is edited). I believe the idea with this kernel was to provide a different shaped kernel, a diamond shape rather than a box shape. It is currently named "Box Sharpen" and "Diamond Sharpen" in the UI for this reason. ![image.png](https://archive.blender.org/developer/F12857199/image.png)
Contributor

In #95275#1304613, @MysteryPancake wrote:

In #95275#1304556, @Rawalanche wrote:
I'd suggest perhaps adding also Sharpen Even Less, Sharpen Slightly More and Sharpen More filters.

No, seriously. Shouldn't this go through some UX sanity check filter before being committed? It's quite obvious that if there's a need for "Sharpen Less" mode, what's really needed is a Sharpen filter with some sort of amount slider/multiplier, like in pretty much any other common sense software out there. The idea of user having a choice between two "Sharpen" and "Sharpen Less" modes, expecting that one or the other will be the exact amount of sharpening they desire is just wrong.

In other words, the sharpening matrix should be parametric, instead of having two hardcoded options.

The Filter node has a "factor" slider for this purpose (it can go above 1 when the text is edited). I believe the idea with this kernel was to provide a different shaped kernel, a diamond shape rather than a box shape.

It is currently named "Box Sharpen" and "Diamond Sharpen" in the UI for this reason.

image.png

Ah, nevermind then. From the original picture as well as the request it was not obvious it has factor, and the "Sharpen Less" name did not really help.

> In #95275#1304613, @MysteryPancake wrote: >> In #95275#1304556, @Rawalanche wrote: >> I'd suggest perhaps adding also Sharpen Even Less, Sharpen Slightly More and Sharpen More filters. >> >> No, seriously. Shouldn't this go through some UX sanity check filter before being committed? It's quite obvious that if there's a need for "Sharpen Less" mode, what's really needed is a Sharpen filter with some sort of amount slider/multiplier, like in pretty much any other common sense software out there. The idea of user having a choice between two "Sharpen" and "Sharpen Less" modes, expecting that one or the other will be the exact amount of sharpening they desire is just wrong. >> >> In other words, the sharpening matrix should be parametric, instead of having two hardcoded options. > > The Filter node has a "factor" slider for this purpose (it can go above 1 when the text is edited). I believe the idea with this kernel was to provide a different shaped kernel, a diamond shape rather than a box shape. > > It is currently named "Box Sharpen" and "Diamond Sharpen" in the UI for this reason. > > ![image.png](https://archive.blender.org/developer/F12857199/image.png) Ah, nevermind then. From the original picture as well as the request it was not obvious it has factor, and the "Sharpen Less" name did not really help.
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Member

As this has been implemented, I’ll close this task.

As this has been implemented, I’ll close this task.

Sorry to ressurect this but shouldn't the filter node have a size (in px) UI element? Or the possibility to submit your own filter kernel...
Something like in photoshop with size, amount (and threshold)?

Sorry to ressurect this but shouldn't the filter node have a size (in px) UI element? Or the possibility to submit your own filter kernel... Something like in photoshop with size, amount (and threshold)?
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
6 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#95275
No description provided.