Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Maxon Cinema 4D CPU vrs GPU – [[ apple M1 ]] using only 32% of all potential [[C4D2023.2]]

  • CPU vrs GPU – [[ apple M1 ]] using only 32% of all potential [[C4D2023.2]]

    Posted by Mauricio Barrientos on September 14, 2023 at 2:16 pm

    Good morning, just a strange question:
    I have a mac studio M1 MAX,
    and I am with the trial of the last C4D 2023.2
    I put the processors to the test, and I realize that ALL THE WORK is done with the CPU and not with the GPU.
    Is there a way to configure in C4D 2023.2
    to take advantage of the potential of the GPUs in Apple’s M1 chip??
    Otherwise I’m only using 32% of the 52 processors that Apple’s MacStudio has.
    I leave here below a photo with green text…..
    Any comment will always be greatly appreciated.

    Mauricio Barrientos replied 2 weeks, 2 days ago 2 Members · 4 Replies
  • 4 Replies
  • George Charoupas

    September 14, 2023 at 6:22 pm

    Hello Mauricio,

    You haven’t provided the most important detail. Which render engine do you use?

    1) If you use the standard render engine, then unfortunatelly you can’t use GPU. The standard render engine is a CPU render engine only.

    2) If you use the physical render engine then you can’t use GPU as well, for the same reason as the CPU.

    3) If you use the redshift render engine, then you should be able to use your gpu cores. Go to Edit->Preferences->Renderer->Redshift and in the Compute Devices you should be able to see your M1 GPU Cores. Now I am not sure if Redshift runs natively on arm processors or if it gets emulated via Rosetta. Also I am not sure if there is a limitation to how many GPU cores the trial version of redshift can utilize.

    I assume that you are using the standard render engine from your provided image (which is the worst by the way), so the 1) applies for you.

  • Mauricio Barrientos

    September 14, 2023 at 7:05 pm

    again thansk …really thanks..

    here the picture of my RENDERER REDSHIFT :

    and i can not see the GPU to render, and YES i use the standar.

    is there a free version to install or add to my cinema 4D on previous version ?

    <b title=”Cinema 4D R25 Hotfix 4 – September 23, 2022″ itemprop=”name”>Cinema 4D R25

    <b title=”Cinema 4D R25 Hotfix 4 – September 23, 2022″ itemprop=”name”>thanks and bless

  • George Charoupas

    September 14, 2023 at 9:21 pm

    The busID:0 is most of the times the GPU and since in M1 the GPU is inside the CPU chip, it should be it. If you want redshift to use both gpu and cpu for rendering you should enable hybrid rendering.
    As for the other things you asked.

    1) Redshift is paid software and there is no free version available.

    2) Earlier Redshift versions might not be compatible with M1 gpus.

    3) The only free GPU render I know (it exists) for Cinema 4D is Centileo. It is in alpha stage and I don’t know how it works and if it supports M1.

    Your 2023 trial version should have redshift that should support your M1, but you need to change your standard render engine to redshift and change all your materials, lighting and cameras into redshift compatible.

  • Mauricio Barrientos

    September 14, 2023 at 10:51 pm

    okay I understand …


    For the moment I will stick with the standard, standard configuration.

    It’s pretty good, in fact, on an imac with an i7 processor it took 4.7 minutes, and in this “MacStudio” it barely took 27 seconds for the same scene.

    but me, I started this question, coz the GPU history on picture, it doesn’t show any GPU usage.

    I will look for a way to take advantage of the 52 processors then.

    Once again thank you very much, very grateful.

    I hope to acquire the new MacStudio M3 when it goes on sale in 2024, an M3 processor that does not yet exist, must be outrageous in power. [96_processors_together] of the latest generation, and although it is the standard rendering, I see that Cinema 4D distributes the rendering to each CORE CPU.

    thank you again.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy