Paulo Lanzarin
Paulo Lanzarin
> Regular conference: generally behaves normally, but there are periods where it shows the behavior of jittery streams in ways the default bridge (straight clientFS) doesn't https://github.com/bigbluebutton/bbb-webrtc-sfu/releases/tag/v2.8.0-alpha.3
This is mostly addressed as far as the original concerns go. It is possible that additional quality concerns may pop up once usage of the new module is more widespread...
As I've mentioned internally, error 1138 is [NotReadableError](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getDisplayMedia#exceptions) which usually is a capture problem between the browser and the OS. So, alongside trying to reproduce in test.bigbluebutton.org, please: - Attach...
@GhaziTriki ping :)
> I'm getting the same error 1138 when screen sharing my full screen in chrome Version 99.0.4844.74 (Official Build) (x86_64). No problem when I share a particular window or chrome...
> I thought that I responded to this. But I don't see it in the thread. Mac OS. 11.6.5 It's not the same thing, then. The OP is talking about...
@relecand [NotReadableError](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getDisplayMedia#exceptions) usually is a capture problem between the browser and the OS. Since it happens with a base sample, I recommend looking at the browser's issue tracker as it...
A dump or quick inspection of chrome://webrtc-internals would also assert what resolution chrome is in fact sending @RaistGH.
@j1elo I'm going to try and take a look at this to make it dual stack compatible.
cc @mariogasparoni (the one who originally pinged me about it)