@camstack/types 1.2.213 → 1.2.215
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/capabilities/ptz-autotrack.cap.d.ts +19 -0
- package/dist/index.js +19 -0
- package/dist/index.mjs +19 -0
- package/dist/node.js +1 -1
- package/dist/node.mjs +1 -1
- package/package.json +1 -1
|
@@ -66,6 +66,25 @@ export declare const ptzAutotrackCapability: {
|
|
|
66
66
|
readonly scope: "device";
|
|
67
67
|
readonly deviceNative: true;
|
|
68
68
|
readonly mode: "singleton";
|
|
69
|
+
/**
|
|
70
|
+
* Two kinds of provider behind one name, the same shape `snapshot` and
|
|
71
|
+
* `doorbell` use:
|
|
72
|
+
*
|
|
73
|
+
* - **Native**: the camera's own firmware autotrack, registered per device by
|
|
74
|
+
* the driver when the probe says it exists (Reolink: yes; Hikvision:
|
|
75
|
+
* model-dependent).
|
|
76
|
+
* - **Wrapper**: the emulated implementation (`@camstack/addon-autotrack`),
|
|
77
|
+
* which follows a subject with `ptz.move` pulses driven by the detection
|
|
78
|
+
* pipeline. `defaultActive: false` — the operator binds it per camera in
|
|
79
|
+
* the bindings UI, exactly as `virtual-doorbell` is bound.
|
|
80
|
+
*
|
|
81
|
+
* The binding chooses WHICH implementation answers; `setEnabled` stays the
|
|
82
|
+
* one switch for the function either way. A camera never has both driving its
|
|
83
|
+
* head, which is the whole reason this is not a second cap with a second
|
|
84
|
+
* toggle (D62, D520).
|
|
85
|
+
*/
|
|
86
|
+
readonly kind: "wrapper";
|
|
87
|
+
readonly defaultActive: false;
|
|
69
88
|
readonly deviceTypes: readonly [DeviceType.Camera];
|
|
70
89
|
readonly deviceConfig: {
|
|
71
90
|
readonly ui: {
|
package/dist/index.js
CHANGED
|
@@ -35444,6 +35444,25 @@ var ptzAutotrackCapability = {
|
|
|
35444
35444
|
scope: "device",
|
|
35445
35445
|
deviceNative: true,
|
|
35446
35446
|
mode: "singleton",
|
|
35447
|
+
/**
|
|
35448
|
+
* Two kinds of provider behind one name, the same shape `snapshot` and
|
|
35449
|
+
* `doorbell` use:
|
|
35450
|
+
*
|
|
35451
|
+
* - **Native**: the camera's own firmware autotrack, registered per device by
|
|
35452
|
+
* the driver when the probe says it exists (Reolink: yes; Hikvision:
|
|
35453
|
+
* model-dependent).
|
|
35454
|
+
* - **Wrapper**: the emulated implementation (`@camstack/addon-autotrack`),
|
|
35455
|
+
* which follows a subject with `ptz.move` pulses driven by the detection
|
|
35456
|
+
* pipeline. `defaultActive: false` — the operator binds it per camera in
|
|
35457
|
+
* the bindings UI, exactly as `virtual-doorbell` is bound.
|
|
35458
|
+
*
|
|
35459
|
+
* The binding chooses WHICH implementation answers; `setEnabled` stays the
|
|
35460
|
+
* one switch for the function either way. A camera never has both driving its
|
|
35461
|
+
* head, which is the whole reason this is not a second cap with a second
|
|
35462
|
+
* toggle (D62, D520).
|
|
35463
|
+
*/
|
|
35464
|
+
kind: "wrapper",
|
|
35465
|
+
defaultActive: false,
|
|
35447
35466
|
deviceTypes: [require_sleep.DeviceType.Camera],
|
|
35448
35467
|
deviceConfig: { ui: {
|
|
35449
35468
|
kind: "widget",
|
package/dist/index.mjs
CHANGED
|
@@ -35443,6 +35443,25 @@ var ptzAutotrackCapability = {
|
|
|
35443
35443
|
scope: "device",
|
|
35444
35444
|
deviceNative: true,
|
|
35445
35445
|
mode: "singleton",
|
|
35446
|
+
/**
|
|
35447
|
+
* Two kinds of provider behind one name, the same shape `snapshot` and
|
|
35448
|
+
* `doorbell` use:
|
|
35449
|
+
*
|
|
35450
|
+
* - **Native**: the camera's own firmware autotrack, registered per device by
|
|
35451
|
+
* the driver when the probe says it exists (Reolink: yes; Hikvision:
|
|
35452
|
+
* model-dependent).
|
|
35453
|
+
* - **Wrapper**: the emulated implementation (`@camstack/addon-autotrack`),
|
|
35454
|
+
* which follows a subject with `ptz.move` pulses driven by the detection
|
|
35455
|
+
* pipeline. `defaultActive: false` — the operator binds it per camera in
|
|
35456
|
+
* the bindings UI, exactly as `virtual-doorbell` is bound.
|
|
35457
|
+
*
|
|
35458
|
+
* The binding chooses WHICH implementation answers; `setEnabled` stays the
|
|
35459
|
+
* one switch for the function either way. A camera never has both driving its
|
|
35460
|
+
* head, which is the whole reason this is not a second cap with a second
|
|
35461
|
+
* toggle (D62, D520).
|
|
35462
|
+
*/
|
|
35463
|
+
kind: "wrapper",
|
|
35464
|
+
defaultActive: false,
|
|
35446
35465
|
deviceTypes: [DeviceType.Camera],
|
|
35447
35466
|
deviceConfig: { ui: {
|
|
35448
35467
|
kind: "widget",
|
package/dist/node.js
CHANGED
|
@@ -1116,7 +1116,7 @@ var FfmpegProcess = class {
|
|
|
1116
1116
|
this.handleFailure(this.producedOutput ? "crashed" : "no-output", code, signal, null, onLive, onDead);
|
|
1117
1117
|
});
|
|
1118
1118
|
this.opts.onChild(child);
|
|
1119
|
-
child.stdout?.once("
|
|
1119
|
+
child.stdout?.once("readable", () => {
|
|
1120
1120
|
this.producedOutput = true;
|
|
1121
1121
|
this.clearFirstDataTimer();
|
|
1122
1122
|
if (settled) return;
|
package/dist/node.mjs
CHANGED
|
@@ -1093,7 +1093,7 @@ var FfmpegProcess = class {
|
|
|
1093
1093
|
this.handleFailure(this.producedOutput ? "crashed" : "no-output", code, signal, null, onLive, onDead);
|
|
1094
1094
|
});
|
|
1095
1095
|
this.opts.onChild(child);
|
|
1096
|
-
child.stdout?.once("
|
|
1096
|
+
child.stdout?.once("readable", () => {
|
|
1097
1097
|
this.producedOutput = true;
|
|
1098
1098
|
this.clearFirstDataTimer();
|
|
1099
1099
|
if (settled) return;
|