Known exisiting OBS issues impacting OBS.Ninja

[steveseguin]

• VP8 video PLI not firing (packet loss recovery)
• Bad packet loss handling in general; even VP9/h264 struggles with heavy packet loss
• No support for Jitter Buffer control (v75 lacks it; >v76 has it tho)
• Hardware Acceleration for Browser source not always enabled by default
• Control Audio from OBS not always checked by default
• macOS support obvs. :) [fixed]
• Auto-play is on, which is good; please ensure it stays that way :)
• When a browser source loads, the event for visibility isn't triggered -- only on subsequent events it issued.
• There's no way to tell if a browser source is on-deck or actually live.
• There's no way to tell the resized Window Size of the browser source. (less an issue)
• Sometimes audio isn't captured or stops being recorded, but still shows up in the audio meter section as active
• sometimes the browser source doesn't play at all -- crashes. Requires a restart.
• 800x600 is an odd resolution these days; 1280x720 might be better?
• no multi channel audio support? https://docs.google.com/spreadsheets/d/1R-y7xZ2BCn-GzTlwqq63H8lorXecO02DU9Hu4twuhuA/edit?usp=sharing (obs v26.1 limited to 8 channels? testing needed)

[olberger]

AFAIU, my main issue wrt OBS Studio, is the availability of the browser plugin for Linux distros.

AFAIU, the plugin depends on an embedded copy of Chromium, which leads to lots of complication for packaging in Debian-based distros, at least (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956086)

So, it seems that using OBS.ninja with OBS on Linux is quite a challenge... or there's an alternative to the browser source in OBS that would deserve better documentation/support, etc.

Sorry if I overlooked a more related issue in the tracker (so many issues, hard to spot). Edit : I just created an issue of its own