You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to get ASR + segmentation to run on a mobile phone (Pixel 6A, 6GB ram). This time on Brave mobile ;-)
ASR alone works fine. But I have a question about also getting the speaker recognition to run (segmentation+verification).
In the example implementation a promiseAll is used to run both ASR and Segmentation in paralel. For my implementation I've tried to run them one after the other, hoping that this would mean less memory is needed. E.g:
Create ASR instance
-- Get text and chunks from audio
Dispose of ASR instance
Create segmentation instance
-- Get segments from audio
Dispose of segmentation instance
Create verification instance
-- Run verification on chunks of audio from each segment
Dispose of verification instance
I don't know if it's related, but I noticed the error below:
My questions are:
Is it a valid assumption that doing things consequtively will allow this cascade to run on devices with less memory? Or was there a good reason that a promiseAll was used?
What does the error mean?
Is running them consecutively part of why the error occurs?
Can I use quantized with the segmentation and verification models in order to save memory? Currently the ASR (tiny-whisper.en_timestamped) is 114MB, and then the segmentation and verification seem to be 512 MB together.
I haven't split up loading the segmentation and verification instances yet, as I thought I'd get your opinion first.
Question
I'm trying to get ASR + segmentation to run on a mobile phone (Pixel 6A, 6GB ram). This time on Brave mobile ;-)
ASR alone works fine. But I have a question about also getting the speaker recognition to run (segmentation+verification).
In the example implementation a
promiseAll
is used to run both ASR and Segmentation in paralel. For my implementation I've tried to run them one after the other, hoping that this would mean less memory is needed. E.g:Create ASR instance
-- Get text and chunks from audio
Dispose of ASR instance
Create segmentation instance
-- Get segments from audio
Dispose of segmentation instance
Create verification instance
-- Run verification on chunks of audio from each segment
Dispose of verification instance
I don't know if it's related, but I noticed the error below:
My questions are:
quantized
with the segmentation and verification models in order to save memory? Currently the ASR (tiny-whisper.en_timestamped) is 114MB, and then the segmentation and verification seem to be 512 MB together.I haven't split up loading the segmentation and verification instances yet, as I thought I'd get your opinion first.
The text was updated successfully, but these errors were encountered: