microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
[PolicyRecordingBot] Recorded file video quality is pretty bad - two user call
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hi,
I'm using the PolicyRecordingBot source code for a POC and testing only two users call.
When both users are in a video call, recorded video call quality is pretty bad. Both users subscribe to the videosockets and bot receive the media streams from both sockets. But video width and height are two different in stream data.
VideoSocket 01:
[1]: Received Video: [VideoMediaReceivedEventArgs(Data=<1790605704432>, VideoFormat=<Video color format: H264, width: 640, height: 360, frame rate: 0, bit rate: 0>, OriginalVideoFormat=<Video color format: H264, width: 640, height: 360, frame rate: 0, bit rate: 0>, Length=136, Timestamp=38091371540071056, Width=640, Height=360, ColorFormat=H264, FrameRate=0)]
VideoSocket 02:
[2]: Received Video: [VideoMediaReceivedEventArgs(Data=<1790535237504>, VideoFormat=<Video color format: H264, width: 960, height: 540, frame rate: 0, bit rate: 0>, OriginalVideoFormat=<Video color format: H264, width: 960, height: 540, frame rate: 0, bit rate: 0>, Length=4497, Timestamp=38091371540535752, Width=960, Height=540, ColorFormat=H264, FrameRate=0)]
After I create the video file(save stream as H264 file) from this video media stream, its pretty bad. When the dominant speakers change it jitters and cant see anything.
Are there any idea to solve this or Am I missed something here ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PolicyRecordingBot source and reproduce a two-user video call while subscribing to both VideoSockets. Compare the recorded H264 output with the reported 640x360 and 960x540 stream dimensions, especially when the dominant speaker changes; done means the saved video no longer jitters or becomes unreadable.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100