-
Notifications
You must be signed in to change notification settings - Fork 156
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 to clear the sinewave when started new recording. #25
Comments
Any suggestion on this please... |
clear() {
const { canvasCtx, width, height } = this.state;
canvasCtx.clearRect(0, 0, width, height);
} A fix would be clear() {
const { width, height } = this.props;
this.state.canvasCtx.clearRect(0, 0, width, height);
} But it will stay clear for a few ms only as as the |
@kkkrist, I implemented your bug fix. What else needs to change in the |
Hey @hackingbeauty, I got rid of the Wave with visualSetting="false". Is there a way to remove the canvas completely? Thanks a lot for the good work |
@AsyncSan You could just take the MicrophoneRecorder lib from react-mic and use it in your own custom UI component. This is how mine looks: https://gist.github.com/kkkrist/6f985ee0f3e6d7c206fd399786262643 (Most of it is about uploading and safely overwriting previous recordings – e.g. attaching only the latest recording to the parent document when it's actually saved – but you get the idea) @hackingbeauty Thanks! Will take another look at Visualizer when I have more time. |
This issue has been fixed with version 12.4.0 of React-Mic. Thank you! |
When i start recording for very first time the sinewave context is clear... when i stop recording the sine wave is staying as is, so here when recording is stopped, the sinewave has to be cleared.. how to achive that....?
So how to achieve clearing sinewave when stopped recording... we are passing the "record" state as true and false when started and stopped recording... but still sinewave stays... can you please let us know..
Is this anything to do with visualizer? how to clear that too...
The text was updated successfully, but these errors were encountered: