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 format or codec 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 size or quality, or prepared for specific playback environments.
Practical examples include:
- Converting an MP3 file to AAC with a specific bitrate for mobile streaming.
- Downmixing stereo audio to mono to reduce file size.
- Changing the audio codec of a podcast episode before publishing.
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 | Additional options for transcoding: • Audio Bitrate (number, e.g., 128) • Audio Channels (number, e.g., 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 resulting audio file encoded with the specified codec and options.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg processing backend accessible via this credential.
- No other explicit environment variables or configurations are indicated in the source.
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 is correctly specified and accessible.
- Unsupported Codec: Specifying an unsupported audio codec may cause errors. Verify that the codec is supported by the ffmpeg backend.
- Incorrect Output Field Name: If the output binary field name conflicts with existing fields or is empty, the output may be lost or overwritten.
- API Authentication Errors: Missing or incorrect API credentials will prevent the node from functioning. Confirm the API key is configured properly in n8n credentials.
- Bitrate or Channel Values: Providing non-numeric or out-of-range values for bitrate or channels can cause transcoding failures.