@camstack/types 1.2.186 → 1.2.187

package/dist/index.js

@@ -442,7 +442,32 @@ var WEBRTC_EGRESS_PROFILE = {
 */
 var ALEXA_EGRESS_PROFILE = {
 	...BASE_LIVE_EGRESS_PROFILE,
-	audio: { codec: "opus" }
+	audio: { codec: "opus" },
+	/**
+	* ONE slice per access unit.
+	*
+	* `-tune zerolatency` turns on x264's sliced threads, and every access unit
+	* came out of this encode as FIVE slices — measured on the hub 2026-09-13 on
+	* the exact argv this path spawns, and reduced to one by this single flag.
+	*
+	* Five slices share one RTP timestamp and carry one marker bit, so a
+	* libwebrtc depacketiser sees five frame-starts and one frame-end per frame.
+	* The Echo renders the first pictures and then freezes for good, while the
+	* audio — a separate plane — plays on. It is the only structural property
+	* that survived the elimination: the same freeze reproduced at 2304×1296
+	* HEVC with 217 KB keyframes AND at 640×360 H.264 with 67 KB keyframes and a
+	* fifth of the bitrate, so source, resolution, bitrate, keyframe burst,
+	* hardware decode, parameter sets, drift and bitstream conformance are all
+	* out — each ruled out by a measurement, not by elimination.
+	*
+	* The tune STAYS: it also drops the lookahead and the B-frames, which a live
+	* path wants. Only the slicing is unwanted, and this is the flag that says so.
+	*
+	* Scoped to Alexa deliberately. HomeKit and the browser transcode inherit
+	* {@link BASE_LIVE_EGRESS_PROFILE}; whether they want the same shape is a
+	* question for their own evidence, and the browser has not been measured.
+	*/
+	outputArgs: ["-x264-params", "sliced-threads=0"]
 };
 /** VBV window for a consumer whose budget is enforced per second (HomeKit). */
 var RATE_CONTROL_TIGHT = {

package/dist/index.mjs

@@ -441,7 +441,32 @@ var WEBRTC_EGRESS_PROFILE = {
 */
 var ALEXA_EGRESS_PROFILE = {
 	...BASE_LIVE_EGRESS_PROFILE,
-	audio: { codec: "opus" }
+	audio: { codec: "opus" },
+	/**
+	* ONE slice per access unit.
+	*
+	* `-tune zerolatency` turns on x264's sliced threads, and every access unit
+	* came out of this encode as FIVE slices — measured on the hub 2026-09-13 on
+	* the exact argv this path spawns, and reduced to one by this single flag.
+	*
+	* Five slices share one RTP timestamp and carry one marker bit, so a
+	* libwebrtc depacketiser sees five frame-starts and one frame-end per frame.
+	* The Echo renders the first pictures and then freezes for good, while the
+	* audio — a separate plane — plays on. It is the only structural property
+	* that survived the elimination: the same freeze reproduced at 2304×1296
+	* HEVC with 217 KB keyframes AND at 640×360 H.264 with 67 KB keyframes and a
+	* fifth of the bitrate, so source, resolution, bitrate, keyframe burst,
+	* hardware decode, parameter sets, drift and bitstream conformance are all
+	* out — each ruled out by a measurement, not by elimination.
+	*
+	* The tune STAYS: it also drops the lookahead and the B-frames, which a live
+	* path wants. Only the slicing is unwanted, and this is the flag that says so.
+	*
+	* Scoped to Alexa deliberately. HomeKit and the browser transcode inherit
+	* {@link BASE_LIVE_EGRESS_PROFILE}; whether they want the same shape is a
+	* question for their own evidence, and the browser has not been measured.
+	*/
+	outputArgs: ["-x264-params", "sliced-threads=0"]
 };
 /** VBV window for a consumer whose budget is enforced per second (HomeKit). */
 var RATE_CONTROL_TIGHT = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/types",
-  "version": "1.2.186",
+  "version": "1.2.187",
   "description": "Shared types, interfaces, and model catalogs for the CamStack detection ecosystem",
   "keywords": [
     "camstack",