On this page |
The opposite operation (extract frame images from a video) is in the FFmpeg extract images node.
Installation
This node is a wrapper around the ffmpeg
command line tool. You must have FFmpeg installed on each machine for this node to work.
-
You can specify an explicit path to the executable using the node’s
-
If the FFmpeg path parameter is blank, the node looks for the environment variable
PDG_FFMPEG
, which if defined should contain a path to the executable. -
If the
PDG_FFMPEG
variable is not defined, the node will assume the executable is in the system path.
TOP Attributes
|
string |
Indicates the ffmpeg operation ( |
|
integer |
Whether the user specified a custom |
|
string |
The path to the |
|
integer |
The playback speed of the output video in frames per second. |
|
string |
The file path of the text file that contains the list of input frame images. |
|
string |
The file path of the output video file. |
|
integer |
When this is |
|
string |
A custom command line to run, when |
|
string |
The file tag to put on the result file path. |
|
string |
List of file paths to the frame images. |
Parameters
Node
Frames Per Second
The playback speed of the output video.
Frame List File
The file path to the frame list file. The frame list file is a text file that contains an ordered list of all of the input images to FFmpeg that are used to construct the video.
It is a requirement of FFmpeg that the paths of the images in this file are specified as relative paths. Therefore, when running on Windows, the frame list file must be placed on the same drive as the input images.
Output Filename
The file path to write the output video to.
Output File Tag
The file tag to put on the output file path. The default is file/video
.
FFmpeg Command
Turn this on to customize the command line passed to ffmpeg
.
FFmpeg Path
Turn this on to set an explicit path to the ffmpeg
executable.
If this is off, the node will look for a PDG_FFMPEG
environment variable.
If the variable is not set, the node will simply assume the executable is on the system path.
Processor
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
Dynamic
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
Static
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
Automatic
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
Examples
example_top_ffmpegencodevideo Example for FFmpeg Encode Video TOP node
This example demonstrates how to use FFmpeg Encode Video node to encode a sequence of images into a video file.
See also |