You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: raspbian/applications/camera.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
3
3
This document describes the use of the three Raspberry Pi camera applications, as of February 19th 2018.
4
4
5
-
There are four applications provided: `raspistill`, `raspivid`, `raspiyuv` and `raspividyuv`. `raspistill` and `raspistillyuv` are very similar and are intended for capturing images; `raspivid` and `raspvidyuv` are for capturing video.
5
+
There are four applications provided: `raspistill`, `raspivid`, `raspiyuv` and `raspividyuv`. `raspistill` and `raspiyuv` are very similar and are intended for capturing images; `raspivid` and `raspvidyuv` are for capturing video.
6
6
7
7
All the applications are driven from the command line, and written to take advantage of the MMAL API which runs over OpenMAX. The MMAL API provides an easier to use system than that presented by OpenMAX. Note that MMAL is a Broadcom-specific API used only on Videocore 4 systems.
8
8
9
-
The applications use up to four OpenMAX (MMAL) components: camera, preview, encoder, and null_sink. All applications use the camera component; `raspistill` uses the Image Encode component; `raspivid` uses the Video Encode component; and `raspistillyuv` and `raspividyuv` don't use an encoder, and sends there YUV or RGB output directly from the camera component to file.
9
+
The applications use up to four OpenMAX (MMAL) components: camera, preview, encoder, and null_sink. All applications use the camera component; `raspistill` uses the Image Encode component; `raspivid` uses the Video Encode component; and `raspiyuv` and `raspividyuv` don't use an encoder, and sends their YUV or RGB output directly from the camera component to file.
10
10
11
11
The preview display is optional, but can be used full-screen or directed to a specific rectangular area on the display. If preview is disabled, the null_sink component is used to 'absorb' the preview frames. The camera must produce preview frames even if these aren't required for display, as they're used for calculating exposure and white balance settings.
12
12
@@ -476,9 +476,9 @@ The camera is run for the requested time (`-t`), and a capture can be initiated
476
476
kill -USR1 <processidofraspistill>
477
477
```
478
478
479
-
### raspistillyuv
479
+
### raspiyuv
480
480
481
-
Many of the options for `raspistillyuv` are the same as those for `raspistill`. This section shows the differences.
481
+
Many of the options for `raspiyuv` are the same as those for `raspistill`. This section shows the differences.
482
482
483
483
Unsupported options:
484
484
@@ -493,7 +493,7 @@ Extra options :
493
493
```
494
494
This option forces the image to be saved as RGB data with 8 bits per channel, rather than YUV420.
495
495
496
-
Note that the image buffers saved in `raspistillyuv` are padded to a horizontal size divisible by 32, so there may be unused bytes at the end of each line. Buffers are also padded vertically to be divisible by 16, and in the YUV mode, each plane of Y,U,V is padded in this way.
496
+
Note that the image buffers saved in `raspiyuv` are padded to a horizontal size divisible by 32, so there may be unused bytes at the end of each line. Buffers are also padded vertically to be divisible by 16, and in the YUV mode, each plane of Y,U,V is padded in this way.
0 commit comments