Comparing 0b8181e5ce...1333e39164 - meet - L'Électron Rare

electron-rare/meet

Fork 0

...

Author	SHA1	Message	Date
lebaudantoine	1333e39164	🔧(frontend) enable dynacast optimizations According to the documentation: Dynacast dynamically pauses video layers that are not being consumed by any subscribers, significantly reducing publishing CPU and bandwidth usage. Dynacast will be enabled if SVC codecs (VP9/AV1) are used. Multi-codec simulcast requires dynacast My goal is to reduce CPU and bandwidth usage for clients. Dynacast is enabled both in OpenTalk and LiveKit demo app!	2024-12-09 17:34:12 +01:00
lebaudantoine	5931c5605a	🔧(frontend) enable adaptive stream optimizations Adaptive stream is a key optimization in large room. Enabled adaptive stream to automatically manage the quality of subscribed video tracks, optimizing for bandwidth and CPU usage. When video elements are visible, it adjusts the resolution based on the size of the largest visible element. If no video elements are visible, it temporarily pauses the track until they are visible again. Additionally, introduced support for custom pixel density, which defaults to `2` for high-density screens (devicePixelRatio ≥ 3) or `1` for standard screens. Setting it to `screen` allows the pixel density to match the actual screen's devicePixelRatio, optimizing video clarity on ultra-high-definition displays. This ensures a balance between streaming quality and resource consumption. This might also significantly increase the bandwidth consumed by people streaming on high definition screens. It needs to be battle tested. OpenTalk uses a adaptiveStream equals true, while LiveKit demo app uses 'screen' value. I followed OpenTalk choice, I was scared 'screen' value creates performance issues for user with high resolution screen in poor network conditions.	2024-12-09 17:31:27 +01:00
lebaudantoine	3a205373dd	🔧(frontend) default to vp9 for video codec As a mandatory codec in WebRTC specifications, VP8 serves as the baseline for compatibility, making it the default choice in LiveKit client configuration. There is room for optimization. Newer codecs like VP9 offer significant efficiency gains compared to VP8, with a 23-33% improvement in compression efficiency. This translates to better video quality at the same bitrate or reduced bandwidth usage for the same quality. VP9 is supported in Safari starting from version 15.0+, and Firefox offers partial support. However, Firefox lacks support for VP9's Scalable Video Coding (SVC). With SVC, participants can send a single VP9 stream with multiple spatial or temporal layers. This allows receivers to dynamically adjust video quality by using lower layers when resolution or bandwidth needs to be reduced, improving adaptability in heterogeneous network conditions. Simulcast, by contrast, sends multiple separate streams at different resolutions. While widely supported in VP8 and VP9, it consumes more bandwidth compared to SVC. The configuration added here is based on the LiveKit demo app, which defaults to VP9 when supported. OpenTalk’s configuration also recommends VP9. If a browser does not support VP9, LiveKit falls back to VP8 or other codecs as needed. Notably, LiveKit disables VP9 encoding for Firefox due to longstanding issues, but it can still decode VP9 streams and encode VP8 for outgoing streams. This ensures compatibility with other participants, even in mixed environments where some browsers use VP9 and others fallback to VP8. In theory, participants do not all need to switch to a single codec, as both LiveKit and browsers intelligently handle codec negotiation on a per-participant basis. This dynamic adaptation ensures seamless communication without manual intervention. A similar challenge with codec compatibility was raised in Jitsi two years ago, check issue #10657. Before any release, this needs to be battle tested with Firefox 115 browsers.	2024-12-09 17:20:07 +01:00

Author

SHA1

Message

Date

lebaudantoine

1333e39164

🔧(frontend) enable dynacast optimizations

According to the documentation:

Dynacast dynamically pauses video layers that are
not being consumed by any subscribers, significantly
reducing publishing CPU and bandwidth usage.

Dynacast will be enabled if SVC codecs (VP9/AV1) are used.
Multi-codec simulcast requires dynacast

