VideoCopilot Saber is a free plugin for After Effects that you can use that for create: Energy Beams; Lightsabers; Lasers, Portals; Neon Lights; Electric; Haze &.
I am using an older MacBook Pro OS 10.6.8 and running Adobe After Effects 6.5. I recently went to Video CoPilot's website to download the free light'saber' plug-in for AE. It looks to be an awesome plug-in but unfortunately i am unable to use the software due to my OS limitations at this moment. The present day software needs an Apple OS of 10.7 or newer.Does anyone know how i can get my hands on an older version of the Video CoPilot 'saber' software that i might be able to use on my OS 10.6.8?Any help with this matter is much appreciated.Michael.
Our graphics package utilizes the Video Copilot effect “Saber”. Because of the hundreds of files we generate I use Deadline to slave them out. One of our nodes refuses to finish a render. It will start and render the quicktime all the way up to 100% but never report that the task is done. Hey polymangler,What version of Deadline of are you running (ie.
Have you tried running the command-line job on the errant Slave outside of Deadline? If you look in the log for the job, you’ll see the full command that we’re running which you can then run.
![Saber plugin after effects cc 2019 Saber plugin after effects cc 2019](/uploads/1/2/4/1/124139847/105525655.jpg)
I’d be interested in the results of that test.I’m not familiar with the Saber plugin, but I wonder if there’s an issue with how Saber is notifying AE that it’s done. If it’s reporting that it’s 100% done and there’s an output file created by that task I could see that being a potential cause if the process is just hanging thereAs a temporary solution, if it’s just the one machine that’s causing issues, you can always blacklist that Slave from rendering jobs containing Saber.Cheers. Many of the Video Co-Pilot plugins make an unfortunate reference to the AE UI, which when executed via the headless aerender executable, causes it to crash/hang at entry point or at exit. This seems to be the latter issue. I would report the issue to Video Co-Pilot directly as they need to fix all their plugins to be compliant, regardless of renderfarm manager used:There is also a known AE CC 2018 issue combined with the “Fast Blur (Legacy)” AE effect in a comp. If you using 2018 version and you use this specific AE effect, they all bets are off here as its highly unstable currently and so, the Saber reported issue may be a false-positive here.
(I doubt that is the case here, but I mention it so you can eliminate it if applicable). Hey guys, just back to the office after some well deserved days off so let me run through the responsesMepp: I’m running version 10.0.10.4, I’ve run the same render through the command line and the results were the same. Sadly blacklisting that one machine would not be a good solution since it is our only slave with all plug-ins loaded. Most of our nodes are off-site now, we just keep this guy kicking around for AE render purposeseamsler: That is a real bummer to hear, it a big part of this shows packageMikeOwen: I will let my voice join the chorus over at Video Copilot and see if they have any solutions.Thank you everyone for taking the time to help me with my issue.Cheers.
Ah, so good news! I was reminded of a hack I implemented for a company. It’s buggy, but it sort of works if you’re not rendering QuickTimes?The gist is that we can hack the Deadline script to forcibly close AE after a timeout, but it was often not that reliable.
You can use it at your own risk sort of thing.What I did was hijack the “HandleRenderSuccess” call which is run when we see “Finished Composition” in the render log. We only seem to see that when AE is rendering a frame sequence and not when rendering a QuickTime if I recall correctly. In that function, I let AE sit for a little while and then close it. Without that pause, final output frames and video wouldn’t be written out correctly.You can test this code by making a copy of the “repo/plugins/AfterEffects” folder and putting it into “repo/custom/plugins”. Then edit “repo/custom/plugins/AfterEffects/AfterEffects.py” and replace the “HandleRenderSuccess” with what’s below. Def HandleRenderSuccess( self ):if not self.ExitInProgress:self.RenderSuccess = True# Edwin: Because Saber locks up AfterEffects, we need to force it to closeself.LogInfo('Found 'Finished Composition', waiting 30 seconds then exiting')sleep(30)self.AbortRender('Exiting due to success', AbortRender.Success)YMMV on this one pretty wildly, but at least AE will eventually close when using Sabre. Hello,I have been running into a similar issue as polymangler, where slaves will get stuck “rendering” on comps that contain Saber.
The difference is that I am rendering out a.TGA sequence and not a quicktime movie.I tried hacking the “HandleRenderSuccess” call as eamsler suggested, but that threw errors saying the “ExitInProgress” attribute was not defined.Currently using Deadline 10.0.20.2 Release (12de851eb) and After Effects 15.1.2.Any suggestions would be greatly appreciated. Let me know if there is any more information I can provide.Thanks! Thanks for the quick reply!I did a quick test render with the update you provided, and I am still getting the same error.
I would like to to try this fix.Currently, I edited the AE submitToDeadline script to search effects used in the Comp. If it finds Saber, it enables the auto-timeout. This was not ideal as a new timeout is always recalculated using the latest recalculated timeout.So, to confirm the code above, we do not use self.ExitInProgress and the code is def HandleRenderSuccess( self ):self.RenderSuccess = True# Edwin: Because Saber locks up AfterEffects, we need to force it to closeself.LogInfo('Found 'Finished Composition', waiting 30 seconds then exiting')sleep(30)self.AbortRender('Exiting due to success', AbortRender.Success)thanks!Jason.