Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
This node provides video processing capabilities using ffmpeg, specifically including an operation to extract audio from a video file ("Video To Audio"). It is useful when you want to convert video content into audio format for purposes such as podcast creation, transcription, or audio analysis. For example, you can input a video URL or binary video data and output an audio file with customized codec, bitrate, and channel settings.
Properties
| Name | Meaning |
|---|---|
| Video Input | A valid video URL or the name of the input binary field containing the video to process. |
| Audio Output Name | The name of the output binary field where the extracted audio file will be stored. |
| Video Processing Options | Collection of optional parameters: • Audio Codec (string) • Audio Bitrate (number, default 128 kbps) • Audio Channels (number, default 1) |
Output
The node outputs the extracted audio as binary data in the specified output binary field. The json output contains metadata about the processed file, while the binary output holds the actual audio file extracted from the input video.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on ffmpeg functionality exposed via an external API or service configured in n8n.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Video Input: If the video input URL or binary field is incorrect or inaccessible, the node may fail to fetch or read the video data. Ensure the input is valid and accessible.
- Unsupported Audio Codec: Specifying an unsupported audio codec may cause errors during processing. Use common codecs supported by ffmpeg.
- Incorrect Binary Field Names: Make sure the input and output binary field names match those used in your workflow to avoid missing data.
- API Authentication Errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Resource Limits: Large video files might cause timeouts or memory issues depending on the execution environment.