blender
/
blender
132
398
Fork 577
Code Issues 6.2k Pull Requests 749 Projects 19 Wiki Activity

Cycles: Added UI to force OIDN to use the CPU #117734

Closed
Stefan Werner wants to merge 2 commits from Stefan_Werner/blender:oidn_gpu_ui into main
pull from: Stefan_Werner/blender:oidn_gpu_ui
merge into: blender:main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Conversation 5 Commits 2 Files Changed 4 +22 -1
Stefan Werner commented 2024-02-01 19:58:04 +01:00
Member
Copy Link

There is now an option in the rendering device selection where the user can explicitly disable OIDN GPU support.

There is now an option in the rendering device selection where the user can explicitly disable OIDN GPU support.
Stefan Werner added 1 commit 2024-02-01 19:58:16 +01:00
59ae7ca175 Cycles: Added UI to force OIDN to use the CPU 
There is now an option in the rendering device selection
where the user can explicitly disable OIDN GPU support.
Stefan Werner requested review from Brecht Van Lommel 2024-02-04 21:59:08 +01:00
Brecht Van Lommel requested changes 2024-02-05 11:23:52 +01:00
intern/cycles/blender/addon/properties.py Outdated
@ -1486,1 +1486,4 @@
use_oidngpu: BoolProperty(
name="OIDN on GPU",
description="",
Brecht Van Lommel commented 2024-02-05 11:23:34 +01:00
Owner
Copy Link

This needs a better name and description, like:

Denoise on GPU
Perform denoising on GPU devices. This is significantly faster than on CPU, but requires additional GPU memory. When large scenes need more GPU memory, this option can be disabled.

Maybe for CUDA/OptiX the name could be dynamically to OpenImageDenoise on GPU since there the meaning is ambiguous.

This needs a better name and description, like: > Denoise on GPU > Perform denoising on GPU devices. This is significantly faster than on CPU, but requires additional GPU memory. When large scenes need more GPU memory, this option can be disabled. Maybe for CUDA/OptiX the name could be dynamically to `OpenImageDenoise on GPU` since there the meaning is ambiguous.
Nikita Sirgienko commented 2024-02-05 16:55:54 +01:00
Member
Copy Link

What about something like this?

name="Allow OIDN on GPU"
description="Allow OpenImageDenoise be executed on GPU, if available and can be used, or only on CPU otherwise"
What about something like this? ``` name="Allow OIDN on GPU" description="Allow OpenImageDenoise be executed on GPU, if available and can be used, or only on CPU otherwise" ```
Brecht Van Lommel commented 2024-02-05 17:30:19 +01:00
Owner
Copy Link

In general we should not use abbreviations like "OIDN" for users. And I prefer to avoid the word "Allow", but mentioning if available in the description is fine.

For the description I think it's also good to have an explanation about why a user might disable it, as I did in mine.

In general we should not use abbreviations like "OIDN" for users. And I prefer to avoid the word "Allow", but mentioning if available in the description is fine. For the description I think it's also good to have an explanation about why a user might disable it, as I did in mine.
Nikita Sirgienko commented 2024-02-05 16:45:07 +01:00
Member
Copy Link

@Stefan_Werner , @brecht , Considering OIDN 2.2 update and OIDN overall support of GPU denoising on multiple vendors - shouldn't we move use_oidngpu option outside the oneAPI panel?

@Stefan_Werner , @brecht , Considering [OIDN 2.2 update](https://projects.blender.org/blender/blender/pulls/117752) and OIDN overall support of GPU denoising on multiple vendors - shouldn't we move `use_oidngpu` option outside the oneAPI panel?
Brecht Van Lommel commented 2024-02-05 17:31:10 +01:00
Owner
Copy Link

@Stefan_Werner , @brecht , Considering OIDN 2.2 update and OIDN overall support of GPU denoising on multiple vendors - shouldn't we move use_oidngpu option outside the oneAPI panel?

From reading the code, I don't think it's specific to oneAPI?

> @Stefan_Werner , @brecht , Considering [OIDN 2.2 update](https://projects.blender.org/blender/blender/pulls/117752) and OIDN overall support of GPU denoising on multiple vendors - shouldn't we move `use_oidngpu` option outside the oneAPI panel? From reading the code, I don't think it's specific to oneAPI?
Nikita Sirgienko commented 2024-02-05 18:02:39 +01:00
Member
Copy Link

@Stefan_Werner , @brecht , Considering OIDN 2.2 update and OIDN overall support of GPU denoising on multiple vendors - shouldn't we move use_oidngpu option outside the oneAPI panel?

From reading the code, I don't think it's specific to oneAPI?

Right, sorry, my apologies for the confusion - I was mistaken due to the differences in the Cycle Settings GUI, where some checkboxes are grayed out when not available (like "Embree on GPU" and "HIP RT"), while others are hidden entirely (like Stefan's OIDN checkbox and "Metal RT" checkbox).
Maybe it worth to address this issue (in a separate PR, of course) by ensuring that all settings checkboxes are hidden when they are not available, I will take a look then.

> > @Stefan_Werner , @brecht , Considering [OIDN 2.2 update](https://projects.blender.org/blender/blender/pulls/117752) and OIDN overall support of GPU denoising on multiple vendors - shouldn't we move `use_oidngpu` option outside the oneAPI panel? > > From reading the code, I don't think it's specific to oneAPI? Right, sorry, my apologies for the confusion - I was mistaken due to the differences in the Cycle Settings GUI, where some checkboxes are grayed out when not available (like "Embree on GPU" and "HIP RT"), while others are hidden entirely (like Stefan's OIDN checkbox and "Metal RT" checkbox). Maybe it worth to address this issue (in a separate PR, of course) by ensuring that all settings checkboxes are hidden when they are not available, I will take a look then.
Brecht Van Lommel commented 2024-02-06 13:47:17 +01:00
Owner
Copy Link

With #117874, I prefer actually only having that per scene option and nothing in the preferences. To me this choice depends more on scene complexity than specific devices not being suitable for GPU denoising.

With #117874, I prefer actually only having that per scene option and nothing in the preferences. To me this choice depends more on scene complexity than specific devices not being suitable for GPU denoising.
Stefan Werner added 1 commit 2024-02-06 14:07:25 +01:00
Alaska commented 2024-03-10 02:29:16 +01:00
Member
Copy Link

This is now handled by a different commit. I will close this pull request.

This is now handled by a different commit. I will close this pull request.
Alaska closed this pull request 2024-03-10 02:29:18 +01:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Brecht Van Lommel
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 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#117734
No description provided.
Delete Branch "Stefan_Werner/blender:oidn_gpu_ui"

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?