Thank you. That clears things up. FYI - I was revoking the object url before assigning it again the next time a pc was created, so you likely have a bug there.
On Thu, Oct 17, 2013 at 11:06 AM, Randell Jesup <[email protected]> wrote: > On 10/17/2013 12:43 PM, [email protected] wrote: > >> I've noticed a couple of problems related to the localMediaStream >> >> First is an error when calling pc.removeStream(localStream) >> > > Firefox doesn't yet support pc.removeStream() > > > Second is a problem with serial reuse of the stream in a push-to-talk >> scenario >> >> Stream reuse works fine if my local display is assigned using >> video.mozSrcObject = localStream >> >> However, if I have used video.src = URL.createObjectUrl(**localStream) >> then >> the stream fails silently and does not emit audio/video after a couple of >> uses. >> > > One of the problems with createObjectURL() is it's hard (ok, impossible) > to tell when the URL is no longer in use. The working group is moving > towards video.srcObject = stream because of this, and I believe we're > deprecating createObjectURL() for streams. See the minutes from a recent > W3 Media Capture telco call and the mailing list. I think we could find > only one legitimate use for a textual representation of an object. > > > So, on to my questions: >> >> Is it necessary to call pc.removeStream if I am calling pc.close() >> immediately afterward? >> > > No. You can close() a stream connected to things; it will cause it to > send black/silence and stop sending in general. > > > What is the offiicial position on mozSrcObject vs createObjectURL ? >> > > See my comments above. > > -- > Randell Jesup, Mozilla > ______________________________**_________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/**listinfo/dev-media<https://lists.mozilla.org/listinfo/dev-media> > _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
