createAsyncRuntime

Creates a runtime that reads media whose bytes may answer later, from an AsyncMediaByteSource. The caller owns the runtime and closes it.

On the JVM, Android and native the runtime owns one thread, and FFmpeg waits there while the byte source works elsewhere. On the web this call fails: a runtime there is a codec module of its own, so create it with KiteFFmpegWeb.loadAsyncRuntime or KiteFFmpegWeb.attachAsyncRuntime. The placeholder backend has no FFmpeg and fails too.

Creates a runtime that reads media whose bytes may answer later, from an AsyncMediaByteSource. The caller owns the runtime and closes it.

On the JVM, Android and native the runtime owns one thread, and FFmpeg waits there while the byte source works elsewhere. On the web this call fails: a runtime there is a codec module of its own, so create it with KiteFFmpegWeb.loadAsyncRuntime or KiteFFmpegWeb.attachAsyncRuntime. The placeholder backend has no FFmpeg and fails too.

Creates a runtime that reads media whose bytes may answer later, from an AsyncMediaByteSource. The caller owns the runtime and closes it.

On the JVM, Android and native the runtime owns one thread, and FFmpeg waits there while the byte source works elsewhere. On the web this call fails: a runtime there is a codec module of its own, so create it with KiteFFmpegWeb.loadAsyncRuntime or KiteFFmpegWeb.attachAsyncRuntime. The placeholder backend has no FFmpeg and fails too.

Creates a runtime that reads media whose bytes may answer later, from an AsyncMediaByteSource. The caller owns the runtime and closes it.

On the JVM, Android and native the runtime owns one thread, and FFmpeg waits there while the byte source works elsewhere. On the web this call fails: a runtime there is a codec module of its own, so create it with KiteFFmpegWeb.loadAsyncRuntime or KiteFFmpegWeb.attachAsyncRuntime. The placeholder backend has no FFmpeg and fails too.

Creates a runtime that reads media whose bytes may answer later, from an AsyncMediaByteSource. The caller owns the runtime and closes it.

On the JVM, Android and native the runtime owns one thread, and FFmpeg waits there while the byte source works elsewhere. On the web this call fails: a runtime there is a codec module of its own, so create it with KiteFFmpegWeb.loadAsyncRuntime or KiteFFmpegWeb.attachAsyncRuntime. The placeholder backend has no FFmpeg and fails too.