# FAQ
Summary of common questions and answers for platform usage
# Common Service FAQs
# Example of calculating the sign value for third-party system integration
Example: The user's obtained appId is "c103af9ac77646ca9fb0122e75f30811", and appKey is "89f81a207e5e4a1297ed1255879191ee". Assuming the current time is 1686730537, then the formula for MD5 calculation should be MD5(c103af9ac77646ca9fb0122e75f30811168673053789f81a207e5e4a1297ed1255879191ee), and the calculated 32-bit lowercase value is "f6ffecf33d2073d9b3b93ba157665cfc".
The request json should be
{
"appId": "c103af9ac77646ca9fb0122e75f30811",
"timestamp": "1686730537",
"sign": "f6ffecf33d2073d9b3b93ba157665cfc",
"grantType": "sign"
}
The accessToken
in the return result is used as the token for access.
{
"//first_comment":"omission",
"accessToken": "ZGQ4OGQ0OGE0ZTgxMGE4ZjE1YWQ2ZjIzYWMwNTc5NWNkMGNjZmY0NC1iNTNlLTQyNmEtYmJjZS1lZGYyYWE2NmVmZjI",
"//second_comment":"omission"
}
CURL request example:
curl --location --request POST 'https://aigc.softsugar.com/api/uc/v1/access/api/token' \
--header 'Content-Type: application/json' \
--data '{
"appId": "c103af9ac77646ca9fb0122e75f30811",
"timestamp": "1686730537",
"sign": "f6ffecf33d2073d9b3b93ba157665cfc",
"grantType": "sign"
}'
# HTTP API Call Example
CURL Request Example:
In the data-raw
section, you specify the actual content of your business request.
curl --location --request POST 'https://aigc.softsugar.com/api/2dvh/v1/xxx/yyy/zzz' \
--header 'Authorization: Bearer YWI1NGE4ZDVhYmM2MTZjMDA0Y2UxZDAwMjdhODk4Mzk4NWUwYTdmOS02ZDM0LTQxNmQtYTAwMi1mMDg0MDAzNGNlZWY' \
--header 'Content-Type: application/json' \
--data-raw '{ }'
# WebSocket API Call Example
Example of WebSocket Service Connection URL:
ws://aigc.softsugar.com/api/voice/stream/v1?Authorization=Bearer M2U2OTkyZjIyMjhiYjM5OGJjY2UyZWFmNTc5MTM0MTI0MThlYTBhMS04OWVjLTRmZjEtYjg2Ni1mMTM4YThkNjRmMTI&
# Error Handling and Solutions
Error Message | Solution |
---|---|
"code": 3333, "message": "The request parameter is null or the format is incorrect, please check" | Ensure that the parameters are correctly passed and the Content-Type is set correctly. |
Null or "" | Check if the http status is 401 Unauthorized, which indicates that the request lacks valid authentication credentials for the target resource. |
# Common Issues with Video Synthesis
# Error Handling and Solutions
Error Message | Solution |
---|---|
"errorMsg":"digital role model must must be in zip format and contain assets and models resources" | This error indicates that the digital role model file URL used in the video synthesis request is incorrect. Please ensure that the digital role model file meets the requirements and has a matching face_feature_id . |
"errorMsg":"FfmpegTask: no pcm sound. taskId:b6c1b82ea3a54c1a9bf683c56a6d443d" | This error suggests that the digital role model used in the video synthesis request does not match the face_feature_id . Please ensure that the digital role model and face_feature_id have a unique corresponding relationship in the system. |
"errorMsg":"engine status error: failed, backend buffer size is too long" | This error indicates that the single TTS query content in the video synthesis request contains too many consecutive characters (more than 80) without punctuation. Please check the readability of the query text content. |
"errorMsg":[worker2d] FfmpegTask: process image info failed: output fps must be smaller than input fps. | This error indicates that the frame rate of the background video used in the video synthesis request does not meet the requirements. The background video should be in mp4 format with a frame rate of 25 or higher. |
# Common Issues with Live Streaming
# Error Handling and Solutions
Error Message | Solution |
---|---|
"errorMsg":"LiveStream: parse scenelist failed. Pass video json to live?" | This error indicates that the live script json file inputted is invalid and lacks necessary information. Confirm the script file format and ensure it is not using content intended for video synthesis for live stream creation. |
# Common Issues with Character Model Generation
# Error Handling and Solutions
Error Message | Solution |
---|---|
"errorMsg":"docker exec gen_sucai_gpu_12 148fc1a251c549c0b72472fe26cb7fba_s1 is failed Error: Frame Index :7489 find 0 faces!" | The key phrase here is "7489 find 0 faces", meaning no faces were detected in frame 7489 of the video. Please check if the video meets the requirements at this position. |
"errorMsg":"d8fcc266be74463286ff8bf06df13367_s1 input_source.mp4 [Errno 2] No such file or directory: '/data/task/d8fcc266be74463286ff8bf06df13367_s1//av_check_res/input_source.mp4/audio_summary.json', video_summary or audio_summary not exit" | This error indicates that the video file used has no audio information. Please ensure that the video meets the requirements. |
# Common Issues in TTS Voice Model Generation
# Task Errors and Solutions
Task Error Message | Solution |
---|---|
"errorMsg":"task is failed in stage: label" | The current version of TTS voice generation does not support manual labeling. Set the value of the humanLabel field to false. |