Skip to content

Commit 0f1f3b0

Browse files
authored
Update camera.md
Changed raspistillyuv references to raspiyuv
1 parent 913bb1b commit 0f1f3b0

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

raspbian/applications/camera.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22

33
This document describes the use of the three Raspberry Pi camera applications, as of February 19th 2018.
44

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.
66

77
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.
88

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.
1010

1111
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.
1212

@@ -476,9 +476,9 @@ The camera is run for the requested time (`-t`), and a capture can be initiated
476476
kill -USR1 <process id of raspistill>
477477
```
478478
479-
### raspistillyuv
479+
### raspiyuv
480480
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.
482482
483483
Unsupported options:
484484
@@ -493,7 +493,7 @@ Extra options :
493493
```
494494
This option forces the image to be saved as RGB data with 8 bits per channel, rather than YUV420.
495495
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.
497497
498498
499499
### raspivid

0 commit comments

Comments
 (0)