Closed Obegg closed 5 months ago
To reproduce you'll need to first start a share and only then view the other's share.
It's caused by this constructor:
And throws this error:
The reason it happens is because the plugin puts the stream's width and height in the videoBudget object, which in "Source" resolution's case, is 0. The constructor explicitly checks for 0 and, logically, throws an error if it is a 0. The reason for this is because it literally cannot construct a ladder if the pixel budget is 0. This wouldn't be a problem normally because the values in videoBudget are usually set to the maximum resolution that the user is allowed to use (i think??), however since we are changing those amounts to for our stream, it starts to complain, because it also changes the values for the stream we're watching, but only if they match the other users stream's configuration...? I have no clue if that's even remotely correct, but that's what I think is happening there. The solution is for the plugin to set literally any other value that isn't 0 to videoBudget's width and height.
Fixed in 5.4.2 (1e72ef4)
Scenario: 2 users who use
YABDP4Nitro
join a voice channel in a server, they both share their screen onSource
and60fps
, they can't view each other's share while they themself share.