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 data field named according to the "Audio Output Name" property. The json output typically contains metadata about the operation or the processed item, but the main content is the binary audio data representing the transcoded file.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on an external ffmpeg-based API or service to perform the actual transcoding.
- No direct local ffmpeg installation is implied; all processing is done via the configured API.
Troubleshooting
- Invalid Audio Input: If the input audio URL is invalid or the specified binary field does not contain audio data, the node will fail. Ensure the input source is correct and accessible.
- Unsupported Codec: Specifying an unsupported audio codec may cause errors. Verify that the chosen codec is supported by the backend ffmpeg service.
- 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 that the API key is correctly configured in n8n credentials.
- Bitrate or Channel Settings Out of Range: Providing invalid numeric values for bitrate or channels might cause transcoding failures. Use reasonable defaults or consult documentation for valid ranges.