Connect Player and Streamer

Last validated: 2026-05-05

OdenVR receives video, audio, and feedback from Oden Streamer through a Remote Streamer entity. In this page, Player means OdenVR or Oden Dome Player. There are two common ways to establish that connection:

  • A fleet-managed connection, where Oden Fleet Streamer and the Fleet Client plugin ask Bifrost to set up the session and network links.

  • A local or direct connection, where you configure the Player and Streamer network links yourself.

Use the fleet-managed path for deployed vehicles. Use the direct path for lab setups, local testing, or networks where the Player receive port is reachable from the Streamer.

Fleet-managed connection

The fleet-managed path requires Oden Fleet Streamer on the vehicle side and the Fleet Client plugin on the Player side. The Fleet Client handles the vehicle list, connection request, relay setup, encryption keys, and peer-to-peer transition when available.

  1. Start Oden Fleet Streamer on the vehicle. If it was installed as a service, make sure the service is running.

  2. Start OdenVR on the operator station.

  3. Enable the Fleet Client plugin. If the project uses Oden Control Pipeline or a web UI, enable those plugins as well.

  4. Open the connection menu in the Player.

  5. Select an online vehicle and press Connect.

When the connection is accepted, the fleet plugin either loads the project assigned to that vehicle or creates a Remote Streamer entity for the session. The plugin then configures the Remote Streamer network links and the corresponding Streamer links.

Plugin checklist before the first fleet connection:

  • On the operator side, enable Fleet Client before selecting a vehicle.

  • Enable Oden Control Pipeline when the Player project should send control values or receive vehicle faults.

  • Enable Webview when the operator workflow uses the portal UI or a project webview.

  • Vehicle-side Oden Fleet Streamer installations normally include the Fleet Client and OCP pieces needed by the Streamer side. If a vehicle is online but control, status, or web UI behavior is missing, check that the matching plugins are enabled and that the license/auth state is valid on both sides.

The same flow can be controlled from a web view by sending named user messages:

const odenClient = getOrCreateOdenLayoutClient();

odenClient.sendNamedUserMessage("fleet_list_vehicles", {});
odenClient.sendNamedUserMessage("fleet_connect", { vehicle_name: "vehicle_name" });
odenClient.sendNamedUserMessage("fleet_disconnect", { vehicle_name: "vehicle_name" });

Use the vehicle name from fleet_online_vehicles, not the vehicle id. See Webview and JavaScript SDK for the full webview API.

Local or direct connection

In a direct connection, the Streamer initiates traffic and the Player listens. By default, a Remote Streamer entity creates a receiver link on port 47000, and a Streamer network link sends to 127.0.0.1:47000.

For two computers on the same network, replace 127.0.0.1 with the Player computer’s reachable IP address. The Player firewall and network route must allow incoming traffic on the configured receive port.

On the Player

  1. Start OdenVR.

  2. Open or create a Player project.

  3. Add a Remote Streamer entity if the project does not already contain one.

  4. In the Remote Streamer entity, open Network.

  5. Use one link in Receiver mode.

  6. Set Receive Port to 47000, or choose another free UDP port.

On the Streamer

  1. Start Oden Streamer.

  2. Open the Streamer project that captures and outputs the video.

  3. In the Streamer sidebar, open Network.

  4. Use one link in Sender mode.

  5. Set Destination Addr. to the Player address: 127.0.0.1 for same-computer testing, or the Player IP address for another computer.

  6. Set Destination Port to the Player Receive Port.

  7. Open Output and press Start.

When packets arrive, the Remote Streamer entity shows video and network statistics. If no video appears, verify that the Streamer output is started, that the Player receive port matches the Streamer destination port, and that the Player address is reachable from the Streamer.

Which path to choose

Path Use when

Fleet-managed

The vehicle is registered in Bifrost, Oden Fleet Streamer is installed, and operators should connect by vehicle name.

Local/direct

The Streamer and Player are on the same computer or on a network where the Streamer can send directly to the Player receive address and port.

For detailed network settings, see Network. For Remote Streamer diagnostics, see Connection or no remote stream. For Streamer output settings, see Bitrate Control and Auto Video Packing.