Don't see the answer you need? Contact us with this Request Form.
PLEASE report any issues you run into to email@example.com.
You may use your 1 license on your desktop and your personal laptop. However you cannot run the software on two machines simultaneously as the two will conflict.
We certainly understand budgets and we do offer volume discounts. For more information, please email firstname.lastname@example.org.
Beachballing most commonly happens whenever FCP starts a render that is using Flicker Free 2.0, so if you have background render set to on, it will start a render anytime FCP recognizes changes to Flicker Free or to the project timeline. Turn off background render and the constant beachballing will go away.
Flicker Free 2.0 now uses your GPU. Renders will be much faster than they were with Flicker Free 1.0.
There are multiple factors that can increase or decrease your render times. Those factors are the length of your footage, the resolution of the footage, your computer’s hardware, which video application you are using and if you are running renders using CPU or GPU.
Additionally, Flicker Free’s settings can affect render times. For example, a Time Radius that’s larger will make for a longer render time. 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. It then has to analyze all the color information in those frames.
New Flicker Free 2.0 settings: Motion compensation and detect motion can both result in slow performance and longer renders. 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.
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. It shouldn't be THAT much slower, so if you’re experiencing an extreme slow down please email us at email@example.com
To ensure your Flicker Free renders are optimized, you need to have your GPU is on/enabled. 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. 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. Now, the next time you render, you should see improvements.
If you are using Premiere, AME, or After Effects, you will also need to make sure you set your mercury renderer correctly for optimization. Set the mercury renderer in these applications to OpenCL, Metal, or CUDA. Not all of these options will be available. The options you will see are based on the graphics card you have in your computer.
Make sure that Background Rendering and Timeline Scrubbing are turned OFF.
With Flicker Free 2.0 being GPU accelerated now, if Flicker Free behaves really slow still, it is likely that you are still using your CPU instead of your GPU for rendering. (see How long are render times?)
Keep in mind that Flicker Free is requesting a lot of frames from the host app.
Again, Flicker Free is requesting a lot of frames from the host. If you have Time Radius set to 10, Flicker Free is asking the host app to render 21 frames at once.
You should apply Flicker Free BEFORE applying other effects. If you apply it afterwards, the host app or graphics card may run out of memory trying to render all those frames and won’t render. In which case, you’ll get a render error, black frames, or some other odd behavior.
If you are getting black frames without other effects involved, this may be a CPU render issue that affects playback. Make sure that the effect is using GPU and not CPU. To see if it is only affecting playback, you can test it by exporting the clip and check if the black frames appear on the export. If you are still running into the issue, contact firstname.lastname@example.org.
The current release has support for After Effects, Premiere Pro, Final Cut Pro, Avid, Davinci Resolve.
The crosshatch lines that appear are the demo watermark. The plugin is fully functional and you should easily be able to see how effective Flicker Free is. However, you'll need to purchase it to permanently remove the watermark.
If you have purchased and activated Flicker Free but still see the watermark, it is due to a cached render issue from the demo and changing the Threshold in the Flicker Free settings will re-render the effect and remove the lines. If this does not solve the problem please email us at email@example.com.
Shading: This is probably the most common problem. FF is trying to blend multiple frames. If there are high contrast areas and the camera moves fast, you may see the lighter areas affected by the darker areas. Causing something that looks like a shadow or shading.
For low contrast areas, Shading can also happen, but it looks more like a blur. For example, if someone moves their head very quickly, you may see some softness in areas like the eyes.
Ghosting: This is kind of rare but happens when you’ve got fast moving objects. Again, it’s more of an issue with high contrast areas of the scene (e.g. a bright tennis ball moving across a black background). The object will appear in a frame with ‘ghosts’ or ‘echoes’ of itself at the positions it was at in prior frames. Reducing the Time Radius can help with this. Also try adjusting the Threshold to a lower value.
If you have other filters applied to your clip, it's best to apply Flicker Free as the first effect in the effect chain.
Often, the render can be dramatically increased when video effects are applied to a clip before Flicker Free does its flicker correction. The host app and type of filter will change the degree to which the render time will be increased. You can avoid this altogether by making sure Flicker Free is applied in your effect chain before any other filters that might change the way your footage appears.
Sometimes you may find it best to do an export of the clip that needs to use Flicker Free first and then reimport the correct clip back into the timeline. Then, you can apply the video effects onto the corrected clip and won’t have to worry about other effects conflicting with Flicker Free and running into potential errors.
Davinci Resolve relies heavily on using your GPU for its renders. With slower video cards, because Flicker Free’s algorithm analyzes multiple 4K resolution frames at once this can quickly become too heavy a load for the graphics card.
If you intend to use 4K footage in your renders we suggest trying the demo first to ensure your GPU is compatible. Please also see Resolve recommendations for GPU.
We have mainly been seeing this happen to users that have any Radeon Pro 5XX series or Radeon RX Vega 64 graphics card. Make sure you are on the most up to date version of FCP and Flicker Free and if the red screen doesn’t go away, contact firstname.lastname@example.org.