-
Notifications
You must be signed in to change notification settings - Fork 111
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 firing #18
Comments
I was able to configure MultiStreamMixer correctly. I am getting events firing from the local stream. But when I use MultiStreamMixer, audioMixer.appendStreams([event.stream]); Doesn't add the additional audio track. This new track does not show up in the file saved. Only localStream.. Update when I build MultiStreamsMixer with both the peer and the local stream it works. If I appendStreams after construction it does not add audio,... looking like bug. Adding stream after recording started , DOES NOT ADD stream to recording. |
I'll fix it in the next release. Relevant: muaz-khan/RecordRTC#536 My plans are:
|
Actually I was still including the MultiStreamMixer.js from your website, I removed this references and now RecordRTC is using the patched( from your commit) internal MultiStreamMixer and it does seem to be recording. Thank you for being so attentive. Do you know if this is possible to do headless on server? Local Stream really isn't too important because the idea is to record all the peer connections. |
@chrismpalmer |
@chrismpalmer Can you explain how you did this? |
hey @muaz-khan , the commit on MultiStreamMixer package works, but wasn't merged with the lib, neither RecordRTC. Is there any prediction of a merge soon? |
I am using webrtc and I haven't been able to successfully mix the peer streams and receive ondataavailable events?
In webrtc, when a new stream is added
if ( audioMixer ) {
audioMixer.appendStreams([event.stream]);
}
Once I do this there are no ondataavailable events. If I only add the local stream I get ondataavailable.
Thanks
The text was updated successfully, but these errors were encountered: