Warp Stabilizer stalls and sometimes freezes Premiere

Hi! 
I tried the following and it worked,

- Nesting the sequence

- Opening the nest 

- Applying Warp Stabilizer within the nested sequence. 

Hope this works!

Try to imagine your computer is Hamlet, and you are the playwright... ( Shakespeare )

I hope you are right. But I kinda think you're missing the main point, and the cummulative effect of what you're trying to do.  Reminds me of Hamlet's 3rd soliquey 

To be, or not to be: that is the question:
Whether 'tis nobler in the mind to suffer
The slings and arrows of outrageous fortune,
Or to take arms against a sea of troubles,
And by opposing end them? To die: to sleep;
No more; and by a sleep to say we end
The heart-ache and the thousand natural shocks
That flesh is heir to, 'tis a consummation
Devoutly to be wish'd. To die, to sleep;
To sleep: perchance to dream: ay, there's the rub;
For in that sleep of death what dreams may come
When we have shuffled off this mortal coil,

Thank you everyone. 

I'm realizing that warp stabilizer is a last ditch thing and hugely intensive. 

This was a walking video that had to be done and hopefully I'll never have to do this again. 

I'l sitting at the computer and it seems to be handling it with me watching so it must be some issue relating to sleep on the computer side. 

Tks again,

I think you're expecting too much of WS to figure out multiple minutes of footage - are you trying to achieve a hyperlapse style effect? Perhaps look at Microsoft Hyperlapse which might be more in line with what you are trying to achieve.

As you can tell, using warp stabilizer is very demanding on your computer resources. Everyone experiences the same thing... using warp stablizer is very demanding on ALL computer systems.

Why ? Because it is comparing all your pixels and the movement of those pixels, and trying to make them move less ( less shaky footage within frame ). In order to do this it has to perform the task and 'zoom in' slightly at the end of the operation ( discarding the pixels along the edges of your frame and replacing the frame with the new stabilized frame). That takes a lot of computing power.

Using H264 ( which your go pro gives you ) is also very demanding on your computer resources. It is a codec that is meant ( originally and even today ) for 'viewing' a video ( highly compressed ). Luckily most modern computers are so powerful it is possible to edit H264 in some cases. You will find that the higher your resolution ( 4K compared to full HD ) the more demanding it is on everyone's computer.

You are combining two very demanding things on your computer.

Even if you use a proxy ( instead of H264) you will find that warp stabliizer is very demanding on your computer.

If the demand on the computer exceeds the capacity of the computer vs. the chore it is given, it will freeze up or crash, etc.

Do a test, is my suggestion. Make a few cuts in your mp4 file, like one cut every 5 minutes... just do a few cuts.

Then use warp stablizer on those individual 5 minute clips you now have for your test. See if it works.

If it does work, just do that for the entire video you are working on.

🙂

Warp was designed as a last-ditch salvage tool for short clips you can't possibly reshoot. It is probably the most hardware intensive tool in Premiere.

Using it on a single hour long clip will hammer most any massive system. Don't use it like that.

Break that into sections no more than five minutes a clip. Work each one. When it's good, render and replace to a good intraframe format/codec such as Cineform, DNxHd/R, or ProRes.

Then do your editing with the replaced media.

Neil