You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by ph...@apache.org on 2018/04/25 17:03:48 UTC

nifi-minifi-cpp git commit: MINIFICPP-464 Clarify GetUSBCamera docs regarding scheduling behavior and image quality selection

Repository: nifi-minifi-cpp
Updated Branches:
  refs/heads/master 1514a3332 -> de0c93806


MINIFICPP-464 Clarify GetUSBCamera docs regarding scheduling behavior and image quality selection

This closes #309.

Signed-off-by: Marc Parisi <ph...@apache.org>


Project: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/commit/de0c9380
Tree: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/tree/de0c9380
Diff: http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/diff/de0c9380

Branch: refs/heads/master
Commit: de0c938065d0d3760ee68769c956af2afdb9cd29
Parents: 1514a33
Author: Andrew I. Christianson <an...@andyic.org>
Authored: Tue Apr 24 14:43:59 2018 -0400
Committer: Marc Parisi <ph...@apache.org>
Committed: Wed Apr 25 13:03:36 2018 -0400

----------------------------------------------------------------------
 PROCESSORS.md | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/nifi-minifi-cpp/blob/de0c9380/PROCESSORS.md
----------------------------------------------------------------------
diff --git a/PROCESSORS.md b/PROCESSORS.md
index fe55b1c..f88eb98 100644
--- a/PROCESSORS.md
+++ b/PROCESSORS.md
@@ -322,10 +322,23 @@ default values, and whether a property supports the NiFi Expression Language.
 
 ### Description
 
-Gets images from USB Video Class (UVC)-compatible devices. Outputs one frame
-per flow file at the rate specified by the `FPS` property in the format
+Gets images from USB Video Class (UVC)-compatible devices. Outputs one flow
+file per frame at the rate specified by the `FPS` property in the format
 specified by the `Format` property.
 
+Camera frames are captured in a separate background thread and are emitted as
+flow files upon capture. The onTrigger of this processor is a NOOP and will
+report an error if inputs are flowed into the processor. Because of this, the
+standard event/timer driven scheduling options have no effect.
+
+If the camera supports multiple image size/quality settings, the highest
+quality is chosen for the given FPS. For example:
+
+- If the FPS is 10 and the camera supports a maximum of 1920x1080 at this FPS,
+  output images will be 1920x780
+- If the FPS is 60 and the camera supports a maximum of 320x240 at this FPS,
+  output images will be 320x240
+
 ### Properties
 
 In the list below, the names of required properties appear in bold. Any other