Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Transcoding → Audio Transcode
AI-generatedOverview
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., "aac", "mp3", "flac"). |
| 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 but primarily the binary data field holds the actual transcoded audio content.
If the input was binary 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.
- The node depends on an external ffmpeg-based service or API to perform the transcoding operations.
- Proper configuration of this API credential within n8n is necessary for the node to function.
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 or misspelled audio codec may cause errors. Verify codec names are correct and supported by the backend.
- API Authentication Errors: Missing or incorrect API credentials will prevent the node from connecting to the transcoding service.
- Output Field Conflicts: Using an output binary field name that conflicts with existing fields may overwrite data unintentionally. Use unique names.
- Bitrate or Channel Values: Providing non-numeric or out-of-range values for bitrate or channels can cause failures. Use sensible numeric values.