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 file 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 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 field named as specified by the "Audio Output Name" property. The json output contains metadata about the operation result, typically including information about the processed file. The binary data represents the actual transcoded audio file ready for further use or storage.
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 additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Audio Input: If the input URL is invalid or the binary field does not contain audio data, the node will fail. Ensure the input points to a valid audio source.
- Unsupported Codec: Specifying an unsupported audio codec may cause errors. Verify that the codec is supported by the underlying ffmpeg service.
- Incorrect Binary Field Names: Mismatches between input/output binary field names and actual data fields can lead to missing data errors.
- API Authentication Errors: Missing or incorrect API credentials will prevent the node from functioning. Confirm that the API key is correctly configured.
- Bitrate or Channel Values Out of Range: Providing invalid values for bitrate or channels might cause transcoding failures. Use sensible numeric values.