Add vp9 support for E2EE

[lukasIO]

Unfortunately av1 fails with TypeError: Destination stream closed when trying to decode frames. This needs further investigation. Until then, VP9 addition is nice, too!

Caveats: this is currently only secure if backupCodec: undefined is specified. Backup codecs are currently sent unencrypted, which is definitely unexpected.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 708003f9695db37b24581e91f895121888a265d2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
livekit-client	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions[bot]]

size-limit report 📦

Path	Size
dist/livekit-client.esm.mjs	80.24 KB (0%)
dist/livekit-client.umd.js	86.06 KB (0%)

[lukasIO]

closing for now due to the backupCodec complications

[Stogas]

@lukasIO

Could you elaborate a little bit?

I'd still consider this open, as VP9 support is still wanted and missing.

[lukasIO]

hi @Stogas,

encryption support for backup codecs is missing, which would be needed to ensure that also clients that don't support vp9 would be able to receive the media stream.

I can reopen the issue, but there's currently no ETA for encryption support of backup codecs

[davidzhao]

We should disable backupCodec when e2ee is used. since vp9 is supported everywhere, I think the impact of that should be fairly minimal

[lukasIO]

We should disable backupCodec when e2ee is used.

That's what we do already today. I'll update this PR in order to merge it in