# Repeated log “RTC::Producer::ReceiveRtpPacket() | key frame received” when use ffmpeg to push stream

**URL:** <https://mediasoup.discourse.group/t/repeated-log-rtc-receivertppacket-key-frame-received-when-use-ffmpeg-to-push-stream/3278>\
**Category:** mediasoup libraries\
**Created:** [September 7, 2021, 5:55am UTC](https://mediasoup.discourse.group/t/repeated-log-rtc-receivertppacket-key-frame-received-when-use-ffmpeg-to-push-stream/3278 "2021-09-07T05:55:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chenzx](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@chenzx](https://mediasoup.discourse.group/u/chenzx)\
**Post date:** [September 7, 2021, 5:55am UTC](https://mediasoup.discourse.group/t/repeated-log-rtc-receivertppacket-key-frame-received-when-use-ffmpeg-to-push-stream/3278/1 "2021-09-07T05:55:11Z")

</div>

Hi ibc,

When i use ffmpeg to do h264 stream rtp-packetize and push to mediasoup server for a realtime streaming scenario, i see the repeated logs:

```auto
 mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:10064] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:10368] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:10617] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:11071] +2s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:11249] +867ms
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:11390] +879ms
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:11587] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:11761] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:11960] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:12326] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:12683] +2s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:13035] +2s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:13167] +971ms
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:13358] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:13598] +935ms
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:13956] +1s
  mediasoup:Channel [pid:3549] RTC::Producer::ReceiveRtpPacket() | key frame received [ssrc:22222222, seq:14478] +2s

```

i thought ffmpeg does not do RTCP PLI feedback from source, (it may do SR, because there is in ffmpeg’s code), while checking libwebrtc’s impl, libwebrtc seems do encode keyframe realtime to response to RTCP PLI request.

does it affect the webrtc end2end latency? The input source is assumed to be realtime-encoded h264 stream, which doesn’t do any webrtc/rtp-related things.

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/nazar-pc/32/369_2.png) [@nazar-pc](https://mediasoup.discourse.group/u/nazar-pc)\
**Post date:** [September 7, 2021, 6:11am UTC](https://mediasoup.discourse.group/t/repeated-log-rtc-receivertppacket-key-frame-received-when-use-ffmpeg-to-push-stream/3278/2 "2021-09-07T06:11:13Z")

</div>

What you see is that ffmpeg creates a key frame roughly every second. Either your source has that or transcoding parameters are configured to produce such GOP. So it probably has nothing to do with PLI in this case.

---

<div class="post-metadata">

**Author:** ![chenzx](https://avatars.discourse-cdn.com/v4/letter/c/ee59a6/32.png) [@chenzx](https://mediasoup.discourse.group/u/chenzx)\
**Post date:** [September 7, 2021, 6:36am UTC](https://mediasoup.discourse.group/t/repeated-log-rtc-receivertppacket-key-frame-received-when-use-ffmpeg-to-push-stream/3278/3 "2021-09-07T06:36:08Z")

</div>

Yes, i’ll try to re-encode the h264 stream to decrease the GOP parameter.

What i’m wondering is, does this has negative affect on streaming latency? I’m using this for `cloud gaming`, e2e latency would be better \<200ms, so just ask.

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [September 7, 2021, 8:11am UTC](https://mediasoup.discourse.group/t/repeated-log-rtc-receivertppacket-key-frame-received-when-use-ffmpeg-to-push-stream/3278/4 "2021-09-07T08:11:06Z")

</div>

> [@chenzx](#):
>
> What i’m wondering is, does this has negative affect on streaming latency?

Not on latency but on generated bitrate which is much higher if a key frame is sent to often.