Tudor Zaharia

Picking up on the discussion above, just my 2 cents: If you want to go more in the direction of having a similar API with mediasoup-client, you will lose some...

True, but it will throw only at runtime. C++ won't even build. Of course there's no logic in calling Produce without listening on the "produce" event. But since you can...

I'm saying that there is a difference of behavior between mediasoup-client and libmediasoup. Anyway, not important. It's good that you mandate the implementation of OnProduce().

> that the compiler requires me to implement OnProduceData() True. But I would actually aim for an even more integrated API, if possible. The way I see it there should...

I didn't say the Producer and DataProducer should be consolidated into a single class. I was talking only about the callback, which is mediasoup specific.

> I don't use data producers or consumers Probably a corner case, but for someone who is ONLY using data producers/consumers might feel awkward that the compiler requires her to...

> If OnProduce and OnProduceData just had their own default implementation that threw an exception Yes, this was [my initial point](https://github.com/versatica/libmediasoupclient/issues/70#issuecomment-606051765). It would also bring it close to the mediasoup-client...

Having similar issues as well. I'll switch to k3s to see if that works better.

@ktsakalozos I've disabled ha-cluster and will give it another go. I have a mixed setup with two nodes running on rpi4 (arm64) and a single amd64 machine. From what I...

Yep, it's really just the devices (/dev/kvm in this case) that don't work.