クレジット消費ルール

FAQ

• Q: What is the response speed of the service? A: The response speed depends on the file size and format, so an exact time cannot be provided. It is recommended to poll the task progress to get the latest status. If a task remains incomplete for an extended period, the system will automatically return a timeout error.
• Q: What is the concurrency limit (QPS) of the service? A: The default supported QPS is 2, with a parallel task limit of 2. To increase the QPS or parallel task limit, please contact the business team for expansion.
• Q: What are the file size and duration limits supported by each API function? A: Speech-to-text and AI Subtitle Generator: file size limit is no more than 4G, duration no more than 3 hours;
  Text-to-speech: input word limit is 30,000;
  Text-to-video: input word limit is 800.
• Q: How to handle task failures? A: Please first check the HTTP response status code and the state parameter description. If the issue persists, provide the error message, task_id, and complete request parameters to contact the business or technical team for assistance.
• Q: What to do if the URL download fails or shows a 403 Forbidden error? A: Ensure that the file can be downloaded properly and that there is sufficient download bandwidth. If the download is not completed within 1 hour, the system will report an error (status code: -3). A 403 error indicates no download permission; please check and ensure that the correct download permissions are provided.
• Q: What should I do if the sample code does not run properly? A: The sample code is for reference only; some parts need to be replaced based on actual conditions, such as techsz.aoscdn.com. Additionally, the example only shows simple parameters; for more supported parameters, please refer to the detailed parameter description table.
• Q: What to do if the URL download fails or shows an AccessDenied error? A: Some tools or editors may automatically convert & in the URL to \u0026, for example, Expires=1679986124\u0026OOSSAccessKeyId=. Please replace \u0026 back to & to resolve the issue. Be sure to check for URL encoding issues.