Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
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 save storage space.
Practical examples include:
- Converting an MP3 file to AAC format for better compatibility with certain devices.
- Reducing the audio bitrate to decrease file size for faster uploads or downloads.
- Changing the number of audio channels (e.g., stereo to mono) to meet 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 data field named according to the "Audio Output Name" property. The json output contains metadata about the operation but primarily the binary field holds the actual transcoded audio content ready for further processing or saving.
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 actual transcoding.
- Proper configuration of this API credential within n8n is necessary for the node to function.
Troubleshooting
- Invalid Audio Input: If the provided audio URL is invalid or the specified binary input field does not contain audio data, the node will fail. Ensure the input is correct and accessible.
- 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. Confirm that the API key is correctly configured.
- Resource Limits: Large audio files might exceed service limits or timeouts. Consider splitting large files or increasing timeout settings if available.