Tag Archives: flicker free

Removing flicker from concert videos (or anything with stage lights)

LED lights are everywhere and nowhere moreso than concerts or other performances. Since they are a common source of flicker when shot with a video camera, it’s something we get asked about fairly regularly.

Other types of stage lights can also be problematic (especially in slow motion), but LED lights are the more common culprit. You can see this clearly in this footage of a band. It’s a slow motion clip shot with an iPhone… which will shoot a few seconds of regular speed video before switching to slo-mo. So the first five seconds are regular speed and the next five are slo-mo:

To remove the flicker we’re using our plugin Flicker Free, which supports After Effects, Premiere, Final Cut Pro, Resolve, and Avid. You can learn more about it and download the trial version here.

The regular lights are fine, but there are some LED lights (ones with the multiple lights in a hexagon) that are flickering. This happens in both the regular speed and slow motion video portions of the video. You’ll notice, of course, the flickering is slower in the slo-mo portion. (mixed frame rates can sometimes be a problem as well but not in this case)

Usually this is something Flicker Free can fix pretty easily and does so in this case, but there are a few variables that are present in this video that can sometimes complicate things. It’s a handheld shot (shaky), there are multiple lights, and there are performers (who, luckily, aren’t moving much).

Handheld shot: The camera is moving erratically. This can be a problem for Flicker Free and it’s something the Motion Compensation checkbox was specifically designed to deal with (in addition to the Detect Motion settings). However, in this case, the camera isn’t moving quickly which is where this really becomes a problem. So we can get away with only having Detect Motion on. Also… with stage performances there is also often a lot of movement of the performers. Not a problem here, but if there is a lot of performer movement, it’s likely you’ll really need to turn Motion Compensation on.

Motion Compensation increases the render time, so if you don’t need to turn it on, then it’s best not to. But some footage will only be fixable with it on, so if the default settings aren’t working, turn on Motion Compensation.

As is often the case the default settings, the preset Rolling Bands, works great. This is very common with LED lights as they produce a certain type of flicker that the preset/default works very well on.

Multiple Lights: It’s possible to have multiple lights in the scene that flicker, and do so at different rates. Flicker Free can usually handle this scenario, but sometimes you need to apply two instances of Flicker Free. If you do this, it’s highly recommended not to use Motion Compensation and either turn Detect Motion off or set it to Fast. If you have Motion Compensation on and use two instances of FF, you’ll get exponentially longer render times and you might run out of memory on the GPU causing a crash.

Slow Motion: Slo-mo footage can really slow the flickering down, requiring you to max out Time Radius. Again, this is a setting that can increase render times, so lower values are better if you can get away with them and it fixes the flicker.

This clip was fairly easy. Only one light was an LED light and flickering, So the default settings worked great. If the default settings don’t work there are a few other presets to try: Stage Lights, Projection Screen, etc. But, even if those don’t work right off the bat, hopefully this gives you some tips on how to fix even the most challenging videos of performances.

Apple Silicon Plugins for Final Cut Pro

We have the initial beta builds of native Silicon versions of Flicker Free and Beauty Box for FCP. FCP is the only released app that is currently Universal and supports Silicon plugins. Samurai Sharpen will be released for FCP/Silicon soon.

Builds for other host apps will be released once they release their Silicon versions. The plan right now is to get the FCP versions solid and that’ll make it more likely the builds for other apps will work out of the gate. Also, I don’t love releasing beta plugins for a beta host app (e.g. Resolve).

Overall they seem in pretty good shape. One caveat is that Analyze Frame doesn’t work in Beauty Box, so you need to manually select the Light and Dark Colors with the color picker. This is not ideal, as it’s not exactly the same thing as using Analyze Frame. But it’s what we’ve got right now. It’s actually more of a problem with FCP’s new FxPlug 4 API, so it won’t be fixed until the next release of FCP.

