-
Rendering is for the birds
So I’ve been using Nucleo Pro since the beta version, but for some reason something is going drastically wrong and I don’t know if it is AE, Nucleo, or OS X.
Here’s the deal — I’m outputting sequences. I do this because lately the power grid in our building has been a total piece of garbage, and screwed me twice this week in the middle of renders. (This project is for NAB too…so this is tough)
This is where it gets strange —- if my machine goes down while running nucleo, the frames it was creating become 0k dummy frames that you have to delete, and re-render, or else they’ll be corrupt. Same with AE, but in my case nucleo makes 4 dummy frames if my box goes down. No big deal, I’ve been dealing with this for a while. But, after I go into my sequence folder, clean out my dummy frames, and then set my output to skip existing files, and then I check to make sure that the render picked up from where it left off, ALL OF MY FRAMES ARE GONE AND WE START BACK AT 1. This is only happening if we lose power, not if the machine goes down. (ie AE crashes)
For instance, I left off at around 10k — and I just re-started it after getting a phone call and I’m back to square one.
Anyone? Comments? Suggestions?