Audio, video and Lottie

Integration

KUI media adapters connect audio/video to their backends. kui_media_audio and kui_media_video use the media protocol and do not register new DOM elements. Check decoder backends, DLL dependencies, formats and platform scope. Parsing a file does not prove device playback.

Constraints and troubleshooting

Lottie rendering uses Skia's Skottie module. Verify loading, initial playback, pause, completion, errors and release rather than just the first frame. Silent tests without devices and actual audio/video device validation are separate evidence.

Audio and video elements

audio and video use built-in media elements. Playback depends on deployed backends, resource paths and decoder dependencies. controls requests controls; check autoplay, seeking and invalid files against the target package.

<audio src="media/notification.wav" controls></audio>
<video src="media/clip.mp4" controls
  style="width:100%;height:360px"></video>

Backends and dependencies

kui_media_audio provides the audio backend. kui_media_video provides FFmpeg video decoding and audio playback. Check backend DLLs, decoding dependencies and their licenses when distributing. An accessible file and recognized container do not guarantee every codec.

• Media examples →
• Media APIs →

From playback to delivery

Verify a minimal scenario in this order before integrating the full application.

1. Establish playback with a known local asset before using a URL.
2. Check codecs, backends and dependencies; an extension alone does not prove support.
3. Test start, pause, end, loading failure and resource release.
4. Include asset and dependency licenses in delivery; Lottie and video use different paths.