Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JitterBuffer: Interceptor #247

Merged
merged 1 commit into from
Apr 21, 2024
Merged

JitterBuffer: Interceptor #247

merged 1 commit into from
Apr 21, 2024

Conversation

thatsnotright
Copy link
Contributor

@thatsnotright thatsnotright commented Apr 11, 2024

Description

This implements a RemoteStream jitter buffer interceptor.

Copy link

codecov bot commented Apr 11, 2024

Codecov Report

Attention: Patch coverage is 82.25806% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 72.14%. Comparing base (1449b4f) to head (6d74945).
Report is 1 commits behind head on master.

Files Patch % Lines
pkg/jitterbuffer/receiver_interceptor.go 73.17% 8 Missing and 3 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #247      +/-   ##
==========================================
+ Coverage   72.08%   72.14%   +0.06%     
==========================================
  Files          77       79       +2     
  Lines        3582     3644      +62     
==========================================
+ Hits         2582     2629      +47     
- Misses        866      876      +10     
- Partials      134      139       +5     
Flag Coverage Δ
go 72.14% <82.25%> (+0.06%) ⬆️
wasm 70.30% <79.03%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@thatsnotright thatsnotright force-pushed the rob/jitterbuffer_interceptor branch 2 times, most recently from 2668bc2 to 249b5d0 Compare April 19, 2024 00:44
The JitterBufferInterceptor is designed to fit in a RemoteStream
pipeline and buffer incoming packets for a short period (currently
defaulting to 50 packets) before emitting packets to be consumed by the
next step in the pipeline.

The caller must ensure they are prepared to handle an
ErrPopWhileBuffering in the case that insufficient packets have been
received by the jitter buffer. The caller should retry the operation
at some point later as the buffer may have been filled in the interim.

The caller should also be aware that an ErrBufferUnderrun may be
returned in the case that the initial buffering was sufficient and
playback began but the caller is consuming packets (or they are not
arriving) quickly enough.
@thatsnotright thatsnotright marked this pull request as ready for review April 19, 2024 01:02
@thatsnotright
Copy link
Contributor Author

@Sean-Der I'm not sure why the nack test failed for WASM this run but not others. I think this PR is close to ready but I'd like to see what else you think it needs?

@dryarullin
Copy link

@thatsnotright Could you look at my issue please?

Copy link
Member

@Sean-Der Sean-Der left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic! Feels really great to see this all come to completion :)

@Sean-Der Sean-Der merged commit 72c0be8 into master Apr 21, 2024
15 checks passed
@Sean-Der Sean-Der deleted the rob/jitterbuffer_interceptor branch April 21, 2024 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants