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 codec or format 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 streaming, or compressed to reduce file size.
Practical examples include:
- Converting an MP3 audio file to AAC format for better compatibility with certain devices.
- Reducing the bitrate of an audio file to save bandwidth when streaming.
- Changing the number of audio channels (e.g., from stereo to mono) for specific playback requirements.
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 data field named according to the "Audio Output Name" property. The json output field typically contains metadata about the operation or the processed item, while the actual audio content is provided as binary data suitable for further processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on the external ffmpeg processing backend accessible via the configured API.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
- Invalid Audio Input: If the input audio URL is invalid or the specified binary field does not contain audio data, the node may fail. Ensure the input is correctly specified and accessible.
- Unsupported Codec: Specifying an unsupported audio codec may cause errors. Verify that the chosen codec is supported by the ffmpeg backend.
- Incorrect Output Field Name: Using an output field name that conflicts with existing fields might overwrite data unintentionally. Use unique names.
- API Authentication Errors: Missing or incorrect API credentials will prevent the node from functioning. Confirm that the API key credential is properly configured.
- Bitrate or Channel Values Out of Range: Providing invalid values for bitrate or channels could lead to transcoding failure. Use reasonable numeric values.