Spaces:
Running on Zero
Persistent error after migration to ZeroGPU: requested GPU duration (300s) is larger than maximum allowed
Good day.
After this space has been migrated to a ZeroGPU, I keep getting same error on any attempt to generate samples:
It is reproducing on any settings given, even if they are not extreme or edge cases. For example, it can be reproduced on "Custom" tab by clicking random example button and trying to generate from it. No other adjustments to input needed to get the error message, so model used is default one: "acestep-v15-turbo".
Before migration of this space to ZeroGPU the error was not present.
Please, take a look at possible causes of this issue - hopefully it is some kind of minor problem. If any additional information on the error is needed I'll provide it.
I have that issue too.
I cannot reproduce your issue
I get the same error
@ChuxiJ The reason you cannot reproduce the issue is because you are likely using a PRO/Enterprise Hugging Face account, which has higher ZeroGPU limits.
For all regular Free-Tier users, Hugging Face recently lowered the maximum ZeroGPU quota. Because your app.py has the decorator @spaces.GPU(duration=300), Hugging Face's security system is instantly killing the request before it even starts because 300 seconds exceeds the new free limit.
To fix this for the community, you just need to update app.py and lower the hardcoded duration to @spaces.GPU(duration=120). Once you do that, the Space will instantly start working for free users again!
Its been like this since the move to Zero. I can't use this space anymore despite the duration being set either below 300 or to -1. Same error every time.
I also can't get this to run locally on my GTX 1080 Ti (11GB). Whenever I try it complains about the Cuda version not being supported.
and when I downgrade to Cuda to a version compatible with the GTX 1080Ti and run the gradio ui ... it auto updates the cuda again automatcally and then doesn't run.
fixed?
just generated 2x2 random songs for testing.
seems a bit slow - but it is running. :)
Thanks ! :)
PS: And I've also found my save-file problem in the meantime:
The application sometimes tries to save two files simultaneously (mp3 and json) - my Windows system refused this - it was a random discovery and I'd never encountered it before.
Fixed, thank you!