Skip to main content
AndrewTheGreat
Known Participant
November 19, 2022
解決済み

Video moves a way outta frame when I playback and returns in the frame as I stop

  • November 19, 2022
  • 返信数 3.
  • 3188 ビュー

Hi. Another Premiere Pro glitch. The footage is iPhone 11 mov-files. The video drivers are up to date. The sequence is old or new - no matter. The video just goes out of the frame a bit when I play back. Tried different preview resolutions. This happens only when CUDA acceleration is on, the Mercury renderer works fine. 

Just watch the video: https://drive.google.com/file/d/1tH_t3cqCe1WDyGazNBe--6UXCOKf1-DI/view?usp=share_link

解決に役立った回答 Ali Jaber

Something similar happens with me when I add a "Warp Stabilizer" effect to a resized 4K clip in a full HD sequence. My workaround is this: I reset the motion, then add a "Transform" effect, and scale down the clip using it, and it magically works...

Give it a try and see if it works in your case.

返信数 3

AndrewTheGreat
Known Participant
March 2, 2023

Hi. An update on this. Premiere Pro 2023.2? this issue is STILL there with EVERY 4k video with warp stabilizer applied. I had a wonderful chat with Adobe Support, spent about 4 hours with them to try and resolve this issue and this did not help. I sent the files in question (both IPhone and downloaded 4k footage) and they say they had no problem with those. So I suppose the problem lies in my Premiere Pro settings but we didn't find which ones. The only time it seemed to get fixed was when I removed all the third party plugins folder from the Adobe Common folder. But I do not have any distructive plugins there and I did not actually use them a lot - only the AtomX transitions, Film Impact transitions and the Misterhorse Premiere Composer (transitions and some simple motion graphics mainly). All of them are found either under the Effects tab or as a separate tab from the Extensions menu. And after I removed those plugins and created a new sequience to test the files out, it worked. But for a minute or two - then it started back again even WITHOUS all those third party plugins. So I suppose the problem appears after womething happens in a freshly installed PP not connected with third party plugins. As far as I remember, the next step after I removed the plugins and checked the 4k footage with Warp Stabilizer was adding my custom S-key shortcut for "Add edit" command in the keyboard shortcuts menu - after this every 4k footage started acting glitchy again. Yeah, I don't see a connection here either.

So for now the only way to fix this is adding .1 to a footage scale.

By the way, I forgot to mention that by default media scaling set to "Set to frame size" for every footage in PP preferences, so any 4k getting into my sequences is automatocally set to Scale 50. May be this is why Adobe Support could not reproduce this issue, so please check.

Once again: set the default media scaling set to "Set to frame size" (Preferences > Media), create a 1080p sequence, add a 4k footage and keep the sequence settings for it, add a warp stabilizer to the footage and stabilize it, Play the stabilized footage.

Community Expert
March 2, 2023

Have you tried my workaround: Reset motion, add transform effect with scale set to 50%, after the transform effect add the Warp Stabilizer.

Let us know if it works for you.

R Neil Haugen
Legend
November 19, 2022

This forum is still mostly user-to-user help. Thanks for posting here, as it does give the rest of us an idea of issues, and means someone else with this will see it.

 

But PLEASE ... post this in great detail over on their Premiere Pro UserVoice  site, as for Premiere, that is still the best input portal to the devs. All posts there are manually logged into their internal system, assigned to the specific team involved.

 

Then post a link on this thread to that UV post, so others can go upvote & comment there.

 

And yes, I've talked with the engineers that do this loggin-in process in-person. Their one complaint ... the vast majority of bug/performance posts do not give NEARLY the detail needed for helping them to isolate the problem. So both of you should post on (hopefully) the same posting there.

 

And "X is broke, fix it ... " which is by far the most common type of post, is essentially useless. If they don't have a system where X is broke, that ain't helpful, is it? So give your system specs, the media/effects involved ... steps that cause the problem ... as these types of things are as much a nightmare for the devs as they are for us.

 

Neil

Everyone's mileage always varies ...
AndrewTheGreat
Known Participant
January 17, 2023

I posted it, spoke to tech suppurt wrote letters to adobe. 2023, the latest PP version and I still have to use workarounds because the problem is still there.

AndrewTheGreat
Known Participant
January 20, 2023

If you use the free utility ShutterEncoder to convert those files to CFR, constant frame rate, do you get proper performance?

 

Long-GOP clips force the computer to create quite a few frames at once before they can complete any specific frame, it's the nature of the compression format.

 

So I'm wondering if this is due to that whole thing of sections of the video being in frame groups. If converting that VFR to CFR 'fixes' the issue, that would seem to be the case.

 

Neil


The problem lies in the IPhone footage only. I have lots of different videos from different cameras and with a different framerate within one shooting and none of them has any problems. I tested it in all the poissible ways. Should I use IPhone footage, there is what is in the screenshots down below (in them you can see what happens when I play back or scrab trough the timeline'change scale).

Ali JaberCommunity Expert解決!
Community Expert
November 19, 2022

Something similar happens with me when I add a "Warp Stabilizer" effect to a resized 4K clip in a full HD sequence. My workaround is this: I reset the motion, then add a "Transform" effect, and scale down the clip using it, and it magically works...

Give it a try and see if it works in your case.

AndrewTheGreat
Known Participant
November 19, 2022

This worked, thanx. There's an obvious problem in Premiere Pro though, this shouldn't get one use any workarounds...