lukasIO

- Are you using nextJS? If so, which version? - Does it work with the default import of `import processors from '@livekit/track-processors'; const VirtualBackground = processors.VirtualBackground`?

thanks for checking. We define the two entrypoints like so: https://github.com/livekit/track-processors-js/blob/main/package.json#L5C2-L6C30 So it sounds to me like your webpack version is picking up the wrong one?

We haven't had any other reports about this (apart from @Mihai-github, who seems to have fixed his issue) Are you able to update webpack to see if the issue resolves...

looks like the issue for you might be the `||=` operator used within mediapipe. maybe [preprocessing it with babel](https://babeljs.io/docs/babel-plugin-transform-logical-assignment-operators) could help, but the mediapipe repo is probably the better place...

@keepingitneil just a heads up I moved a bunch of stuff around in main and merged the changes back in here, hope I didn't break anything!

Comment with some of my findings: https://github.com/livekit/livekit/issues/2716#issuecomment-2112839311

While not ideal, it does work like intended today. The reason is that the quality updates are scoped to participants that are subscribed to another participant’s track(s). So if your...

hey @s-hamdananwar , thank you for your contribution, this is an impressive effort! We'll have to decide internally first whether we want to go down the route of distributing chat...

Thanks for the report! I guess you are not specifying any particular device, but rather the problem is around the default device when you call `setCameraEnabled`?

When requesting a device via `getUserMedia` (which is what our APIs do) browsers should - theoretically - return a device that is available, as long as no specific device is...