Author Topic: Denoising Issues of Intel CPUs in Corona 13/14 on macOS and Inquiry About Fix  (Read 2507 times)

2025-08-18, 15:50:26

CR_love

  • Active Users
  • **
  • Posts: 9
    • View Profile
On macOS systems, neither Corona 13 nor 14’s denoising mode supports Intel CPUs. Moreover, the noise reduction quality and speed of Corona’s High Quality mode are inferior to those when using Intel CPUs, with anomalies at edge details being particularly noticeable. Could you please let us know when the denoising issue for Intel CPUs will be fixed?

« Last Edit: 2025-08-18, 16:35:10 by CR_love »

2025-08-19, 16:36:25
Reply #1

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13834
  • Marcin
    • View Profile
The CPU version of the Intel AI denoiser should work on Mac OS regardless of CPU model. Can you explain what exactly you mean by "neither Corona 13 nor 14’s denoising mode supports Intel CPUs"? Are you getting some error message? Or perhaps the denoiser doesn't work at all?

Regarding the Corona HQ denoiser, what you see is not an issue specific to Intel or other CPU models. It's just how this denoiser works. It's inferior to the AI denoisers - I wouldn't recommend using it.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2025-08-20, 08:56:24
Reply #2

CR_love

  • Active Users
  • **
  • Posts: 9
    • View Profile
The CPU version of the Intel AI denoiser should work on Mac OS regardless of CPU model. Can you explain what exactly you mean by "neither Corona 13 nor 14’s denoising mode supports Intel CPUs"? Are you getting some error message? Or perhaps the denoiser doesn't work at all?

Regarding the Corona HQ denoiser, what you see is not an issue specific to Intel or other CPU models. It's just how this denoiser works. It's inferior to the AI denoisers - I wouldn't recommend using it.

Yes, when selecting the Intel denoiser, there's absolutely no response at all.

2025-08-20, 09:08:24
Reply #3

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13834
  • Marcin
    • View Profile
For interactive or production rendering?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2025-08-20, 10:32:15
Reply #4

CR_love

  • Active Users
  • **
  • Posts: 9
    • View Profile
For interactive or production rendering?

Hi Maru,
The problem occurs during production rendering. The Intel denoiser works as expected on Windows (with the same Intel CPU), but on macOS, selecting the Intel denoiser doesn't work at all.
« Last Edit: 2025-08-20, 10:47:30 by CR_love »

2025-08-20, 10:47:16
Reply #5

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 13834
  • Marcin
    • View Profile
And once you stop rendering, the Intel denoiser effect isn't applied either? (sorry, just making sure that I understand this right)
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2025-08-20, 10:49:02
Reply #6

CR_love

  • Active Users
  • **
  • Posts: 9
    • View Profile
And once you stop rendering, the Intel denoiser effect isn't applied either? (sorry, just making sure that I understand this right)

Yes, that's right.

2025-08-20, 11:04:42
Reply #7

CR_love

  • Active Users
  • **
  • Posts: 9
    • View Profile
And once you stop rendering, the Intel denoiser effect isn't applied either? (sorry, just making sure that I understand this right)

Hi Maru,
Previously, someone encountered the same issue as me.

https://forum.corona-renderer.com/index.php?topic=41502.0

2025-08-25, 18:52:43
Reply #8

Avi

  • Corona Team
  • Active Users
  • ****
  • Posts: 837
    • View Profile
Just a quick update on this: We are checking this internally. Will update you as I find more info about this.
Arpit Pandey | chaos-corona.com
3D Support Specialist - Corona | contact us

2025-08-27, 15:36:08
Reply #9

Avi

  • Corona Team
  • Active Users
  • ****
  • Posts: 837
    • View Profile
I was able to repro this and have reported it internally for our devs to investigate and fix.

(Report ID=CC4D-1135)
Arpit Pandey | chaos-corona.com
3D Support Specialist - Corona | contact us

2025-08-28, 07:24:33
Reply #10

CR_love

  • Active Users
  • **
  • Posts: 9
    • View Profile
I was able to repro this and have reported it internally for our devs to investigate and fix.

(Report ID=CC4D-1135)

Thank you. Hope this can be fixed in the upcoming preview builds.

Today at 02:17:04
Reply #11

Anto3d

  • Active Users
  • **
  • Posts: 23
    • View Profile

Today at 08:04:36
Reply #12

Anto3d

  • Active Users
  • **
  • Posts: 23
    • View Profile
Intel's denoise doesn't work either in the preview or in the final production phase. When cinema4d closes, if corona is installed, the software returns an error.

Today at 09:34:01
Reply #13

Anto3d

  • Active Users
  • **
  • Posts: 23
    • View Profile
This error occurs at the close of cinema 4D even with the official version. Intel's Denise does not work and at the closure of cinema 4D also returns this error:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Cinema 4D [2209]
Path:                  /Applications/Maxon Cinema 4D 2025/Cinema 4D.app/Contents/MacOS/Cinema 4D
Identifier:            net.maxon.cinema4d
Version:               2025.3 (2bba821e6ecca31cd6e668915f472ddaea5f47d5)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2025-09-09 09:31:42.3955 +0200
OS Version:            macOS 15.6.1 (24G90)
Report Version:        12
Anonymous UUID:        E1AE3F18-207D-DA55-756B-CBA54B0D168D

Sleep/Wake UUID:       61185E56-7A8C-4198-85C8-6A6542117010

Time Awake Since Boot: 4600 seconds
Time Since Wake:       1548 seconds

System Integrity Protection: enabled

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   Cinema 4D [2209]

Application Specific Information:
abort() called