teams-for-linux VS nginx-obs-automatic-low-bitrate-switching

I've never used this but apparently this wrapper is useful for linux people: https://github.com/IsmaelMartinez/teams-for-linux

Have you tried an unofficial electron client?

I use https://github.com/IsmaelMartinez/teams-for-linux . It's "just" a wrapper around the PWA but a very decent one at that.

Unofficial and not Microsoft supported, but might be an alternative to Microsoft's official PWA. How do the two compare in your experience with them?

You can try the unofficial client Teams for Linux. It's available as a Flatpak and I didn't have any issues sharing my screen with it. https://github.com/IsmaelMartinez/teams-for-linux

This client works well for me: https://github.com/IsmaelMartinez/teams-for-linux

There is also: https://github.com/IsmaelMartinez/teams-for-linux

That always frustrated me, even more-so considering how that volunteer-built package I mentioned (https://github.com/IsmaelMartinez/teams-for-linux - an Electron build of the web app, nothing flashy but does the job just fine) does support screen sharing. I haven’t checked whether it supports backgrounds as I only use voice when on calls, but I’m guessing it does if the browser variant does.

Look into this software via GitHub and start doing some of your own research into the latest and greatest in IRL streamer setups NOALBS

Now, these are great upgrades however they don't fix your original issue about source freezing -- that's where NOALBS https://github.com/715209/nginx-obs-automatic-low-bitrate-switching comes in. NOALBS monitors your RTMP or SRT relay and automatically changes OBS scenes between "live" (good connection), "low bitrate" (poor connection) and "brb" (no connection) as your phone hiccups through the mobile network. NOALBS also offers chat commands (when used with twitch) to manually change scenes and do some other stuff.

You'll want to give Larix Broadcaster https://apps.apple.com/us/app/larix-broadcaster/id1042474385 a try, and especially look into sending the feed into your home OBS or a paid OBS service instead of sending directly to twitch. This allows for robust overlays and, using NOALBS https://github.com/715209/nginx-obs-automatic-low-bitrate-switching , will give auto scene switch capability when the feed hiccups or drops entirely

While it is possible to stream directly to twitch using either of these apps, you're much better off learning about SRT or RTMP relays which act as a middle man between your phone and OBS. The relay helps stabilize quality of the remote feed and affords the ability to use automatic scene switching (NOALBS https://github.com/715209/nginx-obs-automatic-low-bitrate-switching ) to kick OBS over to brb when the feed goes bad.

Use that in combination with NOALBS https://github.com/715209/nginx-obs-automatic-low-bitrate-switching

As an outdoor streamer, I love OBS! It's hosted in the cloud [0] for me, so I don't have to leave a PC running at home when I'm out streaming. I can control it through NOALBS [1], which basically means I type !start in my chat and my OBS starts streaming for me.

[0] https://antiscuff.com

[1] https://github.com/715209/nginx-obs-automatic-low-bitrate-sw...

PS, I have no affiliation with either of these companies / projects - I just use their services and wanted to praise OBS.

https://github.com/715209/nginx-obs-automatic-low-bitrate-switching If your intent is to use OBS, that will help with situations where your connection between the IRL streaming setup and your home streaming server drops.