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 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 audio codec to use for transcoding (e.g., mp3, aac, wav). |
| Transcoding Options | Collection of optional settings: • Audio Bitrate: Numeric value specifying bitrate in kbps (default 128). • Audio Channels: Number of audio channels (default 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 contains metadata about the operation result, but the main content is the binary audio data ready for further processing or saving.
Dependencies
- Requires an API key credential for accessing the underlying ffmpeg service.
- Depends on an external ffmpeg-based API or service that performs the actual transcoding.
- No additional environment variables are explicitly required by the node itself.
Troubleshooting
- Invalid Audio Input: If the input audio URL or binary field is incorrect or inaccessible, the node will fail. Ensure the input source is valid and reachable.
- Unsupported Codec: Specifying an unsupported audio codec may cause errors. Verify the codec is supported by the underlying ffmpeg service.
- Incorrect Output Field Name: Using an invalid or conflicting output binary field name can lead to data loss or overwrite issues.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from executing successfully. Confirm the API key is correctly configured.
- Bitrate or Channel Values Out of Range: Providing non-numeric or out-of-range values for bitrate or channels might cause transcoding failures.