| ||||||||||
| On Nov 28, 2017, at 3:37 PM, Greg Balint wrote: > Can anyone comment as to how it splits things up and where those "split projects" go? Are the split projects and renders just temporary, or do they need to remain somewhere? > > Also, am I only limited to the render options in stock ae? Or could I use something like AfterCodecs in tandem with this? Does it render out uncompressed files first and then stitch them together using the final file format? Or does it recompress over an already lossy codec if that's what you choose to output? First of all, you can download and run it for free for 7 days, so give it a shot and many of your questions will be answered. When you "Plant the Seeds", RenderGarden makes folders in your "Seed Bank" for each queued item in your render queue. Inside each of these is typically a copy of your project, which will be used for rendering that job. There is also a subfolder in there to hold the segments of your movies before they are combined into the final version. The Seed Bank is like your other cache folders in that you should feel free to trash its contents when there's no more rendering going on. Or even if there is rendering happening, you can delete anything not being used. If you delete folders that are being used, that will kill the render, which maybe was your intention anyway. You should theoretically be able to render anything through RenderGarden that you could render in the standard render queue, which should include AfterCodecs. If you find anything that has problems, let us know, although those issues are typically either a bug in AE or the plug-in developer, since everything is supposed to be able to be rendered on the command line. BTW, RenderGarden has an option to create an H.264 or ProRes movie as a post-process after the AE output has been completed. Like AfterCodecs, it uses FFmpeg to do this. Unlike AfterCodecs, RenderGarden can do a two-pass H.264 encode. Brendan |
