You want the stabalizer to be able to see all the frames in the footage to calculate the best results. That's why nesting works around the issue, as all effects inside a nest are rendered fully before any effects applied to the nest are rendered.ĭo it the other way round though! Nest the clip, apply 'warp stabalizer' inside the nest, then adjust the speed of the nest. If you have 'speed' applied to the clip, when 'warp stabalizer' does its calculation pass, it will be looking at the frames after the speed change has applied.īut since it does the rendering earlier in the effects order than 'speed', it would render incorrectly as it's basically looking at the wrong frames when doing its maths. While the actual rendering is done as any other effect (and thus will occur before 'speed,') it also has to do an initial pass to calculate the stabalization – but that pass is done after rendering any other effects applied to the clip. I ran the warp stabilizer on the first clip, it analyzed and worked great, then I dragged the effect to the second clip, it flashes Initializing and then the blue banner says click analyze, but every time I click it, it doesn’t analyze the clip, it just does the initializing, then goes back to the blue banner. 'Warp stabalizer' is also a unique effect. 'Speed' is a unique effect in Premiere, it's always applied at the end of the effects rendering order - this is to make sure that any other effects you have applied to the clip work correctly. This is kind hard to explain, but bare with me as I try.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |