![]() ![]() ![]() Now, the next time you render, you should see improvements. Open the devices file and change everything that says "Enabled=Off" to "Enabled=On.” Once you’ve changed that, save the file and restart your video editing application. Go to (Mac: Macintosh HD>Users>Shared>Digital Anarchy, Windows: Users>Public>Public Documents>Digital Anarchy) and in this folder location you will find either a DA_CUDA_Device.txt, DA_Metal_Devices.txt, DA_OpenCL_Devices.txt file. It shouldn't be THAT much slower, so if you’re experiencing an extreme slow down please email us at ensure your Flicker Free renders are optimized, you need to have your GPU is on/enabled. If you're using a high resolution image sequence it will be slower because Flicker Free is analyzing more pixels than it would for HD footage. You will have to play around with the two settings because even if they are causing FF to be slow, those may be the settings you need to fix your clip. New Flicker Free 2.0 settings: Motion compensation and detect motion can both result in slow performance and longer renders. It then has to analyze all the color information in those frames. If you have Time Radius set to 10, Flicker Free is asking the host app to render 21 frames at once (the current frame, 10 before, 10 after) when processing a single frame. For example, a Time Radius that’s larger will make for a longer render time. Additionally, Flicker Free’s settings can affect render times. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |