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 supporting 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 the extracted audio in a specified format with custom 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: specify the audio codec (e.g., mp3, aac). - Audio Bitrate: set the audio bitrate in kbps (default 128). - Audio Channels: number of audio channels (default 1). |
Output
The node outputs the extracted audio as binary data under the specified output binary field name. 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 URL or binary field name is incorrect or inaccessible, the node will fail to retrieve or process the video. Ensure the input is valid and accessible.
- Unsupported audio codec: Specifying an unsupported audio codec may cause errors. Use common codecs like "mp3" or "aac".
- Incorrect output field name: The output binary field name must be unique and not conflict with existing fields.
- API authentication errors: Missing or invalid API credentials will prevent the node from executing. Verify that the API key is correctly configured.
- Bitrate or channel misconfiguration: Providing non-numeric or out-of-range values for bitrate or channels may cause processing failures.