Hi all
We are getting red crosses in our render frames from some of our blades and it appears to be related to trapcode licensing. We have installed the trapcode render only license nodes on each blade and submitted the job through the original full license number but some of the blades complain that other blades are using the same serial number. There are 5 render only nodes with each license and we are using 4 blades.
Some of the blades are working fine but we cant identify any particular reason why the others fail other than the trapcode licensing issue.
The job was submitted to run 5 concurrent tasks. I found this post which sounds similar trapcode.com/forum/post/1063522 but there is no response. Any help would be greatly appreciated.
Thanks
IIRC, by using 4 blades and 5 concurrent tasks, you effectively at peak load, were trying to pull 20 trap code licenses, which of course would lead to red-cross frames.
I never had time to fully debug this issue when we had similar issues, so we just rendered out locally on fast machines, as the Trapcode elements were small and render out really fast with Trapcode anyway.
With regard, the forum thread you supplied, it’s totally possible to customise the existing AfterEffects.py plugin file to react differently to certain STDOUT warnings/errors printed out from AE, using RegEx’s. As long as something unique is printed out by AE to identify this issue, then a workaround should be possible.
Does your AE job render logs show anything to identify the Trapcode failure? Can you post it here?
Mike
problem solved. trapcode suite 11 issue. resolved with trapcode. stand down!