- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Mar 2017 14:31:42 +0000
- To: public-media-capture-logs@w3.org
I have naive recording needs, so I don't consider myself a stake-holder here. However, I'm biased against "What should happen?" issues. I'm a fan of use-cases driving functionality, not the other way around. We also seem to be talking about at least two things: 1. What's the least confusing API separation between live sources and a recorder? 2. We want to solve problems that seem to hinge on being able to add/remove things mid-way of a recording. On the first point, RTCPeerConnection switched from `addStream` to `addTrack` exactly to avoid streams becoming remote controls for peer connection functionality. MediaRecorder may be different, but I'm not hearing any reasons to think so. But even if we were to pivot to tracks in MediaRecorder, I'd have the same questions about what kinds of modification functionality we desire. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/4#issuecomment-286759507 using your GitHub account
Received on Wednesday, 15 March 2017 14:31:50 UTC