31
[C4D] General Discussion / Re: CRITICAL SPEED ISSUE WITH APPLE M SYSTEMS
« on: 2024-01-15, 18:53:24 »
@PhilW That's a great suggestion. Turns out the three materials did use C4D Bitmaps. I swapped them with Corona Bitmaps and it rendered :05 sec. slower, so that's nice. There are also Normal maps, but they already use Corona's Normal Map nodes.
@frv Yes, I too have always known that C4D would reliable scale depending on the cores. This iMac Pro has 18 and I just saw my M2 Max has 12 cores (8 performance and 4 efficiency). I would fully expect the new tech in these chips would easily make up the difference in cores, if not surpass it.
As I mention earlier, this Mac Studio wasn't spec-ed out specifically for this purpose, but I expected more. I made a graphic showing my four test just for giggles. Not sure if that info sheds any light on this issue. Since the C4D Grapes test shows a modest 21% speed increase, seems like this is a Corona-related issue. I use After Effects every day and the few jobs I've done on this Mac Studio have blown me away with how smooth, responsive and fast AE was. I did a bunch of tracking and used the new Rotobrush 3.o and it crushed it. Sigh.
@frv Yes, I too have always known that C4D would reliable scale depending on the cores. This iMac Pro has 18 and I just saw my M2 Max has 12 cores (8 performance and 4 efficiency). I would fully expect the new tech in these chips would easily make up the difference in cores, if not surpass it.
As I mention earlier, this Mac Studio wasn't spec-ed out specifically for this purpose, but I expected more. I made a graphic showing my four test just for giggles. Not sure if that info sheds any light on this issue. Since the C4D Grapes test shows a modest 21% speed increase, seems like this is a Corona-related issue. I use After Effects every day and the few jobs I've done on this Mac Studio have blown me away with how smooth, responsive and fast AE was. I did a bunch of tracking and used the new Rotobrush 3.o and it crushed it. Sigh.