Verify evals on Papers with Code
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Start with the linked Papers with Code paper, Audio Generation task page, and AudioCaps result. Verify the score, model name, benchmark protocol, and openness metadata against the paper or official release artifacts; done means reporting any corrections needed.
Written by the indexing model from the issue text.
Description
Hi,
Niels here from the open-source team at Hugging Face. Congratulations on your work!
I've made the paper and 1 paper-native evaluation available on Papers with Code.
The paper is part of the Audio Generation task page.
The Stable Audio Open result currently ranks fourth on AudioCaps.
Would it be possible to verify these results and let me know if any score, model name, benchmark protocol, or openness metadata should be corrected? The imported rows are tied to the paper or its official release artifacts; comparison-table baselines were not added.
You can also edit the task, methods, project page, and GitHub URL directly from the paper page using your Hugging Face account.
Kind regards,
Niels
- Dominant language
- Python
- Stars
- 3.9k
- Forks
- 488
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Stability-AI/stable-audio-tools
-
Possible incorrect use of `and` with multiple context managersPossibly taken @rodriguescarson claimed this 115 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Stability-AI/stable-audio-tools#238 · 2 comments ·
-
run_gradio.py fails out of the box on Apple Silicon (MPS): float64 crash, slice TypeError, missing ui depsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Stability-AI/stable-audio-tools#228 · 4 comments · 1 reaction ·
All issues in Stability-AI/stable-audio-tools
Similar issues
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog checkPossibly taken @ocelotl claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5825 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cuga-project/cuga-agent#1020 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
microsoft/playwright#43640 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
stac-utils/stac-fastapi-elasticsearch-opensearch#965 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day