Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides various ffmpeg-related functionalities, including video processing tasks. Specifically, for the "Video Processing" resource with the "Combine Images" operation, it combines multiple images into a single video sequence where each image is displayed for a specified duration. This is useful for creating slideshows or video compilations from a list of images.
Practical examples:
- Creating a slideshow video from a set of image URLs.
- Generating a video preview by combining product images.
- Making a time-lapse style video from sequential photos.
Properties
| Name | Meaning |
|---|---|
| Images Url List | A valid list of URLs pointing to the images to be combined into the video. |
| Images Duration | The duration (in seconds) that each image will be displayed in the resulting video. |
Output
The node outputs a JSON object representing the result of the video processing operation. Typically, this includes metadata about the generated video file and possibly a binary field containing the actual video data. The binary output represents the combined video created from the input images.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on an external ffmpeg-based service or API to perform video processing.
- The node expects valid image URLs accessible by the ffmpeg service.
Troubleshooting
- Invalid Image URLs: If any URL in the images list is invalid or inaccessible, the operation may fail. Ensure all URLs are reachable and point to valid image files.
- Incorrect Duration Format: The duration should be a valid number (string representing seconds). Non-numeric or negative values may cause errors.
- API Authentication Errors: Missing or incorrect API credentials will prevent the node from executing successfully.
- Timeouts or Large Inputs: Combining many high-resolution images might lead to timeouts or memory issues depending on the backend service limits.