This message was deleted.
# announcements
s
This message was deleted.
n
Hmm appears it was a codec issue. h264 not supported my chrome clients? 😕
d
Hey Mark, I think you meant LiveKit instead of ion? We'll look into this. I think the Chromium version that we are bundling doesn't support H.264.
Filed issue https://github.com/livekit/egress/issues/165. we'll look into this one today.
❤️ 1
n
Haha oops ironic typo :)
@dry-elephant-14928, does that mean Livekit does some form of translation? SFUs as far as I've known, everyone had to use the same codec
a
@nice-beard-68229 Some clients send h264 and some send vp8. Livekit doesn't transcode, and I don't believe there's any requirement that they're all the same (unless you use enabled_codecs on the room)
❤️ 1
d
@nice-beard-68229 just to confirm, this only happens when Egress is deployed on arm64 instances. On amd64, we are using Chrome, which has no problem decoding H.264.
n
@dry-elephant-14928 im on an Intel(R) Xeon(R) CPU E5-2678 v3 @ 2.50GHz for the server, and intel 9900k on client
@able-gigabyte-21598 So that was the issue! We were explicitly enabling vp8 on the startup config! after disabling that it all worked as expected. Thank you!
I ran some 50 person load tests on calls today. It was interesting toi see the loads not handled well on older laptops/hardware
d
are you talking about Egress specifically? or are you talking about the core server? a lot of it depends on the client.. and how much data each person is subscribing to