Skip to content
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

Open
alqa-dash opened this issue Jan 23, 2023 · 0 comments
Open

ondataavailable not fired with waveWorker #274

alqa-dash opened this issue Jan 23, 2023 · 0 comments

Comments

@alqa-dash
Copy link

alqa-dash commented Jan 23, 2023

Hello,

As stated in documentation:

rec.ondataavailable( arrayBuffer )
A callback which returns an array buffer of audio data. If streamPages is true, this will be called with each page of
encoded audio. If streamPages is false, this will be called when the recording is finished with the complete data.

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.

@alqa-dash alqa-dash changed the title ondataavailate not fired ondataavailable not fired with wavaWorker Jan 25, 2023
@alqa-dash 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant