[jitsi-dev] Latest Jitsi nightly and Bria phone tests


#1

Hi,

I have been doing various tests using a Bria 3.0 phone and latest Jitsi
nightly and regarding video calls I get mixed results

I configured each phone to use one codec for video

-using H264 looks good both phones can render & see video properly
-using VP8 Jitsi cannot see Bria stream although it appears to correctly
receive the stream - so this looks to me more like a native libraries or
code issue given how jitsi receives remote video event notifications. It
receives the video event properly, but when it displays the swing Component
- nothing is seen
-using H.263-1998 Jitsi receives the stream from Bria and properly displays
it, but when trying to send video stream back to bria, jitsi just crashes
with the following JVM message:

INFO: Starting

···

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f8b55f92a91, pid=29169, tid=140235804333824
#
# JRE version: 6.0_24-b24
# Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64
compressed oops)
# Derivative: IcedTea6 1.11.6
# Distribution: Fedora release 16 (Verne), package
fedora-71.1.11.6.fc16-x86_64
# Problematic frame:
# C [libjnffmpeg.so+0x335a91] sws_scale+0x81
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

The same - problems appear to be with the latest native libraries:

libjnffmpeg.so at 0x00007f8b55c5d000
libjvm.so at 0x00007f8b6c73b000

Does anybody else seen these before? My opinion is that there is something
wrong with the natives libraries.

Thanks
Mircea


#2

Hey Mircea,

Hi,

I have been doing various tests using a Bria 3.0 phone and latest Jitsi
nightly and regarding video calls I get mixed results

I configured each phone to use one codec for video

-using H264 looks good both phones can render & see video properly

Good to know.

-using VP8 Jitsi cannot see Bria stream although it appears to correctly
receive the stream - so this looks to me more like a native libraries or
code issue given how jitsi receives remote video event notifications. It
receives the video event properly, but when it displays the swing Component
- nothing is seen

Not surprising: our current VP8 support uses a *very* basic and
incomplete packetizer. It needs more work before becoming compatible
with other implementations.

-using H.263-1998 Jitsi receives the stream from Bria and properly displays
it, but when trying to send video stream back to bria, jitsi just crashes
with the following JVM message:

OK. This might be due to some of the ffmpeg updates we did.

We'll need to look into this but I can't give you an ETA at this point.

Cheers,
Emil

···

On Fri, Nov 8, 2013 at 5:47 PM, Mircea Carasel <mirceac@ezuce.com> wrote:

INFO: Starting
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f8b55f92a91, pid=29169, tid=140235804333824
#
# JRE version: 6.0_24-b24
# Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64
compressed oops)
# Derivative: IcedTea6 1.11.6
# Distribution: Fedora release 16 (Verne), package
fedora-71.1.11.6.fc16-x86_64
# Problematic frame:
# C [libjnffmpeg.so+0x335a91] sws_scale+0x81
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

The same - problems appear to be with the latest native libraries:

libjnffmpeg.so at 0x00007f8b55c5d000
libjvm.so at 0x00007f8b6c73b000

Does anybody else seen these before? My opinion is that there is something
wrong with the natives libraries.

Thanks
Mircea

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31


#3

Thanks Emil

I would also like to ask, in case you specify more than one audio/video
codec, is there any way to define the order in which they are used?
In Bria, Polycom, or other phones you can specify the order (in UI a
multi-select widget is used, where you can add/remove codecs *and* specify
the order in which are used)

Thanks again
Mircea

···

> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f8b55f92a91, pid=29169, tid=140235804333824
> #
> # JRE version: 6.0_24-b24
> # Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64
> compressed oops)
> # Derivative: IcedTea6 1.11.6
> # Distribution: Fedora release 16 (Verne), package
> fedora-71.1.11.6.fc16-x86_64
> # Problematic frame:
> # C [libjnffmpeg.so+0x335a91] sws_scale+0x81
> #
> # If you would like to submit a bug report, please include
> # instructions how to reproduce the bug and visit:
> # http://icedtea.classpath.org/bugzilla
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
>
> The same - problems appear to be with the latest native libraries:
>
> libjnffmpeg.so at 0x00007f8b55c5d000
> libjvm.so at 0x00007f8b6c73b000
>
> Does anybody else seen these before? My opinion is that there is
something
> wrong with the natives libraries.
>
> Thanks
> Mircea
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hey Mircea,

Thanks Emil

I would also like to ask, in case you specify more than one audio/video
codec, is there any way to define the order in which they are used?

Yes.

In Bria, Polycom, or other phones you can specify the order (in UI a
multi-select widget is used, where you can add/remove codecs *and* specify
the order in which are used)

Both the "Audio" and "Video" tabs in our "Preferences" panel contain
an "Encoding" sub-tab. You'll notice a codec list there and the order
of the codecs in that list is the order of preference that Jitsi uses
to announce supported formats. You can use the "Up" and "Down" buttons
to rearrange them.

