-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How many milliseconds of delay does different chunk correspond to? #17
Comments
The latency is only related to chunk size and sampling rate(conv2d, 40ms), so for chunk 1, the delay is 1 * 40=40ms, and for chunk 16, the delay is 16 * 40 = 640ms. We are preparing the paper, I will provide the paper link in a few days once it is ready. |
Thanks for your reply. |
Hi TeaPloy, please see more details at https://arxiv.org/abs/2012.05481, the paper is the first draft, we are still refining it. Hope it helps. |
Thanks. |
Bother you again, whether the history context is infinite? |
* [runtime] refactor decoder, asr_model to support more platforms * fix topo error when rescoring * support Copy for asr_model * fix wrong check * refine copy * set inter-op thread
I notice chunk 1 degradation 30% (from 5.51 to 7.83) in section "Unified Dynamic chunk" ctc greedy search.
Please let me know if my understanding is incorrect:
Chunk 1 delay conversion is 12layers*1chunk*40ms(conv2d) = 480 ms.
The text was updated successfully, but these errors were encountered: