You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if Pion has a special mode for your expectation. But your expectation is certainly not true for browser implementations. The reason is that before you set any description the implementation doesn't know for how many streams it needs to provide ICE candidates and if bundle is going to be used or not.
I think the more reasonable expectation would be to say that with pools activated there should be a lot less delay in gathering candidates after setting a description, compared to without using an ICE candidate pool.
Sean-Der
changed the title
ICECandidatePoolSize has no effect
Implement ICECandidatePoolSize (gathering before SetLocalDescription)
Oct 7, 2024
Sean-Der
changed the title
Implement ICECandidatePoolSize (gathering before SetLocalDescription)
Implement ICECandidatePoolSize (gathering before SetLocalDescription/SetRemoteDescription)
Oct 7, 2024
I didn't realize that Pion doesn't have support for ICE candidate pool yet.
Yes having the default pool size be 0 and meaning no gathering before set(Local|Remote)Description makes perfect sense to me. And then an API to set it to some positive number if pooling is desired.
Here is the code
It doesn't do anything unless description is set
The text was updated successfully, but these errors were encountered: