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

Clarification on "not processing video packets" requested #230

Open
luciaalonsomozo opened this issue Aug 15, 2024 · 7 comments
Open

Clarification on "not processing video packets" requested #230

luciaalonsomozo opened this issue Aug 15, 2024 · 7 comments

Comments

@luciaalonsomozo
Copy link

What does processing mean in step 2 of send key frame algorithm?

@luciaalonsomozo
Copy link
Author

It seems from this Web Platform Test that inactive and stopped transceivers would cause this error, is that what step 2 is referring to? Could it be made more explicit?

@alvestrand alvestrand changed the title Clarification requested Clarification on "not processing video packets" requested Aug 15, 2024
@alvestrand
Copy link
Contributor

spec link to editors' draft: https://w3c.github.io/webrtc-encoded-transform/#KeyFrame-algorithms

@alvestrand
Copy link
Contributor

Seems to be intended to mean "if the media type of the encoder is not video".

@guidou
Copy link
Collaborator

guidou commented Aug 15, 2024

@jan-ivar
Copy link
Member

Aligning with implementations seems good here.

@jan-ivar
Copy link
Member

@youennf does that SGTY?

@fippo
Copy link
Collaborator

fippo commented Aug 15, 2024

This simply means that one should not send RTCP for inactive or stopped m-lines, no?
Given that RTCP is not reliable and one can not determine whether this was received anyway, why do browsers attempt to impose behavior on top here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants