# Variable Frame Rate recordings

**URL:** <https://community.wowza.com/t/variable-frame-rate-recordings/55020>\
**Category:** Wowza Streaming Engine\
**Tags:** recording\
**Created:** [April 20, 2020, 10:30pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020 "2020-04-20T22:30:21Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryce\_Seifert](https://avatars.discourse-cdn.com/v4/letter/b/7feea3/32.png) [@Bryce\_Seifert](https://community.wowza.com/u/Bryce_Seifert)\
**Post date:** [April 20, 2020, 10:30pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/1 "2020-04-20T22:30:21Z")

</div>

Despite sending constant frame rates from our encoder, and zero dropped frames being reported, the Wowza Live stream recordings come back as VFR 100% of the time. Any idea what would cause this? The dips in frame rates are usually very slight as well.  
Typical min/max rates:

Encoder settings:

---

<div class="post-metadata">

**Author:** ![Bryce\_Seifert](https://avatars.discourse-cdn.com/v4/letter/b/7feea3/32.png) [@Bryce\_Seifert](https://community.wowza.com/u/Bryce_Seifert)\
**Post date:** [April 21, 2020, 2:14pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/2 "2020-04-21T14:14:45Z")

</div>

@Rose Power-Wowza Community Manager This is regarding Frame Rate, not bit rate. Even with that selected frame rate remains unaffected.

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [April 22, 2020, 6:00pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/3 "2020-04-22T18:00:12Z")

</div>

Oh, my sincere apologies for misreading that! Let me look into this for you right away.

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [April 22, 2020, 6:34pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/4 "2020-04-22T18:34:08Z")

</div>

@Bryce Seifert the engineers would like to know if you’re recording source stream or transcoder output?

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [April 22, 2020, 7:28pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/5 "2020-04-22T19:28:58Z")

</div>

So, this is very peculiar behavior and the engineers would like to ask you to submit a support ticket in order to take a closer look at this. We have an idea of what may be causing it on our end, but will require the ticket to replicate and test. Thanks so much.

[https://www.wowza.com/support/open-ticket](https://www.wowza.com/support/open-ticket)

---

<div class="post-metadata">

**Author:** ![Bryce\_Seifert](https://avatars.discourse-cdn.com/v4/letter/b/7feea3/32.png) [@Bryce\_Seifert](https://community.wowza.com/u/Bryce_Seifert)\
**Post date:** [April 22, 2020, 7:35pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/6 "2020-04-22T19:35:42Z")

</div>

Got it. Submitted under ticket 354939

---

<div class="post-metadata">

**Author:** ![Rose\_Power-Wowza\_Com](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/rose_power-wowza_com/32/431_2.png) [@Rose\_Power-Wowza\_Com](https://community.wowza.com/u/Rose_Power-Wowza_Com)\
**Post date:** [April 22, 2020, 8:29pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/7 "2020-04-22T20:29:01Z")

</div>

Thanks! I’ll keep an eye on it.

---

<div class="post-metadata">

**Author:** ![Bryce\_Seifert](https://avatars.discourse-cdn.com/v4/letter/b/7feea3/32.png) [@Bryce\_Seifert](https://community.wowza.com/u/Bryce_Seifert)\
**Post date:** [April 22, 2020, 7:15pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/8 "2020-04-22T19:15:03Z")

</div>

No worries! It is a source stream recording.

---

<div class="post-metadata">

**Author:** ![Christian\_Siegert](https://avatars.discourse-cdn.com/v4/letter/c/a3d4f5/32.png) [@Christian\_Siegert](https://community.wowza.com/u/Christian_Siegert)\
**Post date:** [June 25, 2020, 10:18am UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/9 "2020-06-25T10:18:13Z")

</div>

Hello, Exist a Fix for this issue ? We have the same. Our Encoder send 50FPS (CONSTANT) and the recording is Variable between 45 and 55 Frames.

```auto
Frame rate mode : Variable
Frame rate : 50.000 FPS
Minimum frame rate : 45.455 FPS
Maximum frame rate : 55.556 FPS

```

---

<div class="post-metadata">

**Author:** ![Christian\_Siegert](https://avatars.discourse-cdn.com/v4/letter/c/a3d4f5/32.png) [@Christian\_Siegert](https://community.wowza.com/u/Christian_Siegert)\
**Post date:** [July 8, 2020, 12:17pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/10 "2020-07-08T12:17:20Z")

</div>

Hello,

can you please post the result from this ticket. We have the same issue.

---

<div class="post-metadata">

**Author:** ![Bryce\_Seifert](https://avatars.discourse-cdn.com/v4/letter/b/7feea3/32.png) [@Bryce\_Seifert](https://community.wowza.com/u/Bryce_Seifert)\
**Post date:** [July 8, 2020, 12:52pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/11 "2020-07-08T12:52:15Z")

</div>

@Christian Siegert

I suspect the problem stems from how we handle the internal timing of frames. Internally we keep track of frames on a millisecond precision timescale and unfortunately most video solutions natively run on a 90KHz time scale which introduces inherent rounding issues when translating to round milliseconds.

If we look at the reported frame rate max and min, you can see how this manifests:  
1/29.412 = 0.339 (aka 34ms)  
1/30.303 = 0.330 (aka 33ms)

We have to have an occasional 34ms frame, because we can’t have a 33.33333333333333333 ms frame as we would want to.

---

<div class="post-metadata">

**Author:** ![Christian\_Siegert](https://avatars.discourse-cdn.com/v4/letter/c/a3d4f5/32.png) [@Christian\_Siegert](https://community.wowza.com/u/Christian_Siegert)\
**Post date:** [October 28, 2020, 2:56pm UTC](https://community.wowza.com/t/variable-frame-rate-recordings/55020/12 "2020-10-28T14:56:04Z")

</div>

> [@Bryce\_Seifert](#):
>
> I suspect the problem stems from how we handle the internal timing of frames. Internally we keep track of frames on a millisecond precision timescale and unfortunately most video solutions natively run on a 90KHz time scale which introduces inherent rounding issues when translating to round milliseconds.
> 
> If we look at the reported frame rate max and min, you can see how this manifests:  
> 1/29.412 = 0.339 (aka 34ms)  
> 1/30.303 = 0.330 (aka 33ms)
> 
> We have to have an occasional 34ms frame, because we can’t have a 33.33333333333333333 ms frame as we would want to.

Would I get a fixed framerate if I enter a value other than 50 in the encoder, or could the streaming engine not be fixed (or made configurable), so that this problem no longer exists.
