Skip to main content
Known Participant
August 16, 2021
Answered

Transform effect + shutter angle is messing up clip position

  • August 16, 2021
  • 18 replies
  • 22221 views

Hello!

 

I am using the transform effect for minor animations because of its motion blur abilities when using shutter angle. Lately however it seems like the shutter angle is messing with the positioning of the anchor point or something like that.

 

For example I wanted an image to rotate a couple times around its own midpoint like a wheel, this worked perfectly fine, then I adjusted the shutter angle to simulate motion blur and all of a sudden the image is rotating around a point somewhere just offscreen. 

 

The same thing happened when I did only a small scale animation, I made an image pop out a bit by having the scale increase in a short amount of time, then I adjust the shutter angle and now it doesn't pop out of its own middle but from some angle in the screen. 

 

The amount of shutter angle does not matter, it either does not happen when it's off or happens all the way when either barely or fully adjusted.

 

Am I goofing? or is this not supposed to happen? Any advice is appreciated!!

Correct answer Jend32771894jr0n

Its incredible - this issue hasnt been fixed for 4 years. Nesting is a disturbing work around that harms the workflow. Adobe please fix a basic effect that hasnt been working for 4 years...

 

Picture 1 and two demomstrates the position of the emoji where the only difference is a shutter angle on 50 on picture 2, which for some annoying reason completely misplaces the emoji to some random place instead of the center

18 replies

Participant
May 18, 2024

"It's not a bug in the software; it is a feature of the way the Transform tool works. Recently, I was working on a 1080p timeline and added an 8K clip. I wanted to zoom in and out on a specific part and also add motion blur. When I added keyframes for scale, everything looked fine. However, when I added a shutter angle, the clip's position got messed up.

The reason is the anchor point. The anchor point is the center of the clip, and different resolutions have different anchor points. You just need to set the anchor point of your clip to match the anchor point of your timeline. For example, the anchor point of an 8K clip is (3840, 2160), and for a 1080p timeline, it is (960, 540). Replace the anchor point numbers of your clip with the anchor point numbers of your timeline.

Then, change the position of the clip to center it, but do not change the position using the same Transform effect. Instead, change the position value from the Motion tab at the top of the Effect Controls panel. You can also add another Transform effect, but make sure to place this new Transform effect before the main Transform effect where you changed the anchor point."

Participant
April 11, 2024

And we're all forgetting that using the transform effect to acheive motion blur is a workaround in itself. Motion blur should be a native option in the "Motion" section like it was in Final Cut 7 15 years ago!

MeKevinB
Known Participant
May 3, 2024

@camerons17794153 You say it's a workaround. You say Motion Blur should be a native option under Motion properties but it isn't. How else can Motion Blur be applied to effects? Are you speaking of adding an adjustment layer and adding the Transform effect to the adjustment layer?

Known Participant
May 3, 2024

I think he means just like after effects still has the option of just toggling the motion blur per layer. The animations I'm doing in premiere are just as easily done with just default motion so I never actually need the transform effect but transform is the only way to add motion blur, how is that not a workaround?

Participant
April 1, 2024

It's year 2024, Adobe.

Participant
April 1, 2024
Inspiring
March 18, 2024

Just to get this out of the way: You can also add the Transform effect to an adjustment layer in Pr or Ae, avoiding nesting/pre-comping if you want.

 

But I thought a summary of my meandering problem solving might help others avoid it. TL;DR: I did all my blurring in Ae with the effect CC Force Motion Blur added to an adjustment layer above every layer I wanted to blur. This way, I could keyframe the blur’s duration and strength in the effect controls. The effect Pixel Motion Blur was just as good but caused more lagging for me. In addition, using a camera tied to a null in Ae to do the scaling and position moves retained my resolution even at extreme scaling, something the Transform effect has an issue with in either app.

 

I'm doing 2D animation and, as in this case, want blur on some layers and not others, often in the same frame at the same time. From one large comp (roughly 5000 x 2500) constructed in Ae, I wanted a shot that starts extremely zoomed in to follow a vehicle driving through a valley with a pan across the comp, then does a swish pan to other vehicles on the other side of comp, and seconds later a quick zoom-out. The vehicles are PNG sequences with wheels animated frame-by-frame that I didn't want motion blur on, but their motion paths are also animated--via Ae. I wanted blur only on the camera moves, the pans and the zoom-out (scale and position). 

 

-- I first decided to render it out as a clip in its full size from Ae to Pr and try applying these camera moves with the Transform effect in Pr. This led to the issue of the randomly shifting frame position.

-- Still in Pr, applying the Transform effect after Nesting the clip or to an adjustment layer above the clip led to the issue of badly decreased resolution when scaling. Compensating for that issue by first scaling up the clip with its own Motion settings eliminated the ability to pan and zoom in the adjustment layer beyond the bounds of the adjustment layer’s frame.

 

