If there are multiple effects, you might try playing with the order of the effects. Another thing if you are just using it on the one clip, you might nest the clip and apply the swivel effect to the nested sequence.
Hope this helps,
I'll give that a try.
Hi, I have the same problem in Premiere Elements 9.0.
Did you solve the problem?
I'm looking for a solution, too.
Hi there. I still haven't found a solution for this. I swapped to After Effects and did everything there. It works a charm in AE.
Yea AE is the way to go with anything 3d really. The Basic 3d in PPro is well...pretty basic
Basic, yes. But there is a difference between being basic and not working properly.
*UPDATE: Problem solved.
Looking for a solution as well...
I figured out, that it's only getting cropped when the footage's size is equal to or greater than than that of the sequence.
In the picture at the top the sequence has a resolution of 1920x1080. Notice how the left video stays untouched while the right one gets cropped. The left one has a native resolution of 1280x720 while the right one is in 1920x1080.
/edit: Found a solution:
dradeke's workaround should work fine, as well. But if you don't want to nest your clip for whatever reason you might have: You just have to add a "Transform" effect ABOVE your "Basic 3D" one and do all the 'motion' related attributes (scaliing, position, etc...) with this one.
Message was edited by: unihumi
@unihumi you are my hero!
Almost 3 years after you posted this workaround (with the added “Transform” effect) there's still no fix from Adobe and your trick still works.
The whole issue with the cropped “Basic 3D” effect is caused by the render engine of Premiere Pro. If you go to File > Project Settings > General > Video Rendering and Playback: Renderer and switch from “Mercury Playback Engine … Software only” to “Mercury Playback Engine … (OpenCL)” the cropping is gone. BUT(!) if you don't have a supported card renders will take ages with this setting!
So @unihumi's workaround still is the way to go
Still a problem with Premiere Pro CC 2014. What an embarrassment. I'll send a bug report to Adobe. This is ridiculous.
Still a problem in 2015. Fortunately, @unihumi's solution worked for me as well. Thanks!