![]() Please queue everything up in Media Encoder and render everything when you’re not using the machine for something else. If not, just render the FF 2.0 sequences. It helps to also have Flicker Free 1.0 installed if you have it. Here’s a benchmark Premiere Pro project that we’d like you to run. But it’s not much longer than this email… you should read it!). See the ReadMe for more details (I know… nobody reads the ReadMe. handheld camera), that’s where the 2.0 improvements will really make a difference, but it’s slower. This is probably what you’ll usually want. So if you want Faster, use the settings for 1.0. 2) Unfortunately, Better AND Faster wasn’t doable. We’re working on it but for now the Mercury Engine HAS to be set to OpenCL. (it helps to have both FF 1.0 and FF 2.0 to see the before/after)īeta ReadMe with info about the parameters:Ī couple important things to note… 1) if you’re on Mac, make sure the Mercury Engine is set to OpenCL. You can download the Premiere project and footage of Callie here: I show the original, what FF 1.0 could do, and what the new FF 2.0 algorithms are capable of. ![]() The camera is moving around Callie, our Director of IT Obsolescence, and this is something that gives 1.0 serious problems. a wedding), it will fix footage that was previously unfixable.Ī great example of this is in the footage below. ![]() However, if you’re trying to salvage a shot you can’t go and reshoot (e.g. The downside is that this is relatively slow. For shots with a moving camera or a lot of movement in the video, this makes a big difference. The other big improvement is better motion detection, that uses optical flow algorithms. Although, on both platforms it varies a bit depending on your CPU, graphic card, and what you’re trying to render. Once the Metal port is finished we expect performance similar to what we’re seeing on Windows. ![]() So on Mac you’re more likely to see a 200% or so increase over FF 1.0. 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. Apple is doing what it can to kill OpenCL, so newer machines, which are AMD only, suffer because of it. Older machines see a bigger increase than newer ones, primarily because they support OpenCL better. Flicker Free 1.0 with the same settings, but often it’s 500% or more. On Windows, on average it’s about 350% faster vs. There are a lot of cool improvements, but the main one is GPU support. Please contact to get added to the beta list and get the serial number. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |