Go Live From OBS Without Retraining the Crew

What you can do together

• Run the meeting as a scheduled event on Nexus: registered viewers get an email reminder with a calendar attachment, late joiners rewind within the DVR window, and the audience watches in the portal or in a player embedded on your own site, restricted to approved domains.
• Take questions on a channel separate from chat, answered by moderators and exported afterwards, while chat runs moderated and archives onto the recording as comments.
• Publish the recording on demand the moment the session ends, with a transcript aligned to the timeline, captions generated from it, and chapters at topic boundaries.
• Ask AI Intelligence Hub what was said about a topic across a year of meetings and get an answer citing the moment in each recording.
• Reach the public on Facebook Live and YouTube alongside the portal stream, from one encode, where the deployment has outbound internet.

How it connects

OBS Studio sends its program feed over RTMP to a publishing point. The point is created on the portal against the configured streaming server, which can be VIDIZMO's own, Wowza in the cloud or on premises, or a general streaming server, and its address goes into OBS's stream settings once. A persistent publishing point keeps the same destination across events, so a weekly meeting never needs the encoder reconfigured.

What flows is the live feed, inbound. The portal delivers it to viewers over HLS in the same HTML5 player used for on-demand content, and by multicast on an on-premises network that supports it. Recording is started on the publishing point. Where the streaming server records server-side, the capture is uploaded into the library; otherwise the recording OBS writes locally is uploaded instead.

Nothing flows back to OBS. Scenes, sources, transitions and encoder settings live in OBS. The schedule, the audience, chat, Q and A, the recording and its retention live in the portal.