microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Deliver Audio source media buffer exception and lipsync issue on video and audio played
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hi guys, how’s everything?
We’re working with a hosted media application to inject media content into a MS Teams meeting. We’re currently facing an issue when trying to send the audio buffers to the corresponding audio socket despite our output seems to be generating perfect 20ms audio chunks.
Sometimes the application throws the exception Deliver Audio source media buffer as the following pictures show.
Exception


Inner Exception


When the exception occurs at the beginning of the stream, we can see in the MS Teams client that the injected content is played out of sync (lipsync issue), the video is played first and, after a second (sometimes more) the audio is played.
We would like to know, what exactly does this exception refer to? taking consideration that the message returned by the exception is not very descriptive.
Also, we would like to know if is it possible that the lipsync issue is related to this exception?
Thanks in advance.
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
The issue names no repository files, tests, or entry points. Start by reproducing the audio-buffer exception in the hosted media application and inspect the linked exception screenshots and the single comment. Done would require identifying what the exception means and establishing whether it causes the reported MS Teams lip-sync delay.
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
- 20/100