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
As part of #87, VideoDecoder is now capable of retrieving the width/height of a video stream. However, to do this, it must be provided a keyframe sequence that it will decode via libav. As a result, the metadata report thread now ends up decoding keyframes twice - first to retrieve the video dimensions, and a second time to generate a JPEG preview image.
It's also worth considering using a different approach to extract the resolution from H264 video. SPS NAL units should contain the information we need. There's some good reference code from the WebRTC implementation here. This will save us from having to decode an entire frame just to get the width/height information.
The text was updated successfully, but these errors were encountered:
As part of #87, VideoDecoder is now capable of retrieving the width/height of a video stream. However, to do this, it must be provided a keyframe sequence that it will decode via libav. As a result, the metadata report thread now ends up decoding keyframes twice - first to retrieve the video dimensions, and a second time to generate a JPEG preview image.
It's also worth considering using a different approach to extract the resolution from H264 video. SPS NAL units should contain the information we need. There's some good reference code from the WebRTC implementation here. This will save us from having to decode an entire frame just to get the width/height information.
The text was updated successfully, but these errors were encountered: