You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a streaming application where native clients stream a vp9 video file to a media server using WebRTC, and there's also a web client where I can consume and view the incoming video track. The video file is in IVF format (vp9) and I can confirm with ffprobe that there's a keyframe every 4 seconds.
I read the IVF video file and stream it using the play_from_disk_vpx example code (IVFReader). But in the web client, when I investigate the webrtc-internals stats, I can see that the number of decoded frames and decoded keyframes are equal. So, somehow every video frame is sent as a keyframe.
I wonder if there's something that I'm missing? Should I do something manually to mark specific RTP packets as keyframes?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
I should add that when I encode the IVF file as VP8, everything is fine and the number of decoded keyframes is as expected. So, the problem only exists when I'm streaming a VP9 video file.
Hi. First of all, thanks for your awesome work!
I'm developing a streaming application where native clients stream a vp9 video file to a media server using WebRTC, and there's also a web client where I can consume and view the incoming video track. The video file is in IVF format (vp9) and I can confirm with ffprobe that there's a keyframe every 4 seconds.
I read the IVF video file and stream it using the play_from_disk_vpx example code (IVFReader). But in the web client, when I investigate the webrtc-internals stats, I can see that the number of decoded frames and decoded keyframes are equal. So, somehow every video frame is sent as a keyframe.
I wonder if there's something that I'm missing? Should I do something manually to mark specific RTP packets as keyframes?
Thanks in advance.
The text was updated successfully, but these errors were encountered: