Do not use Norton Anti-Virus

We highly recommend against using Norton Anti-Virus. In an attempt to be smart, they proactively quarantine programs because “fewer than 50 users in the Norton community have them”. This means many of our plugins get quarantined when you try to install them.

Our installers pose no threat and you can safely install them.

Here’s what Norton puts up:

Do not use Norton Anti-virus as it's unreliable

1- It describes the risk as Heur.AdvML.C and labels it a ‘heuristic virus’ which sounds scary and looks like a virus name. It’s not. It’s a Norton code for their ‘artificial intelligence’. If this is how smart AI is, it’s going to be a long time before the bots take over the world.

2- Our major crimes against humanity seem to be that less than 50 users have installed this and it was uploaded over 4 months ago.

That’s it. So Norton’s ‘malware heuristics’ AI has decided were a High threat.

This is misleading and doing a disservice to us and our users. I assume most other plugins from small companies will fall under the same umbrella of stupidity.

As such we recommend you use a different anti-virus software.

Thoughts on The Mac Pro and FCP X

There’s been some talk of the eminent demise of the Mac Pro. The Trash Can is getting quite old in the tooth… it was overpriced and underpowered to begin  with and is now pretty out of date. Frankly it’d be nice if Apple just killed it and moved on. It’s not where they make their money and it’s clear they’re not that interested in making machines for the high end video production market. At the very least, it would mean we (Digital Anarchy) wouldn’t have to buy Trash Can 2.0 just for testing plugins. I’m all for not buying expensive machines we don’t have any use for.

But if they kill off the Mac Pro, what does that mean for FCP X? Probably nothing. It’s equally clear the FCP team still cares about pro video. There were multiple folks from the FCP team at NAB this year, talking to people and showing off FCP at one of the sub-conferences. They also continue to add pro-level features.

That said, they may care as much (maybe even more) about the social media creators… folks doing YouTube, Facebook, and other types of social media creation. There are a lot of them. A lot more than folks doing higher end video stuff, and these creators are frequently using iPhones to capture and the Mac to edit. They aren’t ‘pro editors’ and I think that demographic makes up a good chunk of FCP users. It’s certainly the folks that Apple, as a whole, is going after in a broader sense.

If you don’t think these folks are a significant focus for Apple overall, just look at how much emphasis they’ve put on the camera in the iPhone 6 & 7… 240fps video, dual lenses, RAW shooting, etc. To say nothing of all the billboards with nothing but a photo ‘taken with the iPhone’. Everyone is a media creator now and ‘Everyone’ is more important to Apple than ‘Pro Editors’.

The iMacs are more than powerful enough for those folks and it wouldn’t surprise me if Apple just focused on them. Perhaps coming out with a couple very powerful iMacs/MacBook Pros as a nod to professionals, but letting the MacPro fade away.

Obviously, as with all things Apple, this is just speculation. However, given the lack of attention professionals have gotten over the last half decade, maybe it’s time for Apple to just admit they have other fish to fry.

Tutorial: Removing Flicker from Edited Video Footage

One problem that users can run into is that Flicker Free will look across edits when analyzing frames for the correct luminance. The plugin looks backwards as well as forwards to gather frames and does a sophisticated blend of all those frames. So even if you create an edit, say to remove an unwanted camera shift or person walking in front of the camera, Flicker Free will still see those frames.

This is particularly a problem with Detect Motion turned OFF.

The way around this is to Nest (i.e. Pre-compose (AE), Compound Clip (FCP)) the edit and apply the plugin to the new sequence. The new sequence will start at the first frame of the edit and Flicker Free won’t be able to see the frames before the edit.

This is NOT something you always have to do. It’s only if the frames before the edit are significantly different than the ones after it (i.e. a completely different scene or some crazy camera movement). 99% of the time it’s not a problem.

This tutorial shows how to solve the problem in Premiere. The technique works the same in other applications. Just replacing ‘Nesting’ with whatever your host application does (pre-composing, making a compound clip, etc).

Wherein Jim Tierney rants and opines about After Effects, Premiere Pro, Final Cut Pro, and other nonsense