Knowledge base
How this actually works
Short explainers on audio-reactive avatars, automated video production, and the parts of Orb Studio worth understanding before you rely on them. Demos where a demo helps, sourced data where a number is claimed, and the honest limits of each feature.
-
The bottleneck 0:42
Why most teams cap out at one video a month
Three quarters of companies publish at least one video a month and almost none publish more. The ceiling is production capacity, not ideas — and the teams that broke through it changed the workflow, not the budget.
-
Fundamentals 0:38
What an audio-reactive avatar actually is
Not a video file, and not a puppet rig. An audio-reactive avatar is a live render driven by the loudness and rhythm of a voice — which is why it can change style instantly and export identically on any machine.
-
How to 0:35
Putting the avatar in OBS, Zoom and Meet
Orb Studio deliberately does not install a virtual camera driver. Here is the route that works instead — a chromeless always-on-top window, the Broadcast preset, and OBS as the bridge.
-
Under the hood 0:40
How the agent decides which clip to show
An AI casting b-roll cannot watch your footage. It reads what you wrote about it — which is why the Asset Library is a described library, not a folder.
-
Record mode 0:44
Three ways to record a demo
You drive, you show it once, or the agent drives. The right choice depends on how well the workflow is known — and only one of them is reliable on an unfamiliar UI.
-
Trust 0:36
What runs on your machine, and what doesn't
Orb Studio ships with no API keys and no account. Here is exactly which work happens locally, which work leaves for a provider you chose, and where the boundary sits.