https://github.com/nordmoen/camera_recorder
ROS service to programatically start and stop camera recordings
https://github.com/nordmoen/camera_recorder
ffmpeg ros v4l2 webcam webcam-capture
Last synced: 5 months ago
JSON representation
ROS service to programatically start and stop camera recordings
- Host: GitHub
- URL: https://github.com/nordmoen/camera_recorder
- Owner: nordmoen
- Created: 2019-03-06T11:39:15.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-03-21T09:56:33.000Z (over 6 years ago)
- Last Synced: 2025-02-17T16:54:02.228Z (8 months ago)
- Topics: ffmpeg, ros, v4l2, webcam, webcam-capture
- Language: Python
- Size: 8.79 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# `camera_recorder`
This ROS package helps starting and stopping video recordings.
The intended use case is for users to configure the node either through
command-line arguments or through the `~configure` service and then start and
stop individual recordings. The individual recordings could be one or several
experiment runs that needs to be recorded.
## Install
This package has a few requirements outside of ROS which needs to be installed
before building, the dependencies are listed in
[`requirements.txt`](requirements.txt) file.
```bash
$ pip install -r requirements.txt
```
## Interface
The interface for this node is mainly through the services `~start` and `~stop`.
The `~start` services takes as input the [`Record` service](srv/Record.srv)
which specifies the output filename (can also be complex path, the node will
create folders as needed) and starts the recording. The recording will continue
until either the node is shutdown or the user calls `~stop` with the [`Trigger`
service](https://docs.ros.org/api/std_srvs/html/srv/Trigger.html). Users should
ensure that `success` is `true` after each service call to ensure that
everything went smoothly. Errors are reported in the `message` type of each
service.
If the output format is different from the input source, `ffmpeg` will transcode
on the fly. If this is not desired it is recommended to not apply any
transformations, like `hflip`, and utilize the same format as the input source.
### Configuration
The node can be configured either through parameters passed during startup, see
[`init.launch`](launch/init.launch), or through the [`~configure`
service](srv/Configure.srv) after the node is started. Configuration will take
effect the next time the `~start` service is called.
## Examples
```bash
# Start the node with 720 resolution and 30fps
$ roslaunch camera_recorder init.launch size:=1280x720 rate:=30
```
```bash
# Record from different input source in raw format
$ roslaunch camera_recorder init.launch source:=/dev/video1 format:=yuyv422
```
```bash
# Additional arguments supported by launch file
$ roslaunch camera_recorder init.launch --ros-args
```
## Checking supported streams
This package uses [`v4l2`](https://en.wikipedia.org/wiki/Video4Linux) to record
data through [`ffmpeg`](https://ffmpeg.org/). This places some restrictions on
the format of the input stream and video sizes. To query your equipment use the
following commands:
```bash
# List connected devices:
$ v4l2-ctl --list-devices
# List supported output formats, stream size and frames per second:
$ v4l2-ctl --list-formats-ext
# List supported formats for specific stream
$ ffmpeg -f v4l2 -list_formats all -i /dev/video0
```
## Direct copy
If it is desired to avoid any-and-all processing of the input stream user should
apply the `copy` option. This by-passes most processing by `ffmpeg`, but places
restriction on what can be done. The `copy` option is incompatible with the
`vflip` and `hflip` options and the output format is restricted to formats that
can be directly copied from the input.