On that note, I’ll mention that there’s a lot of new stuff going on with the Apple builds. FCP announced the new API, which is completely different from FxPlug 3, so it’s required a lot of re-working. Eventually the FxPlug 3 plugins will stop working in FCP, so you’ll need the FxPlug 4 builds sooner or later. We’re also finally porting the GPU code to Metal. So look for new builds that incorporate all that for both Silicon and Intel very soon. Apple is keeping us pretty busy.

If you have any problems please send bug reports to: cs@nulldigitalanarchy.com

Here are the Apple Silicon builds:

https://digitalanarchy.com/beta/flickerfree_21-667_FX4.dmg  (Flicker Free 2.1 Beta)
https://digitalanarchy.com/beta/beautybox_43-337_FX4.dmg  (Beauty Box 4.3 Beta)

Flicker Free 2.0: Up to 1500% faster!

We’re extremely excited about the speed improvements we’ve enhanced Flicker Free 2.0 with! Yes, we have actually seen 1500% performance increase with 4K footage, but on average across all resolutions and computers it’s usually 300-400% increase. Still pretty good and 4K is more like 700-800% on average.

You can see our performance benchmarks in this Google Doc. And download the benchmark projects for Premiere Pro (700mb) and for Final Cut Pro to run your own tests! (However, you need to run the FF1 sequences with FF1 and the FF2 (FF1 settings) with FF2. If you just turn off the GPU in FF2 you won’t get the same results (they’ll be slower than they would be in FF1)

However, it’s pretty dependent on your computer and what video editing app you’re using. We’ve been disappointed by MacBook Pros across the board. They’re just really under powered for the price. If you’re running a MacBook, we highly recommend getting an external GPU enclosure and putting in a high end AMD card. We’d recommend Nvidia as we do on Windows, but… Apple. Oh well.

It’s possible once we implement Metal (Apple’s technology to replace OpenCL) we’ll see some additional improvements. That’s coming in a free update shortly. In fact, because After Effects/Mac only supports Metal, Flicker Free isn’t accelerated at all in AE. It does great in Premiere which does support OpenCL. (Adobe’s GPU support is really lacking, and frustrating, across their video apps, but that’s a topic for another blog post)

Some notes about the Benchmark Google Doc:

  • It’s only Premiere and FCP
  • Not every computer ran every test. We changed the benchmark and didn’t have access to every machine to render the additional sequences.
  • Windows generally saw more improvement than Mac.
  • FCP saw some really significant gains. It’s much faster/efficient to get multiple frames in FCP using the GPU than the CPU. 1.0 was really slow in FCP.
  • The important bit is at the right edge of the spreadsheet where you see the percentages.
  • We’d love to see you run the benchmarks on your computer and please send us the results. If you do, please send results to cs@nulldigitalanarchy.com. However, you need to run the FF1 sequences with FF1 and the FF2 (FF1 settings) with FF2. If you just turn off the GPU in FF2 you won’t get the same results (they’ll be slower than they would be in FF1).
  • After Effects isn’t in the benchmark because AE/Mac doesn’t support OpenCL for GPU acceleration.
  • Davinci Resolve and Avid are coming soon!

Fixing Flicker in Videos with Lots of Motion – Fast Moving Cameras or Subjects

One of the things Flicker Free 1.0 doesn’t do well is deal with moving cameras or fast moving subjects. This tends to result in a lot of ghosting… echos from other frames Flicker Free is analyzing as it tries to remove the flicker (no people aren’t going to stop talking to you on dating apps because you’re using FF). You can see this in the below video as sort of a motion blur or trails.

Flicker Free 2.0 does a MUCH better job of handling this situation. We’re using optical flow algorithms (what’s used for retiming footage) as well as a better motion detection algorithm to isolate areas of motion while we deflicker the rest of the frame. You can see the results side-by-side below:

Better handling of fast motion, called Motion Compensation, is one of the big new features of 2.0. While the whole plugin is GPU accelerated, Motion Compensation will slow things down significantly. So if you don’t need it, it’s best to leave it off. But when you need it… you really need it and the extra render time is worth the wait. Especially if it’s critical footage and it’s either wait for the render or re-shoot (which might not be so easy if it’s  a wedding or sports event!).
We’re getting ready to release 2.0 in the next week or so, so just a bit of tease of some of the amazing new tech we’ve rolled into it!

Flicker Free 2.0 Beta!

It’s been a long time coming, so we’re pretty excited to announce that Flicker Free 2.0 is in beta! The beta serial number is good until June 30th and will make the plugin fully functional with no watermark. Please contact cs@nulldigitalanarchy.com to get added to the beta list and get the serial number.

There are a lot of cool improvements, but the main one is GPU support. On Windows, on average it’s about 350% faster vs. Flicker Free 1.0 with the same settings, but often it’s 500% or more. On Mac, it’s more complicated. Older machines see a bigger increase than newer ones, primarily because they support OpenCL better. Apple is doing what it can to kill OpenCL, so newer machines, which are AMD only, suffer because of it. We are working on a Metal port and that’ll be a free upgrade for 2.0, but it won’t be in the initial release. So on Mac you’re more likely to see a 200% or so increase over FF 1.0. Once the Metal port is finished we expect performance similar to what we’re seeing on Windows. Although, on both platforms it varies a bit depending on your CPU, graphic card, and what you’re trying to render. 

The other big improvement is better motion detection, that uses optical flow algorithms. For shots with a moving camera or a lot of movement in the video, this makes a big difference. The downside is that this is relatively slow. However, if you’re trying to salvage a shot you can’t go and reshoot (e.g. a wedding), it will fix footage that was previously unfixable.

A great example of this is in the footage below. It’s a handheld shot with rolling bands. The camera is moving around Callie, our Director of IT Obsolescence, and this is something that gives 1.0 serious problems. I show the original, what FF 1.0 could do, and what the new FF 2.0 algorithms are capable of. It does a pretty impressive job.

You can download the Premiere project and footage of Callie here: 

https://digitalanarchy.com/beta/beta-project.zip (it helps to have both FF 1.0 and FF 2.0 to see the before/after) 

 

Beta ReadMe with info about the parameters:

https://digitalanarchy.com/beta/flickerfree_readme.zip

A couple important things to note… 1) if you’re on Mac, make sure the Mercury Engine is set to OpenCL. We don’t support Metal yet. We’re working on it but for now the Mercury Engine HAS to be set to OpenCL. 2) Unfortunately, Better AND Faster wasn’t doable. So if you want Faster, use the settings for 1.0. This is probably what you’ll usually want. For footage with a lot of motion (e.g. handheld camera), that’s where the 2.0 improvements will really make a difference, but it’s slower. See the ReadMe for more details (I know… nobody reads the ReadMe. But it’s not much longer than this email… you should read it!).

 

