Frequent questions for the Flicker Free Plugin

Don't see the answer you need? Contact us with this Request Form.

PLEASE report any issues you run into to

If I buy a plugin license, will I be able to use the plugin on more than one computer?

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.

Do you offer any discounts if I buy 2 or more of your products?

We certainly understand budgets and we do offer volume discounts. For more information, please email

Flicker Free is REALLY slow in FCP X

Make sure that Background Rendering and Timeline Scrubbing are turned OFF.

Keep in mind that Flicker Free is requesting a lot of frames from the host app.

For instance, 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.

Especially with 4K or larger, it can take a minute or two to render a frame. If background rendering is on or scrubbing is active, FCP will start trying to request all those frames for multiple frames at once. This can bring FCP to a crawl or even crash it. Move to a point on the timeline, let it render, then make adjustments. Clicking around the timeline without letting the current frame render will just slow things down even more.

Dropping the 4K sequence into a 1080p timeline doesn't make a difference in render speed. It still has to access the 4K source file. However, rendering a 4K file out to a 1080p file and then re-importing it WILL make a difference. Now FCP will just be dealing with HD frames and it makes a huge difference. If you're final delivery is to 1080p or 720p, considering rendering out an intermediary file at that resolution. It'll work much faster.
Read more

Black Frames or Render Errors

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.

Read more

What host applications are supported by Flicker Free?

The current release has support for After Effects, Premiere Pro, Final Cut Pro, Assimilate Scratch, Avid, Davinci Resolve, Sony Vegas, and NUKE.

Why do lines appear across my images?

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.

I’m seeing blurring, ghosting, or 'shadows' in my Flicker Free render.

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.

Reducing the Time Radius will help significantly, as the main problem is that FF is trying to blend too many frames that vary a lot. Also, try adjusting the Threshold to a lower value. That’s really all you can do. Of course, it may not be that big of a deal. Play it back in real time and see how it looks. Frequently the problem is only noticeable when you turn Flicker Free on and off in the host application since you’re looking for a difference. When played back normally much of the time it’s not noticeable by the viewer.

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 contract 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.

Read more

If I have other video filters applied, how should I apply Flicker Free?

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.

Read more

How long are the render times?

For a 1080p project, a 30 second clip should take about 4-6 minutes to render.

Of course, this depends on the speed of the computer, how many cores you have/are using, the host application, and the settings within Flicker Free. For example, a Time Radius that’s larger will make for a longer render time.

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

Flicker Free does not use the GPU on your video card. So the video card will not affect render times.

Read more

During my export of 4K footage Resolve is running out of GPU memory

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.

Read more

FCP X renders a blue image when applying Flicker Free.

This is a bug in FCP X 10.0.8 and earlier. Apple fixed it in FCP X 10.0.9. So please upgrade your copy of Final Cut Pro X.