[jitsi-users] The video quality isn't good with Chrome M62 and H.264


#1

Hi, Saul and George

Sorry for creating another thread but I don't know how to reply to
certain thread when got the e-mail in digest mode.

Personally I've already answered to Saul in DM but for the purpose of
log I'm going to reply the information here.

If you changed nothing other than the Chrome version it might be a problem with Chrome itself. This issue might be related: https://bugs.chromium.org/p/webrtc/issues/detail?id=8022<https://bugs.chromium.org/p/webrtc/issues/detail?id=8022>

I suggest you try https://appr.tc <https://appr.tc/> (make sure you enable H264 with the URL params) and if you see changes between 61 and 62 report a bug on the Chrome / WebRTC bug tracker.

H.264 with appr.tc works fine with Chrome M62 in P2P mode. So this
maybe the issue in the combination of JVB and Chrome M62. Fortunately
as far as I tested, Chrome M64 Canary and H.264 works fine with JVB.

There may be a change in Chrome that the SFU needs to take into account but Saul’s answer has a couple of hidden questions :slight_smile:
Did you change anything else other than Chrome?

No, nothing.

Do you believe this is a “regression” in the SFU?

No, I'm not absolutely sure but the something is wrong with Chrome M62
as M64 works fine with same version of JVB as I wrote above.

Were you happy with the quality before you upgraded to version X? Or has it always been terrible for you?

Actually, H.264 quality seems worse than VP.8 as long as I tested.

Cheers,
Yoshimasa IWASE


#2

Hi, Saul and George

Sorry for creating another thread but I don't know how to reply to
certain thread when got the e-mail in digest mode.

Personally I've already answered to Saul in DM but for the purpose of
log I'm going to reply the information here.

If you changed nothing other than the Chrome version it might be a problem with Chrome itself. This issue might be related: https://bugs.chromium.org/p/webrtc/issues/detail?id=8022<https://bugs.chromium.org/p/webrtc/issues/detail?id=8022>

I suggest you try https://appr.tc <https://appr.tc/> (make sure you enable H264 with the URL params) and if you see changes between 61 and 62 report a bug on the Chrome / WebRTC bug tracker.

H.264 with appr.tc works fine with Chrome M62 in P2P mode. So this
maybe the issue in the combination of JVB and Chrome M62. Fortunately
as far as I tested, Chrome M64 Canary and H.264 works fine with JVB.

There may be a change in Chrome that the SFU needs to take into account but Saul’s answer has a couple of hidden questions :slight_smile:
Did you change anything else other than Chrome?

No, nothing.

Do you believe this is a “regression” in the SFU?

No, I'm not absolutely sure but the something is wrong with Chrome M62
as M64 works fine with same version of JVB as I wrote above.

Were you happy with the quality before you upgraded to version X? Or has it always been terrible for you?

Actually, H.264 quality seems worse than VP.8 as long as I tested.

Hi Yoshimasa,

Thanks for your insights, these are really helpful.

Cheers,

···

On Nov 8, 2017, at 03:49, Yoshimasa IWASE <iwase.yoshimasa@gmail.com> wrote:

Cheers,
Yoshimasa IWASE

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

--
Saúl