Here’s a benchmark Premiere Pro project that we’d like you to run. It helps to also have Flicker Free 1.0 installed if you have it. If not, just render the FF 2.0 sequences. Please queue everything up in Media Encoder and render everything when you’re not using the machine for something else. Please send the results (just copy the media encoder log for the renders: File>Show Log), what graphics card you have, and what processer/speed you have to beta@nulldigitalanarchy.com.

Benchmark project with footage (if you’ve already downloaded this, please re-download it as the project has changed):

https://digitalanarchy.com/beta/FF2-Benchmark.zip (~650mb)

 

Please send any bug reports or questions to cs@nulldigitalanarchy.com

It’s been a long time coming, so we’re pretty excited about this release! Thanks for any help you can give!

Cheers,

Jim Tierney
Chief Executive Anarchist
Digital Anarchy

Speeding Up De-flickering of Time Lapse Sequences in Premiere

Time lapse is always challenging… you’ve got a high resolution image sequence that can seriously tax your system. Add Flicker Free on top of that… where we’re analyzing up to 21 of those high resolution images… and you can really slow a system down. So I’m going to go over a few tips for speeding things up in Premiere or other video editor.

First off, turn off Render Maximum Depth and Maximum Quality. Maximum Depth is not going to improve the render quality unless your image sequence is HDR and the format you’re saving it to supports 32-bit images. If it’s just a normal RAW or JPEG sequence, it  won’t make much of a difference. Render Maximum Quality may make a bit of difference but it will likely be lost in whatever compression you use. Do a test or two to see if you can tell the difference (it does improve scaling) but I rarely can.

