If you find your test animation is too large, then you’ll need to use a codec that compresses the output. You’ll probably want to reduce the file size afterward using something like ffmpeg (see this vCRASH Academy Blog post) or Camtasia. If you can afford the disk space, and you’re not close to the 2 GB output file size, then rendering in full frames is going to be your best option. The avi file size will depend only on your screen size and length (number of frames), so don’t worry about sumpersamples yet. The best way to see if you’re going to run into the 2 GB file size issue is to do a test animation in “current” mode, which will finish much faster than direct light or skylight. Above 2 GB, most video players will not play avi files or will play them with errors. Ideally, you should render all animations in “Full Frames” mode, but often this is impractical due to (1) the output file size which often must be compressed using ffmpeg or some other application, and (2) the often-quoted file size limitation of avi files of 2 GB. In this post we'll review the pros and cons of a few choices. Choosing which codec to use when creating your Virtual CRASH animation can be an important decision.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |