Prior to the landing of
https://bugzilla.mozilla.org/show_bug.cgi?id=823512, the callbacks were
all spoofed using normal function calls rather than event processing.
This has several implications, one of which is the behavior you describe
below.
The patch for that bug has landed on Firefox 24
On Fri, Jun 21, 2013 at 9:27 AM, Ralph Giles wrote:
> On 13-06-21 9:14 AM, Eric Rescorla wrote:
>
> > I believe you and cullen are thinking along different lines. You're
> thinking
> > of static files but he's thinking of WebRTC. Since WebRTC has codec
> > negotiation, the issues you are raising
On 13-06-21 7:02 AM, Cullen Jennings wrote:
> So Daala has made it to slashdot, how come it has not made it to my favorite
> browser?
I filed a tracking bug.
https://bugzilla.mozilla.org/show_bug.cgi?id=885771
-r
___
dev-media mailing list
dev-media@
On 13-06-21 9:14 AM, Eric Rescorla wrote:
> I believe you and cullen are thinking along different lines. You're thinking
> of static files but he's thinking of WebRTC. Since WebRTC has codec
> negotiation, the issues you are raising here don't apply. You just offer
> "Daala version XXX" and the sy
On Fri, Jun 21, 2013 at 8:49 AM, Ralph Giles wrote:
> On 13-06-21 7:02 AM, Cullen Jennings wrote:
>
> > Seriously, why not put it in Firefox and develop this in an agile way,
> just let it keep getting better, break the bitstream whenever for now, just
> put it in and iterate. We need to realize
Robert Kaiser wrote:
widely enough. Apart from that, every line of code adds a maintenance,
stability and security risk to our product, and codec are usually
millions of lines of code, therefore large risks in those terms. For
For reference, sloccount in media/libtheora says 12,594 LOC, and in
Cullen Jennings schrieb:
So Daala has made it to slashdot, how come it has not made it to my favorite
browser?
Well, I think Monty wrote that they only encoded and decoded the first
Daala video experimentally on May 31 or something like that. This means
that there probably isn't a library ye
On 13-06-21 7:02 AM, Cullen Jennings wrote:
> Seriously, why not put it in Firefox and develop this in an agile way, just
> let it keep getting better, break the bitstream whenever for now, just put it
> in and iterate. We need to realize that a successful video codec is partially
> a technical
So Daala has made it to slashdot, how come it has not made it to my favorite
browser?
OK - I realize it is uh, not fully baked, yet. Actually I would describe it as
we were still mixing the flour with the milk for this cake and have not added
the vanilla yet much less starting baking it but ….
When I log the 'this'-Object inside of the onaddstream-Handler to the console,
instead of observing it in Firebug, I can see that it equals the
onaddstream-Function.
But I am still of the opinion, that 'this' (inside of the onaddstream-Handler)
should refer to the corresponding RTCPeerConnect
When I log 'this' inside of the onaddstream-Handler to the console, instead of
observing it in Firebug, I can see that 'this' equals the onaddstream-Function.
But I would still expect that 'this' inside of the onaddstream-Handler should
be the current RTCPeerConnection-Object, on which the onad
Hi all,
I´m currently adding a WebRTC-Videochat to our existing Instant-Messaging. Now
that in Google Chrome everything works fine, I´ve tried to connect 2
Firefox-Beta (Version 22) with each other.
In the onaddstream-Handler, I try to access properties of the current
RTCPeerConnection-Object.
12 matches
Mail list logo
