forked from mattdiamond/Recorderjs
-
Notifications
You must be signed in to change notification settings - Fork 172
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
ondataavailable not fired with waveWorker #274
Comments
alqa-dash
changed the title
ondataavailate not fired
ondataavailable not fired with wavaWorker
Jan 25, 2023
alqa-dash
changed the title
ondataavailable not fired with wavaWorker
ondataavailable not fired with waveWorker
Jan 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
As stated in documentation:
But is doesn't work with:
recorder = new Recorder({encoderPath: "waveWorker.min.js", streamPages: true});
I figured out than when recorder has been created this way, the waveWorker doesn't react to "flush" command neither in AudioWorkletGlobal nor in scriptProcessor scope.
I can provide pr but never did it before.
The text was updated successfully, but these errors were encountered: