José Luis Millán
José Luis Millán
Thanks for the report @alexsharabaykoidt and @rcidt
@vpalmisano, what about the rest of Consumer types? Simulcast, SVC ? Being mediasoup a library we should try not to do changes solely for a specific use case.
> Simulcast audio? 🙃 Of course not talking about audio only Consumers :-)
> Well, this PR is just for audio. I know, I know this PR is just for audio...
Considering that it is assumed (and asserted) that a Consumer will always consume from a Producer with the same RTP Parameters, I believe a more generic solution would be the...
> The proposal of yet another PluggableConsumer (and friends) goes against that direction. I think you have misunderstood it. The proposal is about `PluggableProducer`, not `PluggableConsumer`. It's the opposite.
There is zero change on Consumers within the proposal. https://github.com/versatica/mediasoup/pull/768#issuecomment-1064935370 Yet, it is not 100% defined, neither is it the intention.
> Still I don't understand how it solves the consuming side in which RTP parameters may be different. Just to clarify, let me summarise from the beginning. There are N...
> If we replace the producer a consumer is consuming, we must signal its RTP parameters This would be one approach. Which is legit, but has it's drawbacks: * It...
Not enthusiastic about this. We already know the libwebrtc code extraction inferno (BWE currently), and are working to get rid of it. Let's see how it evolves.