To move a live programme to a new destination, add the replacement output, start it, check picture and sound where it is received, then stop the old output. In Callaba Video Mixer, Program and publishing are separate controls, so changing one output does not require a Stop Program action. The important distinction is simple: Program is the show; each output is one route that carries it onward.
Separate the programme from its destinations
Program is the live scene and programme-audio path. An output is one configured route from that programme to a receiving service, decoder, or platform. The show can remain in Program while you work on one output.
In the publishing area, use Add an Output for the replacement route. Use Start or Stop on that individual output when you are changing one destination. Stop Publish is the broad publishing control. Stop Program ends the programme, so it is not the control for this job.
Name outputs for where they go: Venue decoder and Partner RTMP are much clearer than two outputs called Live.
Build the replacement output before the handoff
Select Add an Output, choose the output type the destination accepts, and name it for that destination. For RTMP, enter the current ingest URL and stream key supplied by the platform. The URL identifies the endpoint; the key authorizes the channel. Keep the key out of screenshots, chat, and event notes.
Match the destination’s current codec, resolution, frame rate, bitrate, audio, and keyframe requirements. Do not rely on a profile copied from an old platform or another event. SRT and NDI outputs need the same care: use the receiver’s current connection and media requirements.
Decide how you will look at the new destination before starting it. That might be a decoder, the platform’s live player, or a monitor at the receiving end. A started output is not the same thing as a destination with the intended picture and sound.
Identify the publishing controls before the event
Use the public mixer example to recognise Program and output concepts before rehearsal. It is not an operator console and cannot create a destination, expose credentials, or check playback at an external receiver.
- Find Program and the publishing area before a live handoff.
- Name the old and new outputs and decide how the new destination will be checked.
- In an authenticated workflow, use Add an Output to prepare the replacement destination before the event.
- Check the new destination before stopping the named old output.
Watch the public mixer here; it is a view-only workspace.
Open Live mixer in a new tab ↗Loading public workspace…
Start the new destination, then retire the old one
Keep the intended scene in Program and start the replacement output. At the new destination, look for a current, recognisable picture and the intended audio. A short spoken identifier or visible time cue helps distinguish the live path from a stale player buffer or preview image.
- Leave Program on the planned scene.
- Start the replacement output.
- Check picture and sound where the new destination receives them.
- Stop the named old output.
Do not substitute a green state in the mixer for the destination check. A platform can reject a profile, use an old key, or show a stale player state after the output has started. If both routes cannot run during the change, agree the order with the production team before the old route is stopped.
If the replacement fails, restore the known route
If the new destination is blank, first make sure the platform or decoder is looking at the correct event or channel. Then compare its current ingest and media requirements with the replacement output. Program can stay on the planned scene while you do this.
If the picture arrives without the intended sound, listen to Program and to the receiving end. Check the output profile and the programme-audio choice. If the old destination was stopped too early, start the known output again and check it at its destination before returning to the replacement route.
If someone uses Stop Publish, identify the outputs that stopped and restart the ones the event needs. If someone uses Stop Program, use the event restart procedure; Program, inputs, recording, and monitoring may need to be set up again.
Check recording as its own path
If the event is recorded, decide whether you are recording Program or a selected output before the handoff. Check the recording state after changing the destination, then inspect the completed asset when it is finalised. Recording and publishing are separate jobs, so each needs its own check.
For the next event, keep the output name, destination type, profile, and handoff order. Leave credentials out of those notes.