So I’m enlarging some sections of footage with the mesh warp filter. Only thing, when ever it is between keyframes it doesn’t look as much enlarged, even though it still is. Then it hits a key frame and goes 100% enlarged. I did change the amount of rows and cols after distortion, could this have caused the problem? This is happening with every keyframe
frame before keyed, then keyed
Might not be too visible in still, but the right belly button is more to the left.
Is the mesh animated in some way? The spatial interpolation of the nodes is always linear, so it may look weird at frames inbetween. Short of that, if you are working with compressed footage some artifacts may simply change the influence regions too much. Hard to tell from the stills indeed…
Mylenium
Don’t ask me, I was told I was getting HD footage and received 720x480, not what I thought I’d be working with. .○
I can tell it’s linear, but its a visible jump of several pixels, not some linear pop like you’d normally see with animation. Its like I took the filter and turned the opacity down to 60% on non keyframes for the mesh distortion, then on keyframes it goes 100%. I’d imagine the footage would effect it, but not like this.
I sort of got it working though. I made keyframes the frame after keyframes and deleted the original frames, that stopped the popping (for the most part), but I had to do that on a lot of frames. Now I need to do it again on another section of the film, and I’m getting those pops again.
Mmh, that’s indeed pretty weird. Haven’t used the effect in eons, but my gut tells me, that this is not what it should do. Since you mention some sort of ghosting/ opacity fade: Is your footage interpretation okay? Do you comp settings match? Do you use time-remapping? Could be field issues or framerate mismatch as well.
Mylenium
How about just rendering one frame of your footage to see if you are still getting the glitch if you use a still image? Could be a way to determine if it is the way your footage is interpreted that is causing something funky to go on.
Pete.
I was just using the % stuff as an example that it looks like it’s dialing down the effect on non keyed frames. And it is doing the same thing on the other part of the footage I’m working on.
That first post is two different frames rendered out, same error.
I had the effect on an adjustment layer because I needed to effect a bunch of layers. But on this other area of footage I have it on the footage layer itself and now it doesn’t seem to be doing that error (at least not yet, only added a few keyframes). I’m going to precomp stuff to see if it fixes the problem on the other area. But I don’t get why it was doing that on an adjustment layer.
Displacement effects need to access the layer’s native info about its bounds to gather info on pre-/post-processing positions and pinning. That may not work properly with adjustments. I think it’s some sort of bug or undocumented feature that is screwing you, most likely the borders being expanded somehow on the adjustment layer, leading to incorrect calculations of the pixel proximities.
Mylenium
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.