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 URL pointing to the audio source or the name of the input binary field containing the audio data. |
| Audio Output Name | The name of the output binary field where the transcoded audio file will be stored. |
| Audio Codec | The codec to use for transcoding the audio (e.g., mp3, aac, wav). |
| Transcoding Options | Collection of additional options: • Audio Bitrate: Numeric value specifying the 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 result, while the binary data holds the actual transcoded audio file ready for further processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Relies on ffmpeg functionality exposed via an external API or service configured within n8n.
- No other external dependencies are indicated in the static code.
Troubleshooting
- Invalid Audio Input: If the input URL or binary field name is incorrect or inaccessible, the node may fail to fetch the audio data. Verify the input source is correct and accessible.
- Unsupported Codec: Specifying an unsupported or misspelled audio codec can cause errors. Ensure the codec name matches supported ffmpeg codecs.
- Bitrate or Channel Errors: Providing invalid values (e.g., negative numbers) for bitrate or channels may lead to failure. Use sensible positive integers.
- API Authentication Issues: Missing or invalid API credentials will prevent the node from functioning. Confirm that the required API key is correctly configured in n8n.
- Common error messages will likely relate to input validation, codec support, or authentication failures. Checking logs and verifying configuration usually resolves these issues.