Closed Bug 825611 Opened 12 years ago Closed 12 years ago

Always provide as much audio data from PeerConnection as MediaStreamGraph asks for

Categories

(Core :: WebRTC: Audio/Video, defect, P2)

x86_64
Windows 7
defect

Tracking

()

RESOLVED FIXED
mozilla20

People

(Reporter: mreavy, Assigned: ekr)

Details

(Whiteboard: [WebRTC], [blocking-webrtc+] [qa-])

Attachments

(2 files)

The GIPS code always provides audio data in 10ms fixed buffers. MediaStreamGraph may ask for audio in any buffer size. Even if MediaStreamGraph requests just slightly more than 10ms, provide the full second 10ms buffer and let the rest of the code handle it. The jitter buffer will grow, but that's ok. We can worry about optimizing the sizes requested by MediaStreamGraph in a separate bug. Implementing this fix should eliminate some (hopefully all) of the audio artifacts we're hearing from the output side of the current PeerConnection code.
See bug 822956 comment 23 and following
Assignee: nobody → ekr
Attachment #698200 - Flags: review?(rjesup)
Comment on attachment 698200 [details] [diff] [review] Have MediaPipeline deliver as much media as requested Review of attachment 698200 [details] [diff] [review]: ----------------------------------------------------------------- ::: media/webrtc/signaling/src/mediapipeline/MediaPipeline.cpp @@ +828,5 @@ > MOZ_MTLOG(PR_LOG_ERROR, "NotifyPull() called from a non-SourceMediaStream"); > return; > } > > + while (MillisecondsToMediaTime(played_) < desired_time) { Just add a comment that that it's done this way to avoid roundoff errors from accumulating.
Attachment #698200 - Flags: review?(rjesup) → review+
Comment on attachment 698322 [details] [diff] [review] Fix unit tests to match fix to MediaPipeline Forget to change the unit tests. Also a bit of trivial reformatting
Attachment #698322 - Flags: review?(rjesup)
Attachment #698322 - Flags: review?(rjesup) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
Whiteboard: [WebRTC], [blocking-webrtc+] → [WebRTC], [blocking-webrtc+] [qa-]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: