Answers.Body: <p>To fix extreme crops when using the warp stabilizer effect.</p>
  
  <p>First try the settings</p>
  
  <h2>Modify settings:</h2>
  
  <p>Click on the advanced settings, and choose the following settings:
  Reduce either the smoothness OR 
  Crop Less and Smooth more which is a better option to try first since it does not require a restabilization phase.</p>
  
  <p>(on a side note)
  If you are getting a wobbly effect then that is down to the rolling shutter effect of the camera and to fix that you would need to set Advanced > Rolling Shutter Ripple to Enhanced Reduction.</p>
  
  <h2>For extreme crops:</h2>
  
  <p>Another way I resolve those issues is to 'razor tool' around the area where the biggest 'shakes' occur causing the warp stabilizer to crop drastically.</p>
  
  <p>I then redo the warp stabilizer effect for those two side clips separately, leaving the middle one untouched.</p>
  
  <p>I can now choose to remove the middle clip or employ a different transition effect.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-02T00:30:20.550Z
Answers.LastActivityDate: 2015-02-02T00:30:20.550Z
Answers.UserDisplayName: eLouai
Answers.Body: <p>The root of the issue might be your footage. If you have high amplitude shakes in your video the stabilizer will try to stabilize those as well. That can result in such issues.
  Try different settings, the default values don't work with every type of camera motion.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-17T23:05:59.793Z
Answers.Text: I've tried multiple pieces of footage and changed all the values - even did a completely still clip and it still did that. It works fine on an older version of Premiere, so the clip is fine.
Answers.UserDisplayName: Kevin
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-18T00:05:40.807Z
Answers.Text: Then you might want to try changing the playback engine as AJ Henderson suggested. Could be an error from the GPU engine.
Answers.UserDisplayName: timonsku
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-17T19:11:26.873Z
Answers.LastActivityDate: 2014-12-17T19:11:26.873Z
Answers.UserDisplayName: timonsku
Body: <p>Has anyone seen this problem before? When I apply (and only when I apply) the warp stabilizer, it seems like only 1/10 of the video shows up.</p>
  
  <p>Here's a screenshot:</p>
  
  <p><img src="https://i.sstatic.net/fNUMd.png" alt="enter image description here"></p>
  
  <p>It works on older versions of Premiere for me, and it happens in the latest (CC 2014) no matter what I do or what clips I use from different sources. </p>
  
  <p>Thanks in advance!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-02-02T03:39:35.143Z
Comments.Text: Not truly a solution, but a workaround for me was to change to software rendering from GPU rendering.
Comments.UserDisplayName: Kevin
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-12-09T21:31:12.573Z
Comments.Text: What resolution is the video and the sequence?  Have you tried changing the playback engine?  Do all clips behave similarly?
Comments.UserDisplayName: AJ Henderson
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-12-10T01:30:25.297Z
Comments.Text: 720p, both the clip and sequence. All clips behave the same way.
Comments.UserDisplayName: Kevin
Tags: <premiere><stabilisation>
Title: Warp stabilizer in Premiere Pro cuts off most of the image
UserDisplayName: Kevin
ThreadText: # Warp stabilizer in Premiere Pro cuts off most of the image
  
  (Asked by: username_0 on 2014-12-09)
  
  Has anyone seen this problem before? When I apply (and only when I apply) the warp stabilizer, it seems like only 1/10 of the video shows up.
  
  Here's a screenshot:
  
  ![enter image description here](https://i.sstatic.net/fNUMd.png)
  
  It works on older versions of Premiere for me, and it happens in the latest (CC 2014) no matter what I do or what clips I use from different sources.
  
  Thanks in advance!
  
  **Tags:** premiere, stabilisation
  
  > **Comments:**
  > **username_1**: What resolution is the video and the sequence?  Have you tried changing the playback engine?  Do all clips behave similarly?  
  > **username_0**: 720p, both the clip and sequence. All clips behave the same way.  
  > **username_0**: Not truly a solution, but a workaround for me was to change to software rendering from GPU rendering.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2015-02-02. Score: 2
  
  To fix extreme crops when using the warp stabilizer effect.
  
  First try the settings
  
  ## Modify settings:
  
  Click on the advanced settings, and choose the following settings:
  Reduce either the smoothness OR
  Crop Less and Smooth more which is a better option to try first since it does not require a restabilization phase.
  
  (on a side note)
  If you are getting a wobbly effect then that is down to the rolling shutter effect of the camera and to fix that you would need to set Advanced > Rolling Shutter Ripple to Enhanced Reduction.
  
  ## For extreme crops:
  
  Another way I resolve those issues is to 'razor tool' around the area where the biggest 'shakes' occur causing the warp stabilizer to crop drastically.
  
  I then redo the warp stabilizer effect for those two side clips separately, leaving the middle one untouched.
  
  I can now choose to remove the middle clip or employ a different transition effect.
  
  
  ---
  
  ### Answer by username_3 on 2014-12-17. Score: 2
  
  The root of the issue might be your footage. If you have high amplitude shakes in your video the stabilizer will try to stabilize those as well. That can result in such issues.
  Try different settings, the default values don't work with every type of camera motion.
  
  > **Comments:**
  > **username_0**: I've tried multiple pieces of footage and changed all the values - even did a completely still clip and it still did that. It works fine on an older version of Premiere, so the clip is fine.  
  > **username_3**: Then you might want to try changing the playback engine as AJ username_1 suggested. Could be an error from the GPU engine.  
  
  ---
  
  