RAW: If at all possible you should shoot your time lapses in RAW. There are some serious benefits which I go over in detailed in this video: Shooting RAW for Time Lapse. The main benefit is that Adobe Camera RAW automatically removes dead pixels. It’s a big f’ing deal and it’s awesome. HOWEVER… once you’ve processed them in Adobe Camera RAW, you should convert the image sequence to a movie or JPEG sequence (using very little compression). It will make processing the time lapse sequence (color correction, effects, deflickering, etc.) much, much faster. RAW is awesome for the first pass, after that it’ll just bog your system down.

Nest, Pre-comp, Compound… whatever your video editing app calls it, use it. Don’t apply Flicker Free or other de-flickering software to the original, super-high resolution image sequence. Apply it to whatever your final render size is… HD, 4K, etc.

Why? Say you have a 6000×4000 image sequence and you need to deliver an HD clip. If you apply effects to the 6000×4000 sequence, Premiere will have to process TWELVE times the amount of pixels it would have to process if you applied it to HD resolution footage. 24 million pixels vs. 2 million pixels. This can result in a HUGE speed difference when it comes time to render.

How do you Nest?

This is Premiere-centric, but the concept applies to After Effects (pre-compose) or FCP (compound) as well. (The rest of this blog post will be explaining how to Nest. If you already understand everything I’ve said, you’re good to go!)

First, take your original image sequence (for example, 6000×4000 pixels) and put it into an HD sequence. Scale the original footage down to fit the HD sequence.

Hi-Res images inside an HD sequenceThe reason for this is that we want to control how Premiere applies Flicker Free. If we apply it to the 6000×4000 images, Premiere will apply FF and then scale the image sequence. That’s the order of operations. It doesn’t matter if Scale is set to 2%. Flicker Free (and any effect) will be applied to the full 6000×4000 image.

So… we put the big, original images into an HD sequence and do any transformations (scaling, adjusting the position and rotating) here. This usually includes stabilization… although if you’re using Warp Stabilizer you can make a case for doing that to the HD sequence. That’s beyond the scope of this tutorial, but here’s a great tutorial on Warp Stabilizer and Time Lapse Sequences.

Next, we take our HD time lapse sequence and put that inside a different HD sequence. You can do this manually or use the Nest command.

Apply Flicker Free to the HD sequence, not the 6000x4000 imagesNow we apply Flicker Free to our HD time lapse sequence. That way FF will only have to process the 1920×1080 frames. The original 6000×4000 images are hidden in the HD sequence. To Flicker Free it just looks like HD footage.

Voila! Faster rendering times!

So, to recap:

  • Turn off Render Maximum Depth
  • Shoot RAW, but apply Flicker Free to a JPEG sequence/Movie
  • Apply Flicker Free to the final output resolution, not the original resolution

Those should all help your rendering times. Flicker Free still takes some time to render, none of the above will make it real time. However, it should speed things up and make the render times more manageable if you’re finding them to be really excessive.

Flicker Free is available for Premiere Pro, After Effects, Final Cut Pro, Avid, Resolve, and Assimilate Scratch. It costs $149. You can download a free trial of Flicker Free here.

De-flickering Bix Pix’s Stop Motion Animation Show ‘Tumble Leaf’ with Flicker Free

Like Digital Anarchy On FacebookLike us on Facebook!

One of the challenges with stop motion animation is flicker. Lighting varies slightly for any number of reasons causing the exposure of every frame to be slightly different. We were pretty excited when Bix Pix Entertainment bought a bunch of Flicker Free licenses (our deflicker plugin) for Adobe After Effects. They do an amazing kids show for Amazon called Tumble Leaf that’s all stop motion animation. It’s won multiple awards, including an Emmy for best animated preschool show.

Many of us, if not most of us, that do VFX software are wannabe (or just flat out failed ;-) animators. We’re just better at the tech than the art. (exception to the rule: Bob Powell, one of our programmers, who was a TD at Laika and worked on Box Trolls among other things)

So we love stop motion animation. And Bix Pix does an absolutely stellar job with Tumble Leaf. The animation, the detailed set design, the characters… are all off the charts. I’ll let them tell it in their own words (below). But check out the 30 second deflicker example below (view at full screen as the Vimeo compression makes the flicker hard to see). I’ve also embedded their ‘Behind The Scenes’ video at the end of the article. If you like stop motion, you’ll really love the ‘Behind the Scenes’.

From the Bix Pix folks themselves… breaking down how they use Flicker Free  in their Adobe After Effects workflow:

——————————————————————-

Using Digital Anarchy’s Flicker Free at Bix Pix

Bix Pix Entertainment is an animation studio that specializes in the art of stop-motion animation, and is known for their award-winning show Tumble Leaf on Amazon Prime.

It is not uncommon for an animator to labor for days sometimes weeks on a single stop motion shot, working frame by frame. With this process, it is natural to have some light variations between each exposure, commonly referred to as ‘flicker’ – There are many factors that can cause the shift in lighting. For instance, a studio light or lights may blow out or solar flare. Voltage and/ power surges can brighten or dim lights over a long shot. Certain types of lights, poor lighting equipment, camera malfunctions or incorrect camera settings. Sometimes an animator might wear a white t-shirt unintentionally adding fill to the shot or accidentally standing in front of a light casting a shadow from his or her body.

The variables are endless. Luckily these days compositors and VFX artists have fantastic tools to help remove these unwanted light shifts. Removing unwanted light shifts and flicker is a very important and necessary first step when working with stop-motion footage. Unless by chance it’s an artistic decision to leave that tell-tale flicker in there. But that is a rare decision that does not come about often.

Here at Bix Pix we use Adobe After Effects for all of our compositing and clean-up work. Having used 4 different flicker removal plugins over the years, we have to say Digital Anarchy’s flicker Free is the fastest, easiest and most effective flicker removal software we have come across. And also quite affordable.

During a season of Tumble Leaf we will process between 1600 and 2000 shots averaging between 3 seconds and up to a couple minutes in length. That is an average of about 5 hours of footage per season, almost three times the length of a feature film. With a tight schedule of less than a year and a small team of ten or so VFX artists and compositors. Nearly every shot has an instance of flicker free applied to it as an effect. The plugin is so fast, simple to use and reliable. De-flickering can be done in almost real time.

Digital Anarchy’s Flicker free has saved us thousands of hours of work and reduced overtime and crunch time delays. This not only saves money but frees up artists to do more elaborate effects that we could not do before due to time constraints, allowing them to focus on making their work stand out even more.

If you are shooting stop-motion animation and require flicker free footage, this is the plugin to use.

———————————————–

For a breakdown of how they do Tumble Leaf, you should definitely check out the Behind the Scenes video!

I even got to meet the lead character, Fig! My niece and nephew (4 and 6) were very impressed. :-)

Hanging out with Fig at BixPix Entertainment

Cheers,
Jim Tierney
Chief Executive Anarchist
Digital Anarchy

Speeding Up Flicker Free: The Order You Apply Plugins in Your Video Editing App

Like Digital Anarchy On Facebook

 

One key way of speeding up the Flicker Free plugin is putting it first in the order of effects. What does this mean? Let’s say you’re using the Lumetri Color Corrector in Premiere. You want to apply Flicker Free first, then apply Lumetri. You’ll see about a 300+% speed increase vs. doing it with Lumetri first. So it looks like this:

Apply Flicker Free first in your video editing application to increase the rendering speed.

Why the Speed Difference?

Flicker Free has to analyze multiple frames to de-flicker the footage you’re using. It looks at up to 21 frames. If you have the effect applied before Flicker Free it means Lumetri is being applied TWENTY ONE times for every frame Flicker Free renders. And especially with a slow effect like Lumetri that will definitely slow everything down.

