![]() ![]() 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |