linto-ai/webvoicesdk

Buildings block for voice-enabled applications in the browser

webvoicesdk's Issues

Hotwords detection is not working with a fresh build

Description

Hotword service worker throw an error message ExitStatus {name: "ExitStatus", message: "Program terminated with exit(1)", status: 1} after a fresh build.

How to reproduce

• Empty the node_module
• Run npm install
• Run npm test
• Go to http://localhost:1234, open the console and run the hotword pipeline

I'm afraid that my knowledges and skills doesn't allow me a further investigation ...

Needs an AGPL warning at the top of the documentation

You library is awesome, it solved all my problems, and I will never be able to use it due to your license choice.

I appreciate it's your code, and you can do what you like with it, but doesn't it seem a waste that another project doing exactly the same thing will need to be created and maintained by someone, just to remove the license restriction that AGPL imposes? If I include your library in my larger web application, releasing all the source code to our competitors is simply not going to fly.

To avoid wasting other people's time spent integrating this, please include a large warning at the top of the readme, indicating it's basically not suitable for most commercial use. If you want to be super-helpful, pointing us to competing projects with different licenses would be rather nice.

It's such a shame, as it works really well.

Calling mic.stop() is not working once hotword has been spotted

Hi Damien,

I'm facing a quite weird issue :
When calling mic.stop() at a first place everything works as expected that means the following icon disappears. But once 'LinTO' hotword has been spotted calling mic.stop() has no effect.

So I tried modifying WebvoiceSDK since track we got had an "ended" status :

this.stream.getTracks().forEach((track) => {
  if (track.kind === 'audio' && typeof track.stop === 'function') track.stop()
})

But still the mic icon persists.

Do you got any idea on how to really stop listening the user ?

Thank you

Recorder is not working on safari

See #1

How to use it in react js , with custom wake word?

Hi i am looking forward for good hotword detection library purely in node js, and i found WebVoiceSDK, it's performance in the demo is really good.
Now can you tell me how to utilise it in react js and with custom wakeword?

any refrence ? if so then this library has very good potenital to scale up.

Recorder on mobile imply a jerky wav output

Description

When using the Recorder on a mobile, the generated wav is damaged.
Mic options :

{
      frameSize: 4096,
      constraints: {
        echoCancellation: true,
        autoGainControl: true,
        noiseSuppression: true
      }
    }

Attached to this issue you'll find a zip (github does not accept audio files to be attached) containing 3 audio files :

• desktop.wav recorded on a desktop with WebVoiceSDK.Recorder
• mobile.wav recorded on an iPhoneX with WebVoiceSDK.Recorder
• usermedia-mediarecorder.webm recorded with native MediaRecorder and navigator.mediaDevices.getUserMedia({ audio: true })

Archive.zip

Do you have any ideas on a way to solve this problem ?
Maybe once I'll be able to start the project I can add "Record mic" "Stop record mic" buttons to the test page and consequently to https://webvoicesdk.netlify.app/
That way we'll be able to test the recorder across many devices.

Thank you

EDIT: After further investigation output wave audio is cleaner if I disable other intensive task (gesture recognition) on my webapp. Anyway that means transcoding AudioContext stream to WAV will be affected when available ressources are low. Maybe we can add options in the Recorder constructor to allow developers to opt for a more Native recording system.

parcelRequire is not defined in Electron build

when using Electron to build desktop app .
after build in exe its happen

but after serve in browser its fine

how to solve ?

Dependency update broke the library

After a fresh build the WASM file doesn't work. A month or two ago everything was working as expected.
npm install + npm test:
Errors in firefox:

Module.asm.c.apply is not a function

this.wasmInterface is undefined

Errors in chrome:

TypeError: ___wasm_call_ctors.apply is not a function

Uncaught TypeError: Cannot read properties of undefined (reading 'HEAPF32')
    at Rnnoise.copyPCMSampleToWasmBuffer

Also, is it possible to prevent such issues by either adding a package-lock file or specifying the version?