@scrypted/types - npm Package Compare versions

Comparing version 0.0.31 to 0.0.32

index.d.ts

@@ -801,2 +801,5 @@ /// <reference types="node" />
 }
+export interface BufferConvertorOptions {
+    sourceId?: string;
+}
 /**
@@ -807,3 +810,3 @@ * Add a converter to be used by Scrypted to convert buffers from one mime type to another mime type.
 export interface BufferConverter {
-    convert(data: string | Buffer | any, fromMimeType: string, toMimeType: string): Promise<MediaObject | Buffer | any>;
+    convert(data: string | Buffer | any, fromMimeType: string, toMimeType: string, options?: BufferConvertorOptions): Promise<MediaObject | Buffer | any>;
     fromMimeType?: string;
@@ -1487,9 +1490,3 @@ toMimeType?: string;
     FFmpegInput = "x-scrypted/x-ffmpeg-input",
-    /**
-     * An RTCSignalingChannel/VideoCamera will return x-scrypted-rtc-signaling-<unique-prefix>/x-<unique-suffix>.
-     * RTC clients can inspect the mime and convert the contents to a buffer containing the string device id.
-     * If the client does not support WebRTC, it may try to convert it to an FFmpeg media object,
-     * which should also be trapped and handled by the endpoint using its internal signaling.
-     */
-    RTCAVSignalingPrefix = "x-scrypted-rtc-signaling-",
+    RTCSignalingChannel = "x-scrypted/x-scrypted-rtc-signaling-channel",
     SchemePrefix = "x-scrypted/x-scrypted-scheme-",
@@ -1496,0 +1493,0 @@ MediaObject = "x-scrypted/x-scrypted-media-object"

index.js

@@ -755,9 +755,3 @@ "use strict";
     ScryptedMimeTypes["FFmpegInput"] = "x-scrypted/x-ffmpeg-input";
-    /**
-     * An RTCSignalingChannel/VideoCamera will return x-scrypted-rtc-signaling-<unique-prefix>/x-<unique-suffix>.
-     * RTC clients can inspect the mime and convert the contents to a buffer containing the string device id.
-     * If the client does not support WebRTC, it may try to convert it to an FFmpeg media object,
-     * which should also be trapped and handled by the endpoint using its internal signaling.
-     */
-    ScryptedMimeTypes["RTCAVSignalingPrefix"] = "x-scrypted-rtc-signaling-";
+    ScryptedMimeTypes["RTCSignalingChannel"] = "x-scrypted/x-scrypted-rtc-signaling-channel";
     ScryptedMimeTypes["SchemePrefix"] = "x-scrypted/x-scrypted-scheme-";
@@ -764,0 +758,0 @@ ScryptedMimeTypes["MediaObject"] = "x-scrypted/x-scrypted-media-object";

index.ts

@@ -1408,2 +1408,7 @@
 }
+
+export interface BufferConvertorOptions {
+  sourceId?: string;
+}
+
 /**
@@ -1414,3 +1419,3 @@ * Add a converter to be used by Scrypted to convert buffers from one mime type to another mime type.
 export interface BufferConverter {
-  convert(data: string | Buffer | any, fromMimeType: string, toMimeType: string): Promise<MediaObject | Buffer | any>;
+  convert(data: string | Buffer | any, fromMimeType: string, toMimeType: string, options?: BufferConvertorOptions): Promise<MediaObject | Buffer | any>;
 
@@ -2162,9 +2167,3 @@ fromMimeType?: string;
   FFmpegInput = 'x-scrypted/x-ffmpeg-input',
-  /**
-   * An RTCSignalingChannel/VideoCamera will return x-scrypted-rtc-signaling-<unique-prefix>/x-<unique-suffix>.
-   * RTC clients can inspect the mime and convert the contents to a buffer containing the string device id.
-   * If the client does not support WebRTC, it may try to convert it to an FFmpeg media object,
-   * which should also be trapped and handled by the endpoint using its internal signaling.
-   */
-  RTCAVSignalingPrefix = 'x-scrypted-rtc-signaling-',
+  RTCSignalingChannel = 'x-scrypted/x-scrypted-rtc-signaling-channel',
   SchemePrefix = 'x-scrypted/x-scrypted-scheme-',
@@ -2171,0 +2170,0 @@ MediaObject = 'x-scrypted/x-scrypted-media-object',

package.json

 {
   "name": "@scrypted/types",
-  "version": "0.0.31",
+  "version": "0.0.32",
   "description": "",
@@ -5,0 +5,0 @@ "main": "index.js",

No alert changes

Worsened metrics

Total package byte prevSize

175045

decreased by-0.52%

Lines of code

5577

decreased by-0.16%

No dependency changes