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 to match requirements of a target platform or device.
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 audio codec to use for transcoding (e.g., mp3, aac, wav). |
| Transcoding Options | Collection of optional settings: - Audio Bitrate: Numeric value specifying 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 according to the "Audio Output Name" property. The json output contains metadata about the operation and possibly information about the processed file, but the main content is the binary data representing the transcoded audio.
If the input was binary audio data, the output binary field will contain the transcoded audio file ready for further processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Relies on an external ffmpeg-based API or service configured within n8n credentials.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Audio Input: If the input audio URL is invalid or the specified binary field does not exist or contain valid audio data, the node will fail. Ensure the input is correctly specified and accessible.
- Unsupported Codec: Specifying an unsupported or misspelled audio codec may cause errors. Verify codec names against supported codecs by the underlying ffmpeg service.
- Bitrate or Channel Errors: Providing non-numeric or out-of-range values for bitrate or channels can lead to failures. Use sensible numeric values.
- API Authentication Failures: Missing or incorrect API credentials will prevent the node from functioning. Confirm that the API key credential is properly set up in n8n.
- Output Field Conflicts: Using an output binary field name that conflicts with existing fields might overwrite data unintentionally. Choose unique output field names.