1. ML noise suppression didn't work on npm start. The denoise worklets, wasm and models were only copied into dist/public/element-call/denoise/ by the lotus-denoisecloseBundle hook. On the dev server the call frame got the SPA fallback (MIME type mismatch) and silently fell back to the raw mic.
The asset list is now one denoiseSources() shared by the build copy and a new configureServer middleware. The middleware serves the same /public/element-call/denoise/… paths in dev, with JS/wasm content types.
The DTLN tree lookup refuses paths outside its directory.
The build's checks and error messages are unchanged; the DeepFilterNet error string became a template literal (it was already failing prefer-template).
2. lotusTheme warning in every call.getWidget now sends lotusTheme=true along with lotusTransparent. The fork applied the theme anyway and logged lotusTransparent is set without lotusTheme each call.
Verified on the dev server (npx vite):
rnnoiseWorklet.js, speexWorklet.js, noiseGateWorklet.js, workadventure/audio-worklet.js and deepfilternet/index.esm.js return 200 text/javascript; rnnoise.wasm and df_bg.wasm return 200 application/wasm. Before, they got the HTML fallback.
Joining a call with ML / RNNoise logs [lotus] denoise processor active (rnnoise, floor=0.15), and no lotusTheme warning.
Seen while testing (not changed here): the host doesn't handle the fork's io.lotus.denoise_state ("host did not ack"), so a silent ML fallback (#260) still isn't surfaced in the UI.
Fixes #293.
**1. ML noise suppression didn't work on `npm start`.** The denoise worklets, wasm and models were only copied into `dist/public/element-call/denoise/` by the `lotus-denoise` `closeBundle` hook. On the dev server the call frame got the SPA fallback (MIME type mismatch) and silently fell back to the raw mic.
- The asset list is now one `denoiseSources()` shared by the build copy and a new `configureServer` middleware. The middleware serves the same `/public/element-call/denoise/…` paths in dev, with JS/wasm content types.
- The DTLN tree lookup refuses paths outside its directory.
- The build's checks and error messages are unchanged; the DeepFilterNet error string became a template literal (it was already failing `prefer-template`).
**2. `lotusTheme` warning in every call.** `getWidget` now sends `lotusTheme=true` along with `lotusTransparent`. The fork applied the theme anyway and logged `lotusTransparent is set without lotusTheme` each call.
**Verified** on the dev server (`npx vite`):
- `rnnoiseWorklet.js`, `speexWorklet.js`, `noiseGateWorklet.js`, `workadventure/audio-worklet.js` and `deepfilternet/index.esm.js` return **200 text/javascript**; `rnnoise.wasm` and `df_bg.wasm` return **200 application/wasm**. Before, they got the HTML fallback.
- Joining a call with ML / RNNoise logs **`[lotus] denoise processor active (rnnoise, floor=0.15)`**, and no lotusTheme warning.
Seen while testing (not changed here): the host doesn't handle the fork's `io.lotus.denoise_state` ("host did not ack"), so a silent ML fallback (#260) still isn't surfaced in the UI.
`tsc` clean · unit tests pass.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
The denoise worklets/wasm/models were only copied into dist/ by the
lotus-denoise closeBundle hook, so on the dev server the call frame got
the SPA fallback for them and silently used the raw mic. The asset list
is now shared (denoiseSources) between that copy and a dev-server
middleware serving the same paths. Also send lotusTheme=true with
lotusTransparent, which the fork warned about in every call.
Fixes#293
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
jared
merged commit 4bfb51c5fe into lotus2026-10-18 09:59:53 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #293.
1. ML noise suppression didn't work on
npm start. The denoise worklets, wasm and models were only copied intodist/public/element-call/denoise/by thelotus-denoisecloseBundlehook. On the dev server the call frame got the SPA fallback (MIME type mismatch) and silently fell back to the raw mic.denoiseSources()shared by the build copy and a newconfigureServermiddleware. The middleware serves the same/public/element-call/denoise/…paths in dev, with JS/wasm content types.prefer-template).2.
lotusThemewarning in every call.getWidgetnow sendslotusTheme=truealong withlotusTransparent. The fork applied the theme anyway and loggedlotusTransparent is set without lotusThemeeach call.Verified on the dev server (
npx vite):rnnoiseWorklet.js,speexWorklet.js,noiseGateWorklet.js,workadventure/audio-worklet.jsanddeepfilternet/index.esm.jsreturn 200 text/javascript;rnnoise.wasmanddf_bg.wasmreturn 200 application/wasm. Before, they got the HTML fallback.[lotus] denoise processor active (rnnoise, floor=0.15), and no lotusTheme warning.Seen while testing (not changed here): the host doesn't handle the fork's
io.lotus.denoise_state("host did not ack"), so a silent ML fallback (#260) still isn't surfaced in the UI.tscclean · unit tests pass.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5