Replies: 2 comments
-
I’ve been unable to confirm if there’s a problem in wavesurfer code. These events are only emitted when audio is playing for me. Maybe you could share a minimal piece of code to replicate this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Did you figure it out? I am also facing the same problem |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug description
I have implemented the wavesurfer & used its recording plugin in react js. Played default audio & then recording need to be started as soon as it get ended. So, in order to achieve this if i subscribe to any event out of timeupdate & audioprocess, it keeps on firing when default audio ends and even recording stop (stopRecording() record plugin events), which in turns add loads to browser & hang/freeze the chrome browser.
Environment
Expected result
It should clear the events on its own, when stopRecording() or wavesurfer.stop() event called.
Obtained result
It hang the browser, even replaying the audio after recording freeze the wavesurfer.
Beta Was this translation helpful? Give feedback.
All reactions