@camstack/types 1.2.49 → 1.2.51

package/dist/interfaces/recording-config.d.ts

@@ -94,6 +94,31 @@ export declare const RecordingBandSchema: z.ZodObject<{
     postBufferSec: z.ZodOptional<z.ZodNumber>;
 }, z.core.$strip>;
 export type RecordingBand = z.infer<typeof RecordingBandSchema>;
+/**
+ * The buffers an `events` band uses when it carries NONE — i.e. what the Basic
+ * recording form persists whenever the operator leaves the pre/post inputs
+ * blank, which is the overwhelmingly common case.
+ *
+ * A zero default is NOT a neutral one, and reading the absent field as `0` is
+ * what made two cameras record nothing for weeks: `postBufferSec` is the LIVE
+ * demand window, so `0` means the window is already shut by the time the
+ * trigger is evaluated. There is no instant at which such a band can attach a
+ * writer.
+ *
+ * `postBufferSec` must therefore exceed one segment length plus the attach
+ * latency (ffmpeg spawn + RTSP dial), or the window closes before the first
+ * segment is ever finalized and the camera records nothing anyway. At the 10 s
+ * default segment length, 30 s leaves room for two full segments. `preBufferSec`
+ * is retroactive only — it costs nothing at record time, it merely keeps
+ * already-written segments — so it is set to one segment length.
+ *
+ * An EXPLICIT `0` is left alone: that is an operator statement, not an omission.
+ */
+export declare const DEFAULT_EVENTS_BAND_BUFFER_SEC: {
+    readonly preBufferSec: 10;
+    readonly postBufferSec: 30;
+};
+export type DefaultEventsBandBufferSec = typeof DEFAULT_EVENTS_BAND_BUFFER_SEC;
 /**
  * Per-device retention overrides. Every field is optional; an unset or `0`
  * value inherits the node-wide recorder default. Only footage-lifetime limits

package/package.json

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