I'm a bit concerned about the assertion that setting the "large event" option will support 200 viewing sessions. The scale is likely not limited by a license, but by network bandwidth. Part of the bandwidth equation is the virtual host NIC provisioned in the Azure cloud (normal vs. large event?) but another part of that is what bit-rate your'e sending and what the viewers are watching.
If someone knows the details, I would like to know what is being provisioned with these two options. If the infrastructure scales to 200 users watching 720p @ 1.5Mbps , will it scale to perhaps 400 users if I drop the resolution to 480p @ 750Kbps? What bitrate was used to derive the 200 user limit?
Here's an approach to scale the existing infrastructure for the tech savvy. You should all be able to find someone in your stakes with Linux skills to help with this (or Windows skills if you're up in Idaho
. Schedule 2 or 3 events at the same time, so you have 3 stream servers. Set up a linux PC and install the rtmp server. You can find guides like this via google: https://sites.google.com/view/facebook- ... rtmps/home
. Use multiple push statements in the rtmp file, one push for each of the backend stream servers. If there are 9 wards in your stake, give each set of 3 wards one of the three codes, so the watchers are distributed. Now you can scale to 600 families watching.
Yeah, it's a bit geeky, but it uses the existing infrastructure which is pretty nice from a control and visibility standpoint.