Project has an unwanted glitch that comes and goes

[Nicholas23048646s80t]

Hi there,

I edited a project with the masking effect. Basically I took three different shots and brought them together in the same frame. Then I used the masking effect to cut out some of the background, keyframed some of the background seeping out of the image, then applied a transition effect so the seperate shots enter the frame smoothly. When I play the video back, during the transition portion for only a few seconds, a weird glitch occurs where it seems to duplicate the frames, and then ignores the keyframes for the background to be cut out. Then it returns to normal. I checked in the timeline and disabled different tracks to see where this momentary glitch was coming from, and the individual clips played normally when they were enabled seperately. Another odd thing is I successfully exported the project once without the glitch peresent, however I am trying to export it again in a different format and the problem seems to have reoccured. Anyone know what could be cuasing this?

[Nicholas23048646s80t]

To clarify this is Premiere Pro

[Joëlle Bh]

Hello Nicholas,

Please share with us your footage source and your pc settings (operating system,ram etc.)

[Nicholas23048646s80t]

Hi Joelle, 

I am on a Mac Mini MacOS Monterey, Chip: Apple M1. My footage source is an mp4 file of a project I previously edited a few years ago. 

[Richard M Knight]

Have you tried rendering that section of the timeline?

[Nicholas23048646s80t]

Hi Richard,

I did. Oddly enough it seems the only time it exported correctly was when I didn't render that section. However, it seems that trick didn't work the second time, so I tried rendering with the same result. The glitch seemed to come up at a different place in the video when I rendered it however. 

[Peru Bob]

Delete the Media Cache and Media Cache files:
https://community.adobe.com/t5/premiere-pro/faq-how-to-clear-your-media-cache-in-30-seconds-in-premi...

If that doesn't work, try resetting the preferences:
https://community.adobe.com/t5/premiere-pro/faq-how-to-reset-trash-preferences-in-premiere-pro/td-p/...

If that doesn't work, try resetting the Workspaces:
Reset a workspace
Reset the current workspace to return to its original, saved layout of panels.
1. Do one of the following:
• Click the Workspace menu icon and select Reset to Saved Layout.
• Choose Window > Workspace > Reset to Saved Layout.
from here:
https://helpx.adobe.com/premiere-pro/using/workspaces.html

If that doesn't work, try Preferences > Audio Hardware and set Input to None.

If that doesn't work, try creating a new project and import the old one into it.

[Nicholas23048646s80t]

Hi Bob, 

Unfortunately none of those steps did the trick

[Nicholas23048646s80t]

Here is a screenshot of what it should look like. 

[Nicholas23048646s80t]

However it uses the shape of the right frame's mask, and repeats the image in the middle frame (depending on the export settings the glitch seems to happen at different points).

[Steve Griffiths]

Is the 'glitch' only appearing during transitions that are applied to a layer that has a mask?

If so this is a recurring Premiere Pro bug.

Delete your transitions (hopefully they are dissolves) and replace them with keyframed 'opacity' changes in your Effects Controls' panel. One key frame for 0% opacity where you want the dissolve to start and a keyframe at 100% where you want to end the dissolve.

* you may also need to *first* nest this layer and then add the opacity change to the nested layer in your main sequence.

[Richard M Knight]

Not sure if it will work in your case but I find nesting clips between adding effects often helps.

[Nicholas23048646s80t]

Unfortunately that didn't work. Could it have something to do with the frame hold? Every time the next frame comes on I added a frame hold to the previous video. I even tested out and made a completely different effect, and  the same glitches occur. 

[Peru Bob]

Instead of using Frame Hold, use the camera icon to get a Frame Grab.

[patrickd55649325]

Hello
I had the same issue, and I found out that it was a denoiser effect wich was before that did that.