[Al Davis]

What version of PP are you using?

I have 12.1.1
It’s a terrible release, but this worked flawlessly. I had never tried this before, but your question seemed like a learning opportunity.

For Lumetri, don’t use an adjustment layer. Just apply the Lumetri color grade to the clip, and then apply the mask (no inverse) and animate the opacity.
This worked for me 1st time, no fuss.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

I just tried this.
Most of the controls (not curves) seem to have individual key framing capabilities in the “effects control” tab.

But worked perfectly was simply creating an overall (entire frame) square mask for Lumetri, and then animating the opacity from 0%-100% over time….or the reverse.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

The application on my main internal drive (obviously).
Project on a different internal drive.
Assets on an external drive (fast!)
Sometimes render files on a different (fast) external drive.

Why? You don’t want a spinning drive doing multiple functions (like running the app and the system while also processing your project file) as it slows it down.

On a complex project (in AE) I sped up an output from 19 hrs. down to an 90 minutes once I spread everything out to 4 different drives.

I have an older (put pretty fast) mac pro.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

Dave and Jon, I don’t know about you, but I consider the 12.1 release as extremely important, because it finally brings color correcting equal to what FCP 7 offered: that being comparative windows for shot matching. The AI stuff is secondary to me.
As much as I like Premiere Pro, and have long since shook loose from my Apple addiction (I never embraced FCP X); this feature is huge in my eyes.

Adobe is two weeks late in fixing this, given how many editors it has marooned.

That said, the old update rule (never in the middle of a project) still stands.

Bryan – role back to 12.0, it should be fine.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

Thank you John.
This was very helpful, as it behaved exactly as you suggested.

It would be great if you could execute multiple masks within the same filter parameter; but this does get the job done.

Cheers!

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

Tx – did that as well.
No luck. It behaved in the same conflicted style as the layer adjustment.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

I think the problem goes deeper.

As I understand this from some moderators on the Adobe thread; it is version 12.1 on computers used 10.11.6.
10.12 and above seems OK.

I am having similar issues.

You can simply re-name the video file, and it then imports normally.

Totally weird.

Adobe is said to be working on a bug fix update.

I am now holding my breath…..

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

Thanks for the suggestion Paul. I did forget about this feature.

I tried it on this color move. I copied the Lumetri filter with my adjustments, and then pasted it into the adjustment layer, and tried to “single” the 2nd mask. Still doesn’t work, as one mask still effects the other and offsets the result.

Nothing to imitate the age old “subtractive” solution.

The masks within filters in PP is a great thing. It would be even better, and more serviceable if it allowed multiple applications (of masks).

I still feel like I am missing something here.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

There are many quality effects out there at varying costs.

Besides FXFactory, there is the entire Red Giant/Magic Bullet group, Boris FX / Sapphire, Digital Anarchy….

These plugins all come with installers that in many cases will allow you to select with programs to “plug into”

Many will install into FCP, Motion, PP, AE. The installer will automatically place the plugin in the relevant folders within your system, for the applications you select.

Al Davis
Visual Velocity
Brookline, MA

[Al Davis]

UPDATE:
I reverted PP to 12.0.1
Now it will see and import all types of XDCAM files – no problems. As always.

At 12.1.0 and 12.1.1 it would only read an import SOME XDCAM files; even within the same project.
Using the Media Browser as an import window, you can see that some files appeared as normal video/audio files that you could scrub through. Others showed up as QT icons only, and were identified an imported as “audio only”.

Adobe clearly lists XDCAM files on their “protected” list of codecs.

What a mess.

Al Davis
Visual Velocity
Brookline, MA