-- Since this clip was constructed in Ae, I returned to that and first attempted Ae’s version of the Transform effect added to an adjustment layer. It did not throw my frame positioning off as in Pr but did lower the resolution, though not as badly as in Pr. [If you're not scaling as much as I am, this solution might work for you.]

 

-- I then created a camera and parented it to a null object that I used to set my zooms and pans--this retained my full resolution when I scaled. [I don’t know why; I'm not paid by Adobe to care about why.] Next, the blur; I could not simply turn motion blur on for all layers, because the resulting blur for to the vehicles’ motion path animations would smear out the clarity of their frame-by-frame animation for the entire duration. To be able to keyframe the blur’s duration and strength, I added Pixel Motion Blur to an adjustment layer above everything. I compared it with CC Force Motion Blur, which proved a little less laggy on my previews (both cause mega-slow rendering).

 

If you made it through all of that, I told you it was meandering. I was more intimidated learning Pr than Ae, so I’m sure you can learn at least the steps above in Ae to give you the best blur controls, even if it’s for a single layer. It’s also a very dramatic thing to see precise blur on one layer with no blur on the layer behind it in the same shot. I suggest the tutorial on CC Force Motion Blur by Jake In Motion on YT.

ViktoriaRobotika
Participant
October 24, 2023

Greetings! I'm having the same issue now (position changes if I apply a simple -100 width transform effect to invert the direction of a clip). It started about a month ago, updated to Premiere Pro 2024 and it's still happening with video clips and if I try this transform effect on any Character Animator layer, it disappears completely (but appears on a still frame). The nesting solution is a good work-around and fixes the issue with video clips (thank you so much SK Mobariz30379441ymqj!), and for Character Animator layers the solution seems to be to transform within CA (which can be a pain because this needs to be factored in for eye movements and draggers) and then export it as a media file, then import. But these kinds of work-arounds add up and end up taking a lot of time and it's quite unacceptable given how much the monthly subscription fee costs. Adobe--please fix this soon! Thank you!

Jend32771894jr0nCorrect answer
Participating Frequently
November 29, 2023

Its incredible - this issue hasnt been fixed for 4 years. Nesting is a disturbing work around that harms the workflow. Adobe please fix a basic effect that hasnt been working for 4 years...

 

Picture 1 and two demomstrates the position of the emoji where the only difference is a shutter angle on 50 on picture 2, which for some annoying reason completely misplaces the emoji to some random place instead of the center

Known Participant
November 30, 2023

Unfortunately this is the correct answer, adobe has done nothing except having employees on the forum asking questions and never following up. Apparently workaround = proper solution.

Participant
June 8, 2023

I had that same problem. What you can do is to nest that particular layer and then apply transform effect on that nested sequence. don't open the nested sequence and apply transform effect op the layer or it will repeat the same problem.

Somehow premiere pro gives more priority to nested sequences, that's why when there is a rendering problem due to a lot effects over there, i just nest those layers and then render it.

In this case, you just have to nest that one layer and then apply transform effect upon that nested sequence. I hope it helps.

Richard van den Boogaard
Community Expert
Community Expert
June 8, 2023

Indeed. Nesting will solve a lot of issues in PPro, much like pre-comping does in Ae.

 

For example, you can't do a warp stabilizer and a speed change without nesting.

ericf6288858
Known Participant
March 14, 2023

I was also experiencing this issue. Read thru the thread and didn't see much help. I went back to work and may have just found a fix for this.

I have a 4k clip in a 1080 sequence at 100%. I dropped the transform effect and set the shutter angle first. Then set my scale + position keyframes. This just worked for me. No weird offset, no nesting, and motion blur is great.

Inspiring
April 19, 2023

Thanks for the update. Does your clip position in the exported video match up with your timeline?

ericf6288858
Known Participant
April 19, 2023

Yes. Is that not the case for you?

Inspiring
October 4, 2022

This has not yet been fixed in 22.6, i just discovered it.  Changing shutter angle in Transform effect changes clip position.

Participant
September 8, 2022

Same case here.

The shutter angle messes up the position of a clip. The only workaround working for me is to nest it and use the transform on the nested clip.

I've tried the Scale to Frame size approach without success.

I'd be grateful if a fix for this year-old issue is provided.

Participant
September 8, 2022

It's a pain to always use a nested clip to just have a centered scaling with a shutter angle. I use that kind of animation a lot, so the project gets messed up with workarounds and the render preview becomes slow on every nested clip animation.

Looking forward to a fix.

Participating Frequently
August 17, 2022

Hi, August 2022 and this bug is still not fixed. What do we pay you for monthly?? Buggy software with no solution in sight?
Nesting might resolve the problem, but it reduces your resolution during zoom-in and defeats the advantage of zooming into a higher-res clip.
I'm fed up with buggy software from a company that pockets millions from students and educators every year. This help post was made a full year ago and should have been an easy code fix if it only has to do with sequence/source scaling mismatch.

Participating Frequently
August 17, 2022

On top of that, Premiere is guaranteed to take a 15 second edit, and turn it into an hour-long headache of having to contact customer support about a basic effect that doesn't work properly.

Kevin-Monahan
Community Manager
Community Manager
August 18, 2022

Hi BB,

Effects construction can be exasperating. Sorry! I think it helps to know that video effects work by mathematics: for example, RGB values get plugged into virtual arrays for some effects. Things like that.

 

What's not widely known: the math for effects needs to obey a particular order of operations, referred to as the "render order pipeline." To place certain functions before others in the pipeline (when they cannot behave alongside others), they need to reside in parentheses, which (as I understand it) appear to editors as "nests."

 

I do wonder if you made the nest larger than the native frame size, do you still face the quality issue when scaling?

I am sorry for the frustration; that's what's happening there. I think. All NLEs and mograph programs face similar issues with the render order pipeline.

 

Continue to file bug reports and feature requests. Some issues might be resolved by background operations or other engineering work.

 

I sure hope the team can fix your issues with this effects technique.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio