Warp Stabilizer Jump/cut

[Larsmulder99]

Hey everyone,

I'm editing underwater footage of dolphins that was shot back in 2015. The footage was only shot at 24 fps to get a cinematic look (don't know if this is relevant for this topic). The footage is shot on a GoPro and pretty shaky. So I tried to apply the warp stabilizer effect to make it smoother. It works pretty good, but in every clip I try to stabilize there is a jump/cut. Does anyone have an idea why this is happening and how to get rid of it?

In the attached video at roughly 4 sec there is a jump/cut.

Thanks in advance

[Ann Bens]

If its very shaky then yes it wont be perfect

What setting did you use.

IMO underwater footage is best shot at high framerate.

Low framerate usually require the use of a trypod to get smooth footage. Bit tricky underwater 😉

[Larsmulder99]

I used 15% smoothness, Subspace Warp, Stabilize Crop Auto-scale and Detailed Analysis. Doesn't have to be perfect, but the cut is a bit annoying because I got to edit that out.

Indeed underwater footage is best in high framerate, a client of mine filmed this and wants me to edit it. 

[Ann Bens]

Can you post the original clip.

[Larsmulder99]

Sure, I'll do that in a minute. Got to resize it to upload

[Ann Bens]

OK

[Larsmulder99]

Here you go

[Ann Bens]

This trimmed clip is 30p with a lot of freeze frames.

[Larsmulder99]

Oh yea, this one is 30fps. Freeze frames?

[ah_photo]

Was the original media shot in 24p and then you edited in a 30p sequence? If so, that's going to duplicate the last frame every 5 frames to make the 24 -> 30 conversion possible. I imagine this could throw off warp stabilizer's analysis.

[Ann Bens]

Scroll frame by frame then you will see it.

[Larsmulder99]

Is that what causes the cut in the warp stabilizer?

[Ann Bens]

If you look closely the glitch is exactly on a freeze frame.

[Ann Bens]

so answers dont get 'burried'.

[Qengineering]

Your file plays at 30.0 fps but was shot at 24 fps, every 5th frame is a repeat of the frame proceeding it.

For any chance of stabilizing this (still no guarantees), you'll have to fix the repeat frame issue.

When I encounter this, I remove the frames manually -

right-click on the original clip in your Project window

select New Sequence from clip

on V2 add a single frame Black clip above the first repeated frame

advance 5 frames forward and repeat with another black clip on V2

repeat for as many times as you can tolerate 😉

now, copy the black frames you added and on V2, paste at the next freeze freeze frame (slide left-right as necessary to position correctly), repeat to end of sequence

Now hightlight (select) all black clips on V2

press option-down arrow (Mac) or equivalent on PC to move black clips to V1

press option-up arrow to return black clips to V2 (this has removed the freeze frames on V1 and left holes)

shift-Delete the highlighted black clips on V2 (this colapses the holes on V1)

Export this sequence as a new movie file

bring new movie file back into your project, right-click and choose Modify > Interpret Footage

under Frame Rate select Assume this frame rate and type in 23.976, click OK

work with is clip in your project

[Steve Griffiths]

One initial simple solution would be to select these clips in the bin > right click and select 'modify' > interpret footage > and change to assume frame rate 30 (or whatever exactly matches you sequence settings). Yes this will speed up the footage by around 18% but should get rid of the warp stabilizer jump cuts.

Another possible way (don't know if this will work though never tried!!):

Right click the clip in your sequence < select 'speed/duration'. Leave the speed setting at 100% but change 'time interpolation' to 'optical flow'. This will do a fairly good standards conversion on the 24fps clip and then give the warp stabilizer a less 'stuttery' scene to work with. This might work if the Premiere Pro rendering pipline processes any speed effects before other effects (like warp stabilizer).

[Steve Griffiths]

... you could also change your sequence to 24fps.

[Larsmulder99]

That's the thing, my sequence is 24 fps. I'll try the second solution and see if that works. Thanks