ffmpeg Node icon

ffmpeg Node

n8n Node for some Ffmpeg functionality

Actions11

Overview

This node provides audio transcoding functionality using ffmpeg. It allows users to convert audio files from one codec or format to another, adjusting parameters such as codec type, bitrate, and number of audio channels. This is useful in scenarios where audio files need to be standardized for compatibility, optimized for streaming, or compressed to reduce file size.

Practical examples include:

  • Converting an MP3 audio file to AAC format for better compatibility with certain devices.
  • Reducing the bitrate of an audio file to save bandwidth when streaming.
  • Changing the number of audio channels (e.g., from stereo to mono) for specific playback requirements.

Properties

Name Meaning
Audio Input A valid audio URL or the name of the input binary field containing the audio to transcode.
Audio Output Name The name of the output binary field where the transcoded audio file will be stored.
Audio Codec The target audio codec to use for transcoding (e.g., mp3, aac, wav).
Transcoding Options Collection of optional settings:
- Audio Bitrate: Target bitrate in kbps (default 128).
- Audio Channels: Number of audio channels (default 1).

Output

The node outputs the transcoded audio file in a binary field named as specified by the "Audio Output Name" property. The json output contains metadata about the operation but primarily the binary data field holds the actual transcoded audio content.

If the input was binary audio data, the output binary field will contain the transcoded audio file in the requested codec and settings.

Dependencies

  • Requires an API key credential for accessing the underlying ffmpeg service.
  • The node depends on an external ffmpeg-based service or API to perform the transcoding operations.
  • Proper configuration of this API credential within n8n is necessary for the node to function.

Troubleshooting

  • Invalid Audio Input: If the input audio URL is invalid or the binary field does not contain audio data, the node will fail. Ensure the input points to a valid audio source.
  • Unsupported Codec: Specifying an unsupported audio codec may cause errors. Verify that the codec is supported by the underlying ffmpeg service.
  • API Authentication Errors: Missing or incorrect API credentials will prevent the node from connecting to the transcoding service.
  • 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.

Links and References

Discussion