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: email@example.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)
One of the fun challenges of developing graphics software is dealing with the many, varied video cards and GPUs out there. (actually, it’s a total pain in the ass. Hey, just being honest :-)
There are a lot of different video cards out there and they all have their quirks. Which are complicated by the different operating systems and host applications… for example, Apple decides they’re going to more or less drop OpenCL in favor of Metal, which means we have to re-write quite a bit of code, Adobe After Effects and Adobe Premiere Pro handle GPUs differently even though it’s the same API, etc. etc. From the end user side of things you might not realize how much development goes into GPU Acceleration. It’s a lot.
The latest release of Beauty Box Video for Skin Retouching (v4.1) contains a bunch of fixes for video cards that use OpenCL (AMD, Intel). So if you’re using those cards it’s a worthwhile download. If you’re using Resolve and Nvidia cards, you also want to download it as there’s a bug with CUDA and Resolve and you’ll want to use Beauty Box in OpenCL mode until we fix the CUDA bug. (Probably a few weeks away) Fun times in GPU-land.
4.1 is a free update for users of the 4.0 plugin. Download the demo and it should automatically remove the older version and recognize your serial number.
Just wanted to give you all some insight on how we spend our days around here and what your hard earned cash goes into when you buy a plugin. You know, just in case you’re under the impression all software developers do is ‘work’ at the beach and drive Ferraris around. We do have fun, but usually it involves nailing the video card of the month to the wall and shooting paintballs at it. ;-)
What causes Final Cut Pro X to re-render? If you’ve ever wondered why sometimes the orange ‘unrendered’ bar shows up when you make a change and sometimes it doesn’t… I explain it all here. This is something that will be valuable to any FCP user but can be of the utmost importance if you’re rendering Beauty Box, our plugin for doing skin retouching and beauty work on HD/4K video. (Actually we’re hard at work making Beauty Box a LOT faster, so look for an announcement soon!)
Currently, if you’ve applied Beauty Box to a long clip, say 60 minutes, you can be looking at serious render times (this can happen for any non-realtime effect), possibly twelve hours or so on slower computers and video cards. (It can also be a few hours, just depends on how fast everything is)
Recently we had a user with that situation. They had a logo in .png format that was on top of the entire video being used as a bug. So they rendered everything out to deliver it, but, of course, the client wanted the bug moved slightly. This caused Final Cut Pro to want to re-render EVERYTHING, meaning the really long Beauty Box render needed to happen as well. Unfortunately, this is just the way Final Cut Pro works.
Why does it work that way and what can be done about it?
Continue reading How Final Cut Pro X Caches Render Files (and how to prevent Beauty Box from re-rendering)