Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
3

Depends on which scripting languages your web server supports. Main requirements The language should be able to execute the application The language should provide secure access the files on the server or a network The language should provide methods to assembly file paths (e.g. relative to absolute paths) The language should provide interaction methods ...


2

You may want to try to write the output of your task to a file and tell your system to start it as a background task by adding the &: exec('aerender.exe -project myproject.aepx -comp "Final" -mp -output video.mov >/dev/null &') It might also be something in your server setup, the max. memory maybe?


2

I would not recommend trying to output your AE Comp using H.264. Unfortunately, regardless of the settings, you will get less than desirable results (typically terrible). The proven workflow / best practice in terms of output is: Under your Output Module Settings: Render out using Format: Quicktime Format Options Button -> Video Codec: Animation ...


2

Aerender does what it says on the tin: it just renders. It can save a comp after rendering if there's a post-render action like setting proxies, but AFAIK it has no other capability to modify projects (figures, because it is available to put on as many machines as you want, so they don't want to be giving away a program capable of editing .aep files). To ...


1

The most efficient way is to use the command line renderer in multi machine mode. That will mean each machine will render the next un-rendered frame independently. You need to set the output module to a frame sequence, like png sequence, JPEG sequence, etc. and you need to make sure that "skip existing frames" is on. Then in a command prompt, type /path/to/...


1

I have been able to at least 10x render times in AE (depending on hardware) by rendering to image sequences and running multiple instances of AE on one machine. Because AE is so inefficient at using your resources you can get away with this in direct proportion to your hardware. I don't have a good rule of thumb for how many instances to run at a time but ...


1

I would try using a seperate ssd for your project files and assets. You'd have one for your os and software and one for the project.


1

I'm not an economist, but I have built and run a small render farm. I'd make the decision on a ROI basis: will you get back a return from your investment? I can't answer this for you, you'll need to add up all the costs for both options and compare. Costs for a physical render farm are mostly fixed - i.e. the capital outlay, but you have to factor in ...


1

The issue was with Camtasia 8's capture. Converting from the AVI format to a MOV format fixed the issue.


1

I usually export as a ProRes Quicktime movie from After Effects directly, then convert my ProRes file to h264. I keep the ProRes as a master file, and compress the h264 as needed. Also sometimes restarting AE before rendering fixes any slowdowns. If the particles are using large (greater than 200x200 pixel) layers for their textures, this will make things ...


Only top voted, non community-wiki answers of a minimum length are eligible