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 obtain the extracted audio as output, optionally customizing audio codec, bitrate, and channels.
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 the extracted audio in a binary field named as specified by the "Audio Output Name" property. The json output contains metadata about the processed file, while the binary data holds the actual audio file extracted from the input video. This allows downstream nodes to access the audio content directly for further processing or storage.
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 retrieve or process the video. Ensure the input is valid and accessible.
- Unsupported Audio Codec: Specifying an unsupported audio codec might cause errors. Use standard codecs supported by ffmpeg.
- Insufficient Permissions: Missing or invalid API credentials will prevent the node from executing. Verify that the API key is correctly configured.
- Output Field Conflicts: Using an output binary field name that conflicts with existing fields may overwrite data unintentionally. Choose unique output names.
Common error messages typically relate to input validation failures, codec incompatibilities, or authentication issues. Reviewing the node's execution logs and verifying input/output configurations usually resolves these problems.