audio.cpp with minimax-music-ui #289
|
Hey everyone, Sorry if this is a dumb question, very new to using audio.cpp! I'm trying to make audio.cpp with minimax work together with minimax-music-ui: When I used the model from the model downloader: And use the following config: {
"host": "127.0.0.1",
"port": 7862,
"backend": "cpu",
"device": 0,
"threads": 6,
"lazy_load": true,
"models": [
{
"id": "minimax-music3",
"family": "minimax_music3",
"path": "C:/LLMs/inference/models/MiniMax-Music3-GGUF",
"task": "gen",
"mode": "offline"
}
]
}I get this error when generating using minimax-music-ui: Using the build-in UI from audio.cpp does work however. Any ideas what I might be doing wrong? |
Replies: 2 comments
|
Hi! minimax-music-ui maintainer here. Before you dive into specifics, just want to let you know that you have done nothing wrong. It's a bug and I'm sure the next audio.cpp release will fix it. Now to the specifics. This error isn't coming from the UI. It's raised by audio.cpp's spec validator ( Why the built-in UI works but this UI doesn't: audio.cpp validates the model spec lazily on the model's first request through the OpenAI-compatible endpoint, and that path resolves through the compiled-in builtin spec table. The bundled web UI loads via the on-disk You can confirm the UI isn't a factor by reproducing with plain curl: then: Same error: it's entirely server-side. Two ways to fix it:
For the UI side there's nothing to change, it sends the standard { |
|
@MerijnHendriks @adambenhassen audio.cpp currently routes Music3 All (almost) models in audio/music generation, audio tools, speech analysis, and voice conversion route only through I’ll still relax the schema validation for the speech endpoint, but the correct endpoint for Music3 integrations is |
@MerijnHendriks @adambenhassen audio.cpp currently routes Music3
via /v1/tasks/run, not/v1/audio/speech. The native audio.cpp UI uses/v1/tasks/runfor Music3, which is why it works there.All (almost) models in audio/music generation, audio tools, speech analysis, and voice conversion route only through
/v1/tasks/runI’ll still relax the schema validation for the speech endpoint, but the correct endpoint for Music3 integrations is
/v1/tasks/run.