►
From YouTube: Jitsi Live Stream
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Oh,
this
is
the.
B
A
We
have
someone
joining,
let's
give
it
a
second,
then
hi,
jignesh
just
started
hey
guys.
Everyone
just
was
about
to
start
so
not
many
people
from
our
King
Julien
Thicke's.
We
have
an
internal
deadline,
so
I
really
only
120
here
today,
just
a
quick
update
from
what
we've
been
doing
the
last
couple
weeks,
there
was
a
little
bit
of
work
on
handling
sequence
number
gaps
during
all
the
mutes
that
George
worked
on.
I
think
that
that
also
included
some
work
from
from
Miriam
and
your
brain.
A
There
was
also,
let
me
think
about
that.
What
else
was
there
there's
some
quite
some
good
progress
on
the
react,
application
which
now
already
also
handles
deep
link
integration
and
a
number
of
fixes
currently
we're
working
on
addressing
this
problem
in
the
chrome
jitter
buffer.
That
would
not
render
audio
unless
it
also
has
video
for
audio
video
media
streams.
A
I
will
making
the
bridge
able
we're
basically
changing,
at
this
end
of
a
black
frame,
a
black
key
frame
to
every
participant
who
joins
in
order
to
invoke
the
jitter
buffer
and
make
sure
that
this
doesn't
happen.
This
way
we
can
do
lip-syncing
without
complicated
gymnastics
and
the
signaling
arm,
and
we
have
a
bunch
of
fixes
planned
or
meet
for
this
week.
Bunch
of
visual
fixes
are
like
having
room
lock
notification
sent
to
everyone,
so
the
lock
button
will
display
properly
and
proper
state
everywhere.
A
There's
a
bug
with
the
toolbar
that
disappears,
even
though
the
mouse
is
on
top
of
it.
There's
a
few
adorations
there
as
well.
So
this
is
partially
that
will
be
reworking
the
settings
dialog
and
that's
that's
pretty
much
it
on
our
side.
I,
don't
have
anything
else.
So
if
you
guys
want
to
talk
about
something,
have
you
know
do.
C
C
A
You
that
doesn't
happen
with
hangouts.
C
C
C
A
Yeah
that
logic
it's
different,
because
that
we
have
access
to
the
full
RTP
stream
there
and
we
can
actually
count
frames,
and
we
know
that
we've
we
got
that
many
frames
on
one
layer
and
known
flames
on
the
other
layer.
So
a
we
have
more
information
and
be
with
the
situation,
allows
for
more
easier
detection.
Now
it
will
be
totally
different
if
you're,
if
you're
the
web
page
and
you're,
trying
to
figure
out
that
your
browser
did,
that
I
would
say:
I'm
sorry,
I.
A
Locally,
the
same
thing
would
be
true
for
simulcast.
We
don't
do
that
detection
locally
and
simulcast.
It
would
have
been
great
because
we
were
actually
well
that's
different,
now
becomes
going
to
say
we
will
be
great
to
have
controlling
and
or.
C
Better
would
be
something
like
TN
and
they
are
right,
because
that's
really
what
you
want,
we
don't
want
to
renegotiate.
This
is
going
to
probably
happen
at
some
high
freq,
like
potentially
high
frequency.
You
want
to
do
offer
an
answer,
so
you
really
rather
like
it
really
be
nice.
They
did
on
the
level
of
a
flow
control.
So
when
it
comes
on
and
off
like
you,
don't
have
to
do
some
big
renegotiation.
The
bridge
yeah.
A
C
A
A
Inside
a
congestion
control
right,
they
have
this
thing
where.
A
Which
would
allow
the
sender
to
make
the
old
the
bandwidth
estimations
in
so
are
even
REM.
Bees
will
be
dropped
or
not
sure
I,
don't
think
they
they're
planning
for
a
lot
of
sfu
side
control
in
interaction,
yeah.
C
Well,
that
sucks
I
mean
the
control
control
here.
I,
don't
care
about
I,
just
think
just
something
knowing
the
notification
side
such
that
like
this,
that
right
and
we
can
avoid
a
frozen
image,
basically
getting
stuck
on
a
receiver
because
timing
out,
because
his
network
socks,
Nov,
just
intentionally
suspended
the
video
stream.
C
A
C
Guess
it
would
be
nice
to
have
the
sender,
probably
what
we
would
want
is
we
would
want
on
that
client
you
I,
to
show
something
like
hey:
we've
temporarily,
you
know
suspended
your
camera
video
due
to
network
issues
or
something
I
mean
we
could
circuitous
Lee
do
that
by
having
the
bridge
or
see
something
at
you
know
the
media
layer
and
then
firing
some
notification
down
because
will
probably
send
that
down
to
everyone,
but
so
I
guess
it
doesn't
really
matter.
I
mean
we
could
probably
make
either
one
more.
A
Okay,
oh
well,
I
I'd
say
that
if
you
want
to
show
it
in
the
client,
then
it
would
probably
be
better
to
have
an
API
thing,
because
otherwise
you
have
to
send
it
to
the
server.
And
besides
it's
going
to
be
rtcp,
so
we're
not
even
certain
that
you're
going
to
get
it
then
send
it
back
from
the
server
to
the
client
on
the
signaling
layer
and
then
show
it
in
the
client.
So
if
you
think
of
it
that
way,
then
maybe
just
the
IP
IP
notification
little
bit,
yeah.
C
A
Although
you've
stopped
your
video,
so
you
might
hope
that
a
single
recipe
message
sent
a
few
times
would
make
it.
But
but
that
also
sounds
more
like
a
hack
yeah.
A
Let's
just
send
it
three
times
and
what
happens
if
you
decide
to
restart
in
the
meantime
or
something
none
yeah
yeah,
but
otherwise
the
old
probing
thing
and
ramping
up
in
simulcast
is
probably
going
to
take
quite
a
lot
of
time
because
there's
a
lot
of
piping
a
lot
of
plumbing
sorry
to
get
right
there
first
ho,
we
have
to
decide
whether
we
want
to
do
that
through
FAQ
or
r-tx,
and.
A
C
Is
there
I
mean
it's
tricky
to
get
right?
I
was
wondering
if
there
might
be
some
poor
man's
method,
even
just
based
on
the
audio
stream
or
streams
or
something
if
it
was
like
hey,
we
haven't
seen
any
loss
on
audio
for
a
while.
What
if
we
just
tried
renaming
you
know
the
next
or
or
the
current
video
stream
of
so
doing?
C
Maybe
we
just
try
renaming
that
the
next
stream
and
see
if,
if
that
worked,
even
just
as
a
poor
man
saying
if
the
other,
if
the
complex
the
other
one
was
gonna,
take
a
while
to
get
right,
I
mean
it's
something
that
we
might.
We
might
tinker
around
with
that
and
see.
If
maybe
for
a
lot
of
scenarios,
it
works.
Okay,.
A
Yeah
but
then
imagine
that
you're
just
limited
to
one
megabit,
like
you,
have
a
hard
block
somewhere.
That
basically
means
that
every
five
seconds,
your
connection
will
be
going
to
for
five
seconds.
Yeah.
C
A
A
And
then
we
are
also
not
currently
the
I,
don't
know
if
you
guys
are
using
this.
Are
you
currently
using
our
sort
of
circuit
breakers
for
dropping
high-quality
layers?
Yeah
I,
don't
think
we've
disabled
those.
So
currently
these
don't.
These
are
not
super
aggressive,
so
they
take
a
while
I
take
at
least
five
seconds
to
kick
in.
A
Because
we
don't
want
to
be
super
aggressive,
given
that
we're
not
ramping
up
again,
but
with
that
in
mind,
I,
don't
know,
I'm
I
see
what
you're
saying
and
it's
probably
worth
trying
I
I
guess:
I,
just
afraid
that
there's
a
good
chance
that
you
might
end
up
discovering
oh
I,
actually
need
better
ramp
up
detection
and
probably
yeah.
C
A
C
C
A
A
A
Well,
if
you
guys,
if
you
guys,
discover
that
a
poor
man's
solution
is
actually
cutting
it
in
a
number
of
scenarios
than
then
would
really
want
to
know,
but
here's
here's
another
thing
to
keep
in
mind
for
a
very
long
time.
We
were
running
me
GT
at
360p,
and
people
were
happy
using
in.
So
if
you
just
have
the
current
circuit
breakers,
that
drove
the
high
quality
where
they
would
basically
put
you
in
that
situation
now,
granted
360p
in
simulcast
doesn't
ramp
up
all
the
way
up
to
what
360p
without
simulcast
us.
C
A
A
So
what
you're
worried
about
is
only
the
case
where
these
five
seconds
were
an
exception
and
not
an
indication
of
a
portaling
yeah,
and
so
this
is
what
you'll
be
optimizing
with
a
poor
man
solution
here.
I
mean
this
is
all
very
interesting
conversation,
and
if
you
try,
then
you
actually
get
some
data
and
you
qualify.
The
behavioral.
B
A
Thanks,
maybe
a
quick
announcement
and
I
think
the
guys
already
said
that
the
previous
time,
but
we're
going
to
have
a
WebRTC
meet
up
in
in
austin
on
wednesday.
Some
a
few
developers
from
logmein
are
also
going
to
be
on
board
and
they
might
make
a
presentation
as
well.
So
if
anyone
is
interested
in
joining
we'll
have
pizza
make
sure
you
you
come
to
the
Atlantean
offices,
is
there
anything
else?
A
C
A
B
We
are
adding
these
new
categories,
for
the
calls
like
two
more
like
missed
calls
and
dropped.
Calls
will
be
seen
that
soon
a
drop
calls
would
be
once
to
be
Chaz,
ice
disruption
and
missed
calls
or
once
which
you
shall
relinquish
some
of
that
I
and
nobody
except
chilling
and
unity.
Explosive
I
think
it's
not
in
the
case
of
gypsy,
you
not
be
able
to
see
any
meat
fault,
but
drop
calls
will
be
able
to
see.