It fact, on slower machines it can bring Premiere to a grinding halt. Premiere has to render the other effect on 21 frames in order to render just one frame for Flicker Free. In this case, Flicker Free takes up a lot of memory, the other effect can take up a lot of memory and things start getting ugly fast.

Renders with Happy Endings

So to avoid this problem, just apply Flicker Free before any other effects. This goes for pretty much every video editing app. The render penalty will vary depending on the host app and what effect(s) you have applied. For example, using the Fast Color Corrector in Premiere Pro resulted in a slow down of only about 10% (vs. Lumetri and a slow down of 320%). In After Effects the slow down was about 20% with just the Synthetic Aperture color corrector that ships with AE. However, if you add more filters it can get a lot worse.

Either way, you’ll have much happier render times if you put Flicker Free first.

Hopefully this makes some sense. I’ll go into a few technical details for those that are interested. (Feel free to stop reading if it’s clear you just need to put Flicker Free first) (oh, and here are some other ways of speeding up Flicker Free)

Technical Details

With all host applications, Flicker Free, like all plugins, has to request frames through the host application API. With most plugins, like the Beauty Box Video plugin, the plugin only needs to request the current frame. You want to render frame X: Premiere Pro (or Avid, FCP, etc) has to load the frame, render any plugins and then display it. Plugins get rendered in the order you apply them. Fairly straightforward.

The Flicker Free plugin is different. It’s not JUST looking at the current frame. In order to figure out the correct luminance for each pixel (thus removing flicker) it has to look at pixels both before and after the current frame. This means it has to ask the API for up to 21 frames, analyze them, return the result to Premiere, which then finishes rendering the current frame.

So the API says, “Yes, I will do your bidding and get those 21 frames. But first, I must render them!”. And so it does. If there are no plugins applied to them, this is easy. It just hands Flicker Free the 21 original frames and goes on its merry way. If there are plugins applied, the API has to render those on each frame it gives to Flicker Free. FF has to wait around for all 21 frames to be rendered before it can render the current frame. It waits, therefore that means YOU wait. If you need a long coffee break these renders can be great. If not, they are frustrating.

If you use After Effects you may be familiar with pre-comping a layer with effects so that you can use it within a plugin applied to a different layer. This goes through a different portion of the API than when a plugin requests frames programmatically from AE. In the case of a layer in the layer pop-up the plugin just gets the original image with no effects applied. If the plugin actually asks AE for the frame one frame before it, AE has to render it.

One other thing that affects speed behind the scenes… some apps are better at caching frames that plugins ask for than other apps. After Effects does this pretty well, Premiere Pro less so. So this helps AE have faster render times when using Flicker Free and rendering sequentially. If you’re jumping around the timeline then this matters less.

Hopefully this helps you get better render times from Flicker Free. The KEY thing to remember however, is ALWAYS APPLY FLICKER FREE FIRST!

Happy Rendering!

Flicker Free and the Bloody Beetroots feat. Tommy Lee

I think the most exciting thing about Flicker Free plugin is that people are willing to let us talk about it when they use it. Beauty Box Video gets used all the time on very high profile projects but no one wants to admit it publicly. It’s not worth some video editors job to say so-and-so pop star doesn’t have the flawless skin it looks like she has.

Flicker Free isn’t even officially released yet and we’re getting producers emailing us, letting us know it saved a shot (or shots) in their video AND they have no problem with us posting it. It’s awesome!

Such is the case with the music video from the Bloody Beetroots featuring Tommy Lee (of Motley Crue fame). One of the LED lights on the set was causing severe strobing in some shots. This isn’t regular flicker, it’s sort of rolling bands. It’s something we’ve seen only from LED lights and possibly electrical interference (the iPhone example in the FF demo reel is a good example of the problem). Flicker Free was the only thing that got rid of it. Just another big problem the plugin can solve. You can check out the final video below.