From d4057e9d8ee73962558b66b9fa2747a3aa02300e Mon Sep 17 00:00:00 2001 From: Marc Rousavy Date: Tue, 6 Jul 2021 15:03:40 +0200 Subject: [PATCH] Update FRAME_PROCESSORS.mdx --- docs/docs/guides/FRAME_PROCESSORS.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/guides/FRAME_PROCESSORS.mdx b/docs/docs/guides/FRAME_PROCESSORS.mdx index 9b7fa95..fcb963f 100644 --- a/docs/docs/guides/FRAME_PROCESSORS.mdx +++ b/docs/docs/guides/FRAME_PROCESSORS.mdx @@ -112,7 +112,7 @@ const frameProcessor = useFrameProcessor((frame) => { #### The `Frame` object -The Frame Processor gets called with a `Frame` object, which is a **JSI HostObject**. It holds a reference to the native (C++) Frame Image Buffer (~10 MB in size) and exposes properties such as `width`, `height`, `bytesPerRow` and more to JavaScript so you can synchronously access them. The `Frame` object can be passed around in JS, as well as returned from- and passed to a native **Frame Processor Plugin**. See [this](https://twitter.com/mrousavy/status/1412300883149393921) tweet for more information. +The Frame Processor gets called with a `Frame` object, which is a **JSI HostObject**. It holds a reference to the native (C++) Frame Image Buffer (~10 MB in size) and exposes properties such as `width`, `height`, `bytesPerRow` and more to JavaScript so you can synchronously access them. The `Frame` object can be passed around in JS, as well as returned from- and passed to a native **Frame Processor Plugin**. See [this tweet](https://twitter.com/mrousavy/status/1412300883149393921) for more information. ### Using Frame Processor Plugins