HF Spaces API support

#30

Uses Gradio Client to fetch the required parameters of public HF Spaces and overrides their TTS defaults if necessary.

A way to fix #15

And to help with #21 and #23

Was able to test the cloned repo locally. But somehow am unable to test it on the cloned TTS-Arena as it goes into some infinite Building loop:
๐Ÿค—https://huggingface.co/spaces/Pendrokar/TTS-Spaces-Arena ๐Ÿคทโ€โ™‚๏ธ

Created the PR hoping that @Wauplin 's Gradio CI would automatically create a Ephemeral Space for the PR. But it seems that it is truly disabled. Or this PR gets skipped as I am not part of the Organization. ๐Ÿคทโ€โ™‚๏ธ

@Pendrokar unfortunately the Gradio CI is currently disabled for this Space as it degrades the UX on the main Space. I plan to investigate why and then re-enable it but for now there's unfortunately no CI here ๐Ÿ˜•

Was able to test the cloned repo locally. But somehow am unable to test it on the cloned TTS-Arena as it goes into some infinite Building loop: https://huggingface.co/spaces/Pendrokar/TTS-Spaces-Arena ๐Ÿคทโ€โ™‚๏ธ

I fixed the issue. The Space now works.

I'll admit that in my TTS-Arena Space I have xVASynth set as always one of the chosen models, just to see how it would fair against others. Hardly ever voted on that Space myself.

Though is the ELO algorithm OK? I recently added HierSpeech and amphion APIs to it. It seems HierSpeech bested xVASynth a few times and that was enough for it to get 1300+ ELO with only a few votes... ๐Ÿ˜ต

reach-vb changed pull request status to closed

I assume PR closure means that the TTS-Arena will not ever use HF Gradio Spaces. Everything will go through the TTS-AGI router?

Sign up or log in to comment