The /audio/merge Robot
We offer a variety of features to reduce audio size while maintaining quality, as well as add effects like loops or watermarks.
The /audio/merge Robot overlays several audio files on top of each other.
||(required) String / Array of Strings / Object||
GeneralSpecifies which Step(s) to use as our input.
Special Step namesA special Step name is
Providing several Steps as inputYou can add arrays to
That's likely all you need to know about
› Advanced use cases
Step bundlingSome Robots can gather several Step results for a single invocation. For example, the /file/compress Robot would normally create one archive for each file passed to it. If you'd set
This is also a crucial parameter for the /video/adaptive Robot, otherwise you'll generate 1 playlist for each viewing quality.
Keep in mind that all input Steps must be present in your Template. If one of them is missing (for instance it is rejected by a filter), no result is generated because the Robot waits indefinitely for all input Steps to be finished. Here's a demo that showcases Step bundling.
Group by originalSticking with the /file/compress Robot example, you can set
FieldsYou can be more discriminatory by only using files that match a field name by setting the
Use AsSometimes Robots take several inputs. For instance, the /video/merge Robot can create a slideshow from audio and images. You can map different Steps to the appropriate inputs. Example:
Sometimes the ordering is important, for instance, with our concat Robots. In these cases, you can add an index that starts at 1. You can also optionally filter by the multipart field name. Like in this example, where all files are coming from the same source (end-user uploads), but with different
For times when it is not apparent where we should put the file, you can use Assembly Variables to be specific. For instance, you may want to pass a text file to the /image/resize Robot to burn the text in an image, but you are burning multiple texts, so where do we put the text file? We use specify it via
||Performs conversion using pre-configured settings.
If you specify your own FFmpeg parameters using the Robot's
||Integer||Auto||Bit rate of the resulting audio file, in bits per second. If not specified will default to the bit rate of the input audio file|
||Integer||Auto||Sample rate of the resulting audio file, in Hertz. If not specified will default to the sample rate of the input audio file|
||Duration of the output file compared to the duration of all merged audio files. Can be
||Specifies if any input files that do not match the target duration should be looped to match it. Useful for audio merging where your overlay file is typically much shorter than the main audio file.|
||Selects the FFmpeg stack version to use for encoding.
These versions do not reflect any real
FFmpeg versions, they reflect our own internal (non-semantic)
versioning for our custom FFmpeg builds.
The current recommendation is to use
||A parameter object to be passed to FFmpeg. If a preset is used, the options specified are merged on top of the ones from the preset. For available options, see the FFmpeg documentation. Options specified here take precedence over the preset options.|
Our /audio/merge Robot can be used in combination with other Robots, to create powerful workflows unique to your use case. Here are a few example scenarios that you can try live on our website:
Transloadit is a SaaS with a subscription model.
We offer a discount of 75%, effectively counting only every fourth byte of audio files that you merge with /audio/merge. It charges at minimum 0MB whenever it is used. Assuming the Startup Plan and an average audio file size of 3.8MB, you could merge 2874 audio files for $49/month.
Just like with your mobile plan, pricing goes down considerably when you commit to larger monthly volumes. You can adjust this every month. More info and available plans on our Pricing page.
Blog posts about the /audio/merge Robot
We wrote the following posts about the /audio/merge Robot on our blog: