# Fragment duration greater than suggested range of 1-4 seconds WARN

**URL:** <https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042>\
**Category:** Wowza Streaming Engine\
**Created:** [November 6, 2011, 10:04pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042 "2011-11-06T22:04:21Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![sherly\_adams](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@sherly\_adams](https://community.wowza.com/u/sherly_adams)\
**Post date:** [November 6, 2011, 10:04pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/1 "2011-11-06T22:04:21Z")

</div>

Hello All,

Just after wowza is restarted I see the following errors in the logs. Is there any specific performance effects of this error?

We do live streaming over jwplayer. What would be a suggested “keyframe interval” in FMLE settings?

Thanks in advance.

I get a

```auto
WARN	server	comment	2011-11-06	01:26:32 -	14963.916	-	LiveStreamPacketizerSmoothStreaming.handlePacket[live/_definst_/credife]: 
Fragment duration greater than suggested range of 1-4 seconds. 
Adjust keyframe interval accordingly: Fragment durations: [4.9,4.9,4.9]

```

---

<div class="post-metadata">

**Author:** ![Randall\_Auriemma](https://avatars.discourse-cdn.com/v4/letter/r/85e7bf/32.png) [@Randall\_Auriemma](https://community.wowza.com/u/Randall_Auriemma)\
**Post date:** [November 6, 2011, 11:58pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/2 "2011-11-06T23:58:38Z")

</div>

Set keyframe interval between 1-4 seconds in FMLE.

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [July 3, 2012, 3:57pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/3 "2012-07-03T15:57:31Z")

</div>

Try changing -g (gop) to 60 and add -r (FPS) set to 30.

```auto
-r 30 -g 60

```

or

```auto
-r 24 -g 48

```

I.e., -g = -r\*2

That should give you a key frame frequency of 2 seconds, which is ideal.

Richard

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [July 3, 2012, 5:22pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/4 "2012-07-03T17:22:29Z")

</div>

Reading from the top, that WARN line will go away if you remove “smoothstreamingpacketizer” from the Application.xml /LiveStreamPacketizers.

If you are only using a Flash RTMP player, which is what JW Player is, you can remove all the packetizers and that will save you some overhead

Richard

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [January 20, 2013, 1:08pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/5 "2013-01-20T13:08:16Z")

</div>

David,

Closer to a little, but probably measurable.

Richard

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [May 31, 2013, 6:15pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/6 "2013-05-31T18:15:38Z")

</div>

A 2 second key frame frequency is gop / fps. For example 60 (gop) / 30 (fps) = 2 second key frame frequency.

b-frames can be a problem. Try with and with b-frames.

Richard

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [June 1, 2013, 12:44pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/7 "2013-06-01T12:44:15Z")

</div>

It is just what we have found to work for smoothstreaming in Silverlight players. You will have to see what works for you, and what trade-offs you have to or are willing to make.

Richard

---

<div class="post-metadata">

**Author:** ![sherly\_adams](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@sherly\_adams](https://community.wowza.com/u/sherly_adams)\
**Post date:** [November 8, 2011, 3:21pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/8 "2011-11-08T15:21:54Z")

</div>

> Set keyframe interval between 1-4 seconds in FMLE.

I can ask the streamers to follow that rule. But if they do not do it would there be any consequence to viewers or wowza service health?

Thanks

---

<div class="post-metadata">

**Author:** ![David\_Good](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@David\_Good](https://community.wowza.com/u/David_Good)\
**Post date:** [January 19, 2013, 11:17pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/9 "2013-01-19T23:17:55Z")

</div>

Richard

You state “… you can remove all the packetizers [that you’re not using] and that will save you some overhead.”

So, if, for example, I never use smoothstreaming for anything I should remove that from all the Application.xml files I have? And that should save me some overhead.

Can you elaborate on exactly what kind of “overhead” this will save me? I’m not looking for hard numbers (as I know that depends on each unique setup) but just a general idea for my general understanding would be greatly appreciated. Is this overhead a “little” or “a lot”? A “little” meaning that I likely will notice no significant difference, and “a lot” meaning that I will be able to get more out of the server if I remove the unused packetizers.

Thanks!

David L Good

---

<div class="post-metadata">

**Author:** ![David\_Good](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@David\_Good](https://community.wowza.com/u/David_Good)\
**Post date:** [January 20, 2013, 11:40am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/10 "2013-01-20T11:40:41Z")

</div>

That’s good enough for me. Thanks!

---

<div class="post-metadata">

**Author:** ![Reza\_Rizvi](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@Reza\_Rizvi](https://community.wowza.com/u/Reza_Rizvi)\
**Post date:** [May 31, 2013, 11:57am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/11 "2013-05-31T11:57:12Z")

</div>

> Try changing -g (gop) to 60 and add -r (FPS) set to 30.
> 
> ```auto
> -r 30 -g 60
> 
> ```
> 
> or
> 
> ```auto
> -r 24 -g 48
> 
> ```
> 
> I.e., -g = -r\*2
> 
> That should give you a key frame frequency of 2 seconds, which is ideal.
> 
> Richard

Hello.

I have a question about this same error.

Fragment duration greater than suggested range of 1-4 seconds. Adjust keyframe interval accordingly: Fragment durations: [0.5,12.4,0.1]

Our current settings on the encoder is:

GOP Size (frames): 12

B-Frames per GOP: 3

Framerate = 25fps (I believe, the source is DVB-S)

Are you saying my GOP size should be 50? In that case what should the B-frames be?

Thanks.

---

<div class="post-metadata">

**Author:** ![Reza\_Rizvi](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@Reza\_Rizvi](https://community.wowza.com/u/Reza_Rizvi)\
**Post date:** [May 31, 2013, 10:59pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/12 "2013-05-31T22:59:37Z")

</div>

> A 2 second key frame frequency is gop / fps. For example 60 (gop) / 30 (fps) = 2 second key frame frequency.
> 
> b-frames can be a problem. Try with and with b-frames.
> 
> Richard

Thanks Richard.

Our encoder has the following “tip” regarding encoding from a DVB tuner card…

_For NTSC the maximum length of a GOP is 18 frames, for PAL it is 15. Typical value is 15 for NTSC and 12 for PAL. Higher GOP values will give you better compression but some decoders might not be able to read them. For strict mpeg1/2/4 compliance, this would have to be \<=132._

_So the default is “12” which is what we have it currently set to for PAL. So for 25 FPS are you saying we should have the GOP at 50 to attain the 2 second key frame frequency? My understanding is that having higher GOP will increase compression and lower quality/resiliency isn’t that true?_

_I have been trying to find some good guidance on this but haven’t had much luck finding tips on how to optimize and the rationale. If you can point me to some resources that would be helpful._

---

<div class="post-metadata">

**Author:** ![Reza\_Rizvi](https://avatars.discourse-cdn.com/v4/letter/r/bc79bd/32.png) [@Reza\_Rizvi](https://community.wowza.com/u/Reza_Rizvi)\
**Post date:** [June 1, 2013, 1:13am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/13 "2013-06-01T01:13:50Z")

</div>

To add:

Apple says: For most media, spacing I-frames about 1/2 second apart gives good results. This equates to a GOP size of 15 frames for NTSC and 12 frames for PAL. The DVD-Video specification prohibits GOP lengths from being much longer than this. Generally, only material with scene changes occurring less than 1/2 second apart frequently throughout the video will benefit from shorter GOP sizes.

[http://documentation.apple.com/en/compressor/usermanual/index.html#chapter=18%26section=5%26tasks=true](http://documentation.apple.com/en/compressor/usermanual/index.html#chapter=18&section=5&tasks=true)

Would be interested to know how Wowza arrived at the 1-4 second recommendation. It would be great if Wowza had a whitepaper on this actually. Thanks for your help.

---

<div class="post-metadata">

**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\
**Post date:** [July 3, 2012, 2:48pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/14 "2012-07-03T14:48:03Z")

</div>

Hi

It could be a meta data issue take a look at this article,

[https://www.wowza.com/docs/how-to-add-resolution-and-codec-metadata-to-ios-streams](https://www.wowza.com/docs/how-to-add-resolution-and-codec-metadata-to-ios-streams)

Did you recreate the application(s) that you had in Wowza 2 or did you try to copy the Application.xml('s) over from the old server?

If your in control of the encoder streaming to the application set keyframe interval between 1-4 seconds.

What is the codec information of the inbound stream to Wowza?

Does it work in VLC?

For it to work for Android it must be H.264/AAC

Jason

---

<div class="post-metadata">

**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\
**Post date:** [July 3, 2012, 3:34pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/15 "2012-07-03T15:34:42Z")

</div>

Hi

I need to know what encoder you’re using to answer that question. 🙂

Jason

---

<div class="post-metadata">

**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\
**Post date:** [July 3, 2012, 3:59pm UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/16 "2012-07-03T15:59:55Z")

</div>

Hi

There should be a command option such as “–keyint 30”

I did a quick Google search and found this,

[https://sites.google.com/site/linuxencoding/x264-ffmpeg-mapping](https://sites.google.com/site/linuxencoding/x264-ffmpeg-mapping)

Jason

---

<div class="post-metadata">

**Author:** ![F\_Marshal](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@F\_Marshal](https://community.wowza.com/u/F_Marshal)\
**Post date:** [July 3, 2012, 6:22am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/17 "2012-07-03T06:22:42Z")

</div>

We recently upgrade to WMS3 and planning to order adaptive bitrate as add-on

but after installation i get some error log.

LiveStreamPacketizerSmoothStreaming.handlePacket[live/_definst_/Stream1]: **Fragment duration greater than suggested range of 1-4 seconds. Adjust keyframe interval accordingly: Fragment durations** : [0.0,7.4,3.2]

Not only ios, rtsp is not showing the video at all, it turn black after 3 second and get audio only.

After that… disconnect and show warning : “cannot play video”

We didn’t get this error when using WMS 2.

We’re using streamschedule.smil to produce live streaming to rtsp, ios and rtmp at same time.

what should i do to fix these error?

Thanks

---

<div class="post-metadata">

**Author:** ![F\_Marshal](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@F\_Marshal](https://community.wowza.com/u/F_Marshal)\
**Post date:** [July 3, 2012, 7:24am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/18 "2012-07-03T07:24:27Z")

</div>

Hi Jason,

I create new application(s) from conf folder and copy some property into it.

It’s H264/AAC and it works in VLC but sometimes i get audio only.

How to set keyframe interval between 1-4 seconds?

---

<div class="post-metadata">

**Author:** ![F\_Marshal](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@F\_Marshal](https://community.wowza.com/u/F_Marshal)\
**Post date:** [July 3, 2012, 7:52am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/19 "2012-07-03T07:52:35Z")

</div>

Oh Sorry,

I use FFMPEG.

320x240, 15fps, vidoe codec: libfaac, libx264 -strict experimental

vprofile : baseline

preset : slow

crf:22 -threads 0 -b 300 -qmin 3 -qmax 5 -bufsize 4096 -g 300

Audio : 96k, 32000

---

<div class="post-metadata">

**Author:** ![F\_Marshal](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@F\_Marshal](https://community.wowza.com/u/F_Marshal)\
**Post date:** [July 3, 2012, 8:24am UTC](https://community.wowza.com/t/fragment-duration-greater-than-suggested-range-of-1-4-seconds-warn/35042/20 "2012-07-03T08:24:41Z")

</div>

wow…

I will encode more than 600 videos ☹

why this not happen to WMS2?

Hi Richard,

Would you check my conf and error log Please?

I might have made a mistake in my application(s).

Thanks
