Compositing File Cinema 4D R13 – Freeze

[Adam Trachtenberg]

Did you replace the R12 AE plugin with the one that came with R13?

[David Biederbeck]

Are you referring to the ae plugin to be installed my ae folder? The freeze happens at export, not import to ae. if there is another plugin I need to export I am not aware of it

[Adam Trachtenberg]

Ah, sorry. Bad assumption on my part.

Is there any commonality you can determine for when it freezes?

[Osiel Garcia]

Hi,
were you able to solve the problem? Iam going through the same situation at the moment and is driving me insane, any help would be really appreciated, thanks.

[David Biederbeck]

No, I have not. I have talked with Maxon on the phone twice. I uploaded the file to them and they were able to export just fine.

I took the file home and it was able to be exported just fine. So, they said my best bet was a re-install.

So, lets compare and see if there are any similarities.

Problem machine:
8 core Mac Pro
OSX 10.6.8
32Gigs Ram
Programs, startup disk and the export location are all on separate drives. This shouldn’t be a problem, but just in case.
Nvidia video card.

I can’t think of any other variables.

[Osiel Garcia]

Thanks a lot, i will try to re-install it and see what happen.

[Osiel Garcia]

Pretty close to mine:
Mac Pro 8 Core
OSX 10.6.8
16 gb of ram
Start up disk and export location both in separate drives
Default Video Card: ATI Radeon HD 2600 ( could this be the issue?)

Thanks.

[David Biederbeck]

Maybe? It sounds like we both have the stock video card… but then again, so does just about everyone who has that computer and uses Maxon… so, It seems there would be more people complaining. I’m not at work, try exporting to the same drive that your program is running on?

[Osiel Garcia]

You are right, i will give it a try and export to my main HD. Thanks a lot, i will let you know.

[Jared Flynn]

Hi there David,

I’m a little late to the party here but I’ve had the same problem several times in my projects, and I’ve managed a workaround in my situations.

For me, the problem NEVER happens when I’m saving compositing project files of DRAFTS (Standard renderer, no bells or whistles, usually with a resolution of 960×540), but when I go for the final compositing pass (often the Physical renderer, 1920×1080, AO, motion blur, DOF, etc), that’s when Cinema pooches and hangs.

My current specs, for the record:
Lenovo ThinkPad W701 on Windows 7 Professional SP1
1.60GHz Intel Core i7 (quad core / hyperthreaded)
16GB RAM
nVidia Quadro FX 2800M

I’ve found a couple of different techniques have worked around this problem, depending on the scene. Hopefully this will work for everyone!

-If you’re using the Physical Renderer, switch to Standard just to save out your project file. This was the most recent fix for me (today, actually).

-If you’re already using Standard and are still having problems, try disabling several (if not all) of the geometry in your scene. Leave only the components you need active for the project file– things like lights, objects with External Compositing tags applied, cameras, etc– and disable everything else. I find an easy way to facilitate this is to put every object I add an External Compositing tag to in its own layer, so when the time comes I can Solo it.

This doesn’t even begin to explain why this problem could be occurring– certainly not to someone like me with no software engineering experience– but it has brute-forced the export for me with perfect results every time I run into this problem. Tested rigorously using a steady mixture of the scientific method and pure unbridled IT rage. 🙂

Good luck!

Jared Flynn
Motion Graphics Designer / Lead AE
Lone Wolf Documentary Group