Answers.Body: <p>The stabilizer doesn’t “care” about the fidelity of time it’s processing.  It looks at the sequence as a whole, calculates the vector magnitude of pixel motion from one frame to the next, and then translates or warps (user choice) each frame in the opposite direction.</p>
  <p>A 3000 FPS video looks the same to the stabilizer as a 30 FPS one.</p>
  <p>HFR video is great at capturing temporal fidelity, but higher temporal fidelity of a shaky camera only gives you higher-frequency camera rotation noise.</p>
  <p>To smooth out the noise, you actually want to blend the frames together.  This is possible in Resolve by blending together nearby frames with motion blur, either through the motion tab of the color page, or as an edit effect.  Last I checked, the color page couldn’t simulate greater than a 360 degree shutter, however.</p>
  <p>But all of this happens naturally, in camera, when you use a lower frame rate and longer shutter speed.  So in most cases, using HFR works against you.</p>
  <p>You see the effect more commonly in time lapse videos because they are essentially the opposite of HFR ones, and high frequency rotational noise is naturally filtered out because each sample is spaced further apart temporally.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-05-15T09:50:35.493Z
Answers.Text: HFR provides signal *and* noise, and excess frames could be used as input for stabilization. In the simplest case, if I shoot in 120fps and deliver in 30fps, point tracker can at least choose from four frames the one that deviates the least. I wonder if this is used by Instagram’s Hyperlapse, which doesn’t produce extremely shaky footage despite being ultimately the same case (stabilization + speed-up discarding excess frames).
Answers.UserDisplayName: Anton Strogonoff
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-05-15T10:20:33.377Z
Answers.Text: BMD are very open to feature requests and recommendations posted on the feature request subforum of their website.  I’ve personally made requests which were implemented in the next point release.  In one simple case, it took them less than three weeks.  It can’t hurt to ask.  They won’t comment publicly, but simple, reasonable requests with community support usually receive prompt attention. Just watch the release notes.
Answers.UserDisplayName: Jason Conrad
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-05-23T19:12:09.403Z
Answers.Text: I guess the answer is “no”, but the question I should’ve asked is “how to achieve this with some workaround or another”…
Answers.UserDisplayName: Anton Strogonoff
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-05-13T09:58:57.920Z
Answers.LastActivityDate: 2022-05-13T09:58:57.920Z
Answers.UserDisplayName: Jason Conrad
Body: <p>DaVinci controls regarding stabilization are very limited, and there seems to be no documentation on how to achieve the following.</p>
  <ul>
  <li>Given moderately shaky 100fps footage, one wants to</li>
  <li>produce a 30fps timeline,</li>
  <li>without slowing footage down (no slow-mo is needed for that bit), but</li>
  <li>making the stabilizer <em>use excess framerate to provide better stabilization</em>.</li>
  </ul>
  <p>An example of similar approach is various timelapse apps, shooting a normal framerate video and produce a very smooth sped-up outcome.</p>
  <p>I have tried using stabilizer on the clip interpreted at 30fps and sped-up 300%, and on the same clip interpreted at 100fps without the speed-up. I have tried cranking up the Smooth parameter and turning off GPU acceleration. However, the outcome doesn’t seem to be improving, which makes me think the Resolve’s stabilizer is not designed to use excess framerate when it’s available.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-30T21:03:26.573Z
Comments.Text: Maybe you actually want some hardware like this: https://store.dji.com/de/shop/handheld-gimbals (I know it's too late if the shots are made, but some recording mistakes are hard to fix post-production)
Comments.UserDisplayName: U. Windl
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-01-31T09:27:27.313Z
Comments.Text: @U.Windl I agree that it’s best to stabilize during the shoot.
Comments.UserDisplayName: Anton Strogonoff
Tags: <davinci-resolve><framerate><post-production><stabilisation>
Title: Is it possible to use high framerate to achieve better stabilization outcomes in DaVinci Resolve?
UserDisplayName: Anton Strogonoff
ThreadText: # Is it possible to use high framerate to achieve better stabilization outcomes in DaVinci Resolve?
  
  (Asked by: username_0 on 2022-04-29)
  
  DaVinci controls regarding stabilization are very limited, and there seems to be no documentation on how to achieve the following.
  
  * Given moderately shaky 100fps footage, one wants to
  * produce a 30fps timeline,
  * without slowing footage down (no slow-mo is needed for that bit), but
  * making the stabilizer *use excess framerate to provide better stabilization*.
  
  An example of similar approach is various timelapse apps, shooting a normal framerate video and produce a very smooth sped-up outcome.
  
  I have tried using stabilizer on the clip interpreted at 30fps and sped-up 300%, and on the same clip interpreted at 100fps without the speed-up. I have tried cranking up the Smooth parameter and turning off GPU acceleration. However, the outcome doesn’t seem to be improving, which makes me think the Resolve’s stabilizer is not designed to use excess framerate when it’s available.
  
  **Tags:** davinci-resolve, framerate, post-production, stabilisation
  
  > **Comments:**
  > **username_1**: Maybe you actually want some hardware like this: https://store.dji.com/de/shop/handheld-gimbals (I know it's too late if the shots are made, but some recording mistakes are hard to fix post-production)  
  > **username_0**: @U.username_1 I agree that it’s best to stabilize during the shoot.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2022-05-13. Score: 1
  
  The stabilizer doesn’t “care” about the fidelity of time it’s processing. It looks at the sequence as a whole, calculates the vector magnitude of pixel motion from one frame to the next, and then translates or warps (user choice) each frame in the opposite direction.
  
  A 3000 FPS video looks the same to the stabilizer as a 30 FPS one.
  
  HFR video is great at capturing temporal fidelity, but higher temporal fidelity of a shaky camera only gives you higher-frequency camera rotation noise.
  
  To smooth out the noise, you actually want to blend the frames together. This is possible in Resolve by blending together nearby frames with motion blur, either through the motion tab of the color page, or as an edit effect. Last I checked, the color page couldn’t simulate greater than a 360 degree shutter, however.
  
  But all of this happens naturally, in camera, when you use a lower frame rate and longer shutter speed. So in most cases, using HFR works against you.
  
  You see the effect more commonly in time lapse videos because they are essentially the opposite of HFR ones, and high frequency rotational noise is naturally filtered out because each sample is spaced further apart temporally.
  
  > **Comments:**
  > **username_0**: HFR provides signal *and* noise, and excess frames could be used as input for stabilization. In the simplest case, if I shoot in 120fps and deliver in 30fps, point tracker can at least choose from four frames the one that deviates the least. I wonder if this is used by Instagram’s Hyperlapse, which doesn’t produce extremely shaky footage despite being ultimately the same case (stabilization + speed-up discarding excess frames).  
  > **username_2**: BMD are very open to feature requests and recommendations posted on the feature request subforum of their website.  I’ve personally made requests which were implemented in the next point release.  In one simple case, it took them less than three weeks.  It can’t hurt to ask.  They won’t comment publicly, but simple, reasonable requests with community support usually receive prompt attention. Just watch the release notes.  
  > **username_0**: I guess the answer is “no”, but the question I should’ve asked is “how to achieve this with some workaround or another”…  
  
  ---
  
  