When submitting a generation job via /release_task without specifying a seed, ACE-Step picks a random seed internally. However the /query_result response does not include the seed that was actually used.
It would be very useful to have the seed returned in the result payload so downstream applications can:
Store it for reproducibility
Allow users to regenerate the same song
Support "retry with same seed" workflows
Expected addition to the query_result response item:
{ "url": "...", "seed": 1234567890 }
When submitting a generation job via /release_task without specifying a seed, ACE-Step picks a random seed internally. However the /query_result response does not include the seed that was actually used.
It would be very useful to have the seed returned in the result payload so downstream applications can:
Store it for reproducibility
Allow users to regenerate the same song
Support "retry with same seed" workflows
Expected addition to the query_result response item:
{ "url": "...", "seed": 1234567890 }