v0.2.0¶
Release Date: 2026-07-16
Adds batch avatar video generation (render) providers for HeyGen, Tavus, and bitHuman, and adopts the omniavatar-core v0.3.0 package rename (avatar → live) with a symmetric registry API.
Highlights¶
- Render providers for all three vendors: generate a talking-head MP4 from narration audio via HeyGen, Tavus, or bitHuman
- HeyGen and bitHuman render providers implement
render.AudioUploaderfor uploading local narration files - Symmetric registry API:
GetLiveProvider/GetRenderProvider(breaking rename; see below)
Breaking Changes¶
- Registry functions renamed for surface symmetry (the
*AvatarProvider*names are removed): RegisterAvatarProvider→RegisterLiveProviderGetAvatarProvider→GetLiveProviderListAvatarProviders→ListLiveProvidersHasAvatarProvider→HasLiveProviderGetAvatarProviderPriority→GetLiveProviderPriority- Requires omniavatar-core v0.3.0 (package
avatarrenamed tolive; renderAvatarLister/helpers). Direct imports ofomniavatar-core/avatarmust move toomniavatar-core/live
Added¶
- Render registry API:
RegisterRenderProvider,GetRenderProvider,ListRenderProviders,HasRenderProvider,GetRenderProviderPriority - Render surface for all three vendors — audio-driven talking-head generation via HeyGen, Tavus, and bitHuman. Following the PlexusOne convention, the render adapters live in the provider SDK repos (
heygen-go/omniavatar,tavus-go/omniavatar,bithuman-go/omniavatar), depending only onomniavatar-core. The batteriesproviders/{heygen,tavus,bithuman}packages register them alongside the live adapters. (The live/LiveAvatar adapters stay here because their LiveKit integration lives here.) - HeyGen and bitHuman render adapters implement
render.AudioUploader; the HeyGen adapter implementsrender.AvatarLister(v2 avatars) - All providers register both live and render surfaces via
providers/all - Unit tests: live/render registry behavior (registration, priority override, independence)
Documentation¶
- README.md and doc.go updated with quick starts for both surfaces and per-provider render options
- Render specs added under
docs/specs/render/(PRD, TRD, PLAN, ROADMAP) - MkDocs site added (getting started, provider pages, architecture/LiveKit/render-lifecycle guides, specs, releases) with a
DocsGitHub Actions workflow deploying viamkdocs gh-deploy