Wave warp keyframes don't work on adjustment layer?

[avpromedia]

When I apply wave warp to an adjustment layer it works fine without keyframe.

If I add keyframes to change the warp height to go from 0 to 70, it doesn't work. The effect would look like 0 height all the time. Why?

What I'm trying to do is to make a transition like this:

I can get it to work without using adjustment layer, but it requires several steps. I want to apply this quickly to many cuts and using an adjustment layer seems ideal -- once I put all the effects on the adjustment layer I could just drag a copy above the desired cut. But because of the above problem, I can't.

Is there another way to do this?

[Steve Griffiths]

Checked your issue in both Premiere Pro 2020 & 21 and can replicate the problem.

Don't have a solution (did try a few things).

What is very interesting - if other keyframed effects are also applied to the same Adjustment layer that has 'Wave Warp' applied - AND wave warp has two different keyframes set for height -

and these effects also have key frames - then those keyframed changes will also not work.

Tried this with 'Transform'. 'Gaussian blur' and 'Color Balance'.

In short:

With the 'Wave Warp' plugin active and 'height' keyframed - other effects will also not follow their keyframed parameters.

If Wave Warp is turned off in the Effects stack. The other keyframed effects will then function normally.

Very weird.

[avpromedia]

Thanks Steve for taking the time to try this.

Should I report this as a bug in the uservoice forum? Or is this forum monitored by adobe?

How about this for a workaround: instead of using keyframes to vary the wave height, use many short duration adjustment layers side-by-side each containing a wave warp of varying height. You'd also have to line up the phases so they look continuous.

Then group these adjustment layers together and use as one.

[Steve Griffiths · Accepted solution]

Please report it at Uservoice. Adobe people do come to this forum to provide help but as far as I know don't necessarily report issues raised here. Uservoice posts will be read by an engineer.

As to your workaround ... might work but sounds like a lot of trouble. You did mention you could do the effect but just not as easily as using an Adjustment layer. I think I'd probably go with putting the wave warp effect directly onto the clips. Once you set it up to work perfectly - copy and paste the effect and keyframes into any new transitions you want it applied to.

You could also try adding the 'Turbulent Displace' effect to your adjustment layer and animating it like you did with 'wave warp' - just checked and this does work (unlike wave warp). Unfortunately it's not the same as wave warp and does not have quite that 1960's dream transition feel ... but you might get it looking OK.

And if cost is not an issue - Boris have a 'water/wave' transition in their Continuum set of effects - again it's not quite the same as what you already have and the cost is pricey.

Good luck, regards Steve

[Dirjampa]

Hi there Avpromedia,

Did you get any further with this one or did you plumb for the work around?

I've got an issue which I think is on the same lines as yours.

https://community.adobe.com/t5/premiere-pro-discussions/adding-a-lens-flare-to-an-adjustment-layer-i...

The keyframes on my adjustment layer seem to be messing with the keyframes on another track.

Dont suppose you have any new ideas on teh subject do you?

Cheers

D

[R Neil Haugen]

Adjustment layers are NOT simply "another video track" that you can use all effects on the same as if you applied them to a clip. And keyframed things in ALs are not actually attached to the clip in any way shape or form, and don't tend to work well.

You can ask in the UserVoice system for this to change, but for now ... do keyframe work on clips, graphics, and nests. And with the few effects that will actually properly work with keyframes on ALs.

Neil

[davidterranova]

FWIW adjustment layer keyframes have worked for me for years, and have been one of premiere's few actual benefits when transitioning from FCP7.  With the latest versions over the past year, this functionality has suddenly stopped working, regressing my workflow by forcing me to nest and other clunky nonsense (premiere devs are clearly not interested in offering default-bin functionality to catch all new sub-seqs).  Spending 5 times the amount of time and energy in finding workarounds to something that worked perfectly well before is just strange. But regressive upgrades are the norm these days, so hey ho.

[R Neil Haugen]

Totally understand. Frustrating but ... I'm a totally practical guy in the end. These are all simply fancy tools. What works, works. What's worked before and doesn't now, is a REAL pain in the tush.

Yea, I'll work as it allows the stuff to get out. But if it's enough of a constant pain, well ... there's other tools to try. At least for certain parts of the workflow.

Neil