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 audio bitrate to create smaller files suitable for mobile streaming.
- Changing the number of audio channels (e.g., from stereo to mono) to meet 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., "aac", "mp3"). |
| 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 according to the "Audio Output Name" property. The json output contains metadata about the operation but primarily the binary data field holds the resulting audio file encoded with the specified codec and options.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- The node depends on an external ffmpeg processing backend accessible via this credential.
- 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 is incorrect or inaccessible, the node will fail to process. Ensure the input points to a valid audio source.
- Unsupported Codec: Specifying an unsupported or misspelled audio codec may cause errors. Verify codec names against supported ffmpeg codecs.
- Bitrate or Channel Errors: Providing invalid values (e.g., negative numbers) for bitrate or channels can lead to failure. Use sensible positive integers.
- Credential Issues: Missing or invalid API authentication tokens will prevent the node from connecting to the ffmpeg service.
- Common error messages will relate to input validation, codec support, or authentication failures. Checking these inputs and credentials usually resolves issues.