My goal is to reduce CPU and bandwidth usage for clients.

Dynacast is enabled both in OpenTalk and LiveKit demo app!

2024-12-09 17:34:12 +01:00

lebaudantoine

5931c5605a

🔧(frontend) enable adaptive stream optimizations

Adaptive stream is a key optimization in large room.

Enabled adaptive stream to automatically manage
the quality of subscribed video tracks, optimizing
for bandwidth and CPU usage.

When video elements are visible, it adjusts
the resolution based on the size of the largest visible
element. If no video elements are visible, it
temporarily pauses the track until they are visible again.

Additionally, introduced support for custom pixel density,
which defaults to `2` for high-density screens
(devicePixelRatio ≥ 3) or `1` for standard screens.
Setting it to `screen` allows the pixel density to match
the actual screen's devicePixelRatio, optimizing video
clarity on ultra-high-definition displays.

This ensures a balance between streaming quality
and resource consumption.

This might also significantly increase the bandwidth
consumed by people streaming on high definition screens.
It needs to be battle tested.

OpenTalk uses a adaptiveStream equals true, while LiveKit
demo app uses 'screen' value. I followed OpenTalk choice,
I was scared 'screen' value creates performance issues
for user with high resolution screen in poor network conditions.

2024-12-09 17:31:27 +01:00

lebaudantoine

3a205373dd

🔧(frontend) default to vp9 for video codec

As a mandatory codec in WebRTC specifications, VP8 serves as
the baseline for compatibility, making it the default choice
in LiveKit client configuration.

There is room for optimization.

Newer codecs like VP9 offer significant efficiency gains
compared to VP8, with a 23-33% improvement in compression
efficiency. This translates to better video quality at
the same bitrate or reduced bandwidth usage for the same quality.

VP9 is supported in Safari starting from version 15.0+,
and Firefox offers partial support. However, Firefox lacks
support for VP9's Scalable Video Coding (SVC).

With SVC, participants can send a single VP9 stream
with multiple spatial or temporal layers. This allows receivers
to dynamically adjust video quality by using lower layers when
resolution or bandwidth needs to be reduced, improving
adaptability in heterogeneous network conditions.

Simulcast, by contrast, sends multiple separate streams
at different resolutions. While widely supported in VP8 and VP9,
it consumes more bandwidth compared to SVC.

The configuration added here is based on the LiveKit demo app,
which defaults to VP9 when supported. OpenTalk’s configuration
also recommends VP9.

If a browser does not support VP9, LiveKit falls back to VP8 or
other codecs as needed. Notably, LiveKit disables VP9 encoding for
Firefox due to longstanding issues, but it can still decode VP9
streams and encode VP8 for outgoing streams. This ensures
compatibility with other participants, even in mixed environments
where some browsers use VP9 and others fallback to VP8.

In theory, participants do not all need to switch to a single codec,
as both LiveKit and browsers intelligently handle codec negotiation
on a per-participant basis. This dynamic adaptation ensures seamless
communication without manual intervention.

A similar challenge with codec compatibility was raised
in Jitsi two years ago, check issue #10657.

Before any release, this needs to be battle tested
with Firefox 115 browsers.

2024-12-09 17:20:07 +01:00

1 changed files with 5 additions and 0 deletions

									
										src/frontend/src/features/rooms/components/Conference.tsx
									
		+5
		
												View File
												
				@@ -65,6 +65,11 @@ export const Conference = ({

				  const roomOptions = useMemo((): RoomOptions => {

				    return {

				      adaptiveStream: true,

				      dynacast: true,

				      publishDefaults: {

				        videoCodec: 'vp9',

				      },

				      videoCaptureDefaults: {

				        deviceId: userConfig.videoDeviceId ?? undefined,

				      },

Compare commits

3 Commits

access/menu-focus-management ... optimization

Compare commits

3 Commits access/menu-focus-management ... optimization

3 Commits

access/menu-focus-management ... optimization