![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 1.2.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | iron |
Last Updated | 2024-04-15 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here
Processing rosbags
Extract an mp4 file from a rosbag
The bag_to_file
merges the ffmpeg-generated packets from a rosbag into a file:
bag_to_file -b input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time] [-e end_time]
The rate
determines the fps used by ffmpeg when producing the
output. The video is not transcoded, so what you get is the original
stream, just in a mp4 container. To get correct playing speed the rate must
match the rate at which the stream was originally recorded.
The start_time
and end_time
is given in seconds since the
epoch, like the times you see when using ros2 bag info
.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -b ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number conincides with the frame number.
Extract frames from a rosbag
The bag_to_frames
decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -b input_bag -t topic [-o out_dir] [-d decoder][-T timestamp_file] [-s start_time] [-e end_time]
The frames are written to out_dir
with the ros header stamps embedded in the file name. A suitable decoder is usually guessed from the encoding used in the packet, but you can specify a valid ffmpeg decoder by using the -d decoder
option. For start and stop times and the timestamp file see bag_to_file
.
License
This software is issued under the Apache License Version 2.0.
Changelog for package ffmpeg_image_transport_tools
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged ffmpeg_image_transport_tools at Robotics Stack Exchange
![]() |
ffmpeg_image_transport_tools package from ffmpeg_image_transport_tools repoffmpeg_image_transport_tools |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 3.0.0 |
License | Apache-2 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-misc-utilities/ffmpeg_image_transport_tools.git |
VCS Type | git |
VCS Version | release |
Last Updated | 2025-08-08 |
Dev Status | DEVELOPED |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Bernd Pfrommer
Authors
Tools for the ffmpeg_image_transport
This repository hosts code for handling data streams produced by the ffmpeg_image_transport.
Supported systems
Continuous integration is tested under Ubuntu with the following ROS2 distros:
How to install
From packages
sudo apt-get install ros-${ROS_DISTRO}-ffmpeg-image-transport-tools
From source
Set the following shell variables:
repo=ffmpeg_image_transport_tools
url=https://github.com/ros-misc-utilities/${repo}.git
and follow the instructions here.
About encoders, decoders, and pixel formats
The tools in this package often have many parameters related to encoders, decoders, and pixel formats.
It is important to understand the terminology, and how single-channel images (like mono8
and Bayer images) are handled.
Please consult the ffmpeg_encoder_decoder repo for more information.
Programs for processing rosbags
bag_to_file
The bag_to_file
tool concatenates the FFMPEGPacket message content from a rosbag into a file, and runs the ffmpeg
tool to embed the stream into a an mp4
container.
bag_to_file -i input_bag -t topic -r rate [-o out_file] [-T timestamp_file] [-s start_time (sec since epoch)] [-e end_time (sec since epoch)]
The rate
determines the fps used by ffmpeg when producing the output.
The video is not transcoded, so what you get is the original stream, just in an mp4 container.
To get correct playing speed the rate must match the rate at which the stream was originally recorded.
For example the following line produces a file video.mp4
and timestamps.txt
from a rosbag:
ros2 run ffmpeg_image_transport_tools bag_to_file -t /cam1/image_raw/ffmpeg -r 40 -i ./my_rosbag/ -e 1710085164.466
The timestamp.txt
file facilitates correlating ROS time stamps with frame numbers. It has the following entries:
# packet no, pts, header_stamp recording_stamp
0 0 1710085154473057750 1710085156001866724
1 1 1710085155950467594 1710085156024209913
A H264 packet typically corresponds to a frame so the packet number should conincide with the frame number.
bag_to_frames
The bag_to_frames
program decodes the ffmpeg-generated packets from a rosbag into frames:
bag_to_frames -i input_bag -t topic [options]
options:
-o out_dir name of the output directory (defaults to "frames")
-d decoder name of the libav decoder (hevc_cuvid, libx264 etc)
-O output_format ros encoding ('bgr8', 'mono', ...) to convert to before writing image.
-f file_type frame file type ('png', 'jpeg'). Defaults to jpeg.
-T timestamp_file name of time stamp file.
-s start_time time in sec since epoch.
-e end_time time in sec since epoch.
If not specified, the decoder will be automatically (not necessarily correctly) picked. Not all decoders for a codec can handle all encoded image formats.
For example if the codec is hevc
and a bayer image (bayer_rggb8
) has been encoded with image format nv12
, then the h265
will throw the following error:
[INFO] [1753428586.070137592] [bag_to_frames]: using decoder: hevc
[WARN] [1753428586.406598438] [Decoder]: hardware frame transfer failed for pixel format yuv420p
Before the image is written a final conversion to the output_format
is performed. The default is bgr8
.
The format string must follow ROS convention rather than the libav convention, i.e. bgr8
rather than bgr24
.
compress_bag
Use ros2 run ffmpeg_image_transport_tools compress_bag
to encode a video stored as Image messages into FFMPEGPacket format.
Usage is as follows:
```
compress_bag -i in_bag -o out_bag -t topic [-t topic … ] [options]
options:
-q enable quality check
-I write debug images
-m max_num_frames_to_keep (for matching encoded/decoded packets. defaults to 100)
-s start_time [in sec since epoch]
-e end_time [in sec since epoch]
——- encoder options ——-
-E
File truncated at 100 lines see the full file
Changelog for package ffmpeg_image_transport_tools
3.0.0 (2025-08-08)
- use head_ref for workflow
- added ffmpeg_encoder_decoder to repos file
- added gitignore for tests and updated README
- added uncompress_bag and tests
- adapt to decoder api changes
- switch to black python formatting
- more documentation, better logging
- be able to compare different size images
- keep recording time stamps for flushing
- dont create emtpy history file
- added quality test/decoding
- added compress_bag and fixed some bugs
- Contributors: Bernd Pfrommer
2.1.2 (2025-05-26)
- avoid ament_target_dependencies
- Contributors: Bernd Pfrommer
2.1.1 (2025-03-17)
- use encoder/decoder instead of transport
- fixed README status badges
- Contributors: Bernd Pfrommer
2.1.0 (2025-03-15)
- fixed README status badges
- Contributors: Bernd Pfrommer
2.0.0 (2025-03-15)
- fix build issues on rolling
- Contributors: Bernd Pfrommer
1.2.0 (2024-04-15)
- initial release of ROS2 package
- Contributors: Bernd Pfrommer