Additionally, every single account you create has an "Encodings" tab
where you can override the default order and choose a custom one for
that specific account.

Hope this helps,
Emil

···

On Fri, Nov 8, 2013 at 11:28 PM, Mircea Carasel <mirceac@ezuce.com> wrote:

Thanks again
Mircea

> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f8b55f92a91, pid=29169,
> tid=140235804333824
> #
> # JRE version: 6.0_24-b24
> # Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64
> compressed oops)
> # Derivative: IcedTea6 1.11.6
> # Distribution: Fedora release 16 (Verne), package
> fedora-71.1.11.6.fc16-x86_64
> # Problematic frame:
> # C [libjnffmpeg.so+0x335a91] sws_scale+0x81
> #
> # If you would like to submit a bug report, please include
> # instructions how to reproduce the bug and visit:
> # http://icedtea.classpath.org/bugzilla
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
>
> The same - problems appear to be with the latest native libraries:
>
> libjnffmpeg.so at 0x00007f8b55c5d000
> libjvm.so at 0x00007f8b6c73b000
>
> Does anybody else seen these before? My opinion is that there is
> something
> wrong with the natives libraries.
>
> Thanks
> Mircea
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31


#5

Hope this helps,
Yes, it helps a lot - Thanks!
Mircea

···

Emil


#6

One more question...

I had a look into sip-communicator.properties and I figured out that the
order in which the codecs are used is specified by:

net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H263-1998/90000=2
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H264/90000=3
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.VP8/90000=1

Value 3 means that this is the first codec used, 1 the last. The higher the
value is, the more important the codec is.

Also, per account we have for example:
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.G722/8000=705
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.GSM/8000=450
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.H263-1998/90000=2
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.H264/90000=1100
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.PCMA/8000=600
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.PCMU/8000=650
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/12000=0
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/16000=713
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/24000=714
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/8000=1
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.VP8/90000=1
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.iLBC/8000=500
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.opus/48000=750
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.speex/16000=700
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.speex/32000=701
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.speex/8000=0
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.telephone-event/8000=1

value 0 means that the codec is not used, Value >0 means that the codec is
used.

My question is, does it matter what value each codec has per account (700,
1100, 2, 450, etc)? or the only rule is greater than 0, means that the
codec is used by the account, equal 0, the codec is not used

Thanks again,
Mircea

···

On Mon, Nov 11, 2013 at 12:06 PM, Mircea Carasel <mirceac@ezuce.com> wrote:

Hope this helps,
Yes, it helps a lot - Thanks!
Mircea

Emil


#7

One more question...

I had a look into sip-communicator.properties and I figured out that the
order in which the codecs are used is specified by:

net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H263-1998/90000=2
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H264/90000=3
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.VP8/90000=1

Value 3 means that this is the first codec used, 1 the last. The higher the
value is, the more important the codec is.

Also, per account we have for example:
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.G722/8000=705
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.GSM/8000=450
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.H263-1998/90000=2
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.H264/90000=1100
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.PCMA/8000=600
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.PCMU/8000=650
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/12000=0
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/16000=713
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/24000=714
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.SILK/8000=1
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.VP8/90000=1
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.iLBC/8000=500
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.opus/48000=750
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.speex/16000=700
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.speex/32000=701
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.speex/8000=0
net.java.sip.communicator.impl.protocol.sip.acc1384166304400.Encodings.telephone-event/8000=1

value 0 means that the codec is not used, Value >0 means that the codec is
used.

My question is, does it matter what value each codec has per account (700,
1100, 2, 450, etc)? or the only rule is greater than 0, means that the codec
is used by the account, equal 0, the codec is not used

Not sure I get the question. One can completely override the codec
priorities for a specific account (not only the set of codecs to be
used) so the values do very much matter.

Cheers,
Emil

···

On Mon, Nov 11, 2013 at 11:57 AM, Mircea Carasel <mirceac@ezuce.com> wrote:

Thanks again,
Mircea

On Mon, Nov 11, 2013 at 12:06 PM, Mircea Carasel <mirceac@ezuce.com> wrote:

Hope this helps,
Yes, it helps a lot - Thanks!
Mircea

Emil

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31


#8

Not sure I get the question. One can completely override the codec
priorities for a specific account (not only the set of codecs to be
used) so the values do very much matter.

Ah, right - there are up and down buttons for the Accout's Encodings tab -
sorry for the noise
It is clear now - thanks again

Mircea

···

Cheers,
Emil

> Thanks again,
> Mircea
>
>
>
>
> On Mon, Nov 11, 2013 at 12:06 PM, Mircea Carasel <mirceac@ezuce.com> > wrote:
>>
>> Hope this helps,
>> Yes, it helps a lot - Thanks!
>> Mircea
>>>
>>> Emil
>>>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev