4 ms·

Haha nice one. Okay yeah I believe it (can imagine 0.02, which is close enough). Although I have to mention judging by when the text appears it's above 0.5, but

• lunixbochs 7y ago
  Sure, that's probably the VAD, which can be tuned (the VAD decides if your phrase is done or not yet). That's part of why I included activity monitor watching w2l, so you could see it wasn't using any CPU while I talked. Would probably be more convincing if I printed something at the moment the VAD cut off the user so you could visually judge from the boundary of what we considered their speech. This video can be partially reproduced with the code and models from here: https://github.com/facebookresearch/wav2letter/issues/327 https://github.com/facebookresearch/wav2letter/issues/327 but most of our decoder optimizations post-date when I compiled that demo. Some of the later code is here: https://github.com/talonvoice/wav2letter/tree/w2lapi_static https://github.com/talonvoice/wav2letter/tree/w2lapi_static https://github.com/ckamm/wav2letter/tree/wip-parallel https://github.com/ckamm/wav2letter/tree/wip-parallel Here is the exact timing loop code I used in that demo: https://bochs.info/p/nhz5cv https://bochs.info/p/nhz5cv
  • Nimitz14 7y ago
    Are your acoustic models 400MB?