José Luis Millán
José Luis Millán
> Is the proposal in the feature description enough to address this?: Definitely a reduced interface should be exposed, yes.
There is a misunderstanding: > Even if we use a channel to communicate worker and plug-in, if we let the plug-in close a Consumer the app state will be ruined....
While I see the benefit of having a plugin system in mediasoup I need to add some points around it: We do offer a control layer on top of the...
I've been giving this a second thought and it seems perfectly fine having a plugin system as it is suggested here[*], which is how, AFAIK, they are typically built. [*]:...
Hi, I don't see any proper solution here since the `6` sequence number should be assigned to the input packet 18 when it arrives. If we assigned the `6` value...
I understand the problem. It is only the codec `H264_SVC.cpp` the one that knows about it. But the codec implementation knows nothing about RTP (and thus RTP seq number). Meaning...
@gitamirp, * Which mediasoup version are you using? * Can you repro? can you provide an STR? * Please provide as much context info as you can.
Yes please, you're using quite an old version. Upgrade it as soon as you can. Don't hesitate to reopen the issue if it comes out in the future.
Seems related to flatbuffers. I'll be checking this in few hours. @PaulOlteanu, I'd suggest using a single worker if possible while we troubleshoot this.
For now I don't see any static and non-thread local variables. Definitely Rust cannot properly read the incoming buffer because it is malformed. In the following case the payload is...