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 of a podcast episode before publishing.
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 target audio codec to use for transcoding (e.g., mp3, aac, wav). |
| Transcoding Options | Additional options for transcoding: • Audio Bitrate (number, e.g., 128) • Audio Channels (number, e.g., 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 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.
- The node depends on an external ffmpeg-based service or API to perform the transcoding operations.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
- Invalid Audio Input: If the input audio URL or binary field name is incorrect or inaccessible, the node may fail to fetch the source audio. Verify the input path or binary field exists and is accessible.
- Unsupported Codec: Specifying an unsupported or misspelled audio codec can cause errors. Ensure the codec name matches supported codecs by the underlying ffmpeg service.
- Bitrate or Channel Errors: Providing invalid values (e.g., negative numbers) for bitrate or channels might cause failures. Use sensible positive integers.
- API Authentication Failures: Missing or invalid API credentials will prevent the node from connecting to the transcoding service. Confirm that the API key credential is correctly configured in n8n.