haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(config) Delete deprecated config. 

Client (receiver constraints)  and bridge use the new b/w allocation strategy by default.
This commit is contained in:
Jaya Allamsetty 2023-01-06 16:14:38 -05:00
parent 7e30053d51
commit 0ad7b3db55
2 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
config.js
View File

@ -418,12 +418,6 @@ var config = {
// 90: 2, // 90: 2,
// }, // },
// Provides a way to translate the legacy bridge signaling messages, 'LastNChangedEvent',
// 'SelectedEndpointsChangedEvent' and 'ReceiverVideoConstraint' into the new 'ReceiverVideoConstraints' message
// that invokes the new bandwidth allocation algorithm in the bridge which is described here
// - https://github.com/jitsi/jitsi-videobridge/blob/master/doc/allocation.md.
// useNewBandwidthAllocationStrategy: false,
// Specify the settings for video quality optimizations on the client. // Specify the settings for video quality optimizations on the client.
// videoQuality: { // videoQuality: {
// // Provides a way to prevent a video codec from being negotiated on the JVB connection. The codec specified // // Provides a way to prevent a video codec from being negotiated on the JVB connection. The codec specified

1
react/features/base/config/configType.ts
View File

@ -511,7 +511,6 @@ export interface IConfig {
useAppLanguage?: boolean; useAppLanguage?: boolean;
}; };
useHostPageLocalStorage?: boolean; useHostPageLocalStorage?: boolean;
useNewBandwidthAllocationStrategy?: boolean;
useTurnUdp?: boolean; useTurnUdp?: boolean;
videoQuality?: { videoQuality?: {
disabledCodec?: string; disabledCodec?: string;