-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Broken stopRecording using RecordRTC with Chrome #210
Comments
Hi. I'm with the same problem. But in Chrome 56.0.2924.87 (64-bit) is working. Wating for a suggestions. |
You can add a looper here to check MediaRecoder state: self._stop = self.stop;
self.stop = function(cb) {
self.manuallyStopped = true;
self._stop(cb);
};
(function(looper) {
if (mediaRecorder) {
console.log(mediaRecorder.state);
}
if (mediaRecorder && mediaRecorder.state == 'inactive') {
if (!self.manuallyStopped) {
mediaRecorder.start(10 * 60 * 1000);
}
}
setTimeout(looper, 1000);
})(); |
Thanks, that fixed the issue... The info you posted was for MediaStreamRecorder.js (which I'm assuming you're developing more now?), so here's the updated code to be stuck into RecordRTC.js at line 1771 for anyone who needs it:
|
@bcbud can you create a pull request? |
@muaz-khan can this be closed? |
Previous versions of Chrome worked fine, but the new version [Version 56.0.2924.87] seems to break/not execute the following line in stopRecording (note: still works fine in FF).
RecordRTC.js - line 107:
mediaRecorder.stop(_callback);
MediaRecorder object is created and defined as:
But when it comes time to call recordRTC.stopRecording, Chrome stops executing after the (!== gif) check...
RecordRTC.js - Line 94:
Again, this works perfectly fine in FF, but has recently stopped working in Chrome.
Any suggestions or workarounds?
The text was updated successfully, but these errors were encountered: