wLipSync


This is a compatibility fork specialized for the bolt-cep Adobe extension framework. Unlike the original library, you must manually call the init() function before use (refer to www/index.ts for implementation details), as Top-level Await was removed to ensure compatibility with older CEF/Chromium environments.



A MFCC-based lip sync library for WebAudio using WASM. This is a port of the uLipSync project.

Usage

Either install the package from npm or load it using import maps:
``HTML

`

The main entrypoint is a single file which has the WASM binary and audio worklet processor code inlined, meaning no further steps are required to initialize the library. See the following code on how to use the library:
`JS
// Import wLipSync
import { createWLipSyncNode } from 'wlipsync';

// Create Audio context
const audioContext = new AudioContext();

// Load wLipSync profile
const profile = await fetch('./profile.json').then(resp => resp.json());

// Create lip sync node
const lipsyncNode = await createWLipSyncNode(audioContext, profile);

// Connect audio source (e.g. audio file, microphone, etc...) to lipsync node
source.connect(lipsyncNode);

// ...

// Read current phoneme state in update/animation loop
console.log(lipsyncNode.weights, lipsyncNode.volume);
`

For a full example using Three.js and a VRM avatar, see the ./example/ folder.

> [!IMPORTANT]
> Since the project uses AudioWorklets it requires a secure context (either localhost or https://).

Creating a profile

A profile is required for wLipSync to work. This project does not come with a way to create these. Instead they can be made in Unity using uLipSync by following their Calibration instructions.

Using binary profiles

By default the profiles are stored in JSON format. While these files tend to compress nicely, a more compact binary representation is also supported by wLipSync. This format not only packs the data, it also stores precomputed values which would otherwise be computed at runtime when loading a profile.

To convert a JSON profile into a binary profile, the json2bin utility in the tools/ directory can be used. This script is also included in the published NPM package, meaning you can run it from your project using the following command:
`sh
node ./node_modules/wlipsync/tools/json2bin.js path/to/profile.json profile.bin
`

To load a binary profile, the following change needs to be made to the code sample above:
`diff
// Import wLipSync
-import { createWLipSyncNode } from 'wlipsync';
+import { createWLipSyncNode, parseBinaryProfile } from 'wlipsync';

// ...

// Load wLipSync profile
-const profile = await fetch('./profile.json').then(resp => resp.json());
+const binaryProfile = await fetch('./profile.bin').then(resp => resp.arrayBuffer());
+const profile = parseBinaryProfile(binaryProfile);

// Create lip sync node
const lipsyncNode = await createWLipSyncNode(audioContext, profile);
`

Building

The project consists of a C part compiled to WASM and corresponding TypeScript code. Everything can be compiled by running bun run build as this will execute all relevant commands in the right order. The following tools are expected to be present on the system:

* clang
* wasm-ld
* wasm-opt (from binaryen)
* make

Development

For testing during development, perform a full build:
`
bun run build
`

Now you can start the dev server, which should listen for changes to any file:
`
bun run
`

> [!NOTE]
> Currently the dev server shows the example which uses the wlipsync-single.js file. As this file inlines the minimized audio-processor.js and optimized wlipsync.wasm` a full build is required to observe changes.