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 get back an audio file extracted from that video.
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 settings: • Audio Codec (string) • Audio Bitrate (number, default 128 kbps) • Audio Channels (number, default 1) |
Output
The node outputs a binary file containing the extracted audio from the input video. The binary data is stored under the field name specified by the "Audio Output Name" property. The json output typically contains metadata about the processed file or operation status, but the main output is the binary audio file ready for further use or download.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Relies on ffmpeg functionality exposed via an external API or service configured in n8n.
- No additional environment variables are explicitly required based on the static code.
Troubleshooting
- Invalid Video Input: If the video URL is invalid or the binary field does not contain proper video data, the node may fail to extract audio. Ensure the input is correct and accessible.
- Unsupported Audio Codec or Parameters: Specifying unsupported audio codec or invalid bitrate/channels values might cause errors. Use standard codecs and reasonable numeric values.
- API Authentication Errors: Missing or incorrect API credentials will prevent the node from functioning. Verify the API key configuration.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow to avoid overwriting data.