- #Saber plugin after effect update#
- #Saber plugin after effect code#
- #Saber plugin after effect windows 7#
You mind sharing the edits you made to the AEsubmitToDeadline scr =ĪttributeError : 'AfterEffectsPlugin' object has no attribute 'ExitInProgress' ()įile "C:\Users\render\AppData\Local\Thinkbox\Deadline10\slave\T7910\plugins\5bec8b98f0d4fd2678963941\AfterEffects.py", line 625, in HandleRenderSuccessĪt (String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)Īt (String taskId, Int32 startFrame, Int32 endFrame)Īt (TaskLogWriter aem)
#Saber plugin after effect update#
Thanks for the quick reply did a quick test render with the update you provided, and I am still getting the same error. YMMV on this one pretty wildly, but at least AE will eventually close when using Sabre. Self.AbortRender("Exiting due to success", AbortRender.Success) Self.LogInfo("Found 'Finished Composition', waiting 30 seconds then exiting") # Edwin: Because Saber locks up AfterEffects, we need to force it to close Then edit “/custom/plugins/AfterEffects/AfterEffects.py” and replace the “HandleRenderSuccess” with what’s below.
#Saber plugin after effect code#
You can test this code by making a copy of the “/plugins/AfterEffects” folder and putting it into “/custom/plugins”. Without that pause, final output frames and video wouldn’t be written out correctly. In that function, I let AE sit for a little while and then close it. We only seem to see that when AE is rendering a frame sequence and not when rendering a QuickTime if I recall correctly. What I did was hijack the “HandleRenderSuccess” call which is run when we see “Finished Composition” in the render log. You can use it at your own risk sort of thing. The gist is that we can hack the Deadline script to forcibly close AE after a timeout, but it was often not that reliable. It’s buggy, but it sort of works if you’re not rendering QuickTimes? Has anyone seen anything similar to this ?Īh, so good news! I was reminded of a hack I implemented for a company.
#Saber plugin after effect windows 7#
The only difference between the 2 machines that I can note is that the troubled node is running windows 7 and the node that renders it fine is a windows 10. There is a incongruity in the output lines and I wonder if that is the cause. 13:45:21: 0: STDOUT: PROGRESS: Total Time Elapsed: 28 Seconds
13:41:53: 0: STDOUT: PROGRESS: Total Time Elapsed: 29 SecondsĪnd here is a snip from a node rendering the same job but can complete it: Here is the end snip of the output from the troublesome node: After doing some digging I discovered when Saber is not present in the comp the issue goes away. It will start and render the quicktime all the way up to 100% but never report that the task is done. One of our nodes refuses to finish a render. Because of the hundreds of files we generate I use Deadline to slave them out. Our graphics package utilizes the Video Copilot effect “Saber”.
0 kommentar(er)
