Do not debug three receiving apps at once. Let the GoPro make one custom RTMP contribution, prove that Callaba is receiving moving video and audio, and only then open the accepted feed in OBS, vMix or VLC.
This creates a clean boundary between the field camera and the production room. The GoPro can move or use a remote network while the downstream tools share one known ingest.
The first proof is in Callaba: the RTMP server shows an active contribution and believable incoming bitrate, while preview or Multiview shows moving picture and audio. Until that happens, OBS, vMix and VLC are downstream distractions.
Prepare the camera side
You need a GoPro model and firmware combination that supports live streaming, the current GoPro Quik app, a phone paired with the camera and a Wi-Fi or hotspot path that can sustain the selected quality. Check battery, heat exposure and the decision to save a local recording before leaving the camera position.
GoPro’s menus and supported resolutions vary by model and app release. Use the current GoPro live-streaming instructions as the camera authority. The stable part of this workflow begins when Quik offers Other/RTMP or a custom RTMP target.
Build the handoff in six moves
Pair GoPro and Quik
Enable wireless connections on the camera, connect it in Quik and confirm that the phone can control the live camera.
Create one RTMP Server
In Callaba, open RTMP Servers, add a clearly named input such as GoPro field camera, and save it.
Make the endpoint reachable
Allow the configured TCP port through the cloud and host firewall. Port 1935 is conventional, but the value shown by your server is authoritative.
Copy the Callaba RTMP URL
Use the endpoint values shown by Callaba. Treat a stream key as a credential: do not paste it into screenshots, tickets or public chat.
Choose Other/RTMP in Quik
Select the intended network, paste the custom RTMP target and begin with a conservative quality for the first field test.
Watch ingest before opening a receiver
Start the GoPro live stream, then wait for Callaba to show incoming media and a decodable preview.
For a first run, 720p is useful because it reduces pressure on the phone, Wi-Fi and uplink while you prove the route. Raise quality only after the contribution is repeatable. A five-second player buffer can hide short Wi-Fi variation during confidence viewing, but it also adds delay; choose it as an operating trade-off, not a universal requirement.
Open the accepted feed where the operator needs it
OBS Studio
Add a Media Source, disable Local File and paste the Callaba playback URL into Input. Name the source for the camera and location, not “Media Source 3”.
vMix
Choose Add Input → Stream/SRT, select the RTMP-capable VLC stream type in the current interface, paste the playback URL and set a deliberate receive buffer.
VLC
Use Open Network Stream with the same playback URL. VLC is a useful independent confidence check before the feed is mixed into a large scene.
The publish URL used by Quik and the playback URL used by production tools may have different jobs. Copy the values from the Callaba interface rather than constructing a URL from memory. When a receiver opens but shows no media, compare its timestamp with the RTMP server state.
The same ingest can do more than feed a switcher
Direct production use
OBS or vMix takes the GoPro as an input. VLC checks the same handoff independently. This is the smallest remote-camera workflow.
Keep the GoPro live while receivers are added; otherwise a receiver timeout can look like a bad URL.
Managed reuse in Callaba
Put the accepted source in Multiview, keep an independent recording, or create separate restream jobs for YouTube, Facebook, Twitch or another destination.
The GoPro still uploads once. Each downstream job can be observed without rebuilding the field-camera connection.
This is also where the product boundary is honest. Callaba does not improve weak GoPro focus, battery life or local radio conditions. It gives the contribution a controlled endpoint and lets the team see and reuse the media after it arrives.
Find the failed boundary in one pass
Run a field rehearsal, not a desk demo
Walk the real camera route. Include the distance, walls, crowd density and hotspot placement expected during the event. Speak into the intended microphone, create motion and leave the feed up long enough to expose heat or power problems. Watch Callaba ingest and one production receiver at the same time.
References: GoPro live-streaming support, OBS Media Sources, Callaba RTMP Server operator guide, and Callaba RTMP Server product page.
