This message was deleted.
# helpdesks
steep-balloon-41261
01/16/2023, 1:00 PMThis message was deleted.
m
magnificent-art-43333
01/16/2023, 4:04 PMcc @able-gigabyte-21598
a
able-gigabyte-21598
01/17/2023, 12:44 AMlooks like you’re running this against a local livekit-server, do you have
insecuref
freezing-ability-3706
01/17/2023, 1:07 AMThe config for my egress service shows above.
freezing-ability-3706
01/18/2023, 1:22 AM@able-gigabyte-21598, the insecure is set to true by default in my config.
a
able-gigabyte-21598
01/18/2023, 4:59 PMwhat environment are you running on? I cannot reproduce this
f
freezing-ability-3706
01/19/2023, 8:25 AMThe egress service is running in a redhat 8.3 environment.
freezing-ability-3706
01/31/2023, 12:12 PM@able-gigabyte-21598 ，what's your environment used to test?
a
able-gigabyte-21598
01/31/2023, 6:07 PMI test on M1 mac and a debian 11 test machine
f
freezing-ability-3706
02/17/2023, 11:07 AMI tested on x86 platform, it works. Looks it is a issue in ARM system.
a
able-gigabyte-21598
02/17/2023, 8:08 PMAh, we only build arm64 (for development on M1s) and amd64
f
freezing-ability-3706
02/18/2023, 12:33 AMBy checking the install-chrome script, for amd64, we installed the google-chrome, but for arm64 system, we only installed bunch of libs, what's the reason behind it?
a
able-gigabyte-21598
02/18/2023, 8:44 AMChrome for arm64 doesn’t include h264 support, but amd64 chrome does. So for amd64 we can just install it directly, but for arm64 we had to build chrome ourselves with h264 enabled. The custom build for arm64 is copied over here https://github.com/livekit/egress/blob/main/build/chrome/install-chrome#L6
able-gigabyte-21598
02/18/2023, 8:45 AMthe arm64 build itself is not committed to the repo (because it’s huge), but the build steps we’re using can be found here https://github.com/livekit/egress/blob/main/build/chrome/README.md, and you can find the build in the
livekit:chrome-installer/chrome-installer/arm643 Views