{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":727265561,"defaultBranch":"master","name":"sfu","ownerLogin":"odoo","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2023-12-04T14:18:13.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/6368483?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715153242.0","currentOid":""},"activityList":{"items":[{"before":"85a063f93079c47a9d921354c43682e51a6ac040","after":null,"ref":"refs/heads/rel-1.2.0","pushedAt":"2024-05-08T06:53:19.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"}},{"before":"3b3a85b197db9b63c8f9b54f222e4299a4537929","after":"0f4f21614889e8cf2bac9a7ffbb6829e0f48ffb2","ref":"refs/heads/master","pushedAt":"2024-05-08T06:53:15.000Z","pushType":"pr_merge","commitsCount":2,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"Merge pull request #8 from odoo/rel-1.2.0\n\n[REL] v1.2.0","shortMessageHtmlLink":"Merge pull request <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2284825173\" data-permission-text=\"Title is private\" data-url=\"https://github.com/odoo/sfu/issues/8\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/odoo/sfu/pull/8/hovercard\" href=\"https://github.com/odoo/sfu/pull/8\">#8</a> from odoo/rel-1.2.0"}},{"before":"9491d17c885e51b6a621a9a30bd04ae0061d8055","after":"85a063f93079c47a9d921354c43682e51a6ac040","ref":"refs/heads/rel-1.2.0","pushedAt":"2024-05-08T06:52:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[REL] v1.2.0\n\n- [IMP] Add per-channel encryption feature","shortMessageHtmlLink":"[REL] v1.2.0"}},{"before":null,"after":"9491d17c885e51b6a621a9a30bd04ae0061d8055","ref":"refs/heads/rel-1.2.0","pushedAt":"2024-05-08T06:51:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[REL] v1.2.0\n\n- [IMP] Add per-channel encryption feature","shortMessageHtmlLink":"[REL] v1.2.0"}},{"before":"9607bdcac5967d9de9066b1571fa0450449d7f86","after":null,"ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-05-07T13:35:25.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"alexkuhn","name":"Alexandre Kühn","path":"/alexkuhn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6569390?s=80&v=4"}},{"before":"beafcc20da055047476a2abc7fddd635e44b3408","after":"3b3a85b197db9b63c8f9b54f222e4299a4537929","ref":"refs/heads/master","pushedAt":"2024-05-07T13:35:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"alexkuhn","name":"Alexandre Kühn","path":"/alexkuhn","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6569390?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"d220d3c50cabd4296d4bc43bb909ef031643c759","after":"9607bdcac5967d9de9066b1571fa0450449d7f86","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-05-07T12:22:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"0fd229e980915e6d83a02a59f21c4c44163c5df8","after":"d220d3c50cabd4296d4bc43bb909ef031643c759","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-26T05:44:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"a9a451a621e2362753ae814702b403b56f85b782","after":"0fd229e980915e6d83a02a59f21c4c44163c5df8","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-25T09:20:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"a03e257e697124856ab67fc285546f1b878f072c","after":"a9a451a621e2362753ae814702b403b56f85b782","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-25T09:14:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"d1bd7464e07102a9a298e7d6c56432b2446cd0b4","after":"a03e257e697124856ab67fc285546f1b878f072c","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-25T08:53:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"cc7c6405c18ad0f22b9c118a0c40b7b8a53c3fca","after":"d1bd7464e07102a9a298e7d6c56432b2446cd0b4","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-25T06:35:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"0a409a23ddd4d917bfb67790a9160be9a3142c02","after":"cc7c6405c18ad0f22b9c118a0c40b7b8a53c3fca","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-24T07:09:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"8a4d3cae7822f963d5d4c5689dbe979b19ae6915","after":"0a409a23ddd4d917bfb67790a9160be9a3142c02","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-23T09:13:34.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"1fa93635ea91139dec203f4157771ab783c85124","after":"8a4d3cae7822f963d5d4c5689dbe979b19ae6915","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-12T10:23:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"a2c7d95484df19eee309fb21f6558d0d33c05c36","after":"1fa93635ea91139dec203f4157771ab783c85124","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-12T10:19:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"4e0320f2155735b18630d6040208065abeae06fb","after":"a2c7d95484df19eee309fb21f6558d0d33c05c36","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-12T08:27:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"cf2ab454d4daf6efae3c82f556d1f9c1648d238c","after":"4e0320f2155735b18630d6040208065abeae06fb","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-12T08:20:07.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis features works by allowing an additional `key` claim in the JWT\nused to request a room. When this claim is set, the JWTs used to\nauthenticate users are expected to be signed by this new key and not\nthe \"global\" SFU key (`AUTH_KEY` global variable).\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"64adef063dcf11ded51e66a7ab1840423260f3fa","after":"cf2ab454d4daf6efae3c82f556d1f9c1648d238c","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-12T07:20:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":null,"after":"64adef063dcf11ded51e66a7ab1840423260f3fa","ref":"refs/heads/master-sfu-sh-compat-tso","pushedAt":"2024-04-12T07:13:51.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] Add per-channel encryption feature\n\nThis commit adds per-channel encryption to prevent users from signing\nJWTs for channels that they did not create.\n\nThis change is useful for cases like Odoo.SH where multiple parties\ncan use the same SFU with the same credentials.\n\ntask-3861455","shortMessageHtmlLink":"[IMP] Add per-channel encryption feature"}},{"before":"6502d2cc68b5ee4dedfbc334f8c34ba8e901daf9","after":null,"ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2024-01-09T16:26:49.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"seb-odoo","name":"Sébastien Theys","path":"/seb-odoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38213504?s=80&v=4"}},{"before":"5e71c03cd1ef1b8ce904905ccd27ead558158de9","after":"beafcc20da055047476a2abc7fddd635e44b3408","ref":"refs/heads/master","pushedAt":"2024-01-09T16:26:37.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"seb-odoo","name":"Sébastien Theys","path":"/seb-odoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/38213504?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as the bundle and the server\nneed to be updated to benefit from the feature (although both the\nclient and the server are backwards compatible).","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"418c3f6d4af60319267d1f75b4c6b4976bf7927f","after":"6502d2cc68b5ee4dedfbc334f8c34ba8e901daf9","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2024-01-09T13:33:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as the bundle and the server\nneed to be updated to benefit from the feature (although both the\nclient and the server are backwards compatible).","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"d47bb25960dc7eb5907205da9c89aa8e0d6e79c3","after":"418c3f6d4af60319267d1f75b4c6b4976bf7927f","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2024-01-09T12:42:01.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as the bundle and the server\nneed to be updated to benefit from the feature (although both the\nclient and the server are backwards compatible).","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"ecf16e539cf0b8633d7724980293f4ba37e586b7","after":"d47bb25960dc7eb5907205da9c89aa8e0d6e79c3","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2023-12-18T08:00:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as the bundle and the server\nneed to be updated to benefit from the feature (although both the\nclient and the server are backwards compatible).","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"9a6c24b2bf9060642fdf71ec44bd65efb9d530d8","after":"ecf16e539cf0b8633d7724980293f4ba37e586b7","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2023-12-15T09:19:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as the bundle and the server\nneed to be updated to benefit from the feature (although both the\nclient and the server are backwards compatible).","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"7c1f32c85d38daaa982bdbca78fd7553c49ddde2","after":"9a6c24b2bf9060642fdf71ec44bd65efb9d530d8","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2023-12-15T09:14:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as the bundle and the server\nneed to be updated to benefit from the feature (although both the\nclient and the server are backwards compatible).","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"7fecffe938d9149e9e0ebf073a37a8e38ce23bee","after":"7c1f32c85d38daaa982bdbca78fd7553c49ddde2","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2023-12-15T07:46:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.\n\nThis commits also bumps the minor version as bundles for earlier\nversions are not compatible.","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"5c843124d737fd610fa90799bf5a721d59ed76ff","after":"7fecffe938d9149e9e0ebf073a37a8e38ce23bee","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2023-12-14T14:05:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.","shortMessageHtmlLink":"[IMP] add simulcast"}},{"before":"63a41a67dccf783624c7e59099e26f5aa107f1dd","after":"5c843124d737fd610fa90799bf5a721d59ed76ff","ref":"refs/heads/master-discuss-call-simulcast-tso","pushedAt":"2023-12-14T14:02:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ThanhDodeurOdoo","name":"Thanh Dodeur","path":"/ThanhDodeurOdoo","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/39259739?s=80&v=4"},"commit":{"message":"[IMP] add simulcast\n\nThis commit adds the support for simulcast:\n\nSimulcast is a way to let producers sent multiple version of the streams\nas different layers of quality. This allows the server to select\nthe optimal layer based on the available bandwidth for each client.\n\nTwo env variables are used to control this feature:\n\n`VIDEO_MAX_BITRATE`: Specifies the bitrate for the highest encoding\nlayer per stream. It sets the `maxBitrate` property of the\nhighest encoding of the `RTCRtpEncodingParameters` and is used\nto compute the bitrate attributed to the other layers.\n\n`MAX_BITRATE_OUT`: The maximum outgoing bitrate (=from the server) per\nsession (meaning that this cap is shared between all the incoming\nstreams for any given user). The appropriate simulcast layers used by\neach consumer will be selected to honor this limit. If the bitrate is\nstill too high, packets will be dropped. Without this limit, the\nconnections will use as much bandwidth as possible, which means that\nthe simulcast layer will be chosen based on the client (or server) max\navailable bandwidth.","shortMessageHtmlLink":"[IMP] add simulcast"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAERE5T1QA","startCursor":null,"endCursor":null}},"title":"Activity · odoo/sfu"}