Processing

Live video transcoding software

Normalize live feeds for the destinations and viewers your workflow serves. Callaba software can convert protocols and, where the selected profile supports it, adjust codec, resolution, bitrate, frame rate, audio, and output variants in cloud or self-hosted deployments. It works with feeds from cameras, OBS, vMix, and hardware encoders; it is not a hardware encoder. API control is available as a secondary automation layer.

What is live video transcoding?

Diagram showing one live contribution feed entering Callaba Live Video Transcoder and branching into two delivery profiles and a supported protocol handoff. — Callaba Live Video Transcoder transforms one live contribution feed into distinct delivery profiles and hands each output to a supported downstream protocol.

Processing

Create multiple output profiles from one source

Produce supported output variants for different bandwidth and playback requirements without asking the source encoder to publish a separate feed for every viewer profile.

Normalize one contribution feed for delivery

Accept a stable live input, then shape supported codec, resolution, bitrate, frame-rate, and audio settings for the actual player, platform, or downstream system that receives it.

Create multiple output profiles from one source

Produce supported output variants for different bandwidth and playback requirements without asking the source encoder to publish a separate feed for every viewer profile.

Convert protocols at the workflow boundary

Keep contribution and delivery choices separate. For supported routes, receive the protocol that fits the source and hand off the protocol expected by a platform, player, or partner endpoint.

Workflow

Validate the exact media profile before production

Codec, container, protocol, acceleration, and output support depend on the selected workflow and infrastructure. Test the real source and destination profile before committing a production event or migration.

Use your existing hardware encoder

Keep cameras and field encoders focused on producing a clean contribution feed. Callaba is the software layer that receives that feed and prepares supported delivery outputs; it does not replace capture hardware.

Run the same product in cloud or self-hosted

Validate the workflow quickly in cloud, or install Callaba on infrastructure you control when data location, capacity planning, or private networking requires a self-hosted deployment.

Validate the exact media profile before production

Technical specification

What the product supports, and what to verify

Supported behavior sits beside a practical acceptance check. The installed Callaba interface and the real source, destination, and infrastructure profile remain authoritative.

Capability	Supported behavior	Acceptance check
Normalize one contribution feed for delivery	Accept a stable live input, then shape supported codec, resolution, bitrate, frame-rate, and audio settings for the actual player, platform, or downstream system that receives it.	Depending on the selected workflow and available infrastructure, a profile can adjust supported codec, resolution, bitrate, frame rate, pixel format, GOP, and audio settings. Validate the exact input and output combination before production.
Create multiple output profiles from one source	Produce supported output variants for different bandwidth and playback requirements without asking the source encoder to publish a separate feed for every viewer profile.	Yes, where the selected profile and deployment have the required capacity. One contribution feed can be used to create supported output variants for different bandwidth or playback requirements.
Convert protocols at the workflow boundary	Keep contribution and delivery choices separate. For supported routes, receive the protocol that fits the source and hand off the protocol expected by a platform, player, or partner endpoint.	Supported routes can separate the contribution protocol from the delivery protocol. This lets the source use the transport that fits contribution while the destination receives the handoff it expects.
Use your existing hardware encoder	Keep cameras and field encoders focused on producing a clean contribution feed. Callaba is the software layer that receives that feed and prepares supported delivery outputs; it does not replace capture hardware.	No. Callaba is software. A camera, OBS, vMix, mobile app, or hardware encoder sends a contribution feed into Callaba, and the software prepares supported routing and delivery outputs.
Run the same product in cloud or self-hosted	Validate the workflow quickly in cloud, or install Callaba on infrastructure you control when data location, capacity planning, or private networking requires a self-hosted deployment.	Use cloud for a fast proof of value and variable workloads. Choose self-hosted when you need direct control over infrastructure, private networking, data location, or capacity planning. Test your real media profiles in either model.
Validate the exact media profile before production	Codec, container, protocol, acceleration, and output support depend on the selected workflow and infrastructure. Test the real source and destination profile before committing a production event or migration.	Start with the cloud launch guide or the self-hosted installation guide . Connect the real source, define the required destination profile, validate quality and resource use, and only then automate it through the API if needed.

Workflow

Run the same product in cloud or self-hosted

Validate the workflow quickly in cloud, or install Callaba on infrastructure you control when data location, capacity planning, or private networking requires a self-hosted deployment.

Cloud live video transcoding

Start with a cloud deployment when you want to validate a real source, output profile, and routing path before planning fixed infrastructure.

Launch Callaba in the cloud

Self-hosted live video transcoding

Install the software on infrastructure you control and size compute or acceleration for the codecs, output profiles, and concurrent channels you plan to run.

Install Callaba self-hosted

Automation references

Automate transcoding workflows after the profile is proven

Use Callaba API modules when ingest, routing, stream state, and delivery outputs need to become part of your operator panel or application. Define and test the media workflow in the product first; automate it second.

Callaba Engine API overview

Frequently Asked Questions

What is live video transcoding?

Live video transcoding decodes an incoming feed and creates a supported output profile with different media settings, such as codec, resolution, bitrate, frame rate, or audio. It is useful when the source format does not match a destination or when one source must serve multiple playback profiles.

Is Callaba a hardware video encoder?

No. Callaba is software. A camera, OBS, vMix, mobile app, or hardware encoder sends a contribution feed into Callaba, and the software prepares supported routing and delivery outputs.

Which live video settings can Callaba normalize?

Depending on the selected workflow and available infrastructure, a profile can adjust supported codec, resolution, bitrate, frame rate, pixel format, GOP, and audio settings. Validate the exact input and output combination before production.

Can one input create adaptive or multi-bitrate outputs?

Yes, where the selected profile and deployment have the required capacity. One contribution feed can be used to create supported output variants for different bandwidth or playback requirements.

Can Callaba convert streaming protocols as well as media profiles?

Supported routes can separate the contribution protocol from the delivery protocol. This lets the source use the transport that fits contribution while the destination receives the handoff it expects.

Should I use cloud or self-hosted transcoding?

Use cloud for a fast proof of value and variable workloads. Choose self-hosted when you need direct control over infrastructure, private networking, data location, or capacity planning. Test your real media profiles in either model.

How do I start a live transcoding workflow?

Start with the cloud launch guide or the self-hosted installation guide. Connect the real source, define the required destination profile, validate quality and resource use, and only then automate it through the API if needed.

Processing