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 the extracted audio in a specified format 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 kbps). |
| 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: Ensure the video URL is accessible or the binary input field name is correct and contains valid video data.
- Unsupported audio codec: If specifying an audio codec, verify it is supported by the ffmpeg service.
- Output binary field conflicts: Make sure the output binary field name does not conflict with existing fields in the workflow.
- API authentication errors: Confirm that the API key credential is correctly set up and has necessary permissions.
- Common error messages typically relate to invalid inputs or failed transcoding operations; checking logs and verifying input formats usually resolves these issues.