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 in scenarios where you need 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 stream with customizable codec, bitrate, and channel options.
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. |
| Audio Codec | (Optional) The audio codec to use for encoding the extracted audio (e.g., "mp3", "aac"). |
| Audio Bitrate | (Optional) The target audio bitrate in kbps (default is 128). |
| Audio Channels | (Optional) Number of audio channels (e.g., 1 for mono, 2 for stereo; default is 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, but the main content is the binary audio file ready for further workflow steps 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 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 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".
- Insufficient Permissions: Missing or invalid API credentials will prevent the node from executing. Verify that the API key is correctly configured.
- Output Field Conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow data to avoid overwriting important data.