This endpoint enables you to retrieve the results from multiple completed audio separation tasks in a single, efficient request. Instead of making individual requests for each audio separation result, you can fetch foreground and background audio components from several processing runs simultaneously, streamlining your workflow when dealing with batch audio operations.
Each audio separation task produces two distinct audio tracks from your original recording: a foreground track containing primary audio elements (speech, vocals, or main instruments) and a background track with supporting elements (ambient sounds, musical accompaniment, or secondary audio). This bulk endpoint allows you to collect these separated components from multiple runs at once, making it ideal for applications processing audio libraries, podcast batches, or large-scale content analysis projects.
The bulk retrieval system operates on a simple principle: you provide an array of run IDs corresponding to your completed audio separation tasks, and the system returns organized results for each requested separation. This approach offers significant advantages over individual retrieval requests:
Efficiency Benefits:
Reduces network overhead by consolidating multiple requests into one
Minimizes latency when retrieving results from several audio separation tasks
Simplifies client-side code for handling multiple audio file collections
Provides better performance for batch audio processing workflows
Practical Applications:
Processing results from multiple podcast episodes or music tracks
Building audio libraries with separated components
Batch operations for content creators working with multiple recordings
Automated workflows that separate audio from video content in bulk
The endpoint expects a JSON payload containing an array of run IDs that identify the audio separation tasks you want to retrieve results for:
Copy
{ "run_ids": [ "12345", "45678", "112233" ]}
Each run ID should correspond to a previously initiated audio separation task. The system processes all provided run IDs and returns results for those that have completed successfully.
The response contains an array of results, where each item corresponds to one of the requested run IDs. For successful separations, each result includes both foreground and background audio URLs:
When working with bulk audio separation results, individual tasks within your batch may have different statuses. The endpoint returns results for all requested run IDs, but some may not be ready yet or may have encountered processing errors.
Common Status Scenarios:
Mixed Status Results: Some separations completed while others are still processing
Invalid Run IDs: Non-existent run IDs will be marked with appropriate error status
Processing Failures: Some audio files may fail separation due to format issues or processing errors
Expired URLs: Older completed separations may have expired download URLs
Best Practices for Status Management:
Always check the status field before attempting to download audio files
Implement retry logic for tasks that are still processing
Handle failed separations gracefully with appropriate user feedback
Store successful results promptly as download URLs may expire
Log processing errors for debugging and quality improvement
Audio Format and Quality:
The separated audio files are typically delivered in high-quality formats suitable for professional audio editing. Both foreground and background components maintain the original audio quality while providing clean separation between different audio elements.
File Size and Storage:
Since each original audio file produces two separate output files (foreground and background), consider storage requirements when processing large batches. The combined size of separated files will be larger than the original due to the dual-track output.
Download URL Expiration:
The presigned URLs returned in the response are temporary and will expire after a certain period. Implement prompt download and storage strategies to ensure you donβt lose access to your separated audio files.
Processing Time Considerations:
Audio separation is a computationally intensive process. When submitting multiple files, processing times can vary based on audio length, complexity, and current system load. The bulk results endpoint helps you efficiently monitor multiple separations without overwhelming the system with frequent individual status checks.
Quality Optimization:
The effectiveness of audio separation depends on the characteristics of your original audio. Files with clear distinction between foreground and background elements (like speech over music) typically produce better separation results than complex multi-layered audio with overlapping frequency ranges.
By leveraging this bulk audio separation results endpoint, you can build sophisticated audio processing applications that handle multiple separations efficiently, enabling creative workflows that scale with your audio production needs while maintaining professional quality standards.
Assistant
Responses are generated using AI and may contain mistakes.
The x-api-key is a custom header required for authenticating requests to our API. Include this header in your request with the appropriate API key value to securely access our endpoints. You can find your API key(s) in the 'API' section of our studio website.
Body
application/json
Response
200
application/json
Successful Response
An object containing the results of one to five audio separation runs. Each key in the object is a unique identifier for a run, and the corresponding value is the files URLs generated by